In place windows 11 upgrade results in a BSOD after the first restart.


Did you also disable both VT-d and VMX Virtualization Technology (VT-x)?
Tried that already. Perhaps the update process is installing incompatible storage controller drivers. My Windows drive is on a nvme ssd. I use the standard NVM Express Controller drivers for these drives. If I try to update these storage controller drivers in Device Manager Phison drivers are installed. These drivers mess up my system. I don't remember if they give me a BSOD when I boot. I know I can specify not to update drivers during a windows update but after an upgrade this might be enabled again and as a result download the Phison drivers.

As mentioned, when I manage to bypass the BSOD my upgrade is reverted back to the version I previously had so it's impossible to see anything on the upgraded system as it no longer exists.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    13th Gen Intel(R) Core(TM) i9-13900K
    Motherboard
    ASUS Maximus Hero Z790
    Memory
    Corsair 2x32GB @ 6600
    Graphics Card(s)
    PNY RTX3080 TI
    Sound Card
    Realtek on motherboard.
    Monitor(s) Displays
    Corsair 4k, BenQ 4k.
    Screen Resolution
    3840x2160
Disable Fast Startup: Fast Startup can sometimes interfere with boot processes. Disable it by navigating to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable > Uncheck "Turn on fast startup."

Perform a Disk Check: Run chkdsk /f /r on the system partition to ensure there are no hidden issues with the file system.

Consider a Repair from Safe Mode and/or with internet disconnected:
Boot into Safe Mode and attempt the in-place upgrade repair from there. This can sometimes bypass driver or service conflicts. Additionally, to prevent the NVMe controller driver from automatically getting replaced with the Phison driver, disconnect internet.

Analyze Setup Logs: After the failed repair, check the setup logs located in C:\$WINDOWS.~BT\Sources\Panther (e.g., setuperr.log and setupact.log). These logs can provide insights into what caused the BSOD.
 

My Computers

System One System Two

  • OS
    11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Asus TUF Gaming F16 (2024)
    CPU
    i7 13650HX
    Memory
    16GB DDR5
    Graphics Card(s)
    GeForce RTX 4060 Mobile
    Sound Card
    Eastern Electric MiniMax DAC Supreme; Emotiva UMC-200; Astell & Kern AK240
    Monitor(s) Displays
    Sony Bravia XR-55X90J
    Screen Resolution
    3840×2160
    Hard Drives
    512GB SSD internal
    37TB external
    PSU
    Li-ion
    Cooling
    2× Arc Flow Fans, 4× exhaust vents, 5× heatpipes
    Keyboard
    Logitech K800
    Mouse
    Logitech G402
    Internet Speed
    20Mbit/s up, 250Mbit/s down
    Browser
    FF
  • Operating System
    11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Medion S15450
    CPU
    i5 1135G7
    Memory
    16GB DDR4
    Graphics card(s)
    Intel Iris Xe
    Sound Card
    Eastern Electric MiniMax DAC Supreme; Emotiva UMC-200; Astell & Kern AK240
    Monitor(s) Displays
    Sony Bravia XR-55X90J
    Screen Resolution
    3840×2160
    Hard Drives
    2TB SSD internal
    37TB external
    PSU
    Li-ion
    Mouse
    Logitech G402
    Keyboard
    Logitech K800
    Internet Speed
    20Mbit/s up, 250Mbit/s down
    Browser
    FF
Fast startup is already disabled. Already did a chkdsk /f /r with no errors found. BTW, I installed the Phison drivers again and I have no problems with them, go figure. Will give the remaining two suggestions a try shortly. Also keep in mind that a clean install works flawlessly but I don't want to reinstall everything.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    13th Gen Intel(R) Core(TM) i9-13900K
    Motherboard
    ASUS Maximus Hero Z790
    Memory
    Corsair 2x32GB @ 6600
    Graphics Card(s)
    PNY RTX3080 TI
    Sound Card
    Realtek on motherboard.
    Monitor(s) Displays
    Corsair 4k, BenQ 4k.
    Screen Resolution
    3840x2160
Well, I finally got the repair install to work. I think my problem boiled down to two things.

1. It appears using the Phison controller drivers enabled me to boot.

2. I had to set my BIOS to the Intel defaults..This mode is Intel's response to the problems with the 13900k and 14900k CPU's. Unfortunately this turns my system into a far less powerful machine. Guess I'll play around with the BIOS again. Now to see if my other little problems are fixed by the repair install.

