Your computer keeps crashing with the bugcheck error 0x00000139.
Your computer keeps crashing with the bugcheck error 0x00000139.
Hey, I own a solid PC that runs everything smoothly and quickly. But after the latest BIOS update—where my system froze mid-update and had to restart from scratch—I’m struggling to play even moderately demanding games regularly. It keeps crashing in various ways, sometimes showing a typical blue screen with error messages like "Lower or not equal." Recently it freezes for a few seconds before going completely black, including the mouse and keyboard. When I try to restart, I land back at the login screen as if I pressed the restart button.
I checked the Event Manager and found an error labeled "bugcheck 0x00000139." A memory diagnostic also flagged issues with my RAM, but swapping in another working set from my brother didn’t resolve the problem. Even after reinstalling the BIOS and Windows, the same issues persisted. I’ll share my specs below if you need them! Let me know if you want more details!
What RAM packages have you tested? If the problem lies with a particular memory controller, the standard XMP settings might be too restrictive. It could also stem from mismatches between your CPU, motherboard, and memory controller, requiring faster timings than what your RAM supports.
Including the exact times for each kit would be helpful. Timing can differ and often affects performance, especially if manufacturers use different packaging. The numbers are typically listed near the memory stick, showing A, B, C, D values.
The 18-22-22-42 configuration should work reliably; most issues arise with CL16 kits at 3600MHz, especially on AM4. Have you experimented with RAM musical chairs for your systems? This approach lets you evaluate every possible DIMM setup. Occasionally a memory controller rejects a particular DIMM, and swapping them can resolve the issue. It remains feasible even when testing different kits, though success is rare unless the alternatives are nearly identical. Running chkdsk, sfc, and DISM commands is also advisable to check for corruption that might affect performance.
I've tested the RAM sticks individually and they functioned fine. I tried a dual configuration, everything worked there too—except for three sticks, which is actually normal. The quad setup I have also works correctly. By "works" I mean it boots when issues occur in the same configuration I haven't tested, but the error messages from the RAM diagnostic always appear regardless of the setup. Regarding chkdsk, sfc, or DISM, I'm not familiar with them and don’t know how to use them. Thanks for your time!
These commands help detect and fix errors. 'Chkdsk' is a simple disk check, 'sfc /scannow' repairs system files, and 'DISM' addresses deeper issues. Running them in order—first chkdsk, then sfc /scannow, finally DISM—ensures problems are resolved. If Windows was recently reinstalled, these steps can identify corruption causing crashes, pointing to hardware faults like CPU, RAM, or boot disk errors.