[IvantheDugtrio]

Ever since I got this keyboard I've had issues testing it on my AMD systems. Usually when I plug it in the computer wouldn't recognize it at all and the keyboard would stay off. Then when I reboot the system after a long while the keyboard would be recognized by the BIOS but not by Windows. The keyboard works perfectly fine on my Intel systems.
Then I found out that it works fine when I plug it into a USB hub rather than directly into the computers. Still that doesn't solve my main issue.

I have an FX-6300 build with a Biostar A880GZ with 8GB of crucial ballistix low profile memory (1600, 8-8-8-24) running Windows Server 2012 Standard and every time I boot up the system freezes and shuts down the monitor/keyboard but keeps running. I started having this issue the moment I tried using the Cooler Master keyboard and even after swapping keyboards it still does this. Reinstalling Windows seems to be the only fix. The strange thing is that I had the Cooler Master keyboard connected the whole time I was setting up Windows and everything worked fine until after the first boot. Then this issue would start and the only way to boot into the installation is in safe mode. In there I don't find any clues as to what caused it.

On another note I also noticed that the motherboard is running my memory at 1333, 9-9-9-24 timings at 1.5 V versus the stock 1600, 8-8-8-24 1.35 V. I'm guessing the motherboard does not support low voltage memory like this.
Still I confirmed that the memory has nothing to do with this issue by swapping it with older memory and it produced the same problem.

 

[BeastRider]

Have you tried reinstalling Windows with a totally different keyboard and not plug in your quickfire at all? My quickfire sometimes has issues being detected by Windows but a quick replugging of the mini-USB to the KB itself fixes the issue, nothing that would cause my Windows to not boot up though. There seems to be a problem with the mini USB sockets on these keyboards.

 

[IvantheDugtrio]

Quote:

Originally Posted by BeastRider

Have you tried reinstalling Windows with a totally different keyboard and not plug in your quickfire at all? My quickfire sometimes has issues being detected by Windows but a quick replugging of the mini-USB to the KB itself fixes the issue, nothing that would cause my Windows to not boot up though. There seems to be a problem with the mini USB sockets on these keyboards.

I've tried that before and it worked fine until I plugged the quickfire in. My instinct to get it working when it wouldn't connect was to reboot and that's when the system would freeze at boot up and shutdown the display/keyboard but keep running.

I wonder if it's a Catalyst 13.8 glitch. I've tested this with a HD 7750, HD 5570, and integrated HD 4250 and they all do this.

 

[IvantheDugtrio]

So I installed Windows from scratch and got around installing everything I needed. The ethernet controller stopped working for whatever reason (poor quality board) and I successfully managed to reboot several times until I got to the graphics drivers.
I installed Catalyst 13.8 successfully but the reboot had issues. Firstly the system would boot up but after I logged in it looked like I had a kernel panic or something and the fans kicked in at full speed. I soon got to the BIOS screen where the board beeped 6 times with the POST code "DB". It then rebooted successfully and is working stably again.
I'll later plug the CM keyboard in and see what happens.

 

[BeastRider]

Quote:

Originally Posted by IvantheDugtrio

So I installed Windows from scratch and got around installing everything I needed. The ethernet controller stopped working for whatever reason (poor quality board) and I successfully managed to reboot several times until I got to the graphics drivers.
I installed Catalyst 13.8 successfully but the reboot had issues. Firstly the system would boot up but after I logged in it looked like I had a kernel panic or something and the fans kicked in at full speed. I soon got to the BIOS screen where the board beeped 6 times with the POST code "DB". It then rebooted successfully and is working stably again.
I'll later plug the CM keyboard in and see what happens.

Sounds like a whole nother issue you got there rather than just the keyboard. Is it too late to RMA your bpard? Seems to me that the issues are coming from your main board.

 

[IvantheDugtrio]

I just rma'd it two weeks ago and all this happened. Now I'm rma'ing it again because the Ethernet controller died. I hope I get a different board when it comes back.

 

[BeastRider]

Quote:

Originally Posted by IvantheDugtrio

I just rma'd it two weeks ago and all this happened. Now I'm rma'ing it again because the Ethernet controller died. I hope I get a different board when it comes back.

Yes good luck with that. Is this the Intel board or the z77 extreme4 based on your rigs? I hope it's not the extreme4, this is the same board I'm using. lol Nevermind it's an AMD board so I guess it's neither. How many rigs do you have?? lol

 

[IvantheDugtrio]

Quote:

Originally Posted by BeastRider

Yes good luck with that. Is this the Intel board or the z77 extreme4 based on your rigs? I hope it's not the extreme4, this is the same board I'm using. lol Nevermind it's an AMD board so I guess it's neither. How many rigs do you have?? lol

lol I have too many now.

First I made the NES rig and then the Home Server rig which already had its motherboard swapped. This was temporarily my mom's rig that I put together using older parts when I was transitioning my Athlon II 640 from DDR2 to DDR3. Then I got the FX-6300 when I was browsing through microcenter (couldn't resist). So essentially I have three rigs, one of which stayed dead for a good six months until it decided to turn on (the NES), and the other which I take to my friend's lan as a loaner PC.

I've dubbed it the Franken PC because of all the extra parts I had around to build it with. Eventually I decided to put money into it and got a proper cooler and memory for it. Still deciding on the power supply (currently stock Rosewill PSU that came with the case).

It's too bad the case doesn't support ATX motherboards since I would have gotten one of those instead of dealing with this crap. I like it's size since it's low profile though it could be even smaller. I'll just have to wait for a mini-ITX AM3+ board to come about for a properly sized FX-6300 rig with sideways 7870 or some other GPU.

By the way we are using the same ASRock motherboards. I have to say I definitely like mine. I had it stable at 4.5 GHz for a really long time with a + 0.25V offset until some applications like [email protected] would crash.

 

[IvantheDugtrio]

So after getting a new motherboard (ASRock 990FX Extreme3) and CPU (FX-8320) I did the same test and unfortunately it had the same results as with the Biostar board.

First bootup after installing Windows worked fine but after that it would BSOD immediately after logging in. At least now it BSODs rather than freezing and shutting down the display.

I got lucky this time around since now after changing keyboards it hangs for a bit after logging in but eventually everything starts up normally and it is stable.

 

[IvantheDugtrio]

So upon further inspection of the BSODs I find out that it was coretemp bugging out and causing them.

I still find it odd that the crashes only coincide with when I plug the quickfire into the system and reboot.