Thanks to all who have me advice.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    13th Gen Intel(R) Core(TM) i9-13900K
    Motherboard
    ASUS Maximus Hero Z790
    Memory
    Corsair 2x32GB @ 6600
    Graphics Card(s)
    PNY RTX3080 TI
    Sound Card
    Realtek on motherboard.
    Monitor(s) Displays
    Corsair 4k, BenQ 4k.
    Screen Resolution
    3840x2160
Another thing I just realized is that when I set my BIOS to the Intel defaults it also turned on Fast Boot. Could Fast Boot have bypassed loading some stuff that was causing my BSOD?
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    13th Gen Intel(R) Core(TM) i9-13900K
    Motherboard
    ASUS Maximus Hero Z790
    Memory
    Corsair 2x32GB @ 6600
    Graphics Card(s)
    PNY RTX3080 TI
    Sound Card
    Realtek on motherboard.
    Monitor(s) Displays
    Corsair 4k, BenQ 4k.
    Screen Resolution
    3840x2160
Could Fast Boot have bypassed loading some stuff that was causing my BSOD?

Possibly? But shouldn’t.

Guess I'll play around with the BIOS again

If you’re going to make BIOS changes. Change something, save and reboot to check, for each thing you change. For elimination purposes.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro 23H2 Build 22631.4974
    Computer type
    PC/Desktop
    Manufacturer/Model
    Sin-built
    CPU
    Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (4th Gen?)
    Motherboard
    ASUS ROG Maximus VI Formula
    Memory
    32.0 GB of I forget and the box is in storage.
    Graphics Card(s)
    Gigabyte nVidia GeForce GTX 1660 Super OC 6GB
    Sound Card
    Onboard
    Monitor(s) Displays
    4 x LG 23MP75 - 2 x 24MK430H-B - 1 x Wacom Pro 22" Tablet
    Screen Resolution
    All over the place
    Hard Drives
    Too many to list.
    OS on Samsung 1TB 870 QVO SATA
    PSU
    Silverstone 1500
    Case
    NZXT Phantom 820 Full-Tower Case
    Cooling
    Noctua NH-D15 Elite Class Dual Tower CPU Cooler / 6 x EziDIY 120mm / 2 x Corsair 140mm somethings / 1 x 140mm Thermaltake something / 2 x 200mm Corsair.
    Keyboard
    Corsair K95 / Logitech diNovo Edge Wireless
    Mouse
    Logitech G402 / G502 / Mx Masters / MX Air Cordless
    Internet Speed
    100/40Mbps
    Browser
    All sorts
    Antivirus
    Kaspersky Premium
    Other Info
    I’m on a horse.
  • Operating System
    Windows 11 Pro 23H2 Build: 22631.4249
    Computer type
    Laptop
    Manufacturer/Model
    LENOVO Yoga 7i EVO OLED 14" Touchscreen i5 12 Core 16GB/512GB
    CPU
    Intel Core 12th Gen i5-1240P Processor (1.7 - 4.4GHz)
    Memory
    16GB LPDDR5 RAM
    Graphics card(s)
    Intel Iris Xe Graphics Processor
    Sound Card
    Optimized with Dolby Atmos®
    Screen Resolution
    QHD 2880 x 1800 OLED
    Hard Drives
    M.2 512GB
    Antivirus
    Defender / Malwarebytes
    Other Info
    …still on a horse.
Could Fast Boot have bypassed loading some stuff that was causing my BSOD?
Yes, enabling Fast Boot in UEFI settings could potentially contribute to a BSOD with the error code INACCESSIBLE_BOOT_DEVICE during an in-place upgrade or repair of Windows 11 24H2, especially if the operating system is installed on a NVMe SSD. Here's why:
  1. Fast Boot skips certain initializations: When Fast Boot is enabled, the system bypasses some hardware initialization processes, including those related to storage devices. This can lead to issues if the NVMe SSD requires specific drivers or configurations to be properly recognized during the boot process.
  2. Driver or boot configuration mismatch: During an in-place upgrade or repair, Windows may update or modify boot-related files and drivers. If the NVMe SSD's driver or configuration is not fully initialized due to Fast Boot, the system might fail to access the boot device, triggering the BSOD.
  3. Changes in Boot Configuration Data (BCD): An in-place upgrade often updates the BCD. If Fast Boot interferes with the proper detection of the NVMe SSD, the updated BCD might point to an inaccessible or improperly initialized boot device.
