I was going to look up your motherboard manual when I noticed you did not let us know what motherboard you have. I then hoped it would be included in your crash report, but instead I found
Code:
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
Please provide your motherboard model so we can provide more assistance with your RAM troubles. System Info - See Your System Specs may help in this regard.
Security Software (this is just a check that you have it and it is working properly; nothing needs to be done with this information at this time):
Code:
avgcsrva.exe c:\program files (x86)\avg\avg2012\avgcsrva.exe 404 8 200 1380 4/11/2012 8:07 AM 12.0.0.1786 507.34 KB (519,520 bytes) 8/15/2011 6:21 AM
avgemca.exe c:\program files (x86)\avg\avg2012\avgemca.exe 3012 8 200 1380 4/11/2012 8:07 AM 12.0.0.1854 1.52 MB (1,593,696 bytes) 9/21/2011 7:53 PM
avgidsagent.exe c:\program files (x86)\avg\avg2012\avgidsagent.exe 2640 8 200 1380 4/11/2012 8:07 AM 12.0.0.1855 4.23 MB (4,433,248 bytes) 10/12/2011 7:25 AM
avgnsa.exe c:\program files (x86)\avg\avg2012\avgnsa.exe 2972 8 200 1380 4/11/2012 8:07 AM 12.0.0.1883 1.90 MB (1,987,424 bytes) 11/28/2011 1:19 AM
avgtray.exe c:\program files (x86)\avg\avg2012\avgtray.exe 3948 8 200 1380 4/11/2012 8:08 AM 12.0.0.1912 2.30 MB (2,416,480 bytes) 1/24/2012 5:24 PM
avgwdsvc.exe c:\program files (x86)\avg\avg2012\avgwdsvc.exe 2172 8 200 1380 4/11/2012 8:07 AM 12.0.0.1773 188.26 KB (192,776 bytes) 8/2/2011 6:09 AM
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\Relough\Windows_NT6_BSOD_jcgriff2\041112-24616-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`03296650
Debug session time: Wed Apr 11 03:57:35.815 2012 (UTC - 6:00)
System Uptime: 0 days 6:17:43.783
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004b66028, be200000, 5110a}
Probably caused by : hardware
Followup: MachineOwner
---------
3: 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: fffffa8004b66028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: FahCore_a4.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff880`02fdda58 fffff800`0301ba3b : 00000000`00000124 00000000`00000000 fffffa80`04b66028 00000000`be200000 : nt!KeBugCheckEx
fffff880`02fdda60 fffff800`031deb33 : 00000000`00000001 fffffa80`052c2ea0 00000000`00000000 fffffa80`052c2ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddaa0 fffff800`0301b700 : 00000000`00000728 fffffa80`052c2ea0 fffff880`02fdde30 fffff880`02fdde00 : nt!WheaReportHwError+0x263
fffff880`02fddb00 fffff800`0301b052 : fffffa80`052c2ea0 fffff880`02fdde30 fffffa80`052c2ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddc50 fffff800`0301af0d : 00000000`00000004 00000000`00000001 fffff880`02fddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddc90 fffff800`0300ee88 : 00000000`c17af80c 00000000`05a6bacc 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02fddcc0 fffff800`030cd56c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fddcf0 fffff800`030cd3d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdde30 00000000`006d7fbe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0360bb80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6d7fbe
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner
---------
FahCore_a4.exe is being blamed for the crash. The crash itself is a 0X124 crash.