BSOD Stop x101 and x009c


  1. icestorm32
    Posts : 5
    Windows 7 64 bit
       New #1

    BSOD Stop x101 and x009c


    Been having this problem lately, been getting these two BSOD errors. Bot x101 and x009c, the x101 is happening more often though. It tends to happen just as I am starting up the PC and it has only been running for about 5 - 10 mins and then it BSOD's.

    I have the details for a few of the times that it has happened but the two main culprits appear to be hal.dll and ntsokrnl.exe. They all share the same crash address: ntoskrnl.exe+7f1c0 though.

    I have a:

    Intel i7 920 x 2.67khz CPU
    EVGA x58 (e760) Classified Motherboard (141-BL-E760-8A79TEVBC-00)
    Nvidia GeForce GTX 580 Graphics Card

    But here is the full information from Blue Screen View.


    Crash Time: 10 - Oct - 2012
    Bug Check Code: 0x00000101
    Parameter 1: 00000000`00000019
    Parameter 2: 00000000`00000000
    Parameter 3: fffff880`030f9180
    Parameter 4: 00000000`00000006
    Caused by Driver: ntoskrnl.exe
    Caused by Address: ntoskrnl.exe+7f1c0
    File Version: 6.1.7601.17835 (win7sp1_gdr.120503-2030)
    Crash Address: ntoskrnl.exe+7f1c0
    Processor Count: 8

    -----------------------------------------------------------------------------------

    Crash Time: 08 - Oct - 2012
    Bug Check String: MACHINE_CHECK_EXCEPTION
    Bug Check Code: 0x0000009c
    Parameter 1: 00000000`00000000
    Parameter 2: fffff880`02fddc70
    Parameter 3: 00000000`00000000
    Parameter 4: 00000000`00000000
    Caused by Driver: Hal.dll
    Caused by Address: hal.dll+12818
    Crash Address: ntoskrnl.exe+7f1c0
    Processor Count: 8

    -----------------------------------------------------------------------------------

    Crash Time: 08 - Oct - 2012
    Bug Check Code: 0x00000101
    Parameter 1: 00000000`00000019
    Parameter 2: 00000000`00000000
    Parameter 3: fffff880`02f64180
    Parameter 4: 00000000`00000002
    Caused By Driver: PCIIDEX.SYS
    Caused By Address: PCIIDEX.SYS+112c
    Crash Address: ntoskrnl.exe+7f1c0
    Processor Count: 8

    -----------------------------------------------------------------------------------

    Bug check Code: 0x00000101
    Parameter 1: 00000000`00000019
    Parameter 2: 00000000`00000000
    Parameter 3: fffff880`030f9180
    Parameter 4: 00000000`00000006
    Caused by Driver: Ntfs.sys
    Caused by Address: Ntfs.sys+fe84
    Crash Address: ntoskrnl.exe+7f1c0
    Processor Count: 08



    Heres also some information from Who Crashed

    On Wed 10-Oct-12 5:34:57 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101012-29172-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880030F9180, 0x6)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System

    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    On Mon 08-Oct-12 6:26:59 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\100812-23322-01.dmp
    This was probably caused by the following module: hal.dll (hal+0x12818)
    Bugcheck code: 0x9C (0x0, 0xFFFFF88002FDDC70, 0x0, 0x0)
    Error: MACHINE_CHECK_EXCEPTION
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL

    Bug check description: This bug check indicates that a fatal machine check exception has occurred.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


    I really hope you can help me as I've been having this for a while and I just want to know how to fix it.
    Last edited by icestorm32; 10 Oct 2012 at 03:28.
      My Computer
    Quote Quote

  3. icestorm32
    Posts : 5
    Windows 7 64 bit
    Thread Starter
       New #2

    Here is also an event viewer file.

    I should also mention that I have run sfc /scannow and dskchk /f
      My Computer
    Quote Quote

  4. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #3

    https://www.sevenforums.com/crashes-d...tructions.html

    STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
      My Computer
    Quote Quote

  6. icestorm32
    Posts : 5
    Windows 7 64 bit
    Thread Starter
       New #4

    Ok I updated the original post with the SF Diagnostic information. I should mention that the x9C error only tends to happen once per session (of using the computer) but the x101 tends to happen fairly randomly. Since reading the information about the problem, it appears that it is the processor for the x101 so that would explain it's randomness.

    I just really hope that it is driver related. Since the CPU up until about a month ago was running all types of games without any problem.
      My Computer
    Quote Quote

  7. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #5

    STOP 0x0000009C: MACHINE_CHECK_EXCEPTION BSOD Index
    Usual causes: Hardware error (similar to STOP 0x124)

    STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT BSOD Index
    Usual causes: Device driver, BIOS bug, hardware defect (see Significant Posts section below)
    Go through this: Stop 0x124 - what it means and what to try
    And this: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
      My Computer
    Quote Quote

 

  Related Discussions
BSOD x101 and x124
in BSOD Help and Support

I've been getting BSOD over the past few weeks. Sometimes everyday, sometimes once a week. I've used bluescreenview to look at dmp its its saying its caused by driver ntoskrnl.exe which i think is memory. Wanted to know if anyone thinks the same. Here is the dmp from bluescreenview Specs: MSI...
Recurring X101 BSOD during gaming
in BSOD Help and Support

Hello A few weeks, or even a couple of months ago, my system became very unstable. While I was playing videogames, it would randomely reboot without BSOD, simply freeze, so that I had to manually restart, or, more often than the previous, display a BSOD about "a clock interrupt was not received...
Random BSOD error x101
in BSOD Help and Support

I am currently running windows home premium x64. I have gotten the BSOD occasionally inthe past but today it has happened numerous times. I recently updated my graphics card driver, however, i had the problem before that. my specs are AMD FX 4100 quad core 3.60 Ghz Nvidia gtx 560 8gb Ram...
Hello i have had 2 BSOD's or more recently. I dont know why, i only saw 2 of them, but ive had around 3 - 4, the other 1 - 2 were seen by family members but they just turned the pc off and back on... anyhow here are some pictures ...
Guys I'm at a loss I'm getting BSOD's all the time I really don't know what to do with it, and I'm not computer heavy so. If someone here could help me that would be appreciated. I've included a Dxdiag file with the rest.
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 23:09.
Find Us