Help with Memory Dump

[Relayman]

Hi Guys,

I have the following system:

Gigabyte GA-Z68-UD3H-B3 MOBO
I5 2500K CPU
16gb G.Skill F3-12800CL9Q-16BXL Ram
OCZ Agility 3 SSD
Coolmaster Hyper 212 cooler
Windows 8
Onboard Graphics

Can anybody help me to understand my memory dump file? I've getting random BSOD for a long while now and am not sure why. I've run all the test like Memtest86 and Prime95 over and over. They always pass. I just learned how to look at my memory dump file but am not sure what it is telling me. I'm a novice at this kind of thing and this is also my first build. I do not overclock at this time and don't have any kind of crazy setup. I just am trying to get a stable system. I've included my latest dump file. If anyone can offer some insight it would be greatly appreciated.

Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
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 Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\cache
Symbol search path is: C:\cache
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff800`89a10000 PsLoadedModuleList = 0xfffff800`89cdca20
Debug session time: Sun Nov  3 13:06:00.528 2013 (UTC - 5:00)
System Uptime: 1 days 8:08:33.150
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007f7`45faf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8010bdf028, bb800000, 175}

Page 10a9a6 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f35c6 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : GenuineIntel

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

1: 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: fffffa8010bdf028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bb800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.

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

Page 3f35c6 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f3a00 not present in the dump file. Type ".hh dbgerr004" for details

BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

STACK_TEXT:  
fffff880`009c9868 fffff800`8a189965 : 00000000`00000124 00000000`00000000 fffffa80`10bdf028 00000000`bb800000 : nt!KeBugCheckEx
fffff880`009c9870 fffff800`89b70ef9 : 00000000`00000001 fffffa80`0c767320 00000000`00000000 fffffa80`10bdf028 : hal!HalBugCheckSystem+0xf9
fffff880`009c98b0 fffff800`8a189703 : 00000000`00000728 00000000`00000001 fffff880`009c9a10 fffffa80`0c767320 : nt!WheaReportHwError+0x249
fffff880`009c9910 fffff800`8a189020 : 00000000`00000010 fffffa80`0c767320 fffff880`009c9ac8 fffffa80`0c767320 : hal!HalpMcaReportError+0x53
fffff880`009c9a70 fffff800`8a188f1b : fffffa80`0c7f96f0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`009c9ac0 fffff800`8a188d78 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`009c9b00 fffff800`8a189f0f : fffffa80`0c7f96f0 fffff880`009c9d30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`009c9b30 fffff800`89a6877b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009c9b60 fffff800`89a6852e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`009c9ca0 fffff960`001f11a0 : fffff880`1a608568 00000000`00000000 00000000`00000000 00000000`0000008e : nt!KiMcheckAbort+0x16e
fffff880`1a608140 fffff960`00220106 : 00000003`00000000 00000000`01cd8569 00000000`00001680 00000000`00000000 : win32k!vDirectStretch32+0xdd
fffff880`1a608180 fffff960`001ea4d0 : fffff8a0`00164880 fffffa80`0c750638 fffff901`000c7010 fffff901`009ee730 : win32k!StretchDIBDirect+0x3a6
fffff880`1a6082d0 fffff960`001f0e67 : 00000000`4705123d fffff880`1a608ad0 fffff880`1a608949 fffff800`89abde62 : win32k!EngStretchBltNew+0x5b0
fffff880`1a608820 fffff960`001f2f02 : fffff901`00000dc0 00000000`00000000 fffff901`000f63c0 fffff901`008eb900 : win32k!EngStretchBlt+0xd7
fffff880`1a608980 fffff960`001f3629 : fffffa80`0d5982b0 00000000`00000000 fffff880`1a608ec0 000000d2`5287a840 : win32k!GreStretchDIBitsInternal+0x872
fffff880`1a608cf0 fffff800`89a69453 : 00000000`4c0113ad 000000d2`00000000 fffff901`00000000 00000000`000005a0 : win32k!NtGdiStretchDIBitsInternal+0x1c9
fffff880`1a608dd0 000007ff`ef3f469a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000d2`5287a658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007ff`ef3f469a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

Followup: MachineOwner

 

[redduc900]

With the DRAM frequency at DDR3-1600 and the timings at 9-9-9-24-2T, first bump the DRAM voltage from the rated 1.50V to 1.55V. If you still receive the 0x124 STOP error, increase QPI/Vtt voltage from 1.05V (Auto) to 1.1V, and no greater than 1.15V.

 

[Relayman]

Thanks for the tip. I will give your advice a try and report back with the results.

Thanks again

 

[Relayman]

I tried setting the voltages as suggested but still get the crashes. I'm at a loss as to why. Anymore help would be great.

Thanks