Windows 10 Inside build 17017 constantly trying to repair

I upgraded one of my laptops a HP Probook 65550b to Insider x64 build 17017 and noticed within Crucial Storage Executive of my Crucial MX300 system drive, that a new client and firmware where available. Installed both, restarted and all was fine.
Next I noticed that the Momentum cache was not enabled. Because of a battery present, I decided to enable it.

Did and I had to reboot. At reboot Windows 10 noticed an error and tried to repair, well, this repair when on and on, each time rebooting and trying to repair, over and over again. After 12 times I stopped and removed the drive and attached it as a 3th disk through eSata to my Dell E6400, but as soon as I switched it on, a blue screen and noise from the internal speaker and dumping and reboot plus repairing. Removed drive asap and my E6400 restarted correctly.

Next tried my Asus Z170 Premium desktop also on build 17017 and attached the drive through an usb/ide/sata adapter, same thing, blue screen, noise from internal speaker and windows dumping and trying to repair. This time it also got into a loop trying to repair. Used an usb windows 10 stick, to repair install and went back to the latest checkpoint and restored, but Windows 10 keeps trying to repair after the next reboot.

Used a backup disk with x32 Windows 7 in my E6400 laptop and I was able to connect to the Crucial ssd and I could read the disk content.

Installed x32 Crucial Storage Executive and saw that Momentum cache was not enabled, so I enabled it again and of course a reboot.

All went fine.
The HP 65550b is now upgrading to Windows 10 17017, using the old Hard disk backup, before I switched to a SSD. When that is finished, I hope I will be able to start up from the SSD, assuming system drive driver got replaced by one that supported cachin, while it appeared cache was not enabled because of a failing reboot?

If not then I am still stuck with two machines that are in a loop trying to repair.

What can I do to get Windows 10 to do a startup in safe mode?

I can boot from usb and use an OS to delete a file or maybe even edit a file, can I do anything without reinstalling two machines completely?

Thanks

Ron

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.

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

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

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

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.

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

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!

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

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.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

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.

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

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. 

For more information on Feedback Hub, see our support article and YouTube video

. 

In order to submit new feedback, please follow these steps:  

1. On a Windows 10 device, search for “Feedback Hub” in Cortana search, then launch the app  

2. Navigate to Feedback in the left menu, then press + Add new feedback  

3. Select the Problem, and share any details you think are relevant, and choose an appropriate category and subcategory  

4. Important: If possible, reproduce the problem(s) after clicking Begin monitoring (or Start capture) near the end of the form; Stop monitoring when you’re done  

5. Once you’ve completed the form and monitoring, click Submit  

6. Click Continue using Feedback Hub  

7. Click My feedback at the top, then find the item you submitted (it may take a while to appear)  

8. Open the item you submitted, then click Share  

9. Click Copy link, then paste the link here in your response (it will look like https://aka.ms/<unique link>)

Let us know if you have other concern.

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I geuss reading my English can be a problem sometimes, but I though I clearly explained, that my initial problem was resolved.
I just included the picture to show the original error in blue AND green screen background.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

 
 

Question Info


Last updated September 24, 2020 Views 1,666 Applies to: