BSOD - usually whilst playing Dishonoured

Hi all,

Playing Dishonoured has been causing my comp to BSOD every 40 mins or so. Temps seem fine but I thought it could be a PSU problem (it's the no-name one that came with the case).

It BSOD this morning whilst Dishonoured was running but minimised, which is weird because the GPU wasn't working hard and CPU was at about 47%.

So anyway, I was hoping that some altruistic soul could check my crashdumps and make sure it's not a driver issue, before I shell out for a new PSU

Thanks!

Hello fraktal and welcome to the forums

What AMD GPU do you have? If you know how to do so, please update your drivers.

Tom

Hi,

I'm having a look at this now. Can you please gather some more information using this tool, then upload the new file here?

https://www.sevenforums.com/crashes-d...tructions.html

Regards,
Golden

Hi,

This is certainly hardware-related.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005232038, b6674000, 135}

Probably caused by : hardware

Code:

0: kd> !errrec fffffa8005232038
===============================================================================
Common Platform Error Record @ fffffa8005232038
-------------------------------------------------------------------------------
Record Id     : 01cdaf6cd58be4bb
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/21/2012 10:26:46
Flags         : 0x00000000

Please start by running Memtest86+ for a minimum of 7 passes, or until you get a memory error:
RAM - Test with Memtest86+

Also review the steps in this thread, and report specifically what you have tried.
Stop 0x124 - what it means and what to try

Regards,
Golden

Hi fraktal,

It was based on your dumps:

Code:

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


Loading Dump File [C:\Users\Tom\AppData\Local\Temp\Temp1_SF_21-10-2012-1.zip\SF_21-10-2012\101912-23859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0344a000 PsLoadedModuleList = 0xfffff800`03686e70
Debug session time: Fri Oct 19 16:22:58.606 2012 (UTC + 1:00)
System Uptime: 0 days 0:23:36.903
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005336038, b601a000, 135}

Probably caused by : AuthenticAMD

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

0: 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: fffffa8005336038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b601a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Dishonored.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8ac8 fffff800`03413903 : 00000000`00000124 00000000`00000000 fffffa80`05336038 00000000`b601a000 : nt!KeBugCheckEx
fffff800`00ba8ad0 fffff800`035cf923 : 00000000`00000001 fffffa80`05336ea0 00000000`00000000 fffffa80`05336ef0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8b10 fffff800`034135c8 : 00000000`00000728 fffffa80`05336ea0 fffff800`00ba8e70 00000000`111d9f00 : nt!WheaReportHwError+0x263
fffff800`00ba8b70 fffff800`03412f1a : fffffa80`05336ea0 fffff800`00ba8e70 fffffa80`05336ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8cc0 fffff800`03406e8f : 00000000`111d8f70 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8d00 fffff800`034b88ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff800`00ba8d30 fffff800`034b8753 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`00cdcf5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`13bff930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xcdcf5d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

Tom :)