Jump to content

I/O not recognized after boot when windows loads up

Go to solution Solved by adithyay328,

Yeah, the BIOS update probably just screwed with the OS. I would reinstall windows, since BSOD means that windows had a bad time loading. So yeah, reinstall would be my path forward.

Also posted this in troubleshooting, but no replies yet...

 

So I have an issue with my updated system. I've essentially updated everything, but the drives and GPU. System booted fine when all the parts were first installed, but after updating the bios from VER 0401 to VER 1401 there have been issues non-stop. Even after reverting the BIOS to 0401 again the same issue persists.

 

Keyboard and mouse are not recognized after passing bios and loading to windows lock page. As soon as the windows logo pops up for loading my keyboard and mouse turn off and don't turn back on leaving me unable to do anything. I/O works perfect in bios without a hitch. I have a feeling this is something on the OS side of things since I only have issues when within the operating system environment. 

Errors seen so far:

- Un"___"able boot device (BSOD) [triggers after going to windows twice unsuccessfully]

- Overclocking error (bios screen) [this one happens after BSOD loop five times]

 

Fixes tried:

- Windows reset in advanced troubleshooting. I get through windows boot and lock screen with ease and everything appears to be perfect, but restarting system brings about same errors.

- BIOS update and flashback. Both make no difference it seems, but did work without error each time.

 

System:

i76800k (no overclock)

x99 asus strix gaming

32gb ddr4 gskill trident z 3200MHz (running at stock 2133 for troubleshooting)

gtx 1070 asus strix

240 GB SSD as boot drive

Windows 10 64-bit Educational

- I've reset windows 3 times now to no avail, but have not done full reformat

Evil exists where good men fail to act.

Link to post
Share on other sites

6 hours ago, adithyay328 said:

Yeah, the BIOS update probably just screwed with the OS. I would reinstall windows, since BSOD means that windows had a bad time loading. So yeah, reinstall would be my path forward.

That's what fixed it, but I was under the impression that resetting Windows did the same thing without getting rid of my files. I guess I was wrong...

Evil exists where good men fail to act.

Link to post
Share on other sites

11 hours ago, Aukmed42 said:

That's what fixed it, but I was under the impression that resetting Windows did the same thing without getting rid of my files. I guess I was wrong...

Ok them. Well, you learned how to fix it! Congrats!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×