BSOD: STOP 0x0000009c

[SidWinkelman]

BSOD: Stop 0x0000009C

Hello,

I have been getting this BSOD.
MACHINE_CHECK_EXCEPTION
STOP: 0x0000009C ( 0x0000000000000000, 0xFFFFF880009F8B70, 0x0000000000000000, 0x0000000000000000)

Hardware:
Asus Z87-DELUXE motherboard
Intel Core i5 4670K Unlocked Quad Core 3.4GHZ Processor LGA1150 Haswell 6MB Cache Retail
Corsair Vengeance CML8GX3M2A1600C9 Lowprofile 8GB 2X4GB DDR3-1600 CL9-9-9-24 Dual Channel Memory Kit
Samsung 840 Series 120GB 2.5IN SATA3 Mdx Solid State Disk Flash Drive SSD
ASUS GeForce GTX 770 1110MHZ 2GB 7010MHZ GDDR5 DVI HDMI PCI-E Video Card
Razer BlackWidow Ultimate 2013 Elite Cherry MX Blue Mechanical Gaming Keyboard
Cooler Master Hyper 212 Evo Direct Touch 4 Heatpipe Heatsink AM2 AM3 1366/1150/1155/1156/2011 120mm
ASUS Z87-DELUXE ATX LGA1150 Z87 DDR3 3PCI-E16 4PCI-E1 SLI SATA3 USB3.0 DVI HDMI Motherboard
Cooler Master CM Storm Enforcer Mid Tower Gaming PC Case - USB 3.0 - ATX - 1 x 200mm Front Fan - x 120mm Rear fan - Water Cooling Support (SGC-1000KWN1)
Asus DRW-24B1ST Internal 24X DVD Burner - 5.25" - 1.5MB Cache - SATA - OEM - Black (DRW-24B1ST/BLK/B/AS)
BenQ RL2455HM 24in Gaming LED LCD w/ Speakers
Alienware tactx mouse
Logitech speaker system
Seagate 4TB backup plus external hard drive

Windows 7 ultimate service pack 1 64-bit operating system

BIOS version: 1504 (10/03/2013)
Bluetooth USB module Driver version: 6.5.1.4500
Microsoft Bluetooth Enumerator Driver version: 6.1.7601.17889
ACPI x64-based PC Driver version: 6.1.7600.16385
ATA Samsung SSD 840 SCSI Disk Device Driver version: 6.1.7600.16385
ATA ST1000DM003-1CH1 SCSI Disk Device Driver version: 6.1.7600.16385
Seagate Backup+ Desk USB Device Driver version: 6.1.7600.16385
NVIDIA GeForce GTX 770 Driver version: 9.18.13.3221
ASUS DRW-24F1ST a ATA Device Driver version: 6.1.7601.17514
Numerous HID-compliant consumer control device Driver version: 6.1.7600.16385
Numerous HID-compliant device Driver version: 6.1.7601.18199
Numerous USB Input Device Driver version: 6.1.7601.18199
Razer BlackWidow Ultimate Driver version: 6.2.9200.16384
2x Asmedia 106x SATA Controller driver version 1.3.4.1
2x ATA Channel 0 Driver Version: 6.1.7601.18231
2x ATA Channel 1 Driver Version: 6.1.7601.18231
2x HID Keyboard Device Driver version: 6.1.7601.17514
Alienware TactX Mouse Driver Version: 4.80.154.0 (driver date: 4/22/2009)
BenQ RL2455 Driver Version: 1.0.0.0
Bluetooth Device (Personal Area Network) Driver Version: 6.1.7600.16385
Bluetooth Device (RFCOMM Protocol TDI) Driver Version: 6.1.7600.16385
Broadcom 802.11ac Network Adapter Driver version: 6.31.95.1
Broadcom Virtual Wireless Adapter Driver version: 6.31.95.1
Intel Ethernet Connection I217-V Driver Version: 12.8.33.0
Microsoft Virtual WiFi Miniport Adapter Driver Version: 6.1.7600.16385
4x Intel Core i5-4670K CPU @ 3.40GHz Driver Version: 6.1.7600.16385
Bluetooth Audio Device Driver Version: 7.4.0.140 (date 5/21/2012)
Bluetooth Hands-free Audio Driver version: 6.5.1.2900 (date 4/27/2012)
High definition Audio device 6.1.7601.17514 (date 11/19/2010)
Nvidia High definition audio driver version: 1.3.30.1
NVIDIA Virtual AUDIO Device driver version: 1.2.20.0
ACPI Fan
ACPI Fixed Feature Button
ACPI Thermal Zone
Composite Bus enumerator
Direct memory access controller
PCI standard PCI-to-PCI bridge
Numeric data processor
Microsoft Windows Management Interface for ACPI
Microsoft virtual drive enumerator driver
Microsoft ACPI-compliant system
microsoft system management BIOS drive
Plug and play software device enumerator
programmable interrupt controller
remote desktop device redirector bus
system CMOS/real time clock
system timer
UMBus Enumerator
UMBus Root Bus Enumerator
Generic USB Hub
USB Composite Device
USB mass storage device
USB root hub