To avoid this issue, you can temporarily disable Fast Boot in the UEFI settings before attempting the repair or upgrade. This ensures that all hardware components, including the NVMe SSD, are fully initialized during the boot process. Once the upgrade or repair is complete, you can re-enable Fast Boot if desired.
 

My Computers

System One System Two

  • OS
    11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Asus TUF Gaming F16 (2024)
    CPU
    i7 13650HX
    Memory
    16GB DDR5
    Graphics Card(s)
    GeForce RTX 4060 Mobile
    Sound Card
    Eastern Electric MiniMax DAC Supreme; Emotiva UMC-200; Astell & Kern AK240
    Monitor(s) Displays
    Sony Bravia XR-55X90J
    Screen Resolution
    3840×2160
    Hard Drives
    512GB SSD internal
    37TB external
    PSU
    Li-ion
    Cooling
    2× Arc Flow Fans, 4× exhaust vents, 5× heatpipes
    Keyboard
    Logitech K800
    Mouse
    Logitech G402
    Internet Speed
    20Mbit/s up, 250Mbit/s down
    Browser
    FF
  • Operating System
    11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Medion S15450
    CPU
    i5 1135G7
    Memory
    16GB DDR4
    Graphics card(s)
    Intel Iris Xe
    Sound Card
    Eastern Electric MiniMax DAC Supreme; Emotiva UMC-200; Astell & Kern AK240
    Monitor(s) Displays
    Sony Bravia XR-55X90J
    Screen Resolution
    3840×2160
    Hard Drives
    2TB SSD internal
    37TB external
    PSU
    Li-ion
    Mouse
    Logitech G402
    Keyboard
    Logitech K800
    Internet Speed
    20Mbit/s up, 250Mbit/s down
    Browser
    FF
what happens when you boot to safe mode. does it boot to desktop or you get BSOD? you can disable all your third party drivers easily with Autoruns
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Lenovo
I've been trying to do an in place upgrade of my Windows 11 system to see if it will fix some issues I am having. I have tried the 'old' in place upgrade using a 24H2 ISO and also tried the newer Settings/System/Recovery Fix problems using Windows Update /Reinstall feature.

The upgrade goes fine in both cases but when the system reboots to Windows it gets a BSOD INACCESSIBLE_BOOT_DEVICE. It appears the upgrade has mucked around with my boot device so that it can't be found. My boot device is setup properly in my BIOS and I've had no problems of this sort other than doing this repair install. When I reboot again things go into revert back to previous version mode to what I had before. So this isn't your run of the mill boot device problem. As I said the install must have made my boot drive inaccessible in some way. After I'm back to my previous version it boots just fine. Also restoring a disk image I took prior to the repair install boots fine. So it must be the install playing games on me. Maybe it's downloading some incorrect disk controller drivers. I boot from a NVMe M.2 PCIe Gen4 SSD.

Any thoughts on this?

BTW... I did a clean install with no problems. I didn't stay with this as I have way to many things to reinstall and don't have the time or where with all to do it.

I have the same problem. I have not been able to resolve it. In-place updates fail the first time with inaccessible device, then succeeds the second time after the roll-back. Tried many things, nothing worked.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro x64
    Computer type
    PC/Desktop
    Manufacturer/Model
    DIY Photoshop/Audio/Game/tinker build
    CPU
    Intel i9 13900KS P/E cores 5.7/4.4 GHz, cache 5.0 GHz
    Motherboard
    Asus ROG Maximus Z790 Dark Hero
    Memory
    96GB (2x48) G.skill Ripjaws 6800 MT/s
    Graphics Card(s)
    Asus ROG Strix 4070 Ti OC
    Sound Card
    Bowers & Wilkins 606 S3 speakers; Audiolabs 7000a integrated amp; Logan Martin Sub; Creative Pebble Pro Minimilist
    Monitor(s) Displays
    Eizo CG2730 ColorEdge, ViewSonic VP2768
    Screen Resolution
    2560 x 1440p x 2
    Hard Drives
    WDC SN850X 4TB nvme, SN850 1TB nvme, SK-Hynix 2 TB P41 nvme, Raid 0: 1TB 850 EVO + 1TB 860 EVO SSD. Sabrent USB-C DS-SC5B 5-bay docking station: 6TB WDC Black, 6TB Ironwolf Pro; 2x 2TB WDC Black HDD
    PSU
    850W Seasonic Vertex PX-850 ATX 3.0/PCI-E 5.0
    Case
    Fractal Design North XL Mesh, Black Walnut
    Cooling
    EKWB 360 Nucleus Dark AIO w/Phanteks T30-120 fans, 1 Noctua NF-A14 Chromax case fan, 1 T30-120 fan cooling memory
    Keyboard
    Keychron Q3 Max TKL with custom GMK Redsuns Red Samuri keycaps, TX Stabs
    Mouse
    Logitech G305 wireless gaming
    Internet Speed
    500 Mb/s down, 12 Mb/s up
    Browser
    Firefox
    Antivirus
    Defender, Macrium Reflect X ;-)
    Other Info
    Runs hot. LOL. SP: P116/E93/M93
    Phangkey Amaterasu V2 Desk Mat
  • Computer type
    Laptop
    Manufacturer/Model
    Apple 13" Macbook Pro 2020 (m1)
    CPU
    Apple M1
    Screen Resolution
    2560x1600
    Browser
    Firefox
