BSOD Stop 0x00000050 PSSNap.sys

D

Docfxit

Contributor
Joined
Feb 22, 2015
Posts
248
I'm getting a BSOD 0x50 in Normal and safe mode.
I have tried Last known good configuration.
I have tried booting up to a Win7 32bit install/repair CD and running chkdsk /r /f twice. Both times it came up with no errors.
I have booted to a USB Win7 install and run Malwarebytes against the Hard Drive on the machine. I realize that doesn't fix anything the Registry of the Machine but it does find any files that are bad. It didn't find any bad files.
This is the BSOD I am getting:
1. PSSNap.sys.jpg
PSSNap.sys BSOD is a known problem with Macrium
They have come up with a fix for it called RemoveSnap.exe
They suggest booting into a bootable image from Macrium and running RemoveSnap.exe from PEExplorer.
When I tried that I get this:
2. PEExplorer.jpg
They suggest if that doesn't work to run RemoveSnap.exe from the cmd prompt
When I tried that I get this:
View attachment 39495
I tried running RemoveSnap.exe after booting from a Win7 32bit install / repair CD using the cmd line.
When I tried that I get this:
View attachment 39496
I renamed the file PSSNap.sys to PSSNap.orig
When I tried booting I get this:
5. BSOD7E -.jpg
I have tried changing the BIOS to IDE. I get the same screen.

I can't run sysnativebsodcollectionapp-exe
because I can't boot into the OS.

· OS - Windows 7
· x86 (32-bit)
· The original installed OS on system was Win7
· The OS is a full retail version
· Age of system (hardware) I don't know
· I have not re-installed the OS

· CPU ?
· Video Card ?
· MotherBoard - Lenovo
· Power Supply - Original
· System Manufacturer
· Exact model number ThinkCentre M90p
· Desktop

Please help me resolve this BSOD,

Thank you,

Docfxit
 

Attachments

  • 1. PSSNap.sys -.jpg
    1. PSSNap.sys -.jpg
    71.3 KB · Views: 10
  • 3. RemoveSnap -.jpg
    3. RemoveSnap -.jpg
    54 KB · Views: 9
axe0 said:
Hi Docfxit,

That sounds like you've downloaded a 64bits version when you need a 32bits version of the program.
You downloaded the removesnap file from Windows 7 32 bit - pagefault_in_non-paged_area pssnap.sys - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase
Click to expand...

Thanks for the reply...

I downloaded the version in your link. I received the same error. I believe it's a 32bit version of Win7. I tried finding a 64bit version of removesnap.exe just in case. I couldn't find it.

Thanks,

Docfxit
 
Do you have a backup prior the crashes?
 
As you may know, Macrium is a program which with you can make a backup of a system or partition. Right now I believe a backup from Macrium prior the crash is the best and safest solution in fixing this problem, whereafter Macrium needs to be removed and reinstalled.
This issue is a known issue that is fixed in version V7.1.2963 which was released in march 2018, currently the latest version is v7.1.3317 released in july 2018.

Reading the changelog of Macrium, they mention the updates of 13th March which are 2 updates.
https://support.microsoft.com/en-us/help/4088875/windows-7-update-kb4088875
https://support.microsoft.com/en-us/help/4088878/windows-7-update-kb4088878

Although I suggest to use a backup, you could also temporary uninstall those updates in the recovery console.

In recovery console run the following command
Code: 
dism /online /get-packages
which returns a list of installed updates, search for a Package Identity named like Package_for_KB4088875 and Package_for_KB4088878.
Copy the entire Package Identity and run the following command for 1 package identity at a time.
Code: 
dism /online /remove-package /PackageName:<package name>
Replace <package name> with the Package Identity.

Assuming the removal process was succesful, reboot the pc and see if you can login. If you can login, either update Macrium and reinstall the removed update or remove Macrium & reinstall it again and reinstall the removed update. You want to have the latest version of Macrium before installing the update.
If you cannot login, do the above again for the other update.

If you bump into a problem, please let me know.
 
