Im on my other computer right now, the windows machine cant get to the desktop. after an update of the insider build it gives me the GSOD says the insider ran into a problem and need to restart. page fault in nonpage area. problem with volsnap.sys

My update is that the solution from hanselman.com worked for me. I copied in a volsnap.sys from another machine using a USB drive, my PC finally booted and I was able to upgrade to 17025 and it seems to be working fine. Thanks for everyone's help

Hi IanI was where you are up until yesterday. I think you have to follow the instructions to replace the 17017 version of volsnap.sys with an older one. Since, like me, you can't get out of the reboot loop, you'll have to boot from a DVD or USB drive. Then find another version and replace it. As I said, this worked for me. If you don't have the resources, you'll have to get help. This situation shows why you only use Insider builds on a spare machine and not your main one. Good luck,Kerry

I see the same thing on 17025, it starts with 'Preparing Automatic Repair' and goes to the GSOD. Same message as Matt. Interestigly it seems to alternate between a GSOD and a GSOD. I'm on a Dell OptiPlex 990. F8 during boot doesn't get me to the Recovery options page.

Hello Kerry, F8 for Windows 10 has been deprecated (though there are instructions on the net - it is easier to get to w/ new instructions). To get to the new boot menu hold this shift button when clicking on the power icon and 'restart'. Keep the shift key held down and before long you'll see a spankin new menu for you. You can do this at the log in or post log in. As far as the issue - I get the exact same thing. Person who replied punted and said it was a graphics driver issue. Here is my reply in response - I hope this helps:Hello, Gowrisha, My current driver for Nvidia is up to date: version 388.00 at this writing which is as up to date as you can get for a 960. Graphic driver updates are no longer the dominant issue for Windows since the decision to include them within their update scheme. Your tech article's example is slightly different from mine (see attached). As I wrote earlier, this is, per the green screen, likely because of volsnap.sys. I believe this file has more to do with software/hardware connection with the USB or storage. I also have no other pending updates except for build 17025. The temporary fix for now for insiders if seeing this issue and their graphic driver is up to date as mine is:1) As SOON as you get your regular windows wallpaper back up post boot try to hit Windows + X(You are working on the clock here and need to get this done before the next update and the inevitable crash happens - so do this quickly!) 2) Select Windows PowerShell Admin 3) You'll unnervingly have to wait for an 'okay' for the shell to run. As soon as it comes up let the OS know that PowerShell Admin is indeed, 'okay.' 4) Run this command ASAP from the PowerShell Admin:net stop wuauservThis should stop the errant update service. 5) Quickly go to Settings / Update and Security. If it was in between initializing and downloading you may have to repeat step 4 because it'll just rerun wuauserv. If you have a button that says Retry, DON'T press it - the OS has temporarily given up on installing updates (this is a good thing for us). Feel free to use your machine for an unlimited time until you have to reboot and restart this entire process again. These steps aren't the best, but at least you can use your computer for longer than 10 minutes at a time. Obviously it is a good idea to every once in a while try the update so you get the best working OS and security, but an OS isn't considered working properly if it is resetting within 10 minutes. Hopefully Microsoft will be taking this situation seriously and working with insiders such as myself and others as to the cause to prevent this issue from reaching the common update ring. Thank you, Rob Milliken

Green Screen after Builder update. volsnap.sys

Deborah Rempala
Copper Contributor
Nov 01, 2017
Same issue. Contacted support. Told me to boot from a USB. I hope it works
- Kerry Ogata
  Copper Contributor
  Nov 01, 2017
  My update is that the solution from hanselman.com worked for me. I copied in a volsnap.sys from another machine using a USB drive, my PC finally booted and I was able to upgrade to 17025 and it seems to be working fine.
  
  Thanks for everyone's help
darren o neill
Copper Contributor
Oct 30, 2017
If you have desktop:I found a temporary fix to the problem if you have a usb to sata adapter put you hard drive sata cable into it then power on your desktop and then plug the usb to your laptop(if you have a laptop)and a window should show up on the laptop it should say scan and if when a window shows up don't change any setting and leave it run when it's finished plug out the sata and turn off your computer/desktop the put the sata cable it in your desktop and turn on your desktop and that's it. Hope it helps.
Kerry Ogata
Copper Contributor
Oct 27, 2017
I see the same thing on 17025, it starts with 'Preparing Automatic Repair' and goes to the GSOD. Same message as Matt. Interestigly it seems to alternate between a GSOD and a GSOD. I'm on a Dell OptiPlex 990. F8 during boot doesn't get me to the Recovery options page.
- Rob Milliken
  Copper Contributor
  Oct 28, 2017
  Hello Kerry,
  
  F8 for Windows 10 has been deprecated (though there are instructions on the net - it is easier to get to w/ new instructions). To get to the new boot menu hold this shift button when clicking on the power icon and 'restart'. Keep the shift key held down and before long you'll see a spankin new menu for you. You can do this at the log in or post log in.
  
  As far as the issue - I get the exact same thing. Person who replied punted and said it was a graphics driver issue. Here is my reply in response - I hope this helps:
  
  Hello,
  
  Gowrisha,
  
  My current driver for Nvidia is up to date: version 388.00 at this writing which is as up to date as you can get for a 960. Graphic driver updates are no longer the dominant issue for Windows since the decision to include them within their update scheme. Your tech article's example is slightly different from mine (see attached). As I wrote earlier, this is, per the green screen, likely because of volsnap.sys. I believe this file has more to do with software/hardware connection with the USB or storage. I also have no other pending updates except for build 17025.
  
  The temporary fix for now for insiders if seeing this issue and their graphic driver is up to date as mine is:
  
  1) As SOON as you get your regular windows wallpaper back up post boot try to hit Windows + X
  (You are working on the clock here and need to get this done before the next update and the inevitable crash happens - so do this quickly!)
  
  2) Select Windows PowerShell Admin
  
  3) You'll unnervingly have to wait for an 'okay' for the shell to run. As soon as it comes up let the OS know that PowerShell Admin is indeed, 'okay.'
  
  4) Run this command ASAP from the PowerShell Admin:
  net stop wuauserv
  This should stop the errant update service.
  
  5) Quickly go to Settings / Update and Security. If it was in between initializing and downloading you may have to repeat step 4 because it'll just rerun wuauserv. If you have a button that says Retry, DON'T press it - the OS has temporarily given up on installing updates (this is a good thing for us). Feel free to use your machine for an unlimited time until you have to reboot and restart this entire process again.
  
  These steps aren't the best, but at least you can use your computer for longer than 10 minutes at a time. Obviously it is a good idea to every once in a while try the update so you get the best working OS and security, but an OS isn't considered working properly if it is resetting within 10 minutes.
  
  Hopefully Microsoft will be taking this situation seriously and working with insiders such as myself and others as to the cause to prevent this issue from reaching the common update ring.
  
  Thank you,
  
  Rob Milliken
  - Ian Calvert
    Copper Contributor
    Oct 30, 2017
    When I tried this, it just keeps saying access denied - any clues?
    
    This has kept crashing on me since Thursday when it updated automatically and I can't use my laptop which is causing major issues for me
darren o neill
Copper Contributor
Oct 27, 2017
Same

Forum Discussion

Green Screen after Builder update. volsnap.sys

Share

Resources