Windows 10: BSOD on Boot, various memory related messages

Some events after that event you see something like below.
Code: Event[6335]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2016-01-30T22:31:26.000 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: MSI Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffd000230ad680, 0xffffd000230ad5d8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 013016-5390-01.[/quote] That dumps aren't always created, could means some of the following options

• hardware too much damaged
• configuration wrong
• system corruption
• counterfeit Windows

I have added all possibilities I can think of (real quick), it is possible that 1 or more are not relevant.
Most occuring is either wrong configuration or corruption.

 

I know that it's a genuine version of Windows, and I would hesitate to say that there was some form of corruption as it did exactly the same thing on an upgrade from Windows 7 on an old disc, and on a fresh install of Windows 10 on a brand new disc.

If it was damaged hardware, wouldn't I see issues more often, not just at boot?

 

Not always, it is unexplainable why though but it is rare.

I wouldn't as there are some updates that sometimes causes corruption.

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 know that I'm a little out of step, as I'm not able to reply as quickly as I'd like due to circumstances outside of my control.

I uninstalled Avira as requested, and it still did a BSOD in the same place. So, unless something was left on the system after the uninstall, it's probably not Avria that's causing it.

I've included the latest set of log files:

Attachment 62672

I will try to do the SFC today.

I have a legacy Sound card that wasn't part of the original build. It's pretty old (Windows Vista vintage from an older PC) but it was the cheapest way that I could put a Fibre optic audio in and out on the PC, could that be the cause of the problems? For example, an older driver conflicting, or it conflicting with the built in sound card?

I don't like going in to the case too often to unplug things, so I haven't taken it out yet.

It didn't give me any trouble under Vista, or Windows 7.

 

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?

 

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.

 

Driver updates, but with a legacy one you can expect no updates.

I'm not certain either what that means *Sad

Let me know how it goes *Smile

 

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?

 

That would be fast startup
Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

The question would be if yours supports hot swapping

That is sometimes suggested yes. Firmware is what I call 'drivers', it is a program that tells the SSD how to function.
If there are any updates available for your SSD, try to update it
[youtube]A7mQ9W3lk50[/youtube]

 

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?

 

I can't say, I don't have any experience with it and never suggested it as it wasn't ever necessary.
If you would like to know more about it I can ask someone to step by for this.