BSOD STOP: 0x00000124. Happens 2x a day, Normally Without Provocation

That's great news and a fantastic outcome for you. I guess that's why they call them Betas. They are not ready for release because they are unstable and/or have bugs. For that reason, I tend to stay away from Beta releases, most of the times. I am running the Windows 10 Preview now, though. Considering it is a pre Beta release, it seems to be pretty good. Not without a few problems, but very usable. It makes me anxious to see the final release. But, as a general rule, you are much better off staying away from Betas, as you found out the hard way, as most of us do. I am very happy to hear of your stable OS for a change. I'm sure not as happy as you though. As far as donations, to the best of my knowledge, this site does not accept them, although I am sure the offer is very much appreciated.

Please keep in touch and let us hear the final outcome. Please don't be a stranger. You would be amazed at what you can learn just by looking around here and reading threads and especially the tutorials. We probably have the most extensive collection of excellent tutorials you will find anywhere on the net. We also have some of the best collection of experts on every aspect of computing you will find anywhere. You just met one of them in Arc.

You're more than welcome and I hope your good fortune continues. Your kind and gracious words in your last post is what makes doing this worthwhile, to me and most of the others, I believe.

SavingHumanity said:

I wanted to thank everyone for their help and for being patient with me. An 0x0124 error oftentimes signifies a hardware failure, but it appears that it's not always the case.

Yes, and that is why it was said, it may be anything and everything included in the computer's environment.

Cheers. We learned a new thing, a great new thing from this thread. Previously we have found many a things contributing to stop 0x124; but it is the first time I noticed that a Chrome build is contributing to this BSOD.

Great job Steve

Thanks, but I think it was more Arc. But, thanks a lot.

The msinfo32.nfo file is missing there. upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Try uninstalling Chrome again. There may be something in chrome that is causing this.

Code:

BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
 
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff800`02ff0ac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

Just try using another browser for a while and see.

I doubt that Chrome is still there in auto start (so I asked for msinfo32, which is not included in the upload). As long as it is not removed, nothing more can be done.