BSOD 0x9C during gaming, new gaming PC, nothing helps

Toggle sidebar Toggle sidebar
L

L4zz1

Reputable
Feb 19, 2015
13
0
4,510
Hi all! About 4 months ago I bought all new parts and assembled a PC for gaming / school work. The goal was to buy parts that are instantly available (sold older PC to a friend and I needed a replacement fast) and the price range was about 1000-1200€ (in Finland). I ended up with the following parts:

- Fractal design Define R4 Black Pearl
- Asus DRW-24F1ST/BLK/G/AS 24x DVD+/-RW
- Kingston HyperX Genesis 8 GB (2 x 4 GB)
- WD Green 1 TB SATA III 64 MB
- MSI GeForce GTX 760 Gaming OC Edition 2048 MB
- Kingston SSDNow v300 120 GB SSD 2,5"
- Corsair CX600W V2
- Intel Core i5 4690K 3,5 GHz LGA1150
- Asus Z97-K Intel Z97 LGA 1150 ATX
(Decided to save some money and buy heatsink/cpu fan later, since I also needed a new monitor)

- Running Windows 7 Ultimate 64 bit

I haven't overclocked anything.

All seemed fine until I installed the first games and Bluescreens started coming up.
There are 2 different BSOD Im getting (more detailed info below). Always Machine Check Exeption 0x9C. The thing is BSOD only comes during gaming. First the sound loops and everything freezes followed by BSOD.

Searching for the problem I have:

- Formatted and re-installed everything 3 times
- Monitored temperatures with Bios, Realtemp, Open hardware monitor (60c-80c with heavy gaming)
- Run sfc / scannow, chkdsk, Seatools, Lifeguard Diagnostic, Memtest, Prime95, Heaven Benchmark, dxdiag
- Borrowed my old rams and graphics card back and replaced the new ones
- Removed and put back pretty much all the parts, checked the wires etc.

Bios is version 0330 which should be compatible with my current build.

I have my system in SSD and all the games and programs in the 1 TB WD. I also installed some games to the SSD but no change.

And nothing makes any difference... BSOD doesn't seem to have any logic; it might come right when I start gaming or after 8 hours of gaming. Record is 6 times a day but it may also wait for 2 days while I think I finally fixed it and then reappears. While Im aware that 80c might be a bit too high, BSOD presents itself also with lower temperatures.

I installed WhoCrashed to open my .dmp files and I got this:

On Thu 19.2.2015 17:43:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021915-3884-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF88002F6DB70, 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 that cannot be identified at this time.



On Thu 19.2.2015 17:43:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalInitializeBios+0x1500)
Bugcheck code: 0x9C (0x0, 0xFFFFF88002F6DB70, 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 that cannot be identified at this time.



On Thu 19.2.2015 16:00:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021915-4586-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF88002FDFB70, 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 that cannot be identified at this time.



As a result I'm out of ideas so before sending my parts back to warranty 1 by 1 and waiting for 2 weeks / piece I'll open a cold one and spam F5 here. All help is greatly appreciated, thanks in advance!
 
Solution
J
put your actual memory .dmp on a cloud server and put a link.
Also, do you have an idea how long the system was up before it crashed? 10 seconds? or longer than 15 minutes?

my assumption is your GPU pulled too much power, the CPU reset but you have a poor power supply and it did not prevent the CPU from restarting before the power supply was stable. Then the CPU generated a error because its power was too low and the CPU called a bugcheck.

to prevent this you would: remove any GPU or CPU overclock software, maybe under clock the GPU memory by 100MHz. (check cooling on the GPU and CPU) AND make sure any supplemental power connections from the PSU to the GPU are connected and working

Or you need to update or reset your BIOS to...
Sort by date Sort by votes
put your actual memory .dmp on a cloud server and put a link.
Also, do you have an idea how long the system was up before it crashed? 10 seconds? or longer than 15 minutes?

my assumption is your GPU pulled too much power, the CPU reset but you have a poor power supply and it did not prevent the CPU from restarting before the power supply was stable. Then the CPU generated a error because its power was too low and the CPU called a bugcheck.

to prevent this you would: remove any GPU or CPU overclock software, maybe under clock the GPU memory by 100MHz. (check cooling on the GPU and CPU) AND make sure any supplemental power connections from the PSU to the GPU are connected and working

Or you need to update or reset your BIOS to defaults if this happens right after you just start the OS.
 
Upvote 0 Downvote
Solution
BSOD may appear right after I start the system or after 24 hours of uptime. So far it seems pretty random. Gaming seems to be the only thing that triggers it. For example running Heaven Benchmark 4.0 over the night didn't trigger bsod (might be "bad" luck tho, since sometimes I have been able to play almost 2 days without BSOD).

I uploaded minidumps; memory.dmp takes a bit longer to upload so I'll provide a link to that when it is ready.

I haven't overcloked anything and I dont have any OC software running either.

http://s000.tinyupload.com/index.php?file_id=05214891624260464484

http://s000.tinyupload.com/?file_id=39962738462319611605
 
Upvote 0 Downvote
Alright so I removed Open Hardware Monitor and decided to uninstall F-Secure completely.
I installed Avast as a temporary solution.

I'll test playing different games and report what happens! So far CS:GO and LoL are the
best choises to get BSOD.
 
Upvote 0 Downvote
Still got a BSOD, completely new one though. Still during gaming and system has been up for about 3 hours.

On Sun 22.2.2015 19:32:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022215-4102-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EF180, 0x1)
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 that cannot be identified at this time.

I uploaded the minidump:

http://s000.tinyupload.com/index.php?file_id=04750814291928848472
 
Upvote 0 Downvote
After removing those 2 system files I still haven't got any Machine Check Exception BSODs
so looks like that helped! That Clock Watchdog Timeout BSOD was weird though.

Could that have been caused by faulty drivers or power supply?

Luckily that has only appeared once.
 
Upvote 0 Downvote
change your memory dump type from minidump to kernel memory dump and post a link to the new memory dump file when it bugchecks the next time. (minidumps strip out the required debug info from the file)

for bugcheck 0x101 CLOCK_WATCHDOG_TIMEOUT
you have to provide a kernel memory dump to debug this type of problem. In this case I think the system thinks one of your processor cores is hung.

Most often I see this because of bogus usb drivers. And most often it is a USB wireless ethernet driver for a USB ethernet thumb device. The device gets plugged in, the plug and play tries to install the driver and fails and plug and play tries to install it again, over and over. At the same time there is another core running something that is trying to use the driver that has not installed yet.






 
Upvote 0 Downvote
oops, I guess I forgot to hit update.

I think your CPU processor 3 got hung. (not certain why)
also, your machine keeps trying to do a silent install for "ACPI\PNP0A0A\2&daba3ff&1"
and fails over and over. Problem = CM_PROB_FAILED_INSTALL
you might go to asus and download the driver.


here is some info on the unknown device. I guess it is a ASUS BIOS extension to let their drivers talk to the BIOS.
here is the info i read: http://kb.stonegroup.co.uk/index.php?View=entry&EntryID=227

downloading the new memory dump now, will look at it in a few minutes



 
Upvote 0 Downvote
I downloaded "ASUS Probe II Sense Driver 1.0.1.0 for Windows Win7 32bit & Win7 64bit & Win8 32bit" from Asus -> Utilities
and I got a little pop-up saying "Asus Probe Installed" but that didn't remove the Unknown device.

I also tried one of the "alternate downloads" from your link but AsusSetup only says "copyfile to folderid_devicemetadatastore OK!" and nothing happens. Maybe I downloaded a wrong driver, gotta go and do one exam and try again in couple of hours.
 
Upvote 0 Downvote
I disabled that Unknown device completely. Hopefully that stops the silent install. Not sure if I can check that from somewhere.
And I still haven't gotten any new Bluescreens since removing F-Secure and Open Hardware Monitor which is absolutely amazing!

Did my latest Memory.dmp give any info about that one time random BSOD? Other than that all seems to be fine.
That BSOD came when I was playing H1Z1 though and that is still very early access. That might have something to do with it.
 
Upvote 0 Downvote
I was hoping that disabling the unknown driver might prevent the problem in this bugcheck.
you have a Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
but have a 2010 version of:
\SystemRoot\system32\mcupdate_GenuineIntel.dll Sat Nov 20 05:03:51 2010

this file has CPU microcode to override known bugs in a intel CPU electronics. you should install the intel CPU chipset drivers to get a update. (just in case it is a known CPU problem) get the updates from here:
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775



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

in that bugcheck, you had a many attempts at a silent install of the driver, then core three stopped responding to the other cores. That core was doing the bulk of the work of your system. It was running a bunch of powerISO, a bunch of USB calls, virus scanning, ... and it just kind of stopped communicating. it looked like some old directx call was waiting and just did not get its signal.

verifier.exe flags were not set so windows did not add extra device driver error checking.

here is more info from the debugger. not sure what to look at but all the CPUs were trying to write their bufffers.

3: kd> !ipi
IPI State for Processor 0

