Windows 10: Memory_Management BSOD on Clean boot, VERY specific circumstances

I think this is significant especially if has been done after an overnight shutdown and helps us to rule out hardware. The clean boot process is going to be your best troubleshooting tool, the difficulty is doing it when you know a BSOD is triggered.

Please review the process here: https://www.tenforums.com/tutorials/4...conflicts.html and if it still happens with all the startup items removed and all the non-Microsoft services disabled we know it is a Microsoft service that is causing the problem and we can start disabling those a few at a time. If it does not happen then you can start adding back services and then eventually the startup items until it does happen.

 

I followed the instructions, but had something slightly different this morning. Instead of a BSOD just as the login screen flashes up, my PC froze a few seconds afterwards. The Mouse moved but the keyboard wouldn't. I also could not click on any of the onscreen elements.

The following were in the system log:

Changing the software\services that startup seems to effect whether this problem is a freeze or a BSOD.

It's still only happening after a clean shutdown, and the PC being left off overnight (for more than a couple of hours).

 

Those error messages refer to Windows Defender which does kick in on any bootup but particularly after a long period of shutdown will always search for new virus definition files. This might be a clue as to what is happening. You could try running with Defender turned off to see if this makes a difference. If you are using another Antivirus like AVIRA make sure these are all removed too in case there are conflicts. If you are concerned about picking up a virus just run with no connection to the internet for a while.

 

I came to a similar conclusion, but I'm not certain if Defender caused the freeze, or if whatever else was causing the freeze caused an error in Defender.

Are these error messages likely a cause, or an effect?

 

It's difficult to be certain if it was a cause of the freeze - things happen so fast that a few milliseconds is all it needs for another process to be operating and be the real trigger of the freeze and of course it does not necessarily get logged.

Have you reached any boot condition that you can say is stable and reproducible?

 

I have a system restore from before I started this thread.

 

Latest dump file. Attachment 92632

I've changed the bios to specify 1.5v for the RAM, rather than automatic, and it had no effect. There are no errors or messages to suggest that RAM under-voltage is an issue.

I also changed the boot options in the Bios to Fastboot with minimal drivers\options. This caused it to freeze at the logon screen rather than to BSOD.

This suggests that the error happened at a different stage of the boot process, but that it still happened. Meaning that this is a software issue (Changing when services are loaded changes at what juncture the error happens because something is added\removed from the boot process).

A hardware error would be far more random and far less predictable.

PC still runs normally after a reboot, no errors even during high intensity activity such as gaming. PC was also rock solid stable during the recent hot weather, despite the temperature being at least 10 Celsius higher than normal during idle, and hotter during gaming.

 

I am not sure why you are running with both Windows Defender and Avira, did you try disabling WD? This was where we had got to two weeks ago. *Smile

 

I wasn't aware that I was running both.

Defender should be switched off, if it's not switched off then it's switched on in error.

 

One more:Attachment 92659

 

Windows Defender is definitely disabled. I downloaded a registry patch that was supposed to disable it from another post on this forum.

When I try to run it from the start menu I see a box that says "This application is turned off by Group Policy".

 

I queried it because of the errors in your post #31. The dump files show that it is not running but I wonder if it is still trying to update or verify itself via Task Scheduler and this is something that triggers from a cold start. It might be worth looking through Task Scheduler to see if the Windows Defender tasks are all turned off.

 

Your latest BSOD dump files confirm that the problem is caused by memory corruption which we already know. The difficulty is tracking down which software driver or process might be causing this.

 

Yes, I had a different message for each BSOD, so I figured that having both files together might help people to track it down.

Out of interest, what software are you using to read the dump file?

 

As this has been going on for a long time, I think that I may just buy a new SSD and do a fresh install using UEFI rather than Bios to cut out as much legacy stuff as possible.

Though I'm going to need to get some cash together as I'm planning on buying a larger SSD than my current one and maybe putting the current on in my media center.