windows 7 unexpected shutdown (dump file)

[sram]

Hello all. I just want to know how to use dump files to see what created problems. Windows 7 shutdown on me and I want to know why. I can upload the dump file in here.

Please help me determine what the problem is.

Dump file;

https://hotfile.com/dl/160318716/f15e0f6/061912-10436-01.dmp.html

Thanks.

 

[Tawnos]

Is this system overclocked?

This is a WHEA fault - basically, something went really screwy in hardware.

 

[Snowknight26]

Loading Dump File [C:\temp\061912-10436-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\dbg*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`01e1d000 PsLoadedModuleList = 0xfffff800`02061670
Debug session time: Mon Jun 18 15:59:00.832 2012 (UTC - 5:00)
System Uptime: 0 days 7:17:17.348
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8019a56028, be200000, 5110a}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware

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

7: 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: fffffa8019a56028, 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: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`022adb58 fffff800`02417a3b : 00000000`00000124 00000000`00000000 fffffa80`19a56028 00000000`be200000 : nt!KeBugCheckEx
fffff880`022adb60 fffff800`01fa9b03 : 00000000`00000001 fffffa80`197f68b0 00000000`00000000 fffffa80`197f6900 : hal!HalBugCheckSystem+0x1e3
fffff880`022adba0 fffff800`02417700 : 00000000`00000728 fffffa80`197f68b0 fffff880`022adf30 fffff880`022adf00 : nt!WheaReportHwError+0x263
fffff880`022adc00 fffff800`02417052 : fffffa80`197f68b0 fffff880`022adf30 fffffa80`197f68b0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`022add50 fffff800`02416f0d : 00000000`00000008 00000000`00000001 fffff880`022adfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`022add90 fffff800`0240ae88 : fffff880`022a5180 fffff880`022b00c0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`022addc0 fffff800`01e9aaac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`022addf0 fffff800`01e9a913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`022adf30 fffff800`01ea60d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`022cdab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x184


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
---------

Stop OCing.

 

[sram]

Is this system overclocked?

This is a WHEA fault - basically, something went really screwy in hardware.

Yes, it is the rig in my sig.

Stop OCing.

Why stop rather than lower my overclock?

Can you please expand? What does it say really? And how bad is it?

And If I'm IBT and prime95 stable with this overclock, how could this happen, and what does it really mean?


Thanks.

 

[Tawnos]

Yes, it is the rig in my sig.

Why stop rather than lower my overclock?

Can you please expand? What does it say really? And how bad is it?

And If I'm IBT and prime95 stable with this overclock, how could this happen, and what does it really mean?


Thanks.

You should read this to see what is possible from OC: http://blogs.msdn.com/b/oldnewthing/archive/2005/04/12/407562.aspx

I didn't bother checking which instruction you faulted on, the important thing is that this is windows detecting a hardware error.