BSODs (Screen freeze) Randomly.

[Bert123]

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]

Welcome to Seven Forums

For a stop 124, please go through: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

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

*******************************************************************************
*                                                                             *
*                        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]

So there's a problem with the hardware?

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

 

[x BlueRobot]

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:

• CPUID - System & hardware benchmark, monitoring, reporting
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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

 

[Bert123]

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

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

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

 

[Bert123]

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

 

[x BlueRobot]

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:

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

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

 

[Bert123]

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]

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

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

 

[Bert123]

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

 

[Bert123]

I closed my windows after about 20min, now I have ran it for a total of 1 hour 30 minutes.

The highest temperature so far is:
CPU: 58c
GPU: 50c
Motherboard: 54c

 

[x BlueRobot]

You need to run the test continuously for 2 hours, you can use CoreTemp, which will give you a TJMax for your CPU too, I would stop the test at about 80*C if your TJMax is within the 100*C+ area, otherwise stop the test 20*C before the listed TJMax value.

:info: Unselect/Uninstall any bloatware which may come bundled with the installation wizard.

Upload the Prime95 results so far, it should be listed under the file location whereby, you saved the Prime95 program. Look for a file named results.txt.

 

[Bert123]

I've reached 1hour 50 minutes or so now.

Results.txt

[Thu Mar 07 16:39:09 2013]
Self-test 20K passed!
Self-test 20K passed!
Self-test 20K passed!
Self-test 20K passed!
[Thu Mar 07 16:54:15 2013]
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
[Thu Mar 07 17:09:30 2013]
Self-test 28K passed!
Self-test 28K passed!
Self-test 28K passed!
Self-test 28K passed!
[Thu Mar 07 17:24:45 2013]
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
Self-test 12K passed!
[Thu Mar 07 17:40:45 2013]
Self-test 24K passed!
Self-test 24K passed!
Self-test 24K passed!
Self-test 24K passed!
[Thu Mar 07 17:56:27 2013]
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
[Thu Mar 07 18:11:38 2013]
Self-test 32K passed!
Self-test 32K passed!
Self-test 32K passed!
Self-test 32K passed!
[Thu Mar 07 18:27:14 2013]
Self-test 16K passed!
Self-test 16K passed!
Self-test 16K passed!
Self-test 16K passed!

 

[x BlueRobot]

Leave it for another 10 minutes, and seems to be no problems with CPU.

 

[Bert123]

It's done, got these results now aswell.

[Thu Mar 07 18:43:05 2013]
Self-test 20K passed!
Self-test 20K passed!
Self-test 20K passed!
Self-test 20K passed!
[Thu Mar 07 18:58:25 2013]
Self-test 8K passed!

What should I do next?

 

[x BlueRobot]

The first parameter or argument has the value of 0x0, which is a Machine Check Exception, which means the CPU has detected a hardware problem.

In such a situation, it is best to use these steps:

• 
  http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

 

[Bert123]

Ok, been gone for a while but now I'm back...

I tested the RAM and got no errors what so ever.

 

[x BlueRobot]

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r