cancel
Showing results for 
Search instead for 
Did you mean: 

Formula V problems for me - Keyboard Problems

Retired
Not applicable
OK just got my Asus Formula V board in along with 16Gig of Muskin RedLine 2133 (17000) memory and a FX-6100 6 Core 3.3 processor.

First attempt at boot didn't work because the processor apparently didn't make a connection on one of the pins. Re-Seated it and now it works.

I've only played with this setup for about 4 hours last night trying to get the keyboard(s) to work after boot to grub or any first boot process.

Let me give you some info on the situation.

I have a Knoppix 6.7.1 boot USB flash stick that I use for general computing. Put it in and all works well. Except that I can't type in "knoppix64" at the boot prompt. Yet the keyboards that I have all work correctly after it gets to asking for my encryption password. Yet sometimes it will let me type it here, about 1 time out of 15 reboots. But only on this Knoppix flash drive and sometimes in grub.

One keyboard is a Logitec on the small round connector. The other is a cheap MSI keyboard on a USB connector. Both behave exactly the same.

Trying to boot from the Windows Vista 64 (Home Premium) to do a few tests and I cannot get it to accept pressing a key to boot from DVD. It will boot the DVD if I unplug the hard drives. Then DVD boots but then you can't install because you don't have the hard drives plugged in.

I've tried turning off the over-clocking settings as best as I can but it seems the board insists on trying to run the processor at 3.6GHz. But it works fine from the Knoppix 6.7.1 flash drive, so I'd think that is not the problem.

So far, I get the best results from loading Optimum Bios settings and change only a few things like "no logo screen" and maybe boot device order if I need to change them.

Some other things to know. My Bios Version is currently at 705. I have downloaded the newest Bios but haven't flashed it yet.

Another test from knoppix is memtest. It gets to about 2% on the first run and locks up. But no errors are shown. This can be a real clue as to what might be the problem. I may swap around some of the memory chips around or take two out and see if I can get it to run normally with only two chips (8 Gig).

By the way, my video card is a PNY GTX-470 (Nvidia).

Any extra clues you guys can send my way are greatly appreciated.
12,560 Views
21 REPLIES 21

Detection
Level 10
UEFI BIOS is a buggy piece of crap, my Wireless logitech keyboard worked fine with a 30 year old BIOS technology, pressing DEL to enter UEFI freezes the entire system

Seriously considering RMA on this board
MOBO - Crosshair V Formula
CPU - AMD FX-8350 @ 4.8GHz
COOLER - Corsair H100i / MX-4
RAM - 12GB G.Skill RIPJAWS X @ 2133MHz
GPU - XFX R9 295X2 8GB
HDD - 2TB Seagate
PSU - Corsair TX950W
CASE - Coolermaster HAF 922
OS - Windows 8.1 Pro 64bit

Retired
Not applicable
OK, just to post an update...

I've kind of narrowed down some of the keyboard problems. It appears that even the round connector is simply an adapter on the USB controller somehow.

My problems seem to be coming from other devices that I have plugged into other USB ports on the back of the board. Un-plugging steering wheels and joy sticks and extra drives I've managed to get a keyboard input most times now.

I did update my BIOS to 903 now. Although it doesn't seem to help the USB/Keyboard problem for me. But the system is actually running at proper speed now. 3.3 MHz for a FX-6100. I don't care to over-clock it at the moment. I just want to get the system running.

I'm typing this on the Formula V system with the FX-6100 now. But I'm still booted into Knoppix 6.7.1. It looks as though I'm going to have to re-install Windows Vista 64 Home Premium for my games (which is why I bought this system in the first place).

I did manage to run the memory test to completion on the Vista install disc. But my system will still not run memtest-86 v3.5 from Knoppix. It locks up at 2% complete every time. The Microsoft memory test didn't show any errors for a complete run. So I feel confident the memory is OK.

I don't have any red LEDs lit on the board as it is running. But during boot, I get a message of something like "Can't Find Any Device." This is before the screen showing you hard drives found and whatnot. You'd think they would put a bit more description in that.

I'll update the thread again on my progress as I get the system game ready.

Detection
Level 10
Don't put Vista on that board 😞

Install 7 and at least give it some respect ! 😉
MOBO - Crosshair V Formula
CPU - AMD FX-8350 @ 4.8GHz
COOLER - Corsair H100i / MX-4
RAM - 12GB G.Skill RIPJAWS X @ 2133MHz
GPU - XFX R9 295X2 8GB
HDD - 2TB Seagate
PSU - Corsair TX950W
CASE - Coolermaster HAF 922
OS - Windows 8.1 Pro 64bit

wolfy
Level 8
there are a few having this problem when connecting other USB devices it stops finding the keyboard
i had the same problem and narrowed it down to one of my devices if i unpluged it then every thing was ok
if i plugged it in then no keyboard on boot just in windows
there does not seem to be a fix as of yet .
i brought a new Keyboard (logitech) and the problem has gone away old keyboard was a Saitek.
i have had the last 2 series of crosshair but must admit this V seems to be givin lots of probs.
cant fnd any device is because its looking for a device connected to the sata E1 on your board turnthat option off in the BIOS
if you have nothing connected it then goes away (option ASM1061 OPROM in bios to disable)
ROG MAXIMUS XI FORMULA
CPU: Intel 9900K @4.7 ghz
2 x Corsair Vengeance RGB PRO DDR4-3200
C16 BK DC - 16GB
1 x Aurous 2080Super 8GB
1x 500GB Samsung 980 M.2 NVMe
1x 500GB AData 8200pro M.2NVMe
2 X 500 GB SSD
1000w PSU from corsair
Tower Lian Li PC-O11DW Dynamic
1 x dell 34" curved + 1 x 24"
CPU and Motherboard.
NZXT Kraken X73 RG

