BSOD caused by ntoskrnl.exe

Xerophyte · 20 Dec 2013

I was running the Steam product Vindictus, which i have had no problems with in the past, when i recieved a BSOD. Checking the dump file, i saw the cause was ntoskrnl.exe. Over the next 4 hours, my computer restarted itself while i attempted to rectify the issue, with no BSOD. I have now updated every driver on my rig, and still receive the same restart, at various intervals when playing Vindictus.I have since ceased to play, and have ran a chkdisk, registry cleanup and full virus scan/virus update with no fix.

koolkat77 · 20 Dec 2013

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 - What it means and what to try

Code:

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


Loading Dump File [C:\Users\USER\Downloads\SF_18-12-2013\121813-48204-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03417000 PsLoadedModuleList = 0xfffff800`0365a6d0
Debug session time: Thu Dec 19 07:58:25.515 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:11.639
Loading Kernel Symbols
.....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800e66a038, 0, 0}

Probably caused by : AuthenticAMD

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

1: 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: fffffa800e66a038, 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`0335b5b0 fffff800`036d7ca9 : fffffa80`0e66a010 fffffa80`0c85b040 fffff8a0`0000000d 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0335bad0 fffff800`035b8ea7 : fffffa80`0e66a010 fffff800`036322d8 fffffa80`0c85b040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0335bb00 fffff800`03520275 : fffff800`03693b40 00000000`00000001 fffffa80`0e564e60 fffffa80`0c85b040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0335bb40 fffff800`03496261 : fffff880`010b6e00 fffff800`03520250 fffffa80`0c85b000 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0335bb70 fffff800`037292ea : 00000000`00000000 fffffa80`0c85b040 00000000`00000080 fffffa80`0c6e9990 : nt!ExpWorkerThread+0x111
fffff880`0335bc00 fffff800`0347d8e6 : fffff880`0316d180 fffffa80`0c85b040 fffff880`031780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0335bc40 00000000`00000000 : fffff880`0335c000 fffff880`03356000 fffff880`0432d7e0 00000000`00000000 : nt!KxStartSystemThread+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
---------