BlueScreen 6.1.7601.2.1.0.256.1 playing Empire TW

[Flaviusx]

Hello, I seem to have a problem with my "ntoskrnl.exe+4b08dc", I get a bluescreen whilst playing Total war games. BlueScreenView brings up this:-

Caused By Address ntoskrnl.exe+4b08dc
File Version 6.1.7601.17727 (win7sp1_gdr.111118-2330)

"WhoCrashed" gives this as the source:-

crash dump file: C:\Windows\Minidump\031613-35147-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x4B08DC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800836F788, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe


Attached below is the crash dump. Anyone have any ideas on how to fix this? Thanks.

 

[koolkat77]

[B]*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008358038, 0, 0}

Probably caused by : AuthenticAMD

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: fffffa8008358038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0317d6f0 fffff800`03328cb9 : fffffa80`08358010 fffffa80`06a35040 00000000`00000008 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0317dc10 fffff800`03209687 : fffffa80`08358010 fffff800`032832b8 fffffa80`06a35040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0317dc40 fffff800`03170a35 : fffff800`032e4ac0 00000000`00000001 fffffa80`079b2820 fffffa80`06a35040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0317dc80 fffff800`030ed471 : fffff880`010efe00 fffff800`03170a10 fffffa80`06a35000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0317dcb0 fffff800`0337df7a : 00000000`00000000 fffffa80`06a35040 00000000`00000080 fffffa80`06a22040 : nt!ExpWorkerThread+0x111
fffff880`0317dd40 fffff800`030d49c6 : fffff880`03088180 fffffa80`06a35040 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0317dd80 00000000`00000000 : fffff880`0317e000 fffff880`03178000 fffff880`03b1d540 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

2: kd> !errrec fffffa8008358038
===============================================================================
Common Platform Error Record @ fffffa8008358038
-------------------------------------------------------------------------------
Record Id     : 01ce227701d722a6
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/16/2013 18:49:43 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80083580b8
Section       @ fffffa8008358190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100fa0
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008358100
Section       @ fffffa8008358250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : a0 0f 10 00 00 08 06 00 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8008358250

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008358148
Section       @ fffffa80083582d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f
[/B]

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 Troubleshooting Strategy

 

[Flaviusx]

Thanks for your response, I checked through that and I think my motherboard driver is out of date, I've downloaded a new updated driver for my motherboard but I can't find a way to install my new driver, how do you do that?

It you need to know this is the current detail of my motherboard and driver:-
Board: ASUSTeK Computer INC. M5A78L-M/USB3 Rev X.0x
Bus Clock: 200 megahertz
BIOS: American Megatrends Inc. 0211 04/28/2011

This is what I downloaded, which is what I think is the right thing it needs to update:-
http://www.asus.com/Motherboards/M5A78LMUSB3/#support_Support_CPU_Phenom%20IIX6%201090T%28HDT90ZFBK6DGR%29,3.2GHz,125W,rev.E0,SocketAM3,6-Core

But how do you get that to run?

 

[Arc]

It depends on the filetype (extension name) .
For every filetype, the different action is needed. What is for the file you downloaded?

 

[Flaviusx]

Okay, I've gone through a lot of stuff and I'm wondering, can overheating cause "Stop 0x124" errors? I'm thinking my graphics card might be overheating. It's a "NVIDIA GeForce GTX 560 [Display adapter]" with a "DELL E197FP [Monitor]", is there a way to test to check if this is definitely the problem and if so what to do about it?

 

[Arc]

Yes, overheating may cause a stop 0x124 for sure. Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

If it is hot, you need to get some additional cooling. Also clean the fan grills and air vents inside the computer so that it can blow the hot air outside.

But it is not easy to say that overheating is the only issue for a stop ox124 ....

 

[Flaviusx]

I've been using Speccy and CPUID hardware monitor thanks, I've seen my graphics card go up to 99 celsius/210 fahrenheit. As for how high it goes before it crashes, I'm not quite sure as I don't get a recording of it whilst it is crashing. It seems to be the graphics card in particular that gets very hot, other things don't get anywhere near as hot as it. The fan for it has been going up to 100% 4350 RPM, so that's what's leading me to think it is that.

 

[Arc]

Remove the graphics card. Use the onboard graphics. Observe if the stop 0x124 comes back in that situation or not.

99 degree C is not anything normal. It must to crash at that high temperature. Either the card is not properly placed, or the card is at its end.