As a sender, awaiting IPI completion from processor(s) 1.

TargetCount 1 PacketBarrier 1 IpiFrozen 0 [Running]


IPI State for Processor 1

As a receiver, unhandled requests are pending from processor(s) 0, 3.

TargetCount 0 PacketBarrier 0 IpiFrozen 5 [Target Freeze]

From processor 0, active request of type: flush all
From processor 3, active request of type: packet ready
WorkerRoutine fffff80002eafe10 (nt!xHalFreeMessageTarget)
Parameter[0] 0 Parameter[1] 0 Parameter[2] 0

IPI State for Processor 2
TargetCount 0 PacketBarrier 0 IpiFrozen 2 [Frozen]


IPI State for Processor 3

As a sender, awaiting IPI completion from processor(s) 1.

TargetCount 1 PacketBarrier 1 IpiFrozen 2 [Frozen]





 
Upvote 0 Downvote
Nope, still got it. The older BSOD came back during Counter Strike.

On Thu 26.2.2015 1:13:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022615-4087-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF88002F6DB70, 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 that cannot be identified at this time.



On Thu 26.2.2015 1:13:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalInitializeBios+0x1500)
Bugcheck code: 0x9C (0x0, 0xFFFFF88002F6DB70, 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 that cannot be identified at this time.

Uploaded the dump here:
http://www.filedropper.com/memory3

Didn't install that chipset yet but that is the first thing to do tomorrow.
 
Upvote 0 Downvote
-it does look like your BIOS is 5 versions old, I would update to the current version.
http://www.asus.com/Motherboards/Z97K/HelpDesk_Download/

this will get bug fixes for your motherboard and CPU microcode updates. I would also install the CPU chipset drivers from intel to get the most current window microcode patches.


looks like you have some problem with a program called jpatch.exe
from Riot Games, Inc.? looks like there were hundreds of copies running(1500?).

machine info:
BIOS Release Date 05/29/2014
BIOS Version 0330
Manufacturer ASUSTeK COMPUTER INC.
Product Z97-K

Processor ID c3060300fffbebbf
Processor Version Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3900MHz
Current Speed 3500MHz


2: kd> !sysinfo cpumicrocode
Initial Microcode Version: 00000019:00000000
Cached Microcode Version: 00000019:00000000
Processor Family: 06
Processor Model: 3c
Processor Stepping: 03


BugCheck 9C, {0, fffff88002f6db70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

Followup: MachineOwner
---------

2: kd> !ipi
IPI State for Processor 0
TargetCount 0 PacketBarrier 0 IpiFrozen 2 [Frozen]


IPI State for Processor 1

As a receiver, unhandled requests are pending from processor(s) 2.

TargetCount 0 PacketBarrier 0 IpiFrozen 5 [Target Freeze]

From processor 2, active request of type: packet ready
WorkerRoutine fffff80002ebde10 (nt!xHalFreeMessageTarget)
Parameter[0] 0 Parameter[1] 0 Parameter[2] 0

IPI State for Processor 2

As a sender, awaiting IPI completion from processor(s) 1.

TargetCount 1 PacketBarrier 1 IpiFrozen 0 [Running]


IPI State for Processor 3
TargetCount 0 PacketBarrier 0 IpiFrozen 2 [Frozen]






 
Upvote 0 Downvote
I updated BIOS and Intel chipset drivers. Have to wait and see if it helped.

That League of Legends' patcher is really weird though, have to monitor if that happens again.
 
Upvote 0 Downvote
Damn, still got it. Another of the 2 original BSODs i've been getting. Just when I thought updating BIOS finally did it.
Opened League of Legends and shortly got the BSOD.

I uploaded dmp again:

http://www.filedropper.com/memory4

On Thu 5.3.2015 16:38:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030515-4711-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF80000BA8BB0, 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 that cannot be identified at this time.



On Thu 5.3.2015 16:38:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalInitializeBios+0x1500)
Bugcheck code: 0x9C (0x0, 0xFFFFF80000BA8BB0, 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 that cannot be identified at this time.

 
Upvote 0 Downvote
well, MACHINE_CHECK_EXCEPTION is considered a hardware error.
I am not sure how to decode the MCA_EXCEPTION structure reported
0: kd> dd fffff80000ba8bb0
fffff800`00ba8bb0 00000001 00000000 d8a446a2 01d05762


- you might be getting a parity error on your PCI/e bus. You might pull your graphics card and re insert it.
- you might try underclocking your GPU
- you might try and overclock you PCI/e bus to match the overclocked GPU.

maybe see if you get the same problem with another GPU
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom