BSOD Loop & Issues Repairing Windows

BDEE

BDEE

BDEE

Soldato
Joined
21 Apr 2011
Posts
3,210
Looking for some assistance please folks.

Turned PC on tonight. After about 20 seconds of getting to desktop I got a BSOD, followed by being stuck in a constant BSOD / repair attempt loop:

39A1C23F-8CE3-4139-B62E-A8EE506637DE_zpsff8rohje.jpg


The repair attempts didn't work and kept on looping round the BSOD over and over, without even getting to desktop.

I installed the Windows 10 ISO file onto a USB stick and attempted some of the options within there to repair / restore - Both options didn't work.

98E71135-E388-469C-9F3E-8E5973A9E8DE_zpsbs0wwwl4.jpg

3FC8EEB0-1F79-45A5-B004-6B5A3DD97F08_zpsxzmwzcv1.jpg

28B0E89A-BB09-4B7A-B858-F6D126BED4FA_zpsown7vuib.jpg



So I tried just re-installing Windows and got this:
B9507911-E535-4C78-B363-6F24AD50654D_zpsd3w3yvmk.jpg



All this is leading me to believe the BSOD relates to the boot drive and it may have an error? It is a Samsung M.2 Drive and is about a month old.

Does anyone have any more suggestions on what I can try here, or is my drive fried? Seems odd for a brand new drive on a brand new board :(

Thanks
 
If your ok to re install W10 on the windows startup screen delete every partition so its seen as one drive and then create a new partition and windows should create what is needed.

doing this will delete everything off the drive so make sure you have everything first
 
That's the one thing I was trying to avoid. Plus doesn't really explain why the BSOD is happening and ensure it won't happen again.

I think I have everything backed up, but no idea how I would if there is anything not, as unable to boot with it connected. Ack. Need to check google drive to see if it has everything there. I know the one thing I do not have it all my music, as I was in progress of sorting it all out over the weekend and hadn't finished - the irony is I was going to copy that all across to my spare drive tonight :(

Not sure how i can pull any data off it with not being able to boot. Might try installing Win10 on the drive I've got 7 on at the moment and then boot from that and see if it sees the M.2 as another drive without BSODing
 
It seems like a boot or OS issue so as you said if you have a spare HDD do a clean install on that and then access the files on the failed to boot drive as everything should still be there.

once you have everything format the failed drive and see if it works.

Do you have a OC on the CPU at all? could try clearing CMOS (remove battery for half hour) or I had a quick google and came across this link which may help

http://www.troublefixers.org/laptops/fix-system-thread-exception-not-handled-in-windows-10/590/
 
Yeah I found that page earlier too but didn't seem to help much. No OC at all.

I'm going to try installing on the spare drive now and go down that route. May end up being one of those strange mysteries where you never find out the route cause.
 
Well that's worked thankfully. Must have been software related. Suspect NVidia drivers as I think there was an update - it's the usual suspect also.

Cheers for the help.
 
Spoke too soon.

Doing it again now. Ugh. Exact same thing as before, so mayabe it is the drive after all.

Will have to run the system off a different drive for a few days to test it I guess
 
The message about GPT partitions when attempting to re-install windows suggests that the Windows installer has been booted in legacy mode whereas your actual Windows installation is using UEFI boot.

Legacy boot mode will not boot from GPT partitions. A Windows installer booted in legacy mode will not install to GPT partitions. You need to boot the Windows installer in UEFI mode - and ensure the USB stick can boot in UEFI mode.

Of course this doesn't fix the main issue but I thought I'd point this out.
 
Thanks for that.

I manged to re-install on it anyway with creating new partition, but as above it hasn't stopped the issue.

I've re-installed onto an old mechanical drive I had laying about and thus far total stability, so the issue must be the drive. What is not clear is if that is hardware or software (probably Windows). I might put it back in as the non-boot drive and see what happens - if I get the BSODs again that would probably indicate more of a hardware issue? I'm kinda stuck with a £240 brick if it is software though I guess, as unlikely I'm going to be able to get an exchange for a different one if there is nothing physically wrong with the drive.
 
Come to think of it, I am wondering if the BIOS could have something to do with it.

I updated the BIOS - I can't remember if I had used the machine again since and it had been working for a few weeks.

Does this sound like a possibility? In which case does anyone know what version of BIOS the Asus Maximums 8 Hero Z170 ships with, as I could flash that back to its default version and see if that makes a difference.
 
To clarify, you managed to fresh install on the m2 drive and still saw bsods and boot issues soon afterwards?
 
Correct. Managed to boot after the install. Installed graphics drivers, no issues. Started installing things like steam, corsair link, itunes - No issues, then suddenly, random BSOD, then stuck back in the BSOD loop. I would say it was about 20 minutes following the boot that the first BSOD came.

I have found a few things online about issues with Samsung M.2 drives on Asus motherboards so it does seem to be some kind of hardware conflict. I am just on using flashback now to try an older BIOS which is listed as having "improved Samsung M.2 drive stability".
 
BIOS rolled back to v1001 and put the M.2 back in. Stuck in BSOD loop again.

Going to delete the partition again and attempt a new install with the BIOS back to 1001 and see what happens...
 
Another update.

I hope this thread might help someone else in the future will the log of everything I am doing.

I didn't clear the partition and re-install again.

I went back to the BIOS again and decided to reset to default and set everything back up.

Didn't see that anything was any different, but was able to load with no BSOD. So this is BIOS v1001.

Appears that the last program I was trying to install when I got the initial BSOD was Googledrive. I am sure this is irrelevant, but you never know.

So now back to re-installation of everything and see what happens. Fingers crossed.

I will add all the BIOS settings later as well in case it helps anyone out.
 
You must log in or register to reply here.
Back
Top Bottom