Are you using the Intel RAID driver? I am - raided two SSD (non-OS).
 

My Computers

System One System Two

  • OS
    Windows 11 Pro x64
    Computer type
    PC/Desktop
    Manufacturer/Model
    DIY Photoshop/Audio/Game/tinker build
    CPU
    Intel i9 13900KS P/E cores 5.7/4.4 GHz, cache 5.0 GHz
    Motherboard
    Asus ROG Maximus Z790 Dark Hero
    Memory
    96GB (2x48) G.skill Ripjaws 6800 MT/s
    Graphics Card(s)
    Asus ROG Strix 4070 Ti OC
    Sound Card
    Bowers & Wilkins 606 S3 speakers; Audiolabs 7000a integrated amp; Logan Martin Sub; Creative Pebble Pro Minimilist
    Monitor(s) Displays
    Eizo CG2730 ColorEdge, ViewSonic VP2768
    Screen Resolution
    2560 x 1440p x 2
    Hard Drives
    WDC SN850X 4TB nvme, SN850 1TB nvme, SK-Hynix 2 TB P41 nvme, Raid 0: 1TB 850 EVO + 1TB 860 EVO SSD. Sabrent USB-C DS-SC5B 5-bay docking station: 6TB WDC Black, 6TB Ironwolf Pro; 2x 2TB WDC Black HDD
    PSU
    850W Seasonic Vertex PX-850 ATX 3.0/PCI-E 5.0
    Case
    Fractal Design North XL Mesh, Black Walnut
    Cooling
    EKWB 360 Nucleus Dark AIO w/Phanteks T30-120 fans, 1 Noctua NF-A14 Chromax case fan, 1 T30-120 fan cooling memory
    Keyboard
    Keychron Q3 Max TKL with custom GMK Redsuns Red Samuri keycaps, TX Stabs
    Mouse
    Logitech G305 wireless gaming
    Internet Speed
    500 Mb/s down, 12 Mb/s up
    Browser
    Firefox
    Antivirus
    Defender, Macrium Reflect X ;-)
    Other Info
    Runs hot. LOL. SP: P116/E93/M93
    Phangkey Amaterasu V2 Desk Mat
  • Computer type
    Laptop
    Manufacturer/Model
    Apple 13" Macbook Pro 2020 (m1)
    CPU
    Apple M1
    Screen Resolution
    2560x1600
    Browser
    Firefox
I have the same problem. I have not been able to resolve it. In-place updates fail the first time with inaccessible device, then succeeds the second time after the roll-back. Tried many things, nothing worked.


Please open a new thread. Post a link into this thread.

In the new thread:



1) Please run the V2 log collector and post a share link into this thread using drop box, or google drive

BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)



2) Run Tuneup plus > post a share link

https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.bat

Batch files for use in BSOD debugging - Page 2 - Windows 10 Forums

Batch files for use in BSOD debugging - Windows 10 Forums



3) Run: upgrade_failure_info > post a share link

https://www.tenforums.com/attachmen...s-use-bsod-debugging-upgrade_failure_info.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Batch files for use in BSOD debugging - Windows 10 Help Forums
 
Last edited:

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation

Similar threads

  • Featured
  • Article Article
Replies
321
Views
608K

Latest Support Threads

Back
Top Bottom