locked
BSOD 0x0000101 caused by ntoskrnl.exe windows 7 x64 RRS feed

  • Question

  • Hello, the trouble started after ra new installation of Windows 7 x64. The mouse start to lag then the screen freezes, and sometimes, i've got a BSOD :

         Infos from Whocrashed :

    crash dump file: C:\Windows\Minidump\090913-27502-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
    Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C: \Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System

    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
    Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C: \Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL

    (I don't have the .dmp file for this one)

    I'm sorry i cant post a pic of Bluescreenview or a link of the .dmp file. :/

    Thanks to help me!!

    Wednesday, September 25, 2013 1:18 PM

Answers

  • Fr_Realmax

    The analysis of this one DMP is inconclusive.  It is a clock watchdog but the driver/process that caused it isnt named.  I can make a good guess as you have one driver from 2005 that is a huge cause of crashes.

    The pre 2009 version of this driver is a known BSOD cause.

    Please visit Asus tek computer inc. -support- drivers and download p7p55d le
    http://support.asus.com/download.aspx?slanguage=en&m=p7p55d%20le&p=1&s=32&os=29&hashedid=e7zic83pvqsr80lm

    Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).
    Download and install it.

    Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).  If you are using Win 8 there is at least a 2012 version which is needed for that.  If you cant find it on the ASUS site you can download it using windows update.  Read about it  here


    STOP 0x101: CLOCK_WATCHDOG_TIMEOUT Troubleshooting

    Here's a good thread on http://www.sysnative.com/forums/showthread.php/1248-0x101-quote-A-clock-interrupt-was-not-received-on-a-secondary-processor-quote


    What you're looking for will be in one of the following categories:

    a) BIOS bug
    b) a driver whose activity is causing the target processor to lock up
    c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...) ?I wonder about CPU defect also)

    So, check the drivers http://www.carrona.org/dvrref.php
    Then check the inside of the case (temperature, voltage, dust, etc).
    Then run hardware stress tests

    Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/

        FurMark Setup:
        - If you have more than one GPU, select Multi-GPU during setup
        - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
        Click "Go" to start the test
        - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
        - Click "Quit" to exit

    Try this free stress test: Free Software - http://download.cnet.com/Prime95-32-bit/3000-2053_4-192895.html
     

        Prime95 Setup:
        - extract the contents of the zip file to a location of your choice
        - double click on the executable file
        - select "Just stress testing"
        - select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
        - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).

        The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
        Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
        The Test selection box and the stress.txt file describes what components that the program stresses.

    More Video Stress Tests:
        1. Thanks to Vir Gnarus (http://www.sysnative.com/forums/members/vir-gnarus.html) for finding this video memory test: https://simtk.org/home/memtest
            Alternate download link (w/o registration) located here: http://folding.stanford.edu/English/DownloadUtils
        2. Two other video stress tests (may be more stressful than FurMark):
            NOTE: I have had reports that some ISP's will block this website
            Video Memory stress Test - http://nvworld.ru/utilities/vmt/
            Artifact Locator - http://nvworld.ru/utilities/alocator/
            Sorry, but I don't read the language that this website is made in.
        3. Another interesting test that came to my attention: http://www.ocbase.com/perestroika_en/index.php?Download
     USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!
        Quote:
        CPU Stress Tests:
        Only need to run 1 or 2 of the tests under most circumstances. I haven't used any of the tests myself, so I listed all that I was able to find.
        - http://downloadcenter.intel.com/Deta...19182&lang=eng
        - http://7byte.com/index.php?page=hotcpu
        - http://www.7byte.com/index.php?page=burnin64
        - http://www.overclock.net/general-pro...ress-test.html
        - http://www.fossiltoys.com/cpuload.html
        - http://www.pcworld.com/downloads/fil...scription.html
        - http://www.overclock.net/general-pro...ress-test.html
        - http://majorgeeks.com/CPU_Stability_Test_d215.html
        - http://www.xtremesystems.org/forums/...d.php?t=201670
        - the test(s) suggested at this link are bootable: http://www.techsupportforum.com/foru...ml#post2232929

    Then try replacing parts.
    Then look up the versions of your BIOS to see what changes were done.


    Recently it was found (here: BSOD Stop 0x00000101 and Stop 0x0000009c ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem. I'd have to recommend at least running SFC.EXE /SCANNOW on any PC that has this problem (simply because it's too easy easy to do and it may fix things). 

    Use !analyze -v to get detailed debugging information.
    BugCheck 101, {31, 0, fffff88002f64180, 2}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    Followup: MachineOwner
    ---------
    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: fffff88002f64180, 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:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  d
    
    If you continue to crash you might want to consider removing Avast (at least to test) and replacing it with MSE>

              


    Wanikiya & Dyami--Team Zigzag

    • Proposed as answer by 暁北 Sunday, October 13, 2013 4:07 PM
    • Marked as answer by ZigZag3143x Sunday, October 13, 2013 4:39 PM
    Thursday, September 26, 2013 3:48 PM

All replies

  • A bugcheck (BSOD) is a mechanism to protect your PC from damage.

    You get this one:

    Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT
    http://msdn.microsoft.com/en-us/library/ff557211%28v=vs.85%29.aspx

    Cause

    The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here. If your account is not verified post a link without HTTP.

    If you can't see dmp files, make sure your Windows is configured correctly [2][3] to generate dumps.

    If you want to analyze them your own, check those videos [4][5] and read this KB article [6].

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    [2] http://support.microsoft.com/kb/254649
    [3] http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
    [4] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-15-WinDbg-Bugchecks
    [5] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-16-WinDbg-Driver-Verifier, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-17-WinDbg-Driver-Verifier-Part-2, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-18-WinDbg-Driver-Verifier-Part-3
    [6] http://support.microsoft.com/kb/315263

    "A programmer is just a tool which converts caffeine into code"

    Wednesday, September 25, 2013 7:52 PM
  • Hi,

    As Andre said, we need at least two dmp files to spot trends and confirm the diagnosis.

    How to enable minidumps:

    1. Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    2. Under the Advanced tab, click on the Startup and Recovery Settings... button.
    3. Ensure that Automatically restart is unchecked.
    4. Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    5. Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    6. Reboot if changes have been made.

    Also please run MSinfo32 and save the system information.

    Link for how to upload below:

    http://www.wikihow.com/Use-SkyDrive

    Thursday, September 26, 2013 3:16 PM
  • Thanks for your help, both of you.

    Here's the .dmp file :

    https://skydrive.live.com/redir?resid=D8F044F3F7E4FFC7!152&authkey=!AA0_gz05PjSCPuA

    And the report from Blue screen viewer.

    https://skydrive.live.com/redir?resid=D8F044F3F7E4FFC7!153&authkey=!AJx51ECp9uS-u0s&v=3

    @V-ANL, everything was ok.

    Thursday, September 26, 2013 3:37 PM
  • Fr_Realmax

    The analysis of this one DMP is inconclusive.  It is a clock watchdog but the driver/process that caused it isnt named.  I can make a good guess as you have one driver from 2005 that is a huge cause of crashes.

    The pre 2009 version of this driver is a known BSOD cause.

    Please visit Asus tek computer inc. -support- drivers and download p7p55d le
    http://support.asus.com/download.aspx?slanguage=en&m=p7p55d%20le&p=1&s=32&os=29&hashedid=e7zic83pvqsr80lm

    Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).
    Download and install it.

    Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).  If you are using Win 8 there is at least a 2012 version which is needed for that.  If you cant find it on the ASUS site you can download it using windows update.  Read about it  here


    STOP 0x101: CLOCK_WATCHDOG_TIMEOUT Troubleshooting

    Here's a good thread on http://www.sysnative.com/forums/showthread.php/1248-0x101-quote-A-clock-interrupt-was-not-received-on-a-secondary-processor-quote


    What you're looking for will be in one of the following categories:

    a) BIOS bug
    b) a driver whose activity is causing the target processor to lock up
    c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...) ?I wonder about CPU defect also)

    So, check the drivers http://www.carrona.org/dvrref.php
    Then check the inside of the case (temperature, voltage, dust, etc).
    Then run hardware stress tests

    Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/

        FurMark Setup:
        - If you have more than one GPU, select Multi-GPU during setup
        - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
        Click "Go" to start the test
        - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
        - Click "Quit" to exit

    Try this free stress test: Free Software - http://download.cnet.com/Prime95-32-bit/3000-2053_4-192895.html
     

        Prime95 Setup:
        - extract the contents of the zip file to a location of your choice
        - double click on the executable file
        - select "Just stress testing"
        - select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
        - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).

        The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
        Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
        The Test selection box and the stress.txt file describes what components that the program stresses.

    More Video Stress Tests:
        1. Thanks to Vir Gnarus (http://www.sysnative.com/forums/members/vir-gnarus.html) for finding this video memory test: https://simtk.org/home/memtest
            Alternate download link (w/o registration) located here: http://folding.stanford.edu/English/DownloadUtils
        2. Two other video stress tests (may be more stressful than FurMark):
            NOTE: I have had reports that some ISP's will block this website
            Video Memory stress Test - http://nvworld.ru/utilities/vmt/
            Artifact Locator - http://nvworld.ru/utilities/alocator/
            Sorry, but I don't read the language that this website is made in.
        3. Another interesting test that came to my attention: http://www.ocbase.com/perestroika_en/index.php?Download
     USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!
        Quote:
        CPU Stress Tests:
        Only need to run 1 or 2 of the tests under most circumstances. I haven't used any of the tests myself, so I listed all that I was able to find.
        - http://downloadcenter.intel.com/Deta...19182&lang=eng
        - http://7byte.com/index.php?page=hotcpu
        - http://www.7byte.com/index.php?page=burnin64
        - http://www.overclock.net/general-pro...ress-test.html
        - http://www.fossiltoys.com/cpuload.html
        - http://www.pcworld.com/downloads/fil...scription.html
        - http://www.overclock.net/general-pro...ress-test.html
        - http://majorgeeks.com/CPU_Stability_Test_d215.html
        - http://www.xtremesystems.org/forums/...d.php?t=201670
        - the test(s) suggested at this link are bootable: http://www.techsupportforum.com/foru...ml#post2232929

    Then try replacing parts.
    Then look up the versions of your BIOS to see what changes were done.


    Recently it was found (here: BSOD Stop 0x00000101 and Stop 0x0000009c ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem. I'd have to recommend at least running SFC.EXE /SCANNOW on any PC that has this problem (simply because it's too easy easy to do and it may fix things). 

    Use !analyze -v to get detailed debugging information.
    BugCheck 101, {31, 0, fffff88002f64180, 2}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    Followup: MachineOwner
    ---------
    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: fffff88002f64180, 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:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  d
    
    If you continue to crash you might want to consider removing Avast (at least to test) and replacing it with MSE>

              


    Wanikiya & Dyami--Team Zigzag

    • Proposed as answer by 暁北 Sunday, October 13, 2013 4:07 PM
    • Marked as answer by ZigZag3143x Sunday, October 13, 2013 4:39 PM
    Thursday, September 26, 2013 3:48 PM
  • please upload the Memory.dmp (compressed as zip, the minidump doesn't contain the data I need to dump out).

    @ZZ read my message on msfn.org!


    "A programmer is just a tool which converts caffeine into code"

    Thursday, September 26, 2013 7:38 PM
  • I think a had a new BSOD today while my computer was performing the primge 95tes, prime95 was no longer started when I returned home.

    Here's the .dmp file : skydrive.live.com/redir?resid=D8F044F3F7E4FFC7!154&authkey=!AMhYDsfsqQgVLjs

    Friday, September 27, 2013 4:21 PM
  • AZ

    Read & replied.


    Wanikiya & Dyami--Team Zigzag

    Friday, September 27, 2013 5:32 PM
  • I just had an other BSOD heres the dmp :

    skydrive.live.com/redir?resid=D8F044F3F7E4FFC7!155&authkey=!AJbD2Fln7KnWjZ

    I don't have any memory.dmp in c:\windows

    Friday, September 27, 2013 6:20 PM
  • please configure your Windows to create full dumps:

    http://support.kaspersky.com/1771


    "A programmer is just a tool which converts caffeine into code"

    Friday, September 27, 2013 8:25 PM
  • Only  have "Kernel image" and "partial image" in Write Debugging Infos (Don't know exactly the english words.)
    Friday, September 27, 2013 10:09 PM
  • kernel is also fine. I need tis large file otherwise I can't see the current thread and what would be the next thread. Maybe I can see something useful from information.

    "A programmer is just a tool which converts caffeine into code"

    Saturday, September 28, 2013 6:46 AM
  • Simply unplug mouse from existing socket and reconnect from another socket, uninstall devices failed correct install (Graphics Controller, Monitor, Video card) and reinstall using all these softwares from Intel website or your computer's motherboard's driver installation CD. Failed Graphics controller install causes these problems.

    Saturday, September 28, 2013 7:38 AM
  • But my graphic card is working fine.
    Saturday, September 28, 2013 12:15 PM
  • I still have some very annoying frezees, the mouse start to lag an I think all the PC. Then everything got stuck.

    And it's happening 4/5 times a day but it never happened when i'm gaming.

    Saturday, September 28, 2013 4:19 PM
  • we need a kernel dump. Have you tried the suggestions from ZigZag?

    "A programmer is just a tool which converts caffeine into code"

    Saturday, September 28, 2013 6:53 PM
  • I'm waiting for a new BSOD and not just only a freeze.

    Yes i've uninstalled avast and installed Kaspersky and the problem is still here.

    Sunday, September 29, 2013 10:29 AM
  • Hello Fr_Realmax,

    Me and also Wanikiya & Dyami--Team Zigzag would tell faulty graphics driver failed install causes windows seizer, carefully select graphics controller compatible for computer motherboard's onboard or PEG/PCI graphics card and operating system, check for successful install of graphics controller.


    Sunday, October 13, 2013 3:46 PM