Solved Computer Freezes/Lockups With Restart BCC 0X124

[kevinbassist91]

I received the new HDD and installed it today. I cloned the old HDD and copied it to the new HDD which is now configured as my boot drive. I'm not sure if the HDD is the issue as I am getting the same results from the old HDD. Here are a few screenshots regarding the new HDD.

 

[centaur78]

Kevin

The only way to read the SMART for both the drives is if the SMART is enabled in BIOS.

Please check to confirm that its enabled.

However based on what we have done here with the BIOS, and info from the dump files ... the finger points to the motherboard.... but before we get to that..... Post the latest BSOD dumps

Also it would be good to test the CPU / motherboard with IntelBurnTest and Prime95 before making a final call.

 

[kevinbassist91]

SMART is enabled in the BIOS and I have run IntelBurnTest, here's a screenshot of the results based on the standard test at 5 runs. I'm running Prime95 right now for the next couple hours to see if that has any effect.

 

[kevinbassist91]

I ran Prime95 for almost 24 hours and there was no shutdowns or reboots during that process. I would assume with that the CPU isn't the issue then. I'm leaning more towards the motherboard but I'll wait for the PC to generate another dump file but there hasnt been in over a week now.

 

[kevinbassist91]

After waiting long enough I finally got a lock up and restart. Here is the dump file...

 

[centaur78]

were you doing something specific when it BSOD 'd ?


could you post the other files as well

 

[kevinbassist91]

You want the other dump files again? Or do you want me to use the sevenforums tool to grab everything?

 

[centaur78]

Well kevin

To summarize.... I am leaning more towards the motherboard... here is why ...

the dump files does point to

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800e9666b8, 0, 0}

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: fffffa800e9666b8, 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`03ba16f0 fffff800`03319ca9 : fffffa80`0e966690 fffffa80`0cb49040 00000000`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03ba1c10 fffff800`031fae87 : fffffa80`0e966690 fffff800`032742d8 fffffa80`0cb49040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03ba1c40 fffff800`03162285 : fffff800`032d5ae0 00000000`00000001 fffffa80`0e7b87e0 fffffa80`0cb49040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03ba1c80 fffff800`030d8251 : fffff880`018e1e00 fffff800`03162260 fffffa80`0cb49000 060e0f08`0f0f0810 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03ba1cb0 fffff800`0336cede : 00000000`00000000 fffffa80`0cb49040 00000000`00000080 fffffa80`0ca9ab30 : nt!ExpWorkerThread+0x111
fffff880`03ba1d40 fffff800`030bf906 : fffff880`03964180 fffffa80`0cb49040 fffff880`0396efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03ba1d80 00000000`00000000 : fffff880`03ba2000 fffff880`03b9c000 fffff880`0381b740 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
---------

0: kd> !errrec fffffa800e9666b8
===============================================================================
Common Platform Error Record @ fffffa800e9666b8
-------------------------------------------------------------------------------
Record Id     : 01ce91f0256f6904
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/5/2013 15:26:41 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e966738
Section       @ fffffa800e966810
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   : 0x0000000000100f43
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 43 0f 10 00 00 08 04 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  @ fffffa800e9668d0

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

[COLOR="Red"]Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  Status      : 0xfa00000000070f0f

Which basically means that the processor bus is the cause of the problem... which would usually be caused when you are Overclocking or with high temperatures... but i can't find any sign's of them either in the logs or the dump files.... Also we did the Prime 95 and IntelBurn test...

Combined with the fact that the BIOS date are weird and plus the fact that windows was reinstall on a new drive and with WD and crystal disk showing that the SMART values cannot be read for both the HDD ... even though you have them enabled in BIOS...

Hence the fault all point to the motherboard... have it RMA'ed to HP for replacement.

 

[kevinbassist91]

Hey,

Thanks for the information and to answer your previous question, it normally occurs when i resume use after its been sitting idle or when im simply browsing the internet. I do notice that the max temp for the CPU is 62C but even when I'm using the computer for simply browsing the CPU is operating at 42-43C. Also, I'm thinking of upgrading the Motherboard to a better one as I have purchased a new CPU case as well. So at this point I shouldn't continue to troubleshoot and just replace the Motherboard?

Thanks again.

 

[centaur78]

Well that would be the best way to go forward... since most of the components on your system has been upgraded...

However i would say you get the motherboard tested... or as a simple test... could you do a visual troubleshooting... look for bulged capacitors or any sign's of burnt component ??

 

[kevinbassist91]

I will take a look tomorrow at the motherboard to see if anything stands out. Also, is there anything else that could be causing this. You said it appears to be an issue with the CPU bus. Could it be the cpu at all that is causing this?

 

[centaur78]

Yes it is possible ... but we have done the IntelBurn test and prime95 .... if it does have errors it should show up on either one of them... (although these are not foolproof way to say that the CPU is good... but close enough.)

Thats why i asked you to get it tested by a professional computer shop before you go with a new motherboard or cpu...

 

[kevinbassist91]

I will have to look into finding a good computer shop as I`m not really aware of any reputable ones around here. I will post back with any results. Also, if the results show that it isn`t the motherboard, would it be safe to say that it is the CPU?

 

[kevinbassist91]

Hello once again, I finally got to switching the motherboard for a new one and BAM! the SMART readings and everything is now appearing in these programs that were not showing anything before. Here are some screenshots. Ill leave it a few days and mark it SOLVED if nothing comes up!

Kudos!

 

[centaur78]

Yes Kevin

That looks good to me ... It was the motherboard as i said before.