Build 14366 BSODs and Reset - Advice Appreciated

Doverboy · 18 Jun 2016

Slow Ring member updated to Build 14366 yesterday with no issues (initially)
Tested apps, etc, all ran normally.
Post-Install ran complete scans with Malwarebytes Anti-Malware Free and Defender, both scans reported clean
Post_Install ran sfc /scannow, clean report
Stressed with Prime95 Blend 2 Hours, clean
Everything was working normally

Last action last night was activating Dropbox, been uploading album collection, 30k+ files, about halfway through, 15k remain to sync, will take better part of month to complete 250GB upload at 800Kbps upload speed. I set it to use full bandwidth each night before bed.

I did not think to check the Power Settings last night. Normally just turn off monitors, leaving PC operational throughout night, no sleep mode, etc. I'm thinking the error may have occurred when it tried to Sleep or Shut Down while full upload bandwidth was being used by Dropbox, just a guess.

This morning greeted with BSOD, BSOD on screen 2 was actually pixelated, new encounter for me.

Attempted normal restart - fail
Booted into Bios, reset default settings, attempted normal reboot - fail
Rebooted again, W10 loaded, but with problems, missing background, could not identify Wireless Adapter, then another BSOD
Used W10 Recovery Disk to repair startup - fail
Booted into W10, still messed up, attempted Refresh - fail

Decided to Reset W10, keeping files but losing settings and installed apps. Successful operation.

Now running Build 14342.rs1_release.160506-1708 without issues. Successful sfc /scannow and P95 stress.

Like a dummy, I stopped creating automatic restore points (already have one for current state)

My windows.old folder on my OS drive appears intact, the one created prior to Build 14366 update.

I'd like to try to revert to that installation, hoping my apps and settings will still be in place. However, I'm a little concerned given today's problems.

Objective: Use refresh/reset/restore/rollback to reinstall everything from windows.old created yesterday prior to 14366 update. Avoid having to reinstall apps and settings.

I believe there is little risk as I now have (I think) a stable OS with a restore point to come back to if it goes sideways. However, before I attempt I thought I'd solicit some feedback.

Thanks!

DB

I have now added the Debug zip attachment. Thanks!

Doverboy · 18 Jun 2016

Upon closer inspection, I now see the windows.old folder is not the version from yesterday prior to the build update, but rather it was created this morning during the reset process. Live and learn...

axe0 · 19 Jun 2016

Hi Doverboy,

Unfortunately the zip is pretty much useless for debugging, the reason is that there is no log or something about a BSOD.

If the Windows.Old folder has minidumps located in \Windows\Minidump then we would like to see them, you can zip them up and upload them.
How to upload files

Doverboy · 19 Jun 2016

Thank-you, Axe. Yes, the dump files are indeed useless in this case. I had originally posted in a different section, but an admin moved it to BSODs. I wasn't actually looking for help on that issue (though would have welcomed and been useful I'm sure). Rather, I was trying to learn whether there might be a workaround to return to my pre-14366 state without restore points, images, etc.

Good lesson for me to learn (again). I became complacent with W10 as this is the first major issue I've had since upgrading in October.

I completed a fresh install and only lost apps and settings, no files. Last night I reinstalled everything and straightened out the settings. Then I created restore points, backed up and created an image.

This morning 14366 was waiting for me again. The update ran smoothly and I stressed the rig. Then I created new restore point, backup and image. Yes, I am being more careful.

All well so far, no crashes or weirdness. Should everything go sideways again, I have the tools in place to avoid having to reinstall apps and tweak settings.

Thanks for responding!