BSOD Randomly Win7-64bit BCCode 124

[evans46f]

Hello,

I'm new here so I hope this post has everything needed. I've recently been having random BSOD in Win7. I havent changed anything in the past month or two. I did move recently, and I read that BCCode 124 could be a hardware issue. So its possible something was damaged in the move.

It happens at random times, internet browsing or playing a game. No real constant theme. I've uploaded the dump files etc.

Would appreciate any help.

Thank you!

 

[Arc]

Hello evans46f.

A stop 0x124 is a hardware error. And yours an old computer, so it is possible. Let us take some tests to determine the failing hardware.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Tell us about your PSU. Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe.

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.

Let us know the results.
________________________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800597d8f8, 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: fffffa800597d8f8, 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`031b66f0 fffff800`030c3ca9 : fffffa80`0597d8d0 fffffa80`0523fb50 00000000`00000011 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6c10 fffff800`02fa4e87 : fffffa80`0597d8d0 fffff800`0301e2d8 fffffa80`0523fb50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6c40 fffff800`02f0c285 : fffff800`0307fae0 00000000`00000202 fffff880`031b6ca8 00000000`00000018 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6c80 fffff800`02e82251 : fffff880`01144e00 fffff800`02f0c260 fffffa80`0523fb00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6cb0 fffff800`03116ede : 00000000`00000000 fffffa80`0523fb50 00000000`00000080 fffffa80`0520d740 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02e69906 : fffff880`02f64180 fffffa80`0523fb50 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b5f70 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
---------

 

[evans46f]

Thanks for your help.

My Ram passed the test. Did 7 full passes with it overnight. No problems.

It also handled the stress test well, though I stopped it after about 20 minutes when I noticed my temps start to creep up.

I think I'll start with replacing my heatsink. My cpu temps got up into the high 60's during the stress test. Case temp is definitely not a problem, it hovers at around 28-30 even at heavy load.

My power supply is an antec 600 watt. Kind of old, I've had it for about 6 years, but it should be enough power.

It very well could be the old board too, Its a crappy foxconn board that I've been using because it works. Maybe not anymore. I'll start with the Heatsink and then report back.

Thanks

 

[evans46f]

Well,

It wasn't the temp of the CPU. Its much cooler now and still no luck. Get 1 BSOD per day. It happens right after startup within the first ten minutes but then never again the rest of the time the computer is on. Under action center it generates a couple messages. I attached the dmp file. Still not sure whats up.... Could it be that some hardware component is just failing during the first few minutes before it warms up?

Source
Windows

Summary
Shut down unexpectedly

Date
‎6/‎30/‎2013 3:34 PM

Status
Report sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Extra information about the problem
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80059878F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Server information: a136613c-4dc7-42ca-be4c-067c2ce3d3e4

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa80059878f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\063013-13041-01.dmp. Report Id: 063013-13041-01.

 

[Arc]

I think you should go through http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696 .