- Joined
- Apr 7, 2016
- Messages
- 12
- Reaction score
- 2
I have a desktop PC running Windows 10 v1809, OS build 17763.134 on a Pentium G4400 CPU, with 8Gb RAM.
A while ago, I had a problem with the system going erpeatedly but randomly into an unresponsive state with minimal CPU activity and minimal disk activity - it appeared to be too busy to respond to input, but it also appeared to be doing nothing, according to Task Manager. It was a puzzle, but thankfully now that problem has gone away, without any relevant changes being made. That is also a puzzle, but not central to my enquiry, except in that it led me to try to reboot into safe mode.
I eventually worked out how to boot into safe mode, the most straightforward being "shutdown /r /o", but when I got there, I found that the keyboard was inactive - I couldn't select the safe mode option, for lack of command input.
This reminded me that I have never been able to interrupt a boot with any key on the keyboard - <ESC>, F2, <return>, whatever - to get in to the BIOS environment. I wonder if these two observations are connected, because in neither case does the <NumLock> LED come on, as it always does at some stage in the normal boot process, after which the keyboard is active.
For information, the USB plug for the keyboard is plugged directly into the motherboard USB socket array on the backplate of the system case, not through any USB hub connections, unless internal. The keyboard is a standard Dell USB component that I have used ever since my PC was a Dell Inspiron, about 300 years ago, although the motherboard is a more recent MSI MS-7982 with Pentium G4400 CPU @ 3.30GHz.
Can anyone throw any light on this conundrum? How can I make the keyboard active from the very start of the boot process? Might a keyboard with a PS2 connection behave any different?
A while ago, I had a problem with the system going erpeatedly but randomly into an unresponsive state with minimal CPU activity and minimal disk activity - it appeared to be too busy to respond to input, but it also appeared to be doing nothing, according to Task Manager. It was a puzzle, but thankfully now that problem has gone away, without any relevant changes being made. That is also a puzzle, but not central to my enquiry, except in that it led me to try to reboot into safe mode.
I eventually worked out how to boot into safe mode, the most straightforward being "shutdown /r /o", but when I got there, I found that the keyboard was inactive - I couldn't select the safe mode option, for lack of command input.
This reminded me that I have never been able to interrupt a boot with any key on the keyboard - <ESC>, F2, <return>, whatever - to get in to the BIOS environment. I wonder if these two observations are connected, because in neither case does the <NumLock> LED come on, as it always does at some stage in the normal boot process, after which the keyboard is active.
For information, the USB plug for the keyboard is plugged directly into the motherboard USB socket array on the backplate of the system case, not through any USB hub connections, unless internal. The keyboard is a standard Dell USB component that I have used ever since my PC was a Dell Inspiron, about 300 years ago, although the motherboard is a more recent MSI MS-7982 with Pentium G4400 CPU @ 3.30GHz.
Can anyone throw any light on this conundrum? How can I make the keyboard active from the very start of the boot process? Might a keyboard with a PS2 connection behave any different?