Mobo: Gigabyte 7TESM
OS: Win 10 Pro
CPU: Dual Xeon X5650s
I’ve been dealing with this problem across two different motherboards. I understand it is an astronomically small possibility this happened back to back and am open to hear ideas.
At POST, I need to press F2 to enter BIOS. The system does not respond to keypresses. Once POST is over, PXE begins, followed by my onboard SAS initializing. Keypresses work fine at both of those screens. Enter Windows 10. Keyboard works without issues. What’s interesting to me is, when I’m pressing F2 at PPST, if I hold the button down, or press multiple buttons, the RAM counter spins slower or stops, so it’s recognizing keys are being pressed. If I press too many keys, it’ll beep after POST like I’ve pressed too many keys (I did ensure these weren’t warning beeps from my mobo, it only happens when I press a lot of keys)
Testing outside of the case worked without issue.
Here’s what I’ve tried so far:
Three keyboards. Two USB, one PS/2.
Making sure no other USB devices are plugged in.
Tried each keyboard on each onboard and front panel USB port.
Disconnecting the USB header and trying the onboard USB ports individually
Resetting CMOS (on both boards more than once)
Unplugging SSD with my OS on it (grasping straws here)
Removing my graphics card.
Inspected both CPU sockets for bent pins
Ensured standoffs were tight and mounted correctly.
I keep hearing it might be a short - but can a short cause a specific problem at a specific screen that isn’t impacting any other function after that screen or process is over? Is it astronomically perfect timing that it only has an issue at POST?