Can Pssnap.sys File Be Replaced Or Repaired On Computer Not Running Windows 7

#1

Timescope

Members
13 posts
OFFLINE

Local time: 04:35 AM

Posted 25 June 2022 - 09:33 AM

Hi everyone,

I am kindly request for assist to solve a BSOD on my Fujitsu Siemens Lifebook model S7210.

The operating system is Windows seven Professional person OEM and I accept been using it since 2010.

The HDD that I have the trouble with is 500GB. I also have the 320GB HDD that I cloned to the 500GB bulldoze in 2022 and information technology works perfectly, ruling out hardware issues.

Last Monday, I updated Windows and got a BSOD on restart. caused past pssnap.sys :

PAGE_FAULT_IN _NON_PAGED_AREA.

Attached File BSOD 25.06.18.jpg 105.15KB 0 downloads

And then far, I have fabricated 16 attempts to repair the operating system using the Windows repair facility on the installation disk, have tried to repair the boot sector using bootrec and bcdedit, take run numerous chkdsk /f /r and have used the fix that Macrium provided "removesnap.exe" to no avail.

I ran removesnap.exe using the cmd prompt and got a message that:

MACRIUM\ControlSet001\Control\Class {4D36E967-E325-11CE-BFC1-08002BE10318} pssnap successfully removed equally an upper filter

Success

Attached File Recovery cmd.jpg 72.74KB 0 downloads

It did non work and so I disabled Windows Update and downloaded Macrium onto the 320GB bulldoze and created the WinPE recovery tool on a usb drive.

I ran removesnap using the WinPE environment: a cmd window flashed briefly but did non solve the trouble I likewise used the kicking repair office in the WinPE.

I could not get the SysnativeBSODCollectionApp.exe requested in the posting instructions to run: Using cmd, I got a "side by side" error and WinPE said "Cannot open file. No associated programme establish".

Attached File Recovery cmd.jpg 72.74KB 0 downloads

Attached File Copy of No program institute.png 851.37KB 0 downloads

Attached File Copy of Sysnative cmd fault.jpg 67.17KB 0 downloads

Arrangement restore says at that place are no restore points, Safe Mode too gives a BSOD, Last Known Skilful Configuration also does not piece of work and I tried to run sfc /scannow but got a message that "at that place is a pending repair that requires a reboot..."

I accept attached images of the various error screens and an epitome of the System Reserved sectionalization.

Attached File Copy of Reserved partitioning.png 810.15KB 0 downloads

Kindly excuse the poor quality of the images

Thanks in advance for your help.

Timescope

Edited past hamluis, 25 June 2022 - 12:02 PM.
Moved from Crashes/BSODs to Win 7 - Hamluis.

BC AdBot (Login to Remove)

BleepingComputer.com
Annals to remove ads

#two hamluis

hamluis

Moderator

Moderator
62,536 posts
OFFLINE

Gender: Male
Location: Killeen, TX
Local time: eleven:35 PM

Posted 25 June 2022 - 12:01 PM

That's a Macrium Reflect file. I would uninstall MR and so reinstall the about current free version.

Louis

Malware Forum

Making routine backup images of your partitions/drives...using 3d-party software...is probably the most of import activity that any user can engage in.

Dorsum to elevation

#3 Timescope

Timescope

Topic Starter

Members
xiii posts
OFFLINE

Local time: 04:35 AM

Posted 25 June 2022 - 12:29 PM

Hi Hamluis,

Thanks for the answer.

Sorry, I did non get in clear that the operating arrangement does not load and gives the BSOD right later the "Starting Windows" splash screen so I can non go to the desktop.

Is at that place a way to uninstall Macrium using cmd or the recovery surround?

Thanks,

Timescope

Back to acme

#4 JohnC_21

JohnC_21

Members
32,186 posts
OFFLINE

Gender: Male person
Local time: 12:35 AM

Posted 25 June 2022 - 12:52 PM

Using your WinPE disk rename the post-obit files. See if you can and so run sfc

C:\Windows\WinSxS\cleanup. xml

C:\Windows\WinSxS\ pending . xml .

You lot can pull the bulldoze, connect information technology to another computer and use AutoRuns on the offline drive to cheque for whatsoever Macrium Gratis startup process and pssnap.sys. Uncheck anything found.

https://world wide web.howtogeek.com/school/sysinternals-pro/lesson6/

Back to superlative

#5 Timescope

Timescope

Topic Starter

Members
13 posts
OFFLINE

Local time: 04:35 AM

Posted 25 June 2022 - 03:32 PM

Thanks JohnC_21, I will give it a attempt.

Timescope

Back to peak

#6 joseibarra

joseibarra

Members
two,460 posts
OFFLINE

Gender: Male person
Location: Downstairs
Local time: 12:35 AM

Posted 26 June 2022 - 06:53 AM

I still similar this idea of only renaming the offending file and so information technology will not load but can't exam it since I don't have the problem with my Macrium:

Of form you lot would have to be in a Command Prompt window or some kind of navigator/explorer to do that either from the Windows DVD/USB or maybe from the MacriumPE or a Hirens Boot CD.

Edited by joseibarra, 26 June 2022 - 07:57 AM.

The mediocre instructor tells. The good teacher explains. The superior teacher demonstrates.

Suggestions that begin with the word "try" are often wild goose chases. Try not. Do or practice non. At that place is no try.

Does a suggestion that says "it's worth a try" and "let usa know how it goes" instill confidence?

Reinstalling Windows should non count equally a "solution".

Back to acme

#7 aswiseman

aswiseman

Members
three posts
OFFLINE

Local time: 05:35 AM

Posted 30 June 2022 - 01:41 PM

I'm having the same problem as the original poster. (I've reported information technology here: https://www.bleepingcomputer.com/forums/t/679850/bsod-pssnapsys-page-fault-in-nonpaged-expanse-macrium-reflect/)

The Macrium gear up didn't work for me either.

I did effort the suggestion of renaming pssnap.sys to pssnap.old. What happens then is when yous reboot you still go the BSOD, but this time without the "pssnap.sys / PAGE_FAULT_IN _NON_PAGED_AREA" text.

I also tried running Autoruns equally an Ambassador to analyze the offline drive. I institute the handful of entries associated with Macrium, Reverberate and Paramount and unticked them all. But once again, all it did was remove the "pssnap.sys" details from the BSOD.