Windows 10: BSOD after automatic repair loop or USB boot

Hi all,

I have a pretty resistant BSOD problem.

It started after the tablet (Dell Latitude 5175, running Windows 10 with auto updates) froze while hooked to a TV via microHDMI. I got a blue screen, with Windows collecting information - can't remember much more, as I was not particularly worried at the time.

Problem is when the tablet rebooted, it showed after boot "Preparing Automatic Repair" (with a loading wheel) and then the screen went black (still active, but entirely black). It stayed stuck there for several hours, until I decided to do a hard reboot. It's been doing the exact same thing since then.

I have tried to access safe mode, but several hard reboots did not trigger Advanced Startup Mode. I then used the Media Creation Tool to create a bootable Win 10 on a USB drive (using another laptop at hand). I tested the drive on the laptop - it boots perfectly well (once fastboot is disabled).

On the tablet, I disabled fastboot (or, in the Dell BIOS, I set it to "thourough"), and tried to either allow (or not) Legacy boots and disable (or not) secure boot. I have also tried to force boot, in UEFI and Legacy, from the USB (you can choose from the menu before accessing the BIOS).

It appears that the tablet boots from USB without issues - the "Preparing Automatic Repair" message disappears. However, that means I just go straight to the active, black screen. And it stays there for hours doing nothing that I can see.

I have ran the Dell hardware diagnostic tools, and all of them come back with a pass which would seem to indicate no clear hardware issue.

At this point, I am not quite sure what to try next and would appreciate any advice I can get!

Note: I have read the instructions for posting... but I can't run the log-collector on the affected device (unless it can be used on boot!). Happy to provide any other information though.

Thanks in advance!!

:)

 

BSOD Loop on boot

Hello,

Earlier today my computer crashed into a BSOD and ever since then it is stuck on a BSOD loop when trying to boot into windows.

Things I have tried so far:

-Booting from a USB Windows (Loads the windows logo then BSOD)

-Letting it do automatic repair (BSOD)

-Letting it do disk check (BSOD)

-Running it with different RAM sticks (BSOD)

-Running it without the 1060 (BSOD)

-Clearing BIOS settings (BSOD)

I am at a loss. Any help appreciated.

System

-Intel i5 6600k

-Nvidia 1060

-16gb ram

-gigabyte z170x

 

Windows 10 is not loadind up

When I started my computer the os is not booting... Soon it restarts again and again like a loop... After that it boots and shows automatic repair and it is also not opening... I created usb installation media to repair the files and it is also not booting..
Pls help

 

If you are booting from a W10 installation USB drive it should not go to an black screen but should go to a setup installation screen. I suspect that it did not boot into the USB drive because you would not see a Preparing Automatic Repair message if it was booting from installation media. You need to continue to find the combination of BIOS settings to allow booting from a USB drive. You could create a UEFI bootable USB using the instructions in option 2 of the following tutorial and see if you have more success:
Create Bootable USB Flash Drive to Install Windows 10

 

Sorry if I was not clear - it goes only to a black screen with the UEFI bootable USB.

In short, 2 outcomes:
- No USB device: Dell logo, then "Preparing automatic repair" loading, then black screen.
- UEFI bootable USB: Dell logo, then straight to black screen.

 

Try creating a new USB drive with a memory test program and see if you can get this to run. Follow the details here: MemTest86+ - Test RAM

 

Sorry - it took over 12 hours to run!

I have run the test, and after 8 passes, no error reported.

 

Try this:

The easiest way to fix it is to create a bootable USB flash drive of Kyhi's Recovery Tools:
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums

Boot the computer from it and run the Macrium Reflect program. Under the restore menu is a utility to Fix Windows Boot Problems.

Above posted by NavyLCDR here Unaccessible boot device

 

I created the bootable USB, and it works - it eventually loads the Win10RE SE. It took about 2 hours to load the first time, but is much faster upon reboot.

Only problem is that I can't use this to fix the Windows Boot with Macrium - because it has the unintended consequence of making my SSD disappear (and this SSD is the only drive on the tablet).
I checked in the BIOS - the SSD is just not seen anymore. But resetting the BIOS to default settings makes the SSD magically reappear! (and disappear again when booting from the USB - which again takes 2 hours!).

I can't even figure out whether this is software or hardware issue at this point!

 

This behaviour suggests that you are switching between UEFI and Legacy boot. The disk shows up in one but not the other. Make sure your USB is working in the same boot mode as your laptop so that it fixes the boot files correctly.

 

It does the same thing in UEFI, and again, not possible to fix the boot because the windows install is not found.

 

There seems to be a hardware problem, I can't understand why the USB recovery disk takes 2h to load and next time is faster.

Can you try running the log file collector when booted from the recovery USB. It might tell us something. Use the new beta v8 one.

 

Just wanted to give a quick update about this - which I have now solved.

It turns out that the SSD was stuck in hibernate, which made it impossible to access and fix. I realized this by booting in a USB-based version of Ubuntu: the SSD was visible, but not accessible.

I then used the Dell BIOS to wipe the disk, and was able to then use the Media Creation Tool USB installer to:
(1) go to command prompt and reformat the disk using Diskpart
(2) install Windows 10 on the formatted SSD

It now works perfectly well. I'm still unsure how exactly the disk ended up being stuck in that mode though!

Thanks for the help!

 

Thanks for the feedback - I've never come across this before.