Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC Insider

magilla · 14 Oct 2017

blackroseMD1 said:

Well, looks like I'm sticking to the FCU, since this update blue screens immediately after rebooting. It's a page fault in nonpaged area BSOD pointing to volsnap.sys.

There is something wrong with programming/code. Too many of us are having problems with page fault in nonpaged area BSOD and pointing to volsnap.sys. I am really pi**ed about this. I have spent last night and most of today getting one computer up and running and it isn't happening. I am now doing a clean, total install. I have also discovered that - once again - the wonderful world of MS has downloaded a video driver that will not allow my computer to come out of sleep mode -- this is on a working computer (HA HA)
Well, so much for the clean install on my other computer. It just BSOD'd with our favorite term!

pbcopter · 14 Oct 2017

magilla said:

There is something wrong with programming/code. Too many of us are having problems with page fault in nonpaged area BSOD and pointing to volsnap.sys. I am really pi**ed about this. I have spent last night and most of today getting one computer up and running and it isn't happening. I am now doing a clean, total install. I have also discovered that - once again - the wonderful world of MS has downloaded a video driver that will not allow my computer to come out of sleep mode -- this is on a working computer (HA HA)
Well, so much for the clean install on my other computer. It just BSOD'd with our favorite term!

As I said earlier, if you disable Restore Points, the system will not crash.

AndreTen · 14 Oct 2017

pbcopter said:

As I said earlier, if you disable Restore Points, the system will not crash.

No restore points here. Not even enabled. Crash and restart right after first install restart

magilla · 14 Oct 2017

pbcopter said:

As I said earlier, if you disable Restore Points, the system will not crash.

Don't have restore points enabled and never have.

magilla · 14 Oct 2017

DavidY said:

Does the driver have the setting in Device Management with a Power Management tab and a checkbox for 'Allow the computer to turn off this device to save power'? If so, I guess you could try un-checking it?

Thanks, but no power mgmt tab with this abomination.

f14tomcat · 14 Oct 2017

I don't have this issue, but I just ran across this. Not suggesting the SFC, which seems to be the universal "take 2 aspirin" cure, but here is this, if anyone wants to try, copy volsnap.sys from a good working recent build and see what happens.

BSOD volsnap.sys

~~Please run SFC /scannowto check system files,~~ volsnap.sys may corrupted. You can copy this files from another PC and replace it.

imcanadian · 14 Oct 2017

I am not sure myself with my desktop. No problem to download through Windows Update then installing the latest version of 17017.1000. Look good to me with the first part then my desktop restarted after installing. I got no screen picture on my monitor and am not sure what is that about. Does the new version take a long time to install in the desktop before you will see the screen picture to login. I wasn't sure about this then I decide to force to shutdown the desktop and restart the desktop. And see the notification message that Windows did not finish installing the update. How long do I have to wait for this to complete the installation of all files for 17017.1000? Maybe I should leave my desktop on through the night to complete installing the files of 17017.1000. What is your suggestion for this?

John

Kari · 14 Oct 2017

Interesting GSOD half an hour ago:

Announcing Windows 10 Insider Preview Fast+Skip Build 17017 for PC-image.png

Timestamp of driver in question: August 15, 1977!

Ztruker · 14 Oct 2017

I upgraded my Oracle VM last night with no problem. Tried to boot just now and I'm in a Automatic Repair / Page Fault In Non Paged Area - volsnap.sys fail loop. I'm going to try to go back to 16200.15 if it will let me.

f14tomcat · 14 Oct 2017

Kari said:

Interesting GSOD half an hour ago:

Timestamp of driver in question: August 15, 1977!

Wasn't that the acquire date of wife #2?