BSOD on Windows 7 upgrade to Windows 10 "The installation failed in the SECOND_BOOT phase"

MingoMongo

Well-known member
Joined
Oct 2, 2020
Posts
146
Location
UK
Stats:

Windows 7 64bit SP1, ASUS P8Z68 Deluxe/Gen3, Intel Core i5-2500K, Corsair Vengeance 8GB Dual Channel DDR3 Memory Kit (CMZ8GX3M2A1866C9), Asus Nvidia GeForce GTX 960, Samsung SSD 860 EVO 500GB (Windows drive), WDC WD1002FAEX, Seagate ST2000DM006, Corsair Gold AX1200 (1200 Watts)

Hi people! You did a great job helping me out once before and I'm hoping you can help me again!

Like the title says, I'm trying to upgrade to Windows 10 using the MediaCreationTool20H2 program but am running into blue screens preventing me from doing so. I know I could try a clean install of Windows 10, but the prospect of redownloading all my programs I'm finding very unappealing and I'm trying to avoid it. FYI, I was trying a lot of fixes a while ago in early October talking to people on the Windows 7 forums but after all the work done on my first thread here I need a break from fixing. Essentially the upgrade goes like this:
  • Upgrade starts running off of the program (have tried external drives and ISOs in the past to the same effect, but will try again if needed)
  • Choose to keep files and apps
  • First part goes well
  • Restarts into the windows 10 screens where it does updates and restarts several times
  • At 75% completion of updates I get a blue screen with "SYSTEM THREAD EXCEPTION NOT HANDLED"
  • System restarts and the app attempts to recover the upgrade
  • "SYSTEM THREAD EXCEPTION NOT HANDLED" again
  • Windows undoes the changes and restarts
  • Boot back up to a window saying "We couldn’t install Windows 10" with the error code 0xC1900101 - 0x40017, The installation failed in the SECOND_BOOT phase with an error during BOOT operation
sfc /scannow in cmd comes up with no issues. CBS and SFCFix results here. CheckSUR.log mentions Avast but I have uninstalled it. From my Windows 7 Forums thread I know there's still some registry entries left over. WhoCrashed doesn't seem to find any crash logs.
 
Ok I learned how to use SFCFix a bit from other forum posts and managed to remove the avast registry keys that were left over after I uninstalled it. I'm pretty sure I did it right, but I backed up my registry with tweaking.com just in case. The CheckSUR now comes up clean (see attached), but the BSOD with "SYSTEM THREAD EXCEPTION NOT HANDLED" still shows up same as before unfortunately. Still no crash logs on WhoCrashed.

I should note that in my thread on Windows Seven Forums someone pointed out there was some troubles with my model of MOBO and Win10, but these problems don't seem to stop people upgrading and seem fixable.

Again, help would be much appreciated, I can post this thread to a different board if this is more of a BSOD problem now.
 

Attachments

Last edited:
Bumping this! I started another thread in the Sys BSOD forums and although the initial problem of upgrading still remains (still the same error code), many bad drivers have been uninstalled and fixed, as well as general registry mess has been cleared up. I don't seem to get any BSOD crash logs when it fails, but we've been looking at logs from panther and SetupDiag which seem to have information. It's difficult to list all the things we've tried up until this point, but most common fixes have definitely been attempted. Anti-virus stuff uninstalled, virtual drive stuff uninstalled, graphic drivers and seemingly other problematic drivers reinstalled, clean boots before upgrading, upgrading from the windows iso on desktop, sigverif is clean, sfc /scannow is clean, WDV now produces no BSODs.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top