I replaced the power supply a few years ago, so it probably just leaves the mobo. Thanks

No errors.
41406

Thanks, yep not overclocking. No errors so far, I'll run it through tomorrow my time.

Update: @3 hours in my sound stopped working. When I right click speakers and click test, this screen pops up.
41290

Thanks, running it now. Note that the voltage dropped when I started the test, but I do not know that the amount is significant. I'll run it up to 24 hours if I need to.
41257

Well it happened again. I always seem to get two in a row, and then nothing for a while. So no other options besides buying a new PC?

I just reset bios to optimized default. The only two noticeable changes were that my cores were re-locked (Now I only have access to 4 instead of 6), and now Turbo CPU is turned off. I guess now I...

I ran it for 30 minutes.
Min temp: 29
Max temp: 76

Okay.
40940

I did not run SeaTools as I am running a SSD.

ChkDsk produced no errors.
40521

Finally I used the Display Driver Uninstaller to remove the Nvidia drivers, and reinstalled using the latest...

I used compressed air to clean the dust out of the PC , all motherboard ports on the rear, and the ram slots. I used rubbing alcohol to gently wipe the contacts of both ram sticks using rubber...

Done, now I just have to remove the memory modules and clean them.

**Something new. When I turn the PC, it just flashes a whiteish screen. I can move a squished looking mouse, but i have to reset...

Will do thanks.
A little weird with this, running but disabled..
40053

Special...memory_corruption
Note I haven't tried cleaning the ram yet, but the error is more specific.
39790

I took a cotton swab, dabbed it in rubbing alcohol, and rubbed the contacts on the ram.

Is there a good way to do that? I did it wrong with my last PC and fried the ram sticks using rubbing alcohol. Thanks for staying with my issue BTW, means a lot!:)

I ran Memtest for 37 hours, ram checker for 8 hours, and driver verifier for 48 hours without any errors.
3928139282

No violations.

Memory_management crash
38505

Done, now we wait.

*sigh* Another crash, kernel_error strikes back.
37779

I had edited the picture as you were posting, so here it is again.
37720

This good news?
37719

37577
37578

I executed the code, got this message, restarted, and same message when I re-ran it. I zipped the file to fit.

No log report screen this time.
37430