BSOD on Boot, no Dump Files, various different messages

axe0 said:

Yes it can, old components could certainly conflict with the drivers and cause problems with the hardware itself.

Comparing with previous installations isn't really fair and also not helpful, Windows 10 is different than Vista and 7 and 8/8.1, Windows 10 is still quite new while the others are years on the market and more stable.

What should I look for if it is a driver conflict?

axe0 said:

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

I ran it, rebooted, and then ran it again. Both times it said "Windows Resource Protection did not find any integrity violation"

I've uploaded the log files anyway, in case they are of any use.

Attachment 62684

It says "Primitive installers committed for repair" a lot, I'm not sure what that means in this context.

I've disabled the on board sound card, and the HDMI sound capabilities in my graphics card in software, just to see if it makes a difference.

I've disabled the on board sound card and graphics card in the bios to see if it makes a difference, and I've also disabled the HDMI sound output on my graphics card for the same reason. I've had to do the latter in software as there is no bios option for that.

At least I can rule out Avira, as it went BSOD even when it wasn't installed.

I've updated all of the motherboard software from the manufacturers website. Even the bits that seem unlikely to be the cause of this.

I've heard a few people saying that they had problems with Windows 10 because of some kind of fast booting system. Where Windows saves an image when it shuts down and then loads it again when it boots. Rather than booting in the old fashioned way. Like some kind of smart hibernate function. It only happens on Boot, rather than reboot. Which fits with the problem that I'm having. Through the people reported it happening much more frequently than my problem.

One person said that they had to make their SSD hot swappable to stop it form going BSOD, another said that they needed to install some kind of firmware update. Both said that the image was being corrupted by their SSD, which was why it went BSOD on them.

I only have anecdotal evidence rather than anything firm.

Does this sound likely?

Hi

I have this SSD

Sandisk 240GB SSD Plus SATA 6GB/s 2.5 Solid State Drive (SDSSDA-240G-G25) - dabs.com

The SanDisk dashbaord says that I'm on the latest firmware.

It looks like Fast startup is already turned off. I disabled both hibernate and sleep when I first went over to Windows 10. I did the same with Windows 7.

do you think that enabling Hot Swap will help, or is this a red herring?