Windows 10: BSOD often on startup with differing errors

Hi again,

I've run the benchmark, health and error scan from HDTune now.
Attachment 49005Attachment 49007Attachment 49009
Attachment 49006Attachment 49008Attachment 49010

 

You have connected your hard drives with sata cables?
I would suggest you to try to reseat the cables and the hard drives properly if with sata.

 

I have now completely unplugged both my harddisks and replugged them. The sata cables connectors were slightly bent/twisted at the end where they connected to the motherboard, which might have been a problem.. but swapped them out with the backup cables I had. and I made sure to not cram the cables this time..

On another note..
The reason I started reseating the HDD's when I did was that I encountered another BSOD.. but this one was while I was streaming a Youtube video and nothing else.. and yesterday in fact I had another similar crash while streaming youtube, though there I had World of Warcraft running in the background.
Are these crashes part of the same problem you think? or something seperate? (I have the specific DMP files for these two crashes, and they don't mention NFTS. But didn't want to dump them here and fill this thread if It wern't related)

 

As the title says, different errors, so just upload them *Wink

It is hard to say if the crashes are related, a crash when streaming or watching something could be caused by many things where list below is most common

• audio driver
• video driver
• memory
• network driver
• etc.

 

Okay then I'll just upload the .DMP files for the crashes yesterday and today.

The crash yesterday (while wow was in the background) gave the Error WHEA_UNCORRECTABLE_ERROR
and the one today was MEMORY_MANAGEMENT

Attachment 49015

edit: this is with the twisted SATA cables btw *Smile

 

0x124(WHEA_UNCORRECTABLE_ERROR) usually points to the hardware.
A 0x1A(MEMORY_MANAGEMENT) usually points to memory problems. Thus with a 0x124 and 0x1A it looks like the memory.
Please keep in mind that both these 2 crashes could also be caused by drivers, but you likely would need to run driver verifier a long time to get the faulty driver.
Even though driver verifier is enabled, it does NOT mean drivers do actually have to be flagged. That is the case with the 2 dumps.

Let me know what the result is with the cables *Smile
If you still get a crash, I suggest you run MemTest86+ to test your memory





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

I have actually already enabled the driver verifier, but I just followed the recommended settings from another website (link to the site). What settings do you recommend I use?

Also I did already run memtest86 and it came back with zero errors after having run 9 passes and been on for over 24 hours, but that was before I made this post.
If it does crash again I'll boot it up again and let it run a test again.

 

MemTest86+ or memtest86?

 

I used memtest86+

I'll just leave the verifier on then and check the dmp files, if I get a crash.

Right now i've configured the verifier to only look at non microsoft drivers and only test for:
▪ Special Pool
▪ Force IRQL checking
▪ Pool Tracking
▪ Deadlock Detection
▪ Security Checks
▪ Miscellaneous Checks
▪ Power framework delay fuzzing
▪ DDI compliance checking

Is this a sufficient setup ?

 

Please follow this tutorial to run driver verifier.