This is very interesting.
Code:
1: kd> .bugcheck
Bugcheck code 0000009C
Arguments 00000000`00000000 ffffd001`487f3e60 00000000`00000000 00000000`00000000
//0x9C, machine check exception
1: kd> vertarget
Windows 8 Kernel Version 9600 MP (4 procs) Free x64 //Windows 8 64bit
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 //1 hour of uptime
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.
