Hunting Down BSODs

[Soichiro]

Lately I've been experiencing occasional BSODs on my new machine. Not overly frequent, but once every few days--enough to be significantly annoying. I managed to get one of the MEMORY.DMP files and open it in WinDbg, and this is what I got from it:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: srv*d:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff800`c7600000 PsLoadedModuleList = 0xfffff800`c78cca20
Debug session time: Thu Oct  3 05:08:36.423 2013 (UTC - 4:00)
System Uptime: 0 days 11:36:35.962
Loading Kernel Symbols
...............................................................
................................................................
....Page 11157b not present in the dump file. Type ".hh dbgerr004" for details
.Page 11254a not present in the dump file. Type ".hh dbgerr004" for details
.......................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7f64a018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80095f4028, be000000, 100110a}

Probably caused by : GenuineIntel

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80095f4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  League of Lege

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`01d54968 fffff800`c7d79965 : 00000000`00000124 00000000`00000000 fffffa80`095f4028 00000000`be000000 : nt!KeBugCheckEx
fffff880`01d54970 fffff800`c7760ef9 : 00000000`00000001 fffffa80`06a08850 00000000`00000000 fffffa80`095f4028 : hal!HalBugCheckSystem+0xf9
fffff880`01d549b0 fffff800`c7d79703 : 00000000`00000728 00000000`00000004 fffff880`01d54b10 fffffa80`06a08850 : nt!WheaReportHwError+0x249
fffff880`01d54a10 fffff800`c7d79020 : 00000000`00000010 fffffa80`06a08850 fffff880`01d54bc8 fffffa80`06a08850 : hal!HalpMcaReportError+0x53
fffff880`01d54b70 fffff800`c7d78f1b : fffffa80`06769e00 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`01d54bc0 fffff800`c7d78d78 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`01d54c00 fffff800`c7d79f0f : fffffa80`06769e00 fffff880`01d54e30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`01d54c30 fffff800`c765877b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`01d54c60 fffff800`c765852e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`01d54da0 00000000`014a2629 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`1302f974 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x14a2629


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

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

Now, the process faulted here is League of Legends but I highly doubt that is the direct cause, or more people would be complaining about it. So I'm trying to figure out what the underlying cause is. It usually occurs when I'm gaming. I've run a Memtest but no errors were found over several passes. Hopefully someone here who is better at understanding memory dumps can help me interpret this and figure out the root of the problem.

Edit: I should also note this is the machine (updated) in my signature and nothing is overclocked. Video card drivers are the latest Geforce 327.23 from Nvidia.

 

[redduc900]

I'd probably start by raising either the Vring (CPU Cache voltage) or Vrin / Vrin Override (CPU Input voltage).

 

[Soichiro]

Hmm, it might be from the EPU switch on the motherboard then. I'll try turning it off and see if the BSODs continue.

 

[TeknoBug]

When I get repeated BSOD I start diagnosing by memtest86 (if possible) and taking out sticks and booting with just 1 stick at a time. BSOD's often happen with faulty memory, at least for me in the past. Other than it's usually my fault by overclocking something without upping voltage, etc.