New
#1
Keyboard + mouse not functioning past BIOS following CPU+MB upgrade
This is NOT the usual problem encountered with an upgrade. I've read previous posts regarding similar (but not identical) issues; this one, for example. My problem is just different enough I felt it warranted it's own post.
BACKGROUND
Upgraded from a previous custom computer built in 2010 following progressively creeping failures. Bit the bullet, ponied up the money, and upgraded the CPU, motherboard, RAM, and power supply (detailed specs at the bottom of post).
Kept the existing GPU as well as the SSD as it has legacy software that I still use regularly but have no way of replacing were the SSD to be reformatted. A clean install of Windows 7, wiping the drive, is NOT an option.
PROBLEM
Successfully installed all hardware. I am able to power on the computer and it POSTs. When it gets to the point where Windows starts to load, it goes to a black and white screen where the options are "Startup Repair" or "Start Windows normally".
If I choose "Start Windows Normally", it attempts to load Windows but then crashes to a BSOD for a split second before going black. I was able to capture the BSOD error message by recording it with my cell phone. If it's felt it's of use, I can type out the message in full. Just let me know.
If I choose "Startup Repair" it loads to the appropriate screen and remains stable. Unfortunately, at this point all input from both the mouse and keyboard is ignored. There is no way to move beyond the initial "Startup Repair" screen at this point. Shortly I will cover in detail what I've already attempted to do to fix the issue (pretty much what all the other posts I've read have suggested; but there's a twist).
I've also attempted to boot from the DVD drive using my original Windows 7 Professional 64-bit disk. I get the same result as "Startup Repair"; as soon as the very first screen appears asking what language to use for the install, it stops accepting input from the mouse and keyboard.
ATTEMPTED SOLUTIONS
The motherboard has two USB 2.0 ports on the rear along with four USB 3.2 Gen 1 and one USB 3.2 Gen 2 ports. The case has two USB ports on the front. It's a Cooler Master case from 2010; I don't know what version of USB but I assume USB 2.0.
Here's where my problem differs from the others I've read about in the other posts. Unlike those other posters where their new motherboard had only USB version 3.x ports, mine actually does have the two USB 2.0 ports on the rear (and likely the front, too). So my problem is NOT that the ports have no driver support from Windows 7 (at least as far as I understand it from reading those other posts stating Windows 7 supports USB 2.0). So it would stand to reason the two USB 2.0 ports on the rear shouldn't have any problem accepting input from the USB mouse and keyboard I've plugged into them. And, yes, the mouse and keyboard do work as evidenced by the ability to navigate my BIOS menu using them.
Yet here I sit unable to use the mouse and keyboard once arriving at any Windows screen. Just to rule out all possibilities, I've plugged the mouse and keyboard into every USB port in every combination possible in conjunction with attempting to boot from the Windows 7 disk as well as the "System Repair" and "Start Windows Normally" options mentioned previously. I've even unplugged/re-plugged them in while at the Windows 7 Install / System Repair screens as some of the posts suggested as a fix; still nothing.
I could revert to my old hardware setup if I have to as a worst-case scenario / last-ditch effort to make changes to my current Windows 7 install - such as installing some additional drivers or whatever - before making another attempt at getting the new hardware setup to work. However, I would prefer to avoid that scenario if possible.
As mentioned previously, though, what is NOT an option is wiping the SDD and starting over from scratch with a new/clean install of Windows 7. I don't have any other HDD, SDD, or other media on which to backup my data. Yes, yes, bad practice; but also water under the bridge in that being chastised about it doesn't get me any closer to a solution to the current problem.
In those other posts, I've read suggestions to use Paragon Adaptive Restore 2010 to fix similar issues. Would that apply to the trouble I'm experiencing? I have a family member with a computer on which I could download and burn to DVD the Paragon Adaptive Restore 2010 app if necessary.
BIOS SETTINGS (I've included those which seem pertinent to this issue)
Boot Option Priorities:
Boot Priority #1 = Pioneer BD-RW optical drive
Boot Priority #2 = WDC WDS100T2BOA-OOSM50 SDD
Boot Configuration:
Fast Boot = Disabled
Boot NumLock State = On
USB Configuration:
USB Device Enable = Enabled
Legacy USB Support = Enabled
XHCI Hand-off = Enabled
CSM (Compatibility Support Module):
Launch CSM = Enabled
Boot Device Control = UEFI and Legacy OPROM
Secure Boot:
OS Type = Other OS (only other choice is "Windows UEFI Mode")
SYSTEM SPECS (Legacy hardware noted where applicable)
OS = Windows 7 Professional 64-bit (already installed on current SDD)
CPU = AMD Ryzen 7 3700X
GPU = ATI Diamond Radeon HD 5850 (Legacy from 2010)
Motherboard = ASUS TUF Gaming B550-Plus, Version: 1202
SSD = Western Digital Blue 3D NAND 1TB Internal SSD - WDS100T2B0A (Legacy from 2018; Windows 7 Professional 64-bit SPK1 already installed)
RAM = Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3200MHz C16 Desktop Memory Kit
Power Supply = ASUS TUF Gaming 750W Bronze PSU
Mouse and Keyboard = Cheap USB-cable mouse and keyboard backups reserved for just this type of situation (they worked when I helped a family member through a Windows 10 install when their own wireless mouse and keyboard weren't being recognized). Up until now I've used a wireless Logitech mouse and wireless Microsoft keyboard, but they weren't working for my own hardware upgrade; so I reverted to the cheap, direct-connect backups (which aren't working, either).
Thank you in advance for any assistance anyone can offer. I've been a week now without access to my computer trying to resolve this issue without success. Hopefully someone out there has a solution.