Random BSOD x124/Crashes

[axe0]

You have tested the hardware components, but also checked for driver updates?
The error 0x124 is often caused by hardware damage, overclocking or driver problems.

The cause is a read error with the level 1 cache from the CPU.
Please make sure you are not overclocking anything, if you do, revert back to stock and test the system

3: kd> !errrec ffffe0015d74d028
===============================================================================
Common Platform Error Record @ ffffe0015d74d028
-------------------------------------------------------------------------------
Record Id     : 01d0fe9eb29469a5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/4/2015 12:27:36 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR="red"]Error Type    : Cache error[/COLOR]
[COLOR="red"]Operation     : Data Read[/COLOR]
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100fa0
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : a0 0f 10 00 00 08 06 04 - 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  @ ffffe0015d74d240

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

[COLOR="Red"]Error         : DCACHEL1_DRD_ERR (Proc 3 Bank 0)[/COLOR]
  Status      : 0xb63b200048000135
  Address     : 0x0000000035551700
  Misc.       : 0x0000000000000000

 

[DarkCowMoo]

No overclocking at all.
We ruled out driver problems.
I might try to underclock the CPU to lower values than the default and see if anything changes.
It's weird though as the crashed aren't related to stress, I've just stressed the computer with Prime95 for an hour and everything was stable. There are times where the computer just reboots when surfing the web or minesweeper.

 

[axe0]

Just to be sure, please check AMD for CPU driver updates

 

[DarkCowMoo]

Well CPU drivers are not something I'm familiar since 10 years ago, couldn't find anything in the link you gave except gpu drivers.

 

[axe0]

No overclocking at all.
We ruled out driver problems.
I might try to underclock the CPU to lower values than the default and see if anything changes.
It's weird though as the crashed aren't related to stress, I've just stressed the computer with Prime95 for an hour and everything was stable. There are times where the computer just reboots when surfing the web or minesweeper.

Try it for a couple of hours, an hour might not be enough.

 

[DarkCowMoo]

Well 4 hours and it's still stable as a rock.
When the computer is stable, it won't crush for the whole duration of time when I'm working/playing on it, but if I restart/computer goes to sleep, chances are things won't be as solid as before.

 

[axe0]

Have you checked for any dirt/dust in the case?

 

[DarkCowMoo]

there is some dust, do you think it might cause so much trouble?

 

[axe0]

there is some dust, do you think it might cause so much trouble?

Dust can cause so much trouble, you can't imagine.
It is adviced to clean the components once in a while, like once in a month.

 

[DarkCowMoo]

there is some dust, do you think it might cause so much trouble?

Dust can cause so much trouble, you can't imagine.
It is adviced to clean the components once in a while, like once in a month.

Well I cleaned everything from top to bottom, computer was very stable for a while. Now just got a random reboot while playing Starwars : Battlefront and listening to an online radio. Nothing too special.

From Event Viewer, nothing else;
""The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.""

 

[axe0]

Please check if the PSU is properly connected, it could be getting a little loose when you're cleaning the pc.

 

[DarkCowMoo]

Well everything is fine as much as I can see, it was solid for a week or so.

 

[axe0]

Please save the event logs of the applications and Windows and upload them.
How far back you need to go is something you need to guess by your self.

 

[DarkCowMoo]

Well this is everything I have, the problem really is that it's not very informative.

 

[axe0]

My guess is that the event logs are from the system?
Please upload the event logs from the applications.

 

[DarkCowMoo]

And this is the one from all the apps.
I tried to look for anything suspicious around the restart time, didn't find anything useful.

 

[axe0]

Please do the 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.

 

[DarkCowMoo]

https://drive.google.com/file/d/0B-2M8yLmFnG3OEpkUk80NEY0VTQ/view?usp=sharing

this is the CBS file, nothing found in the sfc /scannow.
There is another bluescreen attached that I received today.

 

[axe0]

As this is a Windows 10 OS, please create a new thread at the sister forum tenforums.com BSOD section