[SOLVED] Win 8.1 BSOD Gigabyte MB

tony2071

New member
Joined
Feb 23, 2015
Posts
3
Built a new computer and have had BSOD problems continuously. I have updated the BIOS, updated the drivers, and tried reinstalling Windows 3 times. Initially was trying to use Intel Rapid Storage Technology RAID, but was able to trace first rounds of BSODs to an Intel storage driver and so have now reverted to a simpler setup but am still getting MACHINE_CHECK_EXCEPTION and CLOCK_WATCHDOG_TIMEOUT errors. These will occur 20 to 30 minutes after boot up or sooner if I exercise the system by browsing or playing Minecraft.

I have run the Intel Processor Diagnostic Test with no errors. I have also run the MemTest86 for over an hour with no errors. I have also tried running over the native Intel graphics adapter rather than the NVidia graphics card. I have never overclocked any of the components. The errors continue to occur.

Here are some of the stats on the build. Any help you can provide would be appreciated.

All New Hardware
Gigabyte GA-Z97X-UD5H-BK (rev. 1.0) Motherboard
Intel Core i5 - 4690K
EVGA Supernova 750 G2 - 750W 80 Plus Gold
Corsair Vengance Pro 16 GB (2x8GB) DDR3 SDRAM
Gigabyte GE Force GTX 750 Ti
View attachment GAMINGPC_20150223-000003.zipView attachment SysnativeFileCollectionApp.zipWindows 8.1 Pro x64
 
This is very interesting.

Code:
1: kd> .bugcheck
Bugcheck code 0000009C
Arguments 00000000`00000000 ffffd001`487f3e60 00000000`00000000 00000000`00000000

[COLOR="#800080"]//0x9C, machine check exception
[/COLOR]
1: kd> vertarget
Windows 8 Kernel Version 9600 MP (4 procs) Free x64 [COLOR="#800080"]//Windows 8 64bit[/COLOR]
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
Machine Name:
Kernel base = 0xfffff801`ae406000 PsLoadedModuleList = 0xfffff801`ae6d02d0
Debug session time: Mon Feb 23 16:34:15.778 2015 (UTC + 0:00)
System Uptime: 0 days 1:06:55.454 [COLOR="#800080"]//1 hour of uptime[/COLOR]

What is interesting about your common 0x9Cs is that these bugchecks are almost always non existent in Windows Vista and later operating systems. The reaosn is Windows was changed a lot in Vista to include the more sophisticated and much more complex WHEA data structures and mechanisms for hardware errors. I won't go into detail about it, but it essentially replaces the old 0x9Cs.
The only two reasons that I know of for the 0x9Cs, is due to the WHEA data structures not being fully initialised and encounting a hardware error. The second reason is that the processors have no errors in their registers.
Most likely the latter, given that your system has been running for over an hour, it's not likely that the WHEA structure hasn't been initialised.

Code:
0: kd> .bugcheck
Bugcheck code 00000101
Arguments 00000000`00000030 00000000`00000000 ffffd000`b7000180 00000000`00000003

0: kd> k
Child-SP          RetAddr           Call Site
fffff802`7818dc98 fffff802`76620a7d nt!KeBugCheckEx
fffff802`7818dca0 fffff802`76541678 nt!KeAccumulateTicks+0x2f5cd
fffff802`7818dd30 fffff802`7642567f nt!KeClockInterruptNotify+0x788
fffff802`7818df40 fffff802`7655c363 hal!HalpTimerClockInterrupt+0x4f
fffff802`7818df70 fffff802`765e242a nt!KiCallInterruptServiceRoutine+0xa3
fffff802`7818dfb0 fffff802`765e280f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`b70e9590 00000000`00000000 nt!KiInterruptDispatchLBControl+0x11f

As well as having 0x9Cs, which are rare themselves, you're getting 0x101s. These bugchecks are due to a processor not responding to a clock inter-processor interrupt. It didn't respond within the allocated interval, thus crashing.
Given you're getting both of these consistently, I'm almost certain you have a failing CPU.
If it is under warranty I suggest you RMA and get a replacement.
 
Thanks for the quick reply. This sure seems like a hardware error. I was just surprised that the Intel Processor Diagnostic was coming back clean. Odd. I will RMA the processor and see what happens. Thanks.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top