Windows 10 BSOD Can't Access Repair Tool or Advanced Boot Options

[samsmyth93]

I just built a new desktop computer and was very happy with it for the first few days. I assembled the computer and installed Windows 10 Education (get it for free from my university) without any problems. A few days in, a friend was over trying out the computer, and he said his "finger slipped" while he was on the desktop trying to open the Steam app, but an error message came up (unfortunately do not remember what it said) and the app would not launch. I rebooted Windows, but was given an irql_not_less_or_equal blue screen. I still had a bootable USB with Windows 10 Education on it, so I plugged that in and tried to boot from it to access the repair Windows tool.

Here's where it gets odd. When I boot from the USB drive with Windows 10 Education loaded on in a bootable format, I continue to get the irql_not_less_or_equal blue screen. Sometimes it will give me a "kmode exception not handled" error when I boot from the USB drive. I tried taking out the GPU and the second stick of RAM so it only had one stick, but the error message persisted. I also removed all other internal drives besides the C drive. All over the internet it's talking about running the repair tool through the external USB drive, but like I said, I cannot even get to this screen. I did try using the USB drive with Windows 10 Education loaded on to it on another computer, and it booted properly to the screen that allows me to either do a clean install or repair the OS. This makes me think it is something hardware related. That being said, I did run the system 100% properly for a few days, so it is confusing.

Also, when it restarts a few times (it's stuck in a restart loop), it will attempt to go into the recovery tool, but quickly jump to a BSOD again, sometimes not even fully showing the error message, just restarting or freezing on a half-completed frowny face that comes with the BSOD.

Any ideas?!? Thanks for your time!

 

[DarrenBryce]

Although this post was a while ago glad I found it, I couldn’t find any other post with this issues. my brand new laptop getting these similar symptoms only after few hours of use, I believe my cpu is malfunctioning too, awaiting for replacement. This post allows me to relax a bit now knowing it’s cpu and I don’t have to crack my head trying to fix it after days of trying different fixes . But still weird, I really want to know what killed the cpu, was it me or just manufacturing problems.

 

[USAFRet]

Although this post was a while ago glad I found it, I couldn’t find any other post with this issues. my brand new laptop getting these similar symptoms only after few hours of use, I believe my cpu is malfunctioning too, awaiting for replacement. This post allows me to relax a bit now knowing it’s cpu and I don’t have to crack my head trying to fix it after days of trying different fixes . But still weird, I really want to know what killed the cpu, was it me or just manufacturing problems.

Please start a NEW thread for your particular situation.