Hi Gumble316 ^_^,
Thanks for following the instructions closely and uploading the required file. This reveals the culprit. Below is the stack information obtained from the Dump File :-
Code:
0: kd> k
Child-SP RetAddr Call Site
fffff803`394fca38 fffff803`3783f213 nt!KeBugCheckEx
fffff803`394fca40 fffff803`37a37f71 hal!HalBugCheckSystem+0xcf
fffff803`394fca80 fffff803`3783f6a0 nt!WheaReportHwError+0x22d
fffff803`394fcae0 fffff803`3783fa0d hal!HalpMcaReportError+0x50
fffff803`394fcc30 fffff803`3783f8f8 hal!HalpMceHandlerCore+0xe1
fffff803`394fcc80 fffff803`3783fb42 hal!HalpMceHandler+0xe4
fffff803`394fccc0 fffff803`3783fccf hal!HalpMceHandlerWithRendezvous+0xce
fffff803`394fccf0 fffff803`379d67bb hal!HalHandleMcheck+0x40
fffff803`394fcd20 fffff803`379d6571 nt!KxMcheckAbort+0x7b
fffff803`394fce60 fffff800`4d53e318 nt!KiMcheckAbort+0x171
fffff803`394e8690 fffff800`4d53e171 [COLOR=#ff0000][B]athw8x[/B][/COLOR]!readPlatformRegOnce+0xa8
fffff803`394e86e0 fffff800`4d4f7aec athw8x!ath_hal_reg_read+0x25
fffff803`394e8730 fffff800`4d56454d athw8x!ar9300_get_11n_ext_busy+0x5c
fffff803`394e8790 fffff800`4d5e5c5f athw8x!ath_printreg+0x399
fffff803`394e87c0 fffff800`4d5e46ff athw8x!ath_cwm_get_extchbusyper+0x27
fffff803`394e87f0 fffff800`4d5e4576 athw8x!cwm_stop+0x7a7
fffff803`394e8830 fffff800`4d5761e5 athw8x!cwm_stop+0x61e
fffff803`394e8890 fffff800`4d6dd6f3 athw8x!ath_led_suspend_stop+0x109d
fffff803`394e88d0 fffff800`4bc95f76 athw8x!ndis_timer_handler+0x283
fffff803`394e8960 fffff803`378ba760 ndis!ndisMTimerObjectDpc+0xc6
fffff803`394e89b0 fffff803`379cf7ea nt!KiRetireDpcList+0x4f0
fffff803`394e8c60 00000000`00000000 nt!KiIdleLoop+0x5a
So, do you see the red highlighted driver? It is the "athw8x.sys" which is the Qualcomm Atheros Wireless LAN Driver. This is the first time that I have seen that a WHEA Bugcheck being caused by a driver. I was told that it can also be done by a low level driver like Disk, Processor etc but this was the first time in front of me. So, Thanks for providing the dump!
Now, if we check the date of the driver :-
Code:
0: kd> lmvm athw8x
start end module name
fffff800`4d47c000 fffff800`4d805000 athw8x (pdb symbols) c:\symbols\athw8x.pdb\E6244F77554F462D8314845F508649BB1\athw8x.pdb
Loaded symbol image file: athw8x.sys
Image path: \SystemRoot\system32\DRIVERS\athw8x.sys
Image name: athw8x.sys
Timestamp: Thu Jan 17 14:45:39 [COLOR=#0000ff][U][B]2013[/B][/U][/COLOR] (50F7C13B)
CheckSum: 00386204
ImageSize: 00389000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2013 drivers of Qualcomm Atheros installed by the Windows 8.1 (Most likely) almost always cause BSOD's. Happened with my machine and some other machines as well which I saw.
Please download and install the latest drivers from this
**LINK** and then install them. You would need to install them manually as I don't think there would be an executable file. Don't worry about the site, it is trusted.
Let me know how it goes ^_^.
EDIT :- I forgot to mention that since the QUALCOMM Atheros Driver is calling a WHEA or Machine Check Exception, there is a possibility that the Network Card is dying. But, before that let us make sure that the outdated driver is not causing it ^_^.