DocLotus
Level 9
I also had a LOT of non responsive keyboard problems with my CHV until I discovered that the top two USB connectors (next to the round PS2 connector) are USB3. When I move the keyboard down to the next set of USB2 connectors the keyboard became much more reliable. Seems CHV has a slight problem (sometimes) loading the third party USB3 drivers.

After Windows boots up, USB3 is usually OK so I make sure to only plug in devices that are not needed early on.

Even doing this, I still sometimes have a non-responsive keyboard early in the boot process. In my case it was not the keyboard (tried three of them) but CHV.

Either way, having the keyboard on a USB2 port helps but does not totally resolve the problem.

I agree with some others who have have said the CHV is a little too touchy; but, once you have it up and running it is great.

Think of it as a touchy, finely-tuned, high-spirited Italian sports car; loads of fun to drive but a pain to maintain.


Doc
Retired... and Loving it :cool:

DocLotus wrote:
I also had a LOT of non responsive keyboard problems with my CHV until I discovered that the top two USB connectors (next to the round PS2 connector) are USB3. When I move the keyboard down to the next set of USB2 connectors the keyboard became much more reliable. Seems CHV has a slight problem (sometimes) loading the third party USB3 drivers.

After Windows boots up, USB3 is usually OK so I make sure to only plug in devices that are not needed early on.

Even doing this, I still sometimes have a non-responsive keyboard early in the boot process. In my case it was not the keyboard (tried three of them) but CHV.

Either way, having the keyboard on a USB2 port helps but does not totally resolve the problem.

I agree with some others who have have said the CHV is a little too touchy; but, once you have it up and running it is great.

Think of it as a touchy, finely-tuned, high-spirited Italian sports car; loads of fun to drive but a pain to maintain.


Doc



Thanks for that, I had no idea the top USB ports were USB 3.0 either, I assumed only the Blue ones further down were the only USB 3.0 ones

I`ll give my keyboard a go in the USB 2.0 ports next time I reboot and see if I can get in the BIOS that way

That would also explain why I had no mouse during Windows setup !
MOBO - Crosshair V Formula
CPU - AMD FX-8350 @ 4.8GHz
COOLER - Corsair H100i / MX-4
RAM - 12GB G.Skill RIPJAWS X @ 2133MHz
GPU - XFX R9 295X2 8GB
HDD - 2TB Seagate
PSU - Corsair TX950W
CASE - Coolermaster HAF 922
OS - Windows 8.1 Pro 64bit

Retired
Not applicable
OK, another update for the curios.

I'm up and running 100% to what I want now. I bought me a copy of Windows 7 Home Premium (not the upgrade) to put on this brand new system. After I got it up and running I decided to over-clock just a bit...

CPU FX-6100 (3.3 GHz) now at 3.6 GHz

Mushkin 17000 (2133) 16G is now running at 1800.

All seems fully stable and have not had a single crash.

Games are smooth as glass now.

I'm happy till some future game comes along that shows some choppy. 😉

Good luck guys, seems to be a good purchase now after the 903 BIOS.

Detection wrote:
Thanks for that, I had no idea the top USB ports were USB 3.0 either, I assumed only the Blue ones further down were the only USB 3.0 ones

The manual identifies the rear USB ports and correctly shows that the ports below the PS2 connector are USB3.

DocLotus wrote:
I also had a LOT of non responsive keyboard problems with my CHV until I discovered that the top two USB connectors (next to the round PS2 connector) are USB3. When I move the keyboard down to the next set of USB2 connectors the keyboard became much more reliable. Seems CHV has a slight problem (sometimes) loading the third party USB3 drivers.

After Windows boots up, USB3 is usually OK so I make sure to only plug in devices that are not needed early on.

Even doing this, I still sometimes have a non-responsive keyboard early in the boot process. In my case it was not the keyboard (tried three of them) but CHV.

Either way, having the keyboard on a USB2 port helps but does not totally resolve the problem.

I agree with some others who have have said the CHV is a little too touchy; but, once you have it up and running it is great.

Think of it as a touchy, finely-tuned, high-spirited Italian sports car; loads of fun to drive but a pain to maintain.


Doc


Simple fix, to me was.
Just moveing my mouse same time as i press DEL to enter the BIOS.

Works every time with all my keyboards. If i forget to move mouse, i hardly ever get in my BIOS. BIOS version havent change it at least yet, 9920 now.
CPU: AMD FX-8150 MB: ASUS Crosshair V Formula DDR3: 2x4GB G.Skill Sniper DDR3-1866
GPU: ASUS 7970 SSD: 4x Corsair F3 120GB @ Raid0 PSU: SF Golden Silent 500W OS: W7 Ultimate 64bit