BSOD after Upgrade - Unable to start WRE 22H2

Hi
Eventually I managed to end up with a BOD during start-up Windows 10. This worked by running an update and allowing for a functional upgrade at the same time.
Now, if I say 'unable to boot', I mean it! None of all protected-mode, WRE and boot-stick does work anymore. It is so bad, that if I plug the disk (SSD) to a running Windows-machine via USB, that system will blue-screen immediately too.

"Page fault in non-paged area, ntfs.sys" it says.

The only way to access the disk now is by using an Ubuntu-system. The tools on Ubuntu do not find any problem with the device. Partitions and files readable with no issues.

I wonder if anyone can suggest which file, area or partition etc. I need to alter or delete, so that I can re-install W10 and thus gain back my system with applications installed which I have been using for years now.

Thanks for help

The "page fault in nonpaged area" error can be caused by one or any combination of the following issues: Corrupt or damaged RAM. Faulty driver. Windows' inability to find files that are supposed to be in the nonpaged area.

...I read.

Try to pull out the RAM sticks and let only be one left. And then change the stick with another if it doesn't work.


https://www.freecodecamp.org/news/page-fault-in-nonpaged-area-how-to-fix-the-error-on-a-windows-10-pc/#:~:text=The%20"page%20fault%20in%20nonpaged,be%20in%20the%20nonpaged%20area


If checking your RAM fails to fix the error and you still see the BSOD (blue screen of death), start your computer in safe mode and proceed to the remaining fixes in this article.

To update your computer’s outdated drivers, right-click on Start and select “Device Manger”:

Perform an SFC Scan
In Windows, the system file checker (SFC) scan checks your computer for corrupt system files and restores them. So, it can help you get rid of the page fault in nonpaged area error.

Run the Windows Disk Checker Scan
CMD (adm)
In the command line, enter chkdsk C: /f /r and press ENTER.


It usually occurs after changing RAM or graphics cards, updating Windows or apps, or installing anything new. Keeping this in mind, the first step in troubleshooting is to undo your changes. Remove RAM, deactivate the app's service, delete it, or roll back to an older version.....if possible.

Thank you for the swift answer.
All of it does not help - I tried it all of course.

I'm lucky to own several identical lenovos an hence I know it is not the hardware.
The WRE-USB-stick boots fine as long as the SSD is un-pluged. As soon as I plug it in, I get the BOD, no matter if I boot the stick or the SSD.

I have not spent hours, but days trying to re-install. In the mean-time I'm working on a different Lenovo.
Pretty sure by deleting the partitions I would be able to install a new Windows. But herewith I wanted to give it a last try and see whether some guy here has one more ace up his sleeve.

And you don't have any backup available.....made with Macrium or Aomei?

Afraid no.

You have an identical Lenovo...

It could work with taking a back-up from your healthy Lenovo, with Macrium for instance.
Clean install Windows on the sick Lenovo and then put your backup from the healthy Lenovo to the sick one.

The files from disk you could use Ubuntu and save it to a usb.

After clean install you install the Macrium offcourse.
That Macrium will recognize the backup you got from the healthy Lenovo.

Maybe the last solution if nothing else works.

And if you also got docking facilities you could just try clone the disk from the healthy Lenovo to the sick one, probably the easiest way.

That sounds like a plan.
I shall start using Macrium right now then.

At which point should I re-add files from the sik disk so as to have the installed software back? And which files would I need (registry and so on)?

- - - Updated - - -

The point is, on the healthy one not all software is installed which I am using. And it takes time to install all of it one by one.
That is why I am still trying to fix that old system.

Have you tried to put the sick disk into the healthy Lenovo to see if it could boot there?