Windows 10 BSOD Critical_process_died

Lobster1071 · 08 Sep 2015

Running a Dell Latitude E5500. Bought it with Windows 7 Pro, and upgraded it to Windows 10. It wasn't a clean install, but an upgrade. I normally like to do clean installs, but did the upgrade on purpose to get used to the whole Windows 10 update process.

Everything was running fine for 2 or 3 weeks, then all of a sudden, would get multiple, random BSOD crashes every day. It wouldn't matter what application I was in, and I wouldn't have to even be using it. I would just be reading something on the screen, not even touching anything, then the BSOD with the dreaded smiley face would appear.

I followed the BSOD instructions and uploaded the file needed to analyze the issue. I would appreciate any hints that anyone could give me. It appears it always crashes on ntoskrnl.exe, but that's about all I can see. I have nothing important on this computer, so a full wipe is fine with me, but would like to actually find the issue causing the crashes in the event that even after the wipe, the issue returns due to some driver update or program I am installing.

Thanks!

axe0 · 10 Sep 2015

Hi Lobster1071,

Welcome to the 10forums.

First, please check your manufacturer for driver updates.

Please try to boot into safe mode How to boot into safe mode

If the problem does not persist in safe mode, please try a clean boot

Please do the following:

Open taskmanager
- Go to the tab startup
- disable everything
Search msconfig and open it
- Go to the tab services
- Check 'hide microsoft services'
- Uncheck all other services
- Click apply and click ok
Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.

If the problem does persist in safe mode

Please do the following:

Open an admin command prompt
Copy/paste "sfc/scannow" (without quotes) and press enter
When it finished reboot your system
Open again an admin command prompt
Enter sfc/scannow again

If sfc/scannow doesn't say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Lobster1071 · 16 Sep 2015

Axe0, thanks for your reply. I believe it was a driver issue that was causing the problem. I went through each driver in the device manager and downloaded the appropriate one for Win10 from the Dell support site. I should have checked that once I upgraded to Win 10 from Win7. I've since had it on for extended periods with no more BSOD's.

Thanks again.

axe0 · 16 Sep 2015

You're welcome.
I'm glad your issue is solved :)