Help! What caused my crash

Squark · 24 Jan 2010 at 20:58

How can you access a dmp file to tall me what caused my blue screen?

I'll upload the file if someone can do it

http://www.filedropper.com/012410-26598-01_1

Squark · 26 Jan 2010 at 20:41

Is no-one able to help.

I'm just trying to pin down the cause of my crashing, I'm wondering if it's my gfx card but I'm just not sure

davethe11 · 26 Jan 2010 at 21:20

you haven't given us too much to go on regarding your crashing, the dump file mentions reliccoh.exe, does the freezing/crashing/rebooting(?) happen mid-game?

dump file:

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

Loading Dump File [E:\Windows 7 downloads\012410-26598-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03091e50
Debug session time: Sun Jan 24 20:25:38.432 2010 (GMT+0)
System Uptime: 0 days 2:04:16.336
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80058a8028, b6602000, 2b000135}

Probably caused by : hardware

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

2: 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: fffffa80058a8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6602000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000002b000135, Low order 32-bits of the MCi_STATUS value.

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

BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: RelicCOH.exe

CURRENT_IRQL: f

STACK_TEXT:
fffff880`02f78a88 fffff800`02e1d903 : 00000000`00000124 00000000`00000000 fffffa80`058a8028 00000000`b6602000 : nt!KeBugCheckEx
fffff880`02f78a90 fffff800`02fda513 : 00000000`00000001 fffffa80`058cfea0 00000000`00000000 fffffa80`058cfef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02f78ad0 fffff800`02e1d5c8 : 00000000`00000728 fffffa80`058cfea0 fffff880`02f78e30 00000000`00000100 : nt!WheaReportHwError+0x263
fffff880`02f78b30 fffff800`02e1cf1a : fffffa80`058cfea0 fffff880`02f78e30 fffffa80`058cfea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f78c80 fffff800`02e10e8f : 00000000`1c4cce00 00000000`00000001 fffff880`02f78eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f78cc0 fffff800`02ec47ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02f78cf0 fffff800`02ec4613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f78e30 00000000`24108df9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`226feef8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x24108df9

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

Squark · 27 Jan 2010 at 00:08

Well it happened while I was playing Company of Heroes, but has also happened while I was playing GTA4

What other information would you need to know?

Is it possible to locate where the error came from?

davethe11 · 27 Jan 2010 at 11:24

bsod during gaming is usually either driver related, an overclock causing instability, or a faulty piece of hardware. If you are overclocked, then this would be my first guess as to the problem: are you overclocking your rig (your system specs would be useful)? If so what kind of stress testing have you done to verify your systems stability? If you are overclocked then remove it and go back to stock settings and play the games, see if it helps. Always make sure your gfx drivers are up to date too, but I would do one thing at a time (either remove overclock, or update drivers) and test, then change the other and test some more, changing more than one thing before testing may result in you fixing it for now but not knowing the exact cause of the problem.