Windows 10 Constantly Crashing - Critical Process Died

[blank]

I'm having this weird issue where I keep getting BSOD for Critical_Process_Died, and its almost making me want to stop using windows 10 and go back to 7.

 

I think it has something to do with the Microsoft Driver Enumerator. Most of the time a HAS STOPPED WORKING window will pop up a micro second before the blue screen saying Microsoft Driver Enumerator has stopped working.

 

I'm not sure what this is, or why its all of a sudden causing these issues.  windows 10 used to be fine.

 

Windows 10 ran fine for months, then last month or sometime this started, and once it starts it constantly happens, I'm lucky if i can even scan my pc before it BSOD again.

i've ran sfc /scannow and it came up fine

 

i thought it was a driver issue, due to using driver booster installing weird drivers. So i reformatted reinstalled windows 10, only installed drivers the OEM posted for my hardware, and all was fine for a week until tonight.

 

I ran a memory test i case it was a ram issue, and all is fine.

 

I can't seem to find any info online about this, or even about the process that keeps crashing.

this guy is having the same problem as well, and Microsoft doesnt seem to be able to help
http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/microft-driver-enumerator-has-stopped-working/43e41105-8353-4ac9-91bb-c18e0f50ef3d

 

On Mon 1/18/2016 6:42:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011816-5750-01.dmp
uptime: 00:11:03
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xEF (0xFFFFE000D24F7840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Mon 1/18/2016 6:42:01 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:11:03
This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)
Bugcheck code: 0xEF (0xFFFFE000D24F7840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED

 

On Mon 1/18/2016 6:30:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011816-5718-01.dmp
uptime: 00:11:27
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xEF (0xFFFFE0007B975840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

This will constantly happen over and over.
I really don't want to go back to windows 7, but i can't keep dealingwith this.

How can i discover whats causing the issue?
Nothing has changed on my system since yesterday and today.

thanks

 

 

 

Edited January 18, 2016 by blank

[binaryzero]

"Nothing has changed on my system since yesterday and today"

 

Ok...what's changed, because obviously what you've done is causing your machine to fall over. 

 

 

[Eric Veteran]

Did you analyze the dump files to see what specifically is failing? They'll have more information in them than the log does.

[A Real American!]

see this thread and 2nd reply:

http://www.sevenforums.com/bsod-help-support/26960-ntkrnlmp-exe-related-bsod.html

[blank]

This guy over here has been helping me

http://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/constant-bsod-after-being-on-windows-10-for-a/b29a5a3b-d681-43cf-b44c-0905b2ad8eba?tm=1453118152073&auth=1

 

turns out my Mobo was way out of date,  I thought it was updated, but i was using a version from like 2013 or something.

or it could be another issue.

 

we'll see how this goes

 

[blank]

7 hours ago, Jared- said:

"Nothing has changed on my system since yesterday and today"

 

Ok...what's changed, because obviously what you've done is causing your machine to fall over. 

 

 

thats the thing. Nothing changes, it just starts happening after a few days.

 

I used windows 10 from august til december when this issue started happening, so its the weirdest thing. Obviously i'd know if i did something new that triggered it.

thats what makes it confusing.

 

For example, for the past few days it was working good. Came home, turned on PC, started copying picture from iphone to PC and it started to happen, and once it starts it doesnt stop. But im sure this guy over at the microsoft forums will help me figure it out, if it starts again (recent reformatted and clean installed windows 10 again). Last time it started i was tryin to copy data to a USB drive. which made me think it was kinda USB related.

 

[blank]

If anyone comes to this topic with the same issue, i think i have resolved it.

 

Turns out that this Microsoft Driver Enumerator file is not legit, and is a trojan, virus, or something that no modern anti malware, anti virus seems to be able to detect. 

it installs to the system32 folder and is called msde.exe

 

The confusing thing for me was that it didn't start to cause any negative symptoms, or any at all for a week or longer after being created, which Is why i couldn't think of what i did or installed that'd cause it.

 

I had my suspicions on this file since i couldn't find a single thing about "Microsoft Driver Enumerator" online, other than a few people who were having the same issue. Then upon a clean install i noticed that file wasn't in the system32 folder, in which i then monitored the directory and installed my normal applications til i discovered which one was installing the file.

 

Not sure if you can delete the file and then be okay, i just did a clean install. so far 2-3 weeks have passed since this install of windows and all is good.

 

so if anyone is coming here because of "Microsoft Driver Enumerator ", know that its not a legit file.

 

btw, microsoft support is horrible.