BSOD After every startup. Works fine until the next day.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff88000d0e6d6, 0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.

...I'll leave it to the others, as this is too general for me to determine the cause

@all
anythoughts?

No BSOD today, strangely. But here's the intelburntest and furmark. I have not ran the prime95 test yet.

jefflevay0 said:

I turned off the public folder sharing.

What?

Yes actually I have a few new ones Ill .zip up. I'm starting to really consider it being my power supply causing the issue. For the first time during this string of bsods I had one while my windows was still starting up( where the windows loading happens)

Don't forget to run Prime95 as well for a few hours.

Most of your crashdumps show bit flips in the CPU registers, as well as data corruption for some images in memory. If the disk checks don't show up anything, then I fear this is a Trio of Trouble issue, aka CPU/Mobo/PSU. There is no proper testing procedure outside of swapping hardware or using multimeter to test the PSU to reliably determine which of these three is the culprit. It's just a matter of crossing fingers and swapping one of them out and hoping it fixes things.

I'll get back to guys once I've ran the tests. Thank you for your help guys.