Windows 10: Random BSOD when logging in, at desktop. CRITICAL_PROCESS_DIED

Hi good afternoon all. I have some issues with my Sony Vaio Pro 13. It was shipped with Windows 8, which I upgraded to 8.1, then to Windows 10. This is when the BSODs started. The BSODs will occur during the windows login, or after the desktop has loaded. From time to time, I will encounter a BSOD while surfing the net or even reading PDF files. All the BSODs are of the CRITICAL_PROCESS_DIED type. I have also did a fresh installation of Windows 10 from the media disk downloaded from Microsoft, but this problem still persists. Kindly refer to the file attached below.

Your kind help is greatly appreciated.


Attachment 44520

:)

 

random Freezing leads to BSOD. I give up.

Stop code is random.

like CRITICAL_PROCESS_DIED, BAD_SYSTEM_CONFIG_INFO, DPC_WATCHDOG_VIOLATION..

I've got multiple BSOD and the stop code is that random.

right now after multiple debugging the issue, I hypothetically assume it's my nvme fault.

I've ordered a new nvme drive and gonna retest the system if this will works.

 

Random BSODs started last week

Logged in this morning and selected Settings to create a restore point: screen froze then BSOD Critical_Process_Died. Logged in again on 4th attempt (black screen on first three) and ran sfc/scannow: no integrity violations. McAfee Full Scan shows no
issued detected. Black Screen just occurred! Logged in again but everything taking ages to load (spinning disk). Opened Driver Verifier, which Detected Violation. BSOD. Opened in Safe Mode: DMP files are at: Link not found.
Rebooted: Attempting to Repair screen appeared and eventually I was able to login. Running very slowly. Windows Start button not responding. BSOD Critical_Process_Died. I shall keep trying: your suggestions would be appreciated.

Michael

Update: Windows update successfully installed and it appears that my laptop is now behaving. Strange thing is, my desktop is the same specification running the same programmes and it has been incident free.

 

Hi jaihaur2,



Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 4, please remove them as it may cause trouble.

There are no crashes recorded, this would make it a little more difficult to find out what is going wrong.
I'll try a few troubleshooting steps to determine if it is caused by software (including Windows) or hardware to begin with.
This would make it easier for future methods.

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:




Please try 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 does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, 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.

Please try 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 still persist, try booting in safe mode and see if the problem still persist

 

There are no crashes recorded, this would make it a little more difficult to find out what is going wrong.
I'll try a few troubleshooting steps to determine if it is caused by software (including Windows) or hardware to begin with.
This would make it easier for future methods.

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:




Please try 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 does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, 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.

Please try 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 still persist, try booting in safe mode and see if the problem still persist Hi thanks for helping. in the midst of using your method to troubleshoot. So far so good, got the "Windows Resource Protection did not find any integrity violation" message after the second SFC. My guess is that there might be some drivers or hardware issues. Will update if solved 100%.

Thanks so much for the tips, and very sorry for such a late reply.

 

No problem, take the time you need, there is no rush *Wink

If you have had any BSOD meanwhile, please run the DM Log Collector tool again and upload the new zip file.