Windows 10: BSOD every two hours... running out of options. Please help.

Hey support,I have been getting random crashes and restarts on my notebook. Initially, the BSOD showed "memory management" issues and I got the memory changed by Lenovo. The very same day, the PC started to crash with other messages "faulty hardware corrupted page" was one, but there's been more. Lately, the PC crashes when idle or close to idle and I am unable to write down the error, I get off my desk for a few minutes and the PC has restarted. Also, booting up takes a very long time it used to be almost instantaneous, now it runs for at least 45 seconds or more. I have checked drivers

:)

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

BSOD Help Needed.

Making it through 24 hours of Prime means you're most likely ok. I would do an hour of IntelBurnTest and a complete pass of MemTest x86 just to be on the safe side (Prime doesn't stress RAM as much as memtest). If you still have BSODs then you're most likely not chasing a hardware issue. At that point I would suggest looking into some Windows 7 forums and finding their BSOD-specific section and uploading your dump file for their gurus to look at. They could help you far more than I, I'm afraid. TPU may have such a board.

But hopefully you're in the clear. *Rockout :rockout:

 

BSOD at least twice a month - uncertain cause

I have run driver verifier with the below settings for >48 hours. There have been no BSOD. Please advise on next steps

• I/O verification
• Force pending I/O requests
• IRP logging