Question Can't enter Windows, Access BIOS or use Keyboard and Mouse

Toggle sidebar Toggle sidebar
Maxzloch

Maxzloch

Distinguished
Dec 24, 2015
20
0
18,520
I recently started having problems with my PC giving me a bluescreen every time I booted it, then entering a restart loop. I disabled driver signature enforcement, and then I was able to get into Windows after that. I then followed some advice to put these commands into Powershell(admin):

Repair-WindowsImage -Online -RestoreHealth
and press enter
Then type SFC /scannow
and press enter

And restarted. After restarting, it just gave me the same bluescreen errors again. After this, I followed a friend's advice to enable ultra fast boot from BIOS. But after doing this, the computer would give me the same bluescreen, only now I couldn't use my keyboard or mouse, and can't get into BIOS, or do anything for that matter.

Any advice? Thanks in advance.
 
Sort by date Sort by votes
Is there a way to reset BIOS without KB+M?

I'm currently away from my PC atm so I can't currently submit my specs, but will later.
I haven't tried repairing via ISO, no. When/if I get my PC to recognize my keyboard, I'll give that a shot.
 
Upvote 0 Downvote
Once you get your BIOS reset (just pull the battery for 1min and press the Power button a few times to drain the capacitors), disable all Startup items in Windows.

The idea that Ultrafast boot or disabling driver signature enforcement was the route to take here is wrong for a few reasons.

It SOUNDS like a software issue, so again, disable all the things meant to startup with your computer. You can do this in Task Manager via the Startup tab.

Then, if it still BSOD's after rebooting once the startup items are cleared, you can try using a different user account. This is to check if it's something with the user profile.

If that new user account is also rebooting, it's time to start pulling memory sticks and testing them one at a time, because it's likely a hardware issue.
 
  • Like
Reactions: Maxzloch
Upvote 0 Downvote
I reset the CMOS and that worked! Now I'm back to the infinite restart loop again. However, the Driver Signature Enforcement trick no longer works, and I'm back to square one.

As for specs:

AMD Ryzen 5 3600 3-core Processor
650 watt Mag A650BN MSI PSU
B450 Steel Legend p2.90 Motherboard
Geforce RTX 3060 GPU
2 sticks of 8gb DDR4 RAM
1tb HDD
Samsung SSD980 SSD

As best I can get from BIOS, looking in the case, and memory.
 
Last edited:
Upvote 0 Downvote
brandonjclark said:
Once you get your BIOS reset (just pull the battery for 1min and press the Power button a few times to drain the capacitors), disable all Startup items in Windows.

The idea that Ultrafast boot or disabling driver signature enforcement was the route to take here is wrong for a few reasons.

It SOUNDS like a software issue, so again, disable all the things meant to startup with your computer. You can do this in Task Manager via the Startup tab.

Then, if it still BSOD's after rebooting once the startup items are cleared, you can try using a different user account. This is to check if it's something with the user profile.

If that new user account is also rebooting, it's time to start pulling memory sticks and testing them one at a time, because it's likely a hardware issue.
Click to expand...
I don't think I can get to Task Manager now as Windows is just giving me the Bluescreen again and the limited menu of options I had before, unless there is a way to get to Task Manager from the recovery screen.
 
Upvote 0 Downvote
This:
IMG_3209.jpg

Followed by this:
IMG_3208.jpg


I would really prefer not to reset windows. Again, I cannot get into the OS to do any changes or save my files, save for when I disabled driver signature enforcement and entered those commands into powershell, after which I could not get into Windows anymore.
SkyNetRising said:
Can you show a photo of this Bluescreen?
(upload to imgur.com and post link)
Click to expand...
 
Upvote 0 Downvote
The first one is:

the Operating System cannot load due to a missing file, hardware problems, damaged sectors, and corrupted files and applications.

The second one is:

This error occurs when a critical process, such as WinLogon (winlogon.exe) or the Client Server Run-Time Subsystem (csrss.exe) fails.

At this point you'll have to pull the hard drive, plug it into a different computer, save all of your files from it, move the hard drive back into the computer, and reinstall windows.
Although if you don't have another computer you're out of luck there.
Or, if you somehow manage it, fix the computer via the recovery tools, which probably won't work.
 
Upvote 0 Downvote
SkyNetRising said:
How did you prepare the drive with windows iso on it?
Did you just copy iso file onto it?

That's not the correct way.
Either use windows installation media creation tool or
use rufus.
Click to expand...
I did do that. However, I can't get to the recovery environment now, as it just gives me the BSoD that I've posted every time I hit the recovery environment option.
 
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