Blue Screen BCCode 124

I finally got a WHEA error on Windows 7, right after I made the last post.

After that I booted up Win 8.1.1. I've been on Win 8 since (and several reboots) and no WHEA errors. There are none listed in the Windows logs, except the one that I had before all of this started on Win 7.

The only thing that has been done is memory "reseat" since I had removed the GSkill and installed the Corsair then removed the Corsair and reinstalled the GSkill.

There is a different SSD drive for Win 8, an OCZ Vertex 4 with latest firmware (Win 7 has an Intel with latest firmware). About the only software difference is I don't have Google Earth installed on the Win 8 system. All my recording studio software, including the iLok are identical. I have the same Office 2003 installed. Obviously all the Metro apps for Win 8, that are not in Win 7.

Did you ever run the check disk? Do the WHEA errors still point to L0 cache?

I haven't run ckdsk but I've run the Intel SSD Toolbox Full Diagnostic and no errors.

Here is the only one I got today, on Win 7 (none on Win 8).

If it was a memory and/or CPU problem, the errors would occur on both W7 and W8. Since it's occurring only on Windows 7, I suspect it's a disk problem. I would get a second opinion on the Tool Box results and run chkdsk.

Added: If you didn't have to reboot for the Tool Box run, I doubt it's much of a test on the OS partition.

Ckdsk was run (at boot up) and no errors were found.

Well, I'm tapped out. I've researched this all over the net but few hits on Windows 7 with Intel processors. A common theme though seems to be pointing to a failing memory module, Slot or memory controller (CPU). What Steve mentioned earlier about adjusting the memory voltage could be worth try. I'm still puzzled over the fact that W8 has no problem and this same error was addressed in Vista with a patch.

Here's a list of possible causes so far:

- Poor voltage regulation (i.e. power supply problem, voltage regulator malfunction, capacitor degradation)
- Damage due to power spikes
- Static damage to the motherboard
- Incorrect processor voltage setting in the BIOS (too low or too high)
- Overclocking
- Permanent motherboard or power supply damage caused by prior overclocking
- Excessive temperature caused by insufficient airflow (possibly caused by fan failure or blockage of air inlet/outlet)
- Improper BIOS initialization (the BIOS configuring the motherboard or CPU incorrectly)
- Installation of a processor that is too much for your motherboard to handle (excessive power requirement, incompatibility)
- Defective hardware that may be drawing excessive power or otherwise disrupting proper voltage regulation

The hardware can be mostly eliminated. The only hardware device that could be suspect is the Intel SSD, and it passes all tests. All the other hardware is used on Win 8.

The system is on a "pure sine wave" type UPS. It has liquid cooling and rarely goes into the low 40's. Nothing is overclocked, except memory and that is to its rated speed. The error occurred before clocking it to full speed so I don't think that is an issue.

However, other than a "hit" in the Event Viewer it does not seem to be causing any problems.

I've done some more testing this morning. Win 8 is still error free.

Win 7 is now down to (so far) only getting the WHEA error at boot up. It doesn't matter if the Memory profile is disabled, Profile 1 or Profile 2.

Safe mode with and without networking does not get the error.

I've tried some CPU intensive applications and that does not cause the WHEA error.

I ran the Intel SSD full diagnostic scan, and no errors.

Nothing left, that I know of, to try.

I ran the Intel SSD Optimizer and full diagnostic. No errors since. I've rebooted about a dozen times, some just restarts some power off/reboots. No more WHEA errors.

This would account for no errors on Win 8 as a separate SSD is used for Win 8.

I've tried everything else, including ckdsk but that didn't make any difference.



I'm not going to mark this solved right now.

Thanks/Jack

Safe mode with and without networking does not get the error.

Did you run it long enough to rely on that statement? If so, that leans toward a driver/software cause.