Windows 10 Constantly Crashing - Critical Process Died - Microsoft Driver Enumerator.?

[fishstix]

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

 

[johnbl]

to start you would have to put the memory dumps from c:\windows\minidump directories on to a server like microsoft onedrive so that they could be looked at with a debugger.

generally a problem with a bluetooth wireless enumerator will be a problem with the BIOS or the bluetooth driver version you have installed. (or a extension that was added)

The most likely fix will be to update the BIOS and update the drivers to the windows 10 version provided by the motherboard vendor. (if they have any) Often with a windows 7 driver, it will just be a bug in the power management in the machine and you can tell the system not to put your bluetooth device into a low power state using windows control panel device manager.

to actually debug the problem you would have to change the memory dump type to kernel rather than a minidump. Then provide the kernel memory dump to be looked at via a debugger. (file= c:\windows\memory.dmp)

the minidump can also be of help.

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