Windows 10 Inside build 17017 constantly trying to repair

Hi Ron,

It seems that the issue is being caused by corrupted system files. We suggest running a diagnostic to help with the issue. After performing a diagnostic, we suggest performing the steps provided on this article. These troubleshooting steps should resolve the issue that you are experiencing.

If the given steps above didn't work, we suggest that you refer to this article and perform the steps on how to repair upgrade using the Windows 10 ISO file. This will help us resolve unusual behavior or conflicts that you are getting on your Windows system.

Let us know if this works for you.

Hi, I found one issue where more people had these problems relating to build 17017. It seemed with them, that it started without anything had changed.

With me, I got stuck in this repair loop which ended with always the error "page fault in nonpaged area" involving volsnap.sys with a blue and then a green screenbackground.

I upgraded my Asus Z170 Premium, Dell E6400 and HP 65550b all to build 17017 and all was fine until I noticed that on the laptops the system ssd, a Crucial MX300 500 gig, had a new client and firmware and I updated those.

A reboot gave no problems and all was fine.

I noticed that Crucial mementum cache was not enabled on the Dell E6400 so I enabled it, rebooted and all was fine.

tried the same on the HP 65550b and after the reboot I got trapped in this repair loop.

Attached the drive to my Dell E6400 using a eSata cable and as soon as I powered it up, a nasty sound was playing and the system gave a BSDO and after a restart it also got stuck in this same repair loop, giving the same error for volsnap.sys.

Atached the same drive to my Asus Z170 Premium and their the $%#%# samething happened.

Remembering my mainframe times with faulty IBM 3330 disk. I should have know better, but then again, I am getting old, lol.

Repairing using a USB Windows 10 iso image, did not do the trick, restoring a checkpoint neither!

The suggested solution, found in another issue, was;

Rename pagefile,sys, swapfile.sys and hiberfil.sys and copying an old volsnap.sys from windows.old\windows\system32\drivers.

As said with me it started as soon as I enabled the cache of the Crucial ssd, I informed Crucial in England and I hope that they or Microsoft know what happens to the drive when you enable the cache. Is the drive logic changed which triggers another machines OS to act in this way?

At the moment I am very relieved that all my machines are back up and running again, without any loss of data.

Regards

Ron

Thank you for the reply. We suggest contacting your device manufacturer for further assistance on performing a hardware diagnostic. This is for us to know if there's an issue or conflict on your hardware.

Let us know if you have other concern.

I did, but everything went fine when I used a Windows 7 x32 system! No BSOD or GSOD.

With x32 Windows 7 I could read the Crucial MX300 SSD partitions, use the Crucial tool to enable and disable the SSD cache and backup my private files.

Only all off my Windows 10 Insider build 17017 machines gave me the repair loop as soon as I attached or used the drive, so I am sure it is also a Windows 10 build 17017 problem, hence all the other issues I found regarding this repair loop problem/bug!

We would like to verify if you already tried performing the troubleshooting steps that I have provided on my previous response. Also, we want to know what troubleshooting steps you have done so far on your Windows 10 device.

We also suggest performing a clean boot the your Windows 10 to help with the issue. It will start your Windows by using a minimal set of startup programs and drivers. Clean boot will help us eliminate software conflicts that happen when you install, update, or run a program.

Get back to us and give us an update.

I have tried all the the diagnostics steps! And NOTHING worked. On my Asus Z170 premium, I could also restore to a previous checkpoint, but that did not work either.

The only thing that worked, was booting too a Command prompt (booted from a USB Windows10 iso)

Renamed  pagefile.sys, swapfile.sys and hiberfil.sys and copied c:\windows.old\windows\system32\drivers\volsnap.sys to  c:\windows\system32\drivers . That did the trick! Nothing else worked.

Based on the information that you've provided, it seems that you wont be able to repair your Windows and what you need is to reinstall it again. You need to deleted all the partitions and create a new one.Also, we suggest reporting your concern by submitting your issue using the Feedback Hub. You can either vote on an existing submission or submit a new issue. When you submit a feedback item we gather additional details and information about your issue that will help determine what’s causing it and address it. Feedback items regularly receive Microsoft responses on the submissions in the Feedback app so you can see what we are doing about your feedback. Please revisit frequently to see the status of your feedback items. 

Let us know if you have other concern.