BSOD happens randomly ' 0x00000101 '


  1. Ripa98070
    Posts : 3
    Windows 7 Enterprise 64 bit
       New #1

    BSOD happens randomly ' 0x00000101 '


    I have bought a new computer last August - so it is 6 months old.
    Since I have got it, I randomly get the BSOD Stop 0x00000101 "A clock interrupt was not received on a secondary processor within the allocated time interval".

    I have updated all of my drivers, and now the computer is just randomly freezing.

    I have attached my pc spec and the Windows_NT6_BSOD_jcgriff2, i tried to get the 'perfmon /report ' and it gave an error

    'An error occured while attempting to generate the report.


    The system cannot find the path specified. '

    PC Spec -

    Windows 7 64 bit
    i5 2500k CPU @ 3.30 GHz
    BIOS - American megatrends 0501, 9/5/11
    SMBIOS version: 2.6
    Motherboard: ASUSTEK Comp Inc, model P8Z68-V
    Chipset:
    Northbridge Intel Sandy Bridge rev. 09
    Southbridge Intel Z68 rev. B3
    Graphic Interface PCI-Express
    PCI-E Link Width x16
    PCI-E Max Link Width x16
    Memory Type DDR3
    Memory Size 4096 MBytes
    Channels Dual

    Graphics: NVIDA GeForce GTX 560


    Please help.
      My Computer
    Quote Quote

  3. Anak
    Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       New #2

    Hi Ripa98070, welcome to 7F! :)

    This is your Bugcheck report:
    Code:
    0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003565180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`009a9628 fffff800`032d88c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03565180 : nt!KeBugCheckEx
fffff880`009a9630 fffff800`0328b497 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffff800`032838a4 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`009a96c0 fffff800`037f7895 : fffff800`0381d460 fffff880`009a9870 fffff800`0381d460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`009a97c0 fffff800`0327d173 : 00000000`1ccc54c7 fffff800`033f6e80 fffff880`035d7180 fffffa80`09514660 : hal!HalpHpetClockInterrupt+0x8d
fffff880`009a97f0 fffff800`032b7327 : fffff800`033f6e80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`009a9980 fffff800`032867cc : 00000000`00000000 fffff880`009a9ab8 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x93
fffff880`009a99c0 fffff800`03248469 : 00000000`0000000a 00000000`0000007f fffffa80`0204d7d0 00000000`00000080 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`009a9a90 fffff800`03248cb7 : 00000000`000ac400 00000000`0000007f 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
fffff880`009a9ad0 fffff800`0351bfee : fffffa80`036b8040 00000000`00000080 fffffa80`03656890 fffff800`032725d9 : nt!MmZeroPageThread+0x83a
fffff880`009a9c00 fffff800`032725e6 : fffff800`033f6e80 fffffa80`036b8040 fffff800`03404cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
    This will explain what is wrong:
    BSOD Index

    With a link to this thread: https://www.sevenforums.com/crashes-d...tml#post356791
    What you're looking for will be in one of the following categories:
    a) BIOS bug (you have the latest BIOS version installed)
    b) a driver whose activity is causing the target processor to lock up
    c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)

    Source from: BSOD Index
    All courtesy of usasma.


    It would help if you could enter your System Specs in the area provided
    Here's how to do it: System Info - See Your System Specs
      My Computer
    Quote Quote

  4. Ripa98070
    Posts : 3
    Windows 7 Enterprise 64 bit
    Thread Starter
       New #3

    Thanks.

    So, you're saying that it isn't my BIOS - as I have the latest version installed.

    Hardware:
    - I don't think it is temperature, as the CPU is always between 40-50 degrees C, and the crashes happen even after I have just turned the computer on.
    - I would like to exclude hardware, as the crashes started soon after I bought the desktop and are now simply increasing in frequency.

    I have just updated all of my drivers.

    What can I do? or is there a tool you can recommend that I use to check if any of my drivers are causing the issue?
      My Computer
    Quote Quote

  6. Anak
    Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       New #4

    a.) Could mean the latest BIOS is the one that has the bug.

    b.) You could run Prime95 - 64bit
    Code:
    CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. 

This indicates that the specified processor is hung and not processing interrupts.
    This means your Central Processing Unit (CPU) may be bad.

    c.) Driver Verifier - Enable and Disable
      My Computer
    Quote Quote

  7. Ripa98070
    Posts : 3
    Windows 7 Enterprise 64 bit
    Thread Starter
       New #5

    I have been running prime 95 - 64 bit for about 2 hours now, I will let it keep running until it finds a fault.

    And I will check the driver verifer if no faults have been found by prime 95- at the end of its cycle.

    If I have any problems I will let you know.

    Thanks for the help.
      My Computer
    Quote Quote

  8. Anak
    Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       New #6

    Your welcome!
    You should run Prime for at least 10 to 12 hours on blend, and then do an IntelBurn test for at least 50 passes: IntelBurnTest - 2.4 Download - EXTREME Overclocking

    There is also this CPU test at the bottom of this page: Stability / Burn-in - Tests - EXTREME Overclocking
      My Computer
    Quote Quote

 

  Related Discussions
Hello everyone, since yesterday my pc started having the BSOD randomly. When i turn on my pc after 20-30 minutes my PC either freezes or i get the blue screen with the above code. I will upload the needed files here and i would very much appreciate your help ! Thank you
Random BSOD 0x00000101
in BSOD Help and Support

Hello, I have an issue. Apperantly my PC rarely and randomly BSODs. Like either watching a video or playing a game. Here is my PC. Processor - Intel i5 3570K @ 3.40GHz Memory - PC3-12800 Crucial 8GB DDR3 Hard Drive 1 - Samsung HD320KJ (320GB) Hard Drive 2 - WD Blue 640GB Video Card -...
I recently upgraded my CPU from a FX4100 to an FX6300. The first FX6300 was faulty so I returned it and I got a replacement from AMD. The CPU idle temp is 35 degrees. On prime95, It passed the torture test and the CPU temp was 65 degrees and it didn't BS. All of my drivers are up to date and I cant...
BSOD Error 0x00000101
in BSOD Help and Support

Recently I built my own pc and randomly while using it I am getting the BSOD error, mainly when trying to play games. I get the error; STOP 0X00000101 (0X0000000000000031, 0X0000000000000000, 0XFFFFF88002F64180, 0X0000000000000002). This has been annoying me to no end and I cannot seem to find the...
BSOD 0x00000101 and 0x0000009c
in BSOD Help and Support

I made a post a while ago that never got resolved because I couldn't retrieve the error reports from my PC. It's been a couple weeks but was finally able to get them off my PC. Could someone take a look at my thread and let me know if they can see what's causing my PC to BSOD? Perfmon/error reports...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 21:42.
Find Us