Windows 7: Generic 0x124 stop BSOD ntoskrnl.exe

flabbyflamingo · 02 Sep 2012

I am helping a friend out. Me and him have done quite a few things to troubleshoot this error but now I am coming here for some additional help.

It seems ntoskrnl.exe is the main driver that comes up. from reading it seems this driver is very generic also.

We have Reinstalled windows
tried updating multiple drivers
tried switching keyboards

I came here because i dont know where else to look, or how to look.

I hope you guys can help. I have attached 2 dumps since it began. I've talked to him to use his pc to create more.

I am going to sleep and wont be awake for a while so ill respond when I wake up.

He is running a AM3 8 core cpu with 8 gigs ddr3 1333 ram. 1tb hard drive @ sata 2. AMD HD 6850. 750w psu.

**koolkat77** · 02 Sep 2012

Welcome to the forum.

Warning

I am new to debugging so please bear with me.

BSOD Analyze

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80084218f8, 0, 0}

Probably caused by : hardware

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

5: 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: fffffa80084218f8, 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:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0335b5b0 fffff800`02d1eca9 : fffffa80`084218d0 fffffa80`06a10040 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0335bad0 fffff800`02bff547 : fffffa80`084218d0 fffff800`02c792d8 fffffa80`06a10040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0335bb00 fffff800`02b66945 : fffff800`02cdaae0 00000000`00000001 fffffa80`07950820 fffffa80`06a10040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0335bb40 fffff800`02ae5841 : fffff880`01179e00 fffff800`02b66920 fffffa80`06a10000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0335bb70 fffff800`02d72e6a : 00000000`00000000 fffffa80`06a10040 00000000`00000080 fffffa80`069f5040 : nt!ExpWorkerThread+0x111
fffff880`0335bc00 fffff800`02accec6 : fffff880`03189180 fffffa80`06a10040 fffff880`031940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0335bc40 00000000`00000000 : fffff880`0335c000 fffff880`03356000 fffff880`042307b0 00000000`00000000 : nt!KxStartSystemThread+0x16


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_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

Both your dumps indicate hardware issues.

Go through:

Stop 0x124 - what it means and what to try

flabbyflamingo · 02 Sep 2012

Thanks, we have been trying stuff on that page thats why I finally decided to post.

**koolkat77** · 02 Sep 2012

Keep us posted.

flabbyflamingo · 03 Sep 2012

I need someone to see if they can pinpoint error a little closer, because we have tried a bunch of stuff

**koolkat77** · 03 Sep 2012

Upload the new dumps?

flabbyflamingo · 03 Sep 2012

I havent talked to him all day, ill try tomorrow.

flabbyflamingo · 04 Sep 2012

here are 5 more dumps from the days, hopefully someone can notice something.

thanks in advance

flabbyflamingo · 04 Sep 2012

Just preformed a bios update, will post updates.

**koolkat77** · 04 Sep 2012

BSOD Analyze

Still showing hardware as a problem

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800799b8f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner

Lets see how your computer performs with driver verifier on, its for ruling out buggy drivers. Follow instructions on the tutorial below:

Driver Verifier - Enable and Disable

Windows 7: Generic 0x124 stop BSOD ntoskrnl.exe

Generic 0x124 stop BSOD ntoskrnl.exe problems?