Multiple Consecutive BSOD 0x00000009c

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Ultimate x64
       #1

    Multiple Consecutive BSOD 0x00000009c


    Hi,

    My computer restarted many times in a row. I could barely get all the start up programs running and open Chrome before it restarts again. Sometimes I get the BSOD with error 0x00000009c and sometimes there is nothing. I starting in Safe Mode with Networking, but that didn't work either.

    I used Nirsoft BlueScreenView and it identified hal.dll every time.

    Can someone assist me in solving this? :)

    Attached is info gathered using SF Diagnostics Tool.

    Details shown sometimes after restarting:
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033

    Additional information about the problem:

    BCCode: 9c
    BCP1: 0000000000000000
    BCP2: FFFFF88002F6CB70
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\042313-21777-01.dmp
    C:\Users\user\AppData\Local\Temp\WER-63398-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
      My Computer


  2. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #2

    anyone?
      My Computer


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

    A stop 9C is common to Machine Check Exception 124: BSOD Index

    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

    You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 Troubleshooting Strategy
    Security App

    Crashes indicate avast! being a possible cause. Remove avast! and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

    Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

    Microsoft Security Essentials, Free antivirus for windows

    Malwarebytes Anti-Malware Free

       Information
    DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.


    Stress Test

    Hardware - Stress Test With Prime95: Hardware - Stress Test With Prime95

    CPU - Stress Test Using IntelBurnTest: CPU - Stress Test Using IntelBurnTest

    Video Card - Stress Test with Furmark: Video Card - Stress Test with Furmark

    Monitor temperature of the system during the tests: Speccy - System Information - Free Download

    Perform steps mentioned in this tutorial: USB Driver - General Fix for Problems

    This tutorial USB Selective Suspend - Turn On or Off may help you.
    To Disable Selective Suspend:

    1. open the control panel
    2. go to power options (you may have to set view to small icons)
    3. click change plan settings
    4. in the window that opens:
    5. click change plan settings
    6. click change advanced power settings, expand usb and ensure usb selective suspend is disabled.
    The below is for information purpose only:
    Code:
    Debug session time: Wed Apr 24 08:05:29.111 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\042313-21138-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 0:11:44.453
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    BugCheck 9C, {0, fffff88002fddb70, 0, 0}
    BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
    Bugcheck code 0000009C
    Arguments: 
    Arg1: 0000000000000000
    Arg2: fffff88002fddb70
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x9C_GenuineIntel
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+2c61
    MaxSpeed:     2670
    CurrentSpeed: 2666
    BiosVersion = F1
    BiosReleaseDate = 12/03/2009
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = H55M-S2H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Wed Apr 24 07:52:05.538 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\042313-21777-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 0:00:47.491
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    BugCheck 9C, {0, fffff88002f6cb70, 0, 0}
    BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
    Bugcheck code 0000009C
    Arguments: 
    Arg1: 0000000000000000
    Arg2: fffff88002f6cb70
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x9C_GenuineIntel
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+2c61
    MaxSpeed:     2670
    CurrentSpeed: 2666
    BiosVersion = F1
    BiosReleaseDate = 12/03/2009
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = H55M-S2H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Wed Apr 24 07:49:53.107 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\042313-21184-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 0:03:16.997
    Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )
    BugCheck 9C, {0, fffff80000ba6bb0, 0, 0}
    BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
    Bugcheck code 0000009C
    Arguments: 
    Arg1: 0000000000000000
    Arg2: fffff80000ba6bb0
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x9C_GenuineIntel
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c
    MaxSpeed:     2670
    CurrentSpeed: 2666
    BiosVersion = F1
    BiosReleaseDate = 12/03/2009
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = H55M-S2H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Wed Apr 24 07:38:04.654 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\042313-24694-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 0:02:20.606
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    BugCheck 9C, {0, fffff8000407fbb0, 0, 0}
    BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
    Bugcheck code 0000009C
    Arguments: 
    Arg1: 0000000000000000
    Arg2: fffff8000407fbb0
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x9C_GenuineIntel
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+2c61
    MaxSpeed:     2670
    CurrentSpeed: 2666
    BiosVersion = F1
    BiosReleaseDate = 12/03/2009
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = H55M-S2H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Wed Apr 24 03:47:47.513 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\042313-20997-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 1:38:43.856
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : intelppm.sys ( intelppm+2c61 )
    BugCheck 9C, {0, fffff88002f6cb70, 0, 0}
    BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
    Bugcheck code 0000009C
    Arguments: 
    Arg1: 0000000000000000
    Arg2: fffff88002f6cb70
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x9C_GenuineIntel
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+2c61
    MaxSpeed:     2670
    CurrentSpeed: 2666
    BiosVersion = F1
    BiosReleaseDate = 12/03/2009
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = H55M-S2H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Fri Apr 19 15:57:37.526 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\041913-23540-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 1 days 14:22:26.900
    *** ERROR: Module load completed but symbols could not be loaded for usbccgp.sys
    Probably caused by : usbccgp.sys
    BugCheck 9F, {3, fffffa8006e60460, fffff8000407c518, fffffa8008f77010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Bugcheck code 0000009F
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8006e60460, Physical Device Object of the stack
    Arg3: fffff8000407c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa8008f77010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_lvuvc64_IMAGE_usbccgp.sys
    MaxSpeed:     2670
    CurrentSpeed: 2666
    BiosVersion = F1
    BiosReleaseDate = 12/03/2009
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = H55M-S2H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Tue Apr 16 12:13:56.942 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\041613-22198-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 10:23:41.284
    *** ERROR: Module load completed but symbols could not be loaded for usbccgp.sys
    Probably caused by : usbccgp.sys
    BugCheck 9F, {3, fffffa800ab45a00, fffff80004077518, fffffa800d74c830}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Bugcheck code 0000009F
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800ab45a00, Physical Device Object of the stack
    Arg3: fffff80004077518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800d74c830, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_lvuvc64_IMAGE_usbccgp.sys
    MaxSpeed:     2670
    CurrentSpeed: 2666
    BiosVersion = F1
    BiosReleaseDate = 12/03/2009
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = H55M-S2H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
      My Computer


  4. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #4

    Thanks for you help. :) I performed all the tests and actions you suggested.

    At first Prime95 caused a reboot after a few minutes, but it ran fine for 6 hours after a bios update.

    I think the bios update may have solved my issue. Thanks again!!!

    Attached is the data from the tests.
      My Computer


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

    Great news and Logs look fine.

    Post here if you have them again, good luck :)
      My Computer


  6. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #6

    It started to happen again after I left the computer on for a couple days in a row. Now I am getting BSOD error 9c every time it resets.

    After starting up, it would BSOD within minutes if not seconds then automatically restart, repeat. I forced it to shut off and turned off the power supply for a few minutes. Then, when I turned it back on it ran fine for a few minutes before BSOD again. It finally started up long enough for me to do a proper shut down and then I left it off for about 12 hours and now it seems to be working fine.

    It would seem that there is a correlation between the duration it is turned off and the duration it will stay on before it will BSOD.

    That was also the only time I did a proper shut down so there's a possibility that had effect.

    Does this info help identify the problem? Is there someway I can fix this or is this just something that is common and I should just accept it by turning it off every night?
      My Computer


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

    Have you gone through this: Stop 0x124 - what it means and what to try
      My Computer


  8. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #8

    I did all the steps up to re-installing Windows. I was hoping I wouldn't have to resort to that. Unfortunately I will not have access to the computer for the next week. I will try re-installing and update when I can get to the computer again.

    Thanks :)
      My Computer


  9. Posts : 15,026
    Windows 10 Home 64Bit
       #9

    Alright take your time
      My Computer


  10. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Updating to resolve the issue:

    Reinstalled W7 and it appears to have fixed the issue. Unsure whether it's just a temporary fix since I did it a year or so ago. I will be happy if it lasts another 2 years since I will probably need an upgrade by then anyways.

    Thanks!
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
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 05:22.
Find Us