BSOD bootup OR watching YouTube videos, Bug Check Code 0x00000124

needhelp01 · 10 May 2015

Frequent BSOD which would either occur while Windows is booting or when using Chrome, particularly when watching YouTube videos. I have attached the output of the DM Log Collector as instructed in the BSOD - Posting Instructions.

What I've tried:
- I have run the Windows Memory Diagnostic Tool, no memory errors were found.

- I have run the Disk Check for any hard drive errors, from what I remember, no issues were found.

- I have tried removing one of the 2x2GB memory sticks to see if one of the sticks were malfunctioning.
Then boot windows twice and had about 7 tabs with YouTube videos playing after each boot. Then I switched the sticks, retried the same test...the BSOD did not occur in either case.

Any help would be much appreciated. Please let me know if you need any more information from me. Thanks!

SGT Oddball · 12 May 2015

Please try any tests bellow that you have not already done.

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, 8860d024, b2000040, 800}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------