BSOD - even in safe mode - CRITICAL_PROCESS_DIED ... 0x000000EF

dtolman · 11 Sep 2017

Just happened again with virtual clone drive uninstalled. No dump created.
Should I turn off driver verifier? Its the only thing I've changed since minidumps/dumps stopped getting created (besides running the log gatherer tool).

zbook · 11 Sep 2017

Whenever you have a bsod please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

Sometimes when there is no new mini dump there is useful information in the logs: event.vwr, msinfo32, dxdiag, etc.

dtolman · 11 Sep 2017

Sorry - here is the newest zip
Attachment 152870

zbook · 11 Sep 2017

Please update the system specs:

How To Fill Out Your System Specs
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Please include PSU, cooler, case, peripherals (mouse, keyboard, joystick) and anything attached by wireless or wired (printer, headset, xbox etc.)
Please include all drives HD, SSD, internal, external, etc.

There were unexpected shutdowns.

Windows failed fast startup.
Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

Code:

Event[13742]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-09-11T18:42:08.327  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DanielEig-PC  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[13731]:  Log Name: System  Source: EventLog  Date: 2017-09-11T18:42:14.700  Event ID: 6008  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DanielEig-PC  Description: The previous system shutdown at 6:39:37 PM on ?9/?11/?2017 was unexpected.

Code:

Event[2085]:  Log Name: System  Source: Disk  Date: 2017-07-31T08:04:16.580  Event ID: 7  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DanielEig-PC  Description: The device, \Device\Harddisk3\DR13, has a bad block.

Code:

Event[2233]:  Log Name: System  Source: Disk  Date: 2017-08-02T08:00:39.959  Event ID: 7  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DanielEig-PC  Description: The device, \Device\Harddisk3\DR17, has a bad block.

Code:

Event[2713]:  Log Name: System  Source: Disk  Date: 2017-08-07T07:28:02.969  Event ID: 7  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DanielEig-PC  Description: The device, \Device\Harddisk2\DR7, has a bad block.

dtolman · 11 Sep 2017

zbook said:

Please update the system specs:
Please include PSU, cooler, case, peripherals (mouse, keyboard, joystick) and anything attached by wireless or wired (printer, headset, xbox etc.)
Please include all drives HD, SSD, internal, external, etc.
----
Windows failed fast startup.
Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

I've updated my profile with all my notes on what is attached to the machine, etc.

Turning off Fast Startup also, and I'll reboot (full shut down, power down, startup - no restart).

dtolman · 11 Sep 2017

Nope - crashed after a few minutes sitting idle with Fast Startup off (post power cycle). It must be some system level maintenance process triggering it - I mean its just sitting there with nothing running.

Attachment 152881

zbook · 11 Sep 2017

There was no new bsod.
There were unexpected shutdowns.

Which Texas Instruments products do you use?

Download and install:
Blue screen of death (STOP error) information in dump files.
http://www.resplendence.com/whocrashed

Code:

Event[14004]:  Log Name: System  Source: EventLog  Date: 2017-09-11T22:26:08.655  Event ID: 6008  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DanielEig-PC  Description: The previous system shutdown at 9:36:59 PM on ?9/?11/?2017 was unexpected.

Code:

Event[14008]:  Log Name: System  Source: Microsoft-Windows-Kernel-XDV  Date: 2017-09-11T22:25:59.950  Event ID: 1  Task: N/A  Level: Information  Opcode: Start  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DanielEig-PC  Description: XDV driver loaded!

Code:

Event[14015]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-09-11T22:26:02.234  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DanielEig-PC  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[14043]:  Log Name: System  Source: Server  Date: 2017-09-11T22:26:11.503  Event ID: 2511  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DanielEig-PC  Description: The server service was unable to recreate the share My Apps because the directory D:\BlueStack\BlueStacks\UserData\Library\My Apps no longer exists.  Please run "net share My Apps /delete" to delete the share, or recreate the directory D:\BlueStack\BlueStacks\UserData\Library\My Apps.

Code:

Event[14044]:  Log Name: System  Source: Microsoft-Windows-Time-Service  Date: 2017-09-11T22:26:11.387  Event ID: 158  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DanielEig-PC  Description: The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well.

BSODHunter · 12 Sep 2017