I do have a bunch of other drivers for system devices & universal serial bus controllers but there all newer than 2012. All the bold worded drivers are all dated to 2006.
As I said this is my error: STOP: 0x0000009C ( 0x0000000000000000, 0xFFFFF880009F8B70, 0x0000000000000000, 0x0000000000000000)
If i need to provide any log files please request me to upload specific ones, with simple instructions if possible please.

Thanks in advance.

 

[SidWinkelman]

Thanks!

The attached DMP file is of the MACHINE_CHECK_EXCEPTION (9c) bug check.

This bug check indicates that a fatal machine check exception has occurred.

*9C primarily appears on versions of Windows that predate Vista. For example, XP, Server 2003, etc. Nowadays, in Vista and later, we have *124 instead of *9C. However, in very uncommon cases, *9C is presented instead of *124 because the WHEA may not be fully initialized (Windows Error Hardware Architecture) or when a special processor issue on SMP systems occurs that is characterized by a failure with shared memory synchronization.

BugCheck 9C, {0, fffff880009f8b70, 0, 0}

Parameters 1, 3, and 4 are all 0 so I have no idea what happened here in this crash. Parameter 2 contains the address of the MCA_EXCEPTION structure which doesn't really help us in this case since the rest is 0.

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

There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *9C or *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite, AI Charger software, etc. If you have something like this software-wise, remove it ASAP (which I see you do have Asus software installed).

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick Barker
From microsoft forum answered this for me.
Post can be deleted

 

[johnbl]

basically, it sounds like pretty good advice but I would not give up on the CPU yet

yes, update your BIOS, set ot them to the defaults and make sure the voltages to your CPU are good.
and do not overclock your CPU. in particular make sure that the voltage to the CPU VccPLL is within spec so your cpu cache memory works as expected. (confirm with memtest86)

Thanks!

The attached DMP file is of the MACHINE_CHECK_EXCEPTION (9c) bug check.

This bug check indicates that a fatal machine check exception has occurred.

*9C primarily appears on versions of Windows that predate Vista. For example, XP, Server 2003, etc. Nowadays, in Vista and later, we have *124 instead of *9C. However, in very uncommon cases, *9C is presented instead of *124 because the WHEA may not be fully initialized (Windows Error Hardware Architecture) or when a special processor issue on SMP systems occurs that is characterized by a failure with shared memory synchronization.

BugCheck 9C, {0, fffff880009f8b70, 0, 0}

Parameters 1, 3, and 4 are all 0 so I have no idea what happened here in this crash. Parameter 2 contains the address of the MCA_EXCEPTION structure which doesn't really help us in this case since the rest is 0.

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

There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *9C or *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite, AI Charger software, etc. If you have something like this software-wise, remove it ASAP (which I see you do have Asus software installed).

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick Barker
From microsoft forum answered this for me.
Post can be deleted