[SOLVED] BSOD when entering safe mode, fine when booting normally

Toggle sidebar Toggle sidebar
TMinz

TMinz

Mar 14, 2022
8
0
10
I can't find anything online for this issue. When booting normally, everything works. I've been trying to enter safe mode to uninstall display drivers but I'm unable to even make it into safe mode before blue screening with the error, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

Any ideas on possible cause/solution would be helpful. I have already run sfc and DISM scans.
 
Solution
Darkbreeze
It's possible. I'd honestly recommend that you back up anything important off that Corsair drive and the 970 EVO Plus, and then do a clean install of Windows on the EVO Plus.

Sort by date Sort by votes
Full hardware specs, Windows version, Windows BUILD version (winver then hit enter in any run or search box on the start menu)?

Are you trying to do this manually or are you using the DDU?

DO you have the most recent motherboard BIOS version installed?

Do you have any other hardware connected to the system that might be causing the BSOD?
 
Upvote 0 Downvote
At what stage did it bsod? in the blue screens before you choose safe mode or after the logon to safe mode?
there shouldn't be any drivers running then.
I wonder how windows records an error that occurs when its not logged in.

(forgets you can get in via msconfig)

Maybe run chkdsk C: /f in command prompt (admin)
it will pop up 2 paragraphs after this choice is entered, agree to running at restart and then restart PC to let it run.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

if it happens everytime we can see what cause is.
 
Upvote 0 Downvote
Specs:
CPU: Intel Core i7 9700K
GPU: NVIDIA GeForce RTX 2070
Motherboard: MSI MPG z390 Gaming Pro Carbon
Ram: G.Skill F4-3200C16-8GTZR (x2)
Windows 10 Version 21H2 (OS Build 19044.1586)

The most recent Bios version is installed (flashed after seeing issue, before posting).
Only other hardware connected is mouse/keyboard and an internal Elgato HD60

I was using DDU to remove graphics drivers but it recommend safe mode in it's readme.

BSOD happens after selecting safe mode, before the login screen comes up. It loads for a bit after selecting then blue screens.

I will run chkdsc and get the minidump later tonight and upload
 
Upvote 0 Downvote
Try removing the Elgado HD60 game capture device, then retry the safe boot. In a pinch, you can probably get by with just choosing the Clean install option using the Nvidia updater which does an ok job, not as good as the DDU but better than standard upgrade routine, unless you've already tried that and didn't have success.

What is the actual reason you are trying to do a clean install of the graphics drivers? Were you having other issues that led you to doing a clean install using the DDU?
 
Upvote 0 Downvote
Upvote 0 Downvote
Colif has the next idea I was going to suggest. Remove the graphics card, plug your display into the motherboard video output, and then see if you can boot into safe mode to run the DDU uninstallation.

Personally, not to contradict Colif, but I'd be careful with the "repair installation" as I've seen equal numbers of "it worked" and "whole thing is borked now" happen as a result. Make sure you have EVERYTHING important backed up before you attempt it.
 
Upvote 0 Downvote
Colif said:
does the error screen show a file name?

if its at the startup going into safe mode, there shouldn't be any drivers running. So its either a windows problem or the C drive

what storage do you have?
Click to expand...

The error screen does not show a file name, only the error message, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

My C drive is kind of old so that could potentially be an issue, it's a Corsair Force LX SSD 128 GB
 
Upvote 0 Downvote
Results from Hard disk sentinel,
I4w3M2G.png


C:
Health: 83%
Temp: 31 C
 
Last edited:
Upvote 0 Downvote
I honestly just never got around to it. It's a much newer drive that I only installed in the last 6 months so the OS was always on the other SSD. Was planning on getting a new SSD to be my C drive when I next update my specs. (Planning around the next gen CPU and GPU releases). Do you think the 83% health on that SSD could cause the BSOD when booting safe mode specifically?
 
Upvote 0 Downvote
It's possible. I'd honestly recommend that you back up anything important off that Corsair drive and the 970 EVO Plus, and then do a clean install of Windows on the EVO Plus.

 
Upvote 0 Downvote
Solution
Colif said:
So its either a windows problem or the C drive
Click to expand...
It seems this random thought about it being drive could be it. I remember saying it and then wondering why... With no drivers running apart from windows at that stage, it had to be hardware of some sort but then PC appeared to be okay rest of time.

Thats problem with ssd, they don't really give signs they faultering, unlike HDD that can make noises. Age is probably a good clue. And possibly what its been used for. Boot drive will wear out faster than storage only.
128gb is a little small for windows now anyway. It can be done but means you can't really use drive for very much else.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom