BSODs (Screen freeze) Randomly.

Bert123 · 05 Mar 2013

Hello, I've had this problem for about a year or so. Can't really remember when it started but was about a year ago. My computer started to randomly freeze, at first it happend once a week, then a couple of times per week. Suddenly I had BSODs 10-30 times a day. I googled a lot to try to fix it never found a real solution. After a while it magically stopped crashing, no idea why really. Then a couple of months later it started the exact same way again. Going from not that often to several times a day. It has been like this on and off for about a year now. I've tried to completly wipe my harddrives and reinstall windows but it keeps coming back.

Now I have had enough of this and is seeking help on how to solve this.

During all this time I have never been able to find a real pattern of when it crashes. It happens when I play video games, watch tv, go afk, surf on the internet and so on.

During this 1 year I have tried all kinds of things, I've tried to unplug certain hardware to see if it stopped, I've ran tons of different tests but never managed to solve it.

I'm willing to do this all over again if you were to tell me to. So please help me on how to solve this, it's driving me insane.

koolkat77 · 05 Mar 2013

Welcome to Seven Forums

For a stop 124, please go through: Stop 0x124 - what it means and what to try

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

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007b3b688, 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: fffffa8007b3b688, 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`031a16f0 fffff800`032d6ca9 : fffffa80`07b3b660 fffffa80`06aaa040 fffff8a0`00000009 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a1c10 fffff800`031b7077 : fffffa80`07b3b660 fffff800`032312d8 fffffa80`06aaa040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a1c40 fffff800`0311e435 : fffff800`03292ae0 00000000`00000001 fffffa80`07991820 fffffa80`06aaa040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a1c80 fffff800`03093ca9 : fffff880`010b0e00 fffff800`0311e410 fffffa80`06aaa000 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a1cb0 fffff800`0332b34a : 00000000`00000000 fffffa80`06aaa040 00000000`00000080 fffffa80`06a25040 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`0307b946 : fffff880`02f64180 fffffa80`06aaa040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`03d06790 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 fffffa8007b3b688
===============================================================================
Common Platform Error Record @ fffffa8007b3b688
-------------------------------------------------------------------------------
Record Id     : 01ce1a151c9d47a5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/6/2013 2:48:46 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007b3b708
Section       @ fffffa8007b3b7e0
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   : 0x0000000000100f42
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 42 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  @ fffffa8007b3b8a0

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

Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xa2000010000b0c0f

Bert123 · 05 Mar 2013

So there's a problem with the hardware?

How do I test to see what part there's a problem with?

x BlueRobot · 06 Mar 2013

Firstly, are you overclocking any hardware? If so, which reset these values back to the their defaults within the BIOS.

What are your temperatures idle? Post a screenshot using:

Remember to unselect any additional programs which may be offered during the installation, these programs are usually bloatware and are not needed.

Bert123 · 06 Mar 2013

No I'm not overclocking anything, never have either.

Picture of CPUID:
http://gyazo.com/24b6472302e77b25fb4...png?1362618263

Took that picture right when I got back in windows after a crash.

Bert123 · 06 Mar 2013

Just got another crash, I had the window open when it crashed and they were 40-45 Celsius.

x BlueRobot · 07 Mar 2013

Update your System Specifications with Speccy, and then copy this information into your System Specifications: Go to your UserCP, and then select Edit System Spec in the left pane. Copy the information from Speccy into the required fields. These System Specifications will then follow your every post.

Then begin testing the CPU for any errors or faults:

Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

Bert123 · 07 Mar 2013

Updated my System Specifications, my computer crashed 20 seconds after I started stressing with Prime95.

Haven't been able to stay 2 minutes in windows since that crash before I get a new one.. Having a seriously hard time trying stressing for 1-2hours.

Bert123 · 07 Mar 2013

Just opend my window and it stopped crashing....

What are the maximum temprature the different parts should have before they crash the computer?

Bert123 · 07 Mar 2013

Since I opend my window I've been able to run the stresser for 15 minutes with no problems...