1) The BSODs itself which point to a specific direction. But fixing seems to be very time consumption because of the different solutions for it and we dont know whta you excatly done with your system. You know you system better, you now your hard and software configuration and what u have done to it.

2) BSODs and eventlog show errors which point to harddisks, controller, controller drivers, controller (software) configuration, virtual drive configuration, SSD firmware problem maybe, windows file system errors (maybe messing/bad windows updates too) also hardware side like SATA cables, SATA ports, harddisk controller (hardware side), storage controller firmware (not BIOS firmware) etc...u should check that one by one.

3) Your BIOS is old, its the first version and extremely outdated. Update it from here since therey where MANY fixes over the years: MAXIMUS VII GENE BIOS & FIRMWARE| Motherboards | ASUS Global
Yours dated:

Code:

BIOS_VERSION:  0401 BIOS_DATE:  04/23/2014

4) Another strange thing is ALL disk and drive informations are missing in the dxdiag.txt log. Thats not normal and I never saw that before.

5) I found a problem with the NVIDIA driver too. Its blamed in the MEMORY.DMP and I also see three errors in windows eventlog, that show that the GPU driver crashed:

Code:

MEMORY.DMP 
0x000000EF:    CRITICAL_PROCESS_DIED (9.09.2017 05:14:39) [Windows 10] 
 
CAUSED BY:     ntdll.dll     
               nvlddmkm.sys [22.08.2017] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx  
 
PROCESS:       svchost.exe

eventlog:

Code:

2017-07-13 16:22:55  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
2017-08-14 03:28:49  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
2017-09-01 09:16:36  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.

6) Theres also software installed which is known for causing bluescreens (GPU overclocking, turbo modes and special profiles)
- EVGA Precision
- ASUS AI Suite III

dtolman · 12 Sep 2017

zbook said:

There was no new bsod.
There were unexpected shutdowns.

Hi zbook - each of those shutdowns was preceded by a bluescreen - with the same "CRITICAL PROCESS DIED" message. For whatever reason it did not produce any minidump or dump file.

The only changes I've made since they stopped being produced was activating the driver verifier - I'm shutting that off and seeing if that makes a difference.

---

I'm not aware of any TI products in my system - but then again I'm not entirely sure of my PSU or Memory vendors - I'd have to take them out and look. Why do you ask?

dtolman · 12 Sep 2017

BSODHunter said:

1) The BSODs itself which point to a specific direction. But fixing seems to be very time consumption because of the different solutions for it and we dont know whta you excatly done with your system. You know you system better, you now your hard and software configuration and what u have done to it.

2) BSODs and eventlog show errors which point to harddisks, controller, controller drivers, controller (software) configuration, virtual drive configuration, SSD firmware problem maybe, windows file system errors (maybe messing/bad windows updates too) also hardware side like SATA cables, SATA ports, harddisk controller (hardware side), storage controller firmware (not BIOS firmware) etc...u should check that one by one.

3) Your BIOS is old, its the first version and extremely outdated. Update it from here since therey where MANY fixes over the years: MAXIMUS VII GENE BIOS & FIRMWARE| Motherboards | ASUS Global
Yours dated:

Code:

BIOS_VERSION:  0401 BIOS_DATE:  04/23/2014

4) Another strange thing is ALL disk and drive informations are missing in the dxdiag.txt log. Thats not normal and I never saw that before.

5) I found a problem with the NVIDIA driver too. Its blamed in the MEMORY.DMP and I also see three errors in windows eventlog, that show that the GPU driver crashed:

Code:

MEMORY.DMP 
0x000000EF:    CRITICAL_PROCESS_DIED (9.09.2017 05:14:39) [Windows 10] 
CAUSED BY:     ntdll.dll     
               nvlddmkm.sys [22.08.2017] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx  
PROCESS:       svchost.exe

eventlog:

Code:

2017-07-13 16:22:55  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
2017-08-14 03:28:49  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
2017-09-01 09:16:36  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.

6) Theres also software installed which is known for causing bluescreens (GPU overclocking, turbo modes and special profiles)
- EVGA Precision
- ASUS AI Suite III

Thanks for the tips. I updated my video drivers two weeks or so ago as part of troubleshooting - I'll try rolling that back in case that is responsible for making things worse, not better.

I'll also update the system bios

For #2 - if it is a disk issue I'm not sure what to do first. Should I get a new boot drive, attach it to the system, reinstall the OS and see if that clears things up?