WIN11User
Well-known member
- Local time
- 8:34 AM
- Posts
- 18
- OS
- Windows 11 Pro
Been going thru some odd repetitive boot issues and am not certain why or how to rectify.
I was running a dual boot system with Windows 11 Pro (23H2) as primary and a lite version of Windows 11 23H2. Each time this happens (quite out-of-the-blue) only the primary OS
(Windows 11 Pro 24H2) no longer boots. I get a BSOD, not always with the same error. The last couple times there is no error code but just the statement "INACCESSIBLE_BOOT_DEVICE."
The data on the NVMe drive is still accessible via the other boot OS Lite Windows 11. So I restore the partition with the .mrimgx image that I have created.
formatted the entire NVMe Drive and installed Windows 11 Pro (4H2) instead. The same thing happened once again. I asked myself, is the NVMe drive faulty? It seems unlikely as the lite Windows version continues to function. Recently I ran EasyBoot to view the boot loader information and noticed the new Windows 11 Pro 24H2 system was missing. This led me to believe the "winload.efi" file is corrupt. YES???, MAYBE??? Would backing this up and replacing this file patch the system so I wouldn't have to restore via .mrimgx image?
But, bottom line what is happening??
What can I do to troubleshoot this issue?
P.S. I believe I ran chkdsk once before. Will run again and see if there were errors.
UPDATE: cksdsk found no errors on ether OS partitions.
Brian
I was running a dual boot system with Windows 11 Pro (23H2) as primary and a lite version of Windows 11 23H2. Each time this happens (quite out-of-the-blue) only the primary OS
(Windows 11 Pro 24H2) no longer boots. I get a BSOD, not always with the same error. The last couple times there is no error code but just the statement "INACCESSIBLE_BOOT_DEVICE."
The data on the NVMe drive is still accessible via the other boot OS Lite Windows 11. So I restore the partition with the .mrimgx image that I have created.
formatted the entire NVMe Drive and installed Windows 11 Pro (4H2) instead. The same thing happened once again. I asked myself, is the NVMe drive faulty? It seems unlikely as the lite Windows version continues to function. Recently I ran EasyBoot to view the boot loader information and noticed the new Windows 11 Pro 24H2 system was missing. This led me to believe the "winload.efi" file is corrupt. YES???, MAYBE??? Would backing this up and replacing this file patch the system so I wouldn't have to restore via .mrimgx image?
But, bottom line what is happening??
What can I do to troubleshoot this issue?
P.S. I believe I ran chkdsk once before. Will run again and see if there were errors.
UPDATE: cksdsk found no errors on ether OS partitions.
Brian
My Computer
System One
-
- OS
- Windows 11 Pro
- Computer type
- PC/Desktop
- Manufacturer/Model
- Self-Built
- CPU
- AMD RYZEN 7 5800X
- Motherboard
- ASUS ROG STRIX X570-I Gaming
- Memory
- (2) GSkill 32GB
- Graphics Card(s)
- NVIDIA GeForce RTX 3060
- Sound Card
- NVIDIA GM206(On-Board)
- Monitor(s) Displays
- NEC EA244UHD
- Screen Resolution
- 3840 x 2160
- Hard Drives
- Sabrent 500GB Rocket NVMe PCIe 4.0 M.2 2280
SAMSUNG 980 PRO M.2 2280 1TB PCI-Express Gen 4.0 x4, NVMe 1.3c
- PSU
- CORSAIR 1000W etc...
- Case
- Thermaltake Tower 100
- Cooling
- NZXT Kracken M22 120mm
- Keyboard
- TMI
- Mouse
- TMI
- Internet Speed
- TMI
- Browser
- TMI
- Antivirus
- TMI
