Computer Bluescreens once a day

[morgangord]

Sorry for only having one dmp file. i had to do a system restore.

But basically my computer Bluescreens once a day, restarts and is fine for the rest of the day.

 

[Hacb]

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  [COLOR="Red"]AuthenticAMD[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner

it seems to be a processor issue, try running Prime 95 as per this tutorial to stress test your hardware
http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

if your pc overheats while running this, try getting a new fan, then run the test again, if the same thing happens, get a new processor.

P.S if you do need a new processor, try for the same type you already had, it will save you the trouble of worrying about compatibility with the rest of your hardware.

 

[morgangord]

okay, ill be back in 2 hours thanks.

 

[morgangord]

Hey, it's been around 2 hours. they have all passed. what does this mean now?

 

[morgangord]

update. still no fails

 

[Hacb]

right, the processor may have been a red herring, I'll stew on it for a while, have another look at the dumps and get back tomorrow.

 

[morgangord]

ok, thanks a bunch mate.

 

[morgangord]

I think i should tell you that i did this test after the computer bluescreened. i usually never have problems for the rest of the day after the 1 bluescreen daily.

 

[axe0]

Just a FYI, the problem is more complicated then the CPU.
A component (hardware, driver) is not responding to a request for sending data, so there is too much time out between data 1 and data 2 in a bus. This could be caused by many things, but a 0x124 usually doesn't reveal more then this kind of information what makes it difficult to debug a 0x124.
The processor is mentioned in the dumps, because the processor is the component that executes the data that the other components give. However this does not mean the processor is the cause, the processor is the one that is reporting the problem.
Unfortunately, because there is only 1 dump file this information from the dump is not really enough for conclusive results.

Please check {windows partition}\windows\minidump and check if there are more dump files saved.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial

3: kd> !errrec fffffa800837b8f8
===============================================================================
Common Platform Error Record @ fffffa800837b8f8
-------------------------------------------------------------------------------
Record Id     : 01d111df35ca2b27
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/29/2015 0:17:47 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800837b978
Section       @ fffffa800837ba50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR="red"]Error Type    : BUS error
Operation     : Generic[/COLOR]
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f12
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 12 0f 60 00 00 08 06 00 - 0b 22 98 1e 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  @ fffffa800837bb10

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

[COLOR="Red"]Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000fbffc1e0
  Misc.       : 0xc00a0fff01000000

 

[morgangord]

Hey axe, unfortunately i reinstalled windows which is why i only have 1 new dmp file. however if you want, i can go into my windows.old folder and grab the 7 dmps in there. they're about a week old though, if that matters. thanks

 

[axe0]

If you reinstalled Windows, then there should be only 1 bugcheck error from BSOD's in the event logs, but there are quite some.

 

[morgangord]

Yeah, i reinstalled windows last week. but yesterday, i had to do a system restore to the 25th of October. i had a lot more dmp files before i restored yesterday

 

[axe0]

Please create your recovery media if you have no recovery media.

Please test your hardware as the 0x124 is usually caused by the hardware.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

If you're overclocking your system, revert back to stock clocks now.

   Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: MemTest86+ RAM Diagnostic
Part Two: Hard Drive Diagnostics
Part Three: GPU Stress Test

ONE

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

TWO

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools - HDD test - Windows 7 Help Forums

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Chkdsk - HDD Test - Windows 7 Help Forums

THREE

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

 

[morgangord]

ok, i'll get back to you tomorrow when its done. thanks mate

 

[axe0]

Shall we keep it in this thread instead of PM'ing, would make the progress clearer

 

[morgangord]

Okay, my bad.

but yeah.

Got to 5000 frames(96 degrees) and it stopped responding on furmark

and all the seagate tests passed

ill have to do the memtest tomorrow(hopefully)

 

[axe0]

Please run Furmark again, but stop the test when 85C is reaching. That is generally the temperature that could damage some GPU's due to overheating if the temperature is holding for a long period and with not a proper cooling system.

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU and cooling system.
How to fill in your system specs:

 

[morgangord]

Hey, i've updated my system specs.

What happened just now is. I turned my computer off for 1 hour or two. and turned it on just now, ran furmark, it got to 1500 frames and my computer bluescreened.

the computer restarted and i ran furmark again, and had no problems i got to 3000 frames at 85 degrees and my computer is still on working perfectly fine.

this is always seems to be the case. The computer bluescreens after the first time i turn it on after its been off for a while and then it's fine until I shut it down for a long period of time again.

i've ran the dm log collector again with the new minidump and attached it to this reply.

 

[axe0]

I think i should tell you that i did this test after the computer bluescreened. i usually never have problems for the rest of the day after the 1 bluescreen daily.

That would point to a driver issue, fortunately there aren't that many drivers, but mostly from Windows.

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

 

[morgangord]

okay, ill do this when i wake up tomorrow before i goto my class and get back to you. thanks