Memory_Management BSOD on Clean boot, VERY specific circumstances

philc43 said:

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:

{Registry Hive Recovered} Registry hive (file): '\??\C:\Windows\AppCompat\Programs\Amcache.hve' was corrupted and it has been recovered. Some data might have been lost.

Faulting application name: mrt.exe, version: 5.37.12704.0, time stamp: 0x575783a5
Faulting module name: mpengine.dll, version: 1.1.12805.0, time stamp: 0x57475a8f
Exception code: 0xc0000005
Fault offset: 0x00000000000f6909
Faulting process ID: 0xea0
Faulting application start time: 0x01d1dc02ca466554
Faulting application path: C:\Windows\system32\mrt.exe
Faulting module path: C:\Windows\Temp\mpengine.dll
Report ID: 72ba3872-201a-4ded-8335-031833d07647
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: MsMpEng.exe, version: 4.9.10586.0, time stamp: 0x5632d908
Faulting module name: mpengine.dll, version: 1.1.12902.0, time stamp: 0x5769b915
Exception code: 0xc00000fd
Fault offset: 0x000000000008f2f1
Faulting process ID: 0x8ac
Faulting application start time: 0x01d1dc02c60259f1
Faulting application path: C:\Program Files\Windows Defender\MsMpEng.exe
Faulting module path: C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{8216EF64-66B2-4322-92B6-6B1A17041C55}\mpengine.dll
Report ID: 0c6ea4a4-9049-4e02-9759-b61107c8f964
Faulting package full name:
Faulting package-relative application ID:

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.

philc43 said:

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?

philc43 said:

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. :)

philc43 said:

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. :)

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

philc43 said:

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. :)

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".