Welcome everyone, welcome forum :)
Some time ago I installed a fresh Windows and now the BSOD just happened.
I was listening to the music @Creative Media player and checking out internet @Chrome.
Hoping for help guys :)
The dump gave the cause as a 124 error, 0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components.
If overclocking, reset all overclocks back to their default settings and then follow these:
RAM - run for a minimum of 8 consecutive passes
RAM - Test with Memtest86+
CPU - run the HIGH test
CPU - Stress Test Using IntelBurnTest
Video - run the FURMARK test for 20mins
Graphics Card Problems - Diagnose
Video Card - Stress Test with Furmark
Storage - run the SHORT test using the DOS version
SeaTools for DOS and Windows - How to Use
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8004aad038, b6000000, 10015} Probably caused by : AuthenticAMD Followup: MachineOwner ---------
Thx for your reply.
Here are the screens of the tests:
RAM:
CPU:
FURMARK: (didn't see any artifacts)
SEATOOLS:
Anyone could help?
Btw, is it possible that after SeaTools that I run with my pendrive it changed a size? I had 32GB and now is 48MB -.-
Look at Stop 0x124 - what it means and what to try ... do the other steps those are not already done.
About the pendrive, format it ... it should be back to its capacity.
Thx for a link. It didn't help me though. I can't seem to find the problem. Are those screens above okay? No other BSOD since.
About the pendrive, I had to use Diskpart to make it useable.
All those tests are OK. I would suggest you to take another CPU stress test.
It saves the result as a .txt file in the prime95's folder. Upload the file for us.
Thank You for your reply.
The results are attached.
Also attaching new BSODS... had 3 in one day. Same story @Chrome and @Creative Media Player. Isn't that weird that those two programs were active every time the BSOD happened? I realize bug 124 = probably hardware problems but well...
It is seen a little few times too, that some chrome builds (specially teh beta builds) contribute to BSODs.
I would suggest you to not use Chrome for the time being. There are lots of other good browsers there. See if any other browser cause the same BSOD. Let us know.
Quote