axe0 said:
As you may know, Macrium is a program which with you can make a backup of a system or partition. Right now I believe a backup from Macrium prior the crash is the best and safest solution in fixing this problem, whereafter Macrium needs to be removed and reinstalled.
This issue is a known issue that is fixed in version V7.1.2963 which was released in march 2018, currently the latest version is v7.1.3317 released in july 2018.

Reading the changelog of Macrium, they mention the updates of 13th March which are 2 updates.
https://support.microsoft.com/en-us/help/4088875/windows-7-update-kb4088875
https://support.microsoft.com/en-us/help/4088878/windows-7-update-kb4088878

Although I suggest to use a backup, you could also temporary uninstall those updates in the recovery console.

In recovery console run the following command
Code: 
dism /online /get-packages

If you bump into a problem, please let me know.
Click to expand...

DISMError.jpg

When I tried it I got this error.

Any ideas?

Thanks,

Docfxit
 
Hi!

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.

2. Copy it to your USB drive.
3. Boot to recovery environment.
4. Launch CMD and launch FRST.exe from the USB.
5. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
6. Press Scan button.
7. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the USB)
6. Please attach the log back here.
 
That's my bad. Addition.txt is not produced in recovery mode.

Copy the attached fixlist.txt to your USB drive and go back to the CMD as you have previously.

Launch FRST.

Click Fix.

Wait for it to finish and try rebooting the system.
 

Attachments

I see the cause. Your system is missing a critical file:

C:\Windows\System32\codeintegrity\Bootcat.cache IS MISSING <==== ATTENTION

Let me prepare a fix and I'll be with you.
 
Okay:

1. Please extract the fix.zip file onto the root of your USB drive.
2. Verify that there is a file called Bootcat.cache present.
3. Delete the previous fixlist.txt from the usb and put the new one onto the root of your drive.
4. Please boot into recovery mode again and when at CMD, please open FRST and click the Fix button. Wait for it to finish.
5. Retry booting and provide Fixlog.txt in your next reply.
 

Attachments

I tried Safe Mode
I tried Safe Mode with Networking
I tried Save Mode with Command Prompt
I tried Last Known Good Configuration

They all give me Stop 0x0000007b

I tried setting the BIOS to SATA IDE from AHCI
After it gave me the same BSOD I set it back to AHCI

I tried running EasyRE. It didn't fix it.
I tried running the Win7 bootup CD Startup Repair 3 times.
I still get the BSOD 0x7b

Here is the Log:
I don't recognize M4-Service.exe
View attachment FRST.txt

Thank you for working on this,

Docfxit
 
M4-Service.exe is a service of Mikogo used to improve performance.
https://www.mikogo.com/downloads/mikogo-m4service.pdf

It appears your system is still missing the same critical file softwaremaniac mentioned earlier
C:\Windows\System32\codeintegrity\Bootcat.cache IS MISSING <==== ATTENTION
 
Launch FRST from the CMD again and enter Bootcat.cache into the Search Box.
Afterwards, please click Search Files.

A file called Search.txt will be created on your USB drive. Please attach it to your next reply.
 
I see Bootcat.cache isn't there.
I followed your instructions on post #13 to replace Bootcat.cache once again.
Fixlog.txt shows it copied it again:
View attachment 39720
I ran the search to make sure it was found correctly.
The search shows it is on the drive:
View attachment 39721
I re-booted to the Win7 Install disk and ran the search again.
It shows the Bootcat.cache is still there:
View attachment Search.txt
I tried letting it boot normal.
I received the BSOD.
I booted the Win7 install CD.
I ran the search to make sure it was still there.
It shows the Bootcat.cache is still there:
View attachment Search.txt
I ran another Scan with FRST.
It doesn't show that Bootcat.cache is missing
The forum won't let me upload the proof.
I ran another scan.
It doesn' t mention Bootcat.cache this time.
View attachment FRST.txt
I am still getting the BSOD.

I hope that helps.

Docfxit
 

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

Back
Top