CRITICAL_PROCESS_DIED - Windows 8.1 x64

U

Ulysses

Member
Joined
Aug 17, 2014
Posts
16
Location
Vancouver BC
Hi:

This is my first post. I'm glad I came across this site in my attempt to find information about this BSOD. I experienced the CRITICAL_PROCESS_DIED BSOD yesterday and searched for explanations. I eventually ran sfc /scannow with the result, "Windows Resource Protection found corrupt files but was unable to fix some of them..." I ran it again in Safe Mode with the same result. I saved CBS.Log. I continued to use my computer after rebooting and didn't discover the intstructions for BSOD posts until some time later after I had run Ace Utilities Registry Cleaner and rebooted. So, while I have downloaded the two files and zipped the resulting folder, I don't know if it still contains the required data but I have attached it in any case.

I tried to run perfmon /report from an Administrator command prompt twice, but each time I but received the following ERROR: An error occured while attempting to generate the report. The operator or administrator has refused the request.
I believe I just uploaded a file BSOD CRITICAL_PROCESS_DIED.zip after clicking on the paperclip icon.

OS Windows 8.1
x64
Original Installation July 26, 2013
OEM OS
Hardware new July 26, 2013
Replaced hard drive months ago but recovered system from backup, so not new OS installation.
CPU intel i7-3770 3.40 GHz
Video Card nVidia GeForce GT 640

I don't know where to find mobo and power supply.

Dell XPS 8500

Hope the above is satisfactory.
 

Attachments

Hi,

There are no crash dumps located in your output folder. However, this bug check + SFC finding unrepairable corruptions tells me your OS is corrupt so much in it that your have critical process(es) unexpectedly dying. It may be in your best interest to perform what is known as a Refresh (or Reset if you want to start from scratch) - How to refresh, reset, or restore your PC - Windows Help

Regards,

Patrick
 
Patrick said:
Hi,

There are no crash dumps located in your output folder. However, this bug check + SFC finding unrepairable corruptions tells me your OS is corrupt so much in it that your have critical process(es) unexpectedly dying. It may be in your best interest to perform what is known as a Refresh (or Reset if you want to start from scratch) - How to refresh, reset, or restore your PC - Windows Help

Regards,

Patrick
Click to expand...

Thanks, Patrick.

After posting, I followed the recommendation on the BSOD page to run driver verifier. That did not turn out well. At the end, it produced a BSOD DRIVER_VERIFIER_DETECTED_VIOLATION, identifying driver 'pwipf6.sys'. However, after showing the message that it was collecting information and would restart, my computer was put into a loop. Each time, prior to completing the boot, the same BSOD kept appearing with the same message, shutting down and restarting in the same manner. I could not stop it. The only option left to me at that point was to boot from my Windows PE 5.0 disk and restore my computer to the last backup, which I made on Tuesday. That obviously was successful as evidenced by this response. However, I do not know if the corruption took place before or after the backup. I intend to run sfc again and will post the result.

Regards,
Allan
 
Interesting!

pwipf6.sys is the Webroot Desktop Firewall driver. It wouldn't surprise me by any means if that was actually causing a conflict and causing critical processes to die. I would uninstall it ASAP if the crashes do happen to continue.

Regards,

Patrick
 
Patrick said:
Interesting!

pwipf6.sys is the Webroot Desktop Firewall driver. It wouldn't surprise me by any means if that was actually causing a conflict and causing critical processes to die. I would uninstall it ASAP if the crashes do happen to continue.

Regards,

Patrick
Click to expand...

I don't have Webroot Desktop Firewall installed on my system. However, the file could be related to Privatefirewall 7.0 from privacyware that I do use as my software firewall. I ran an sfc scan with the same result, i.e. could not fix some corrupt files. I extracted the sfc [SR] entries from the CBS.log and have attached it. You will note "cannot repair" entries 0000085c and 0000085e and reference to 0000085f at the bottom.

Regards,
Allan
 

Attachments

Ah, yes. I would remove the firewall for troubleshooting purposes and see if the crashes stop. The SFC errors may not be related, although I will take a look if they do after the removal.

Regards,

Patrick
 
Patrick said:
Ah, yes. I would remove the firewall for troubleshooting purposes and see if the crashes stop. The SFC errors may not be related, although I will take a look if they do after the removal.

Regards,

Patrick
Click to expand...

I've only had the single CRITICAL_PROCESS_DIED crash. AFIAK, Privatefirewall hasn't caused any problems in the past and I've been using it for over a year on my Windows 8.1 system and long before that on my Windows XP system. So, barring another similar crash, I am reluctant to uninstall it. I have written to privacyware support, advising them of the DRIVER_VERIFIER_DETECTED_VIOLATION issue and will see what light they can shine it.

Any suggestions regarding the "Can't repair...member file [l:16{8}]"Logo.png" of Checkpoint-VpnPlugin-Appx..." entries?

Regards,
Allan
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top