ASUS A8N32-SLI Deluxe and the Microsoft Natural 4000 keyboard problem (Memtest related)

UPDATE: I’M A FREAKING ‘TARD!!!!!!!!!!!!

On Friday I thought I had updated my A8N32’s BIOS to the newest available, 1303, but for some odd reason I downloaded the 12xx version and flashed it to that.  Sure enough, after troubleshooting all weekend,  and all of today, ready to give up and admit defeat, I go to attempt to downgrade the BIOS thinking I had the 1303 installed but what do I see?  I see that my current BIOS is the 12xx version and the one I plan to supposedly downgrade to is the same 12xx.  To make a long story short, I did not flash to the newest 1303.  After flashing to 1303 the Natural 4000 works fine in Memtest.  I also do not have to disable APM anymore.  I can boot into Windows with no problems whatsoever.  Take that!!!!!!!!!!!!!!

ASUS A8N32-SLI Deluxe and the Microsoft Natural 4000 keyboard problem.

My motherboard and PSU failed due to an earthquake so I went out and bought a new mobo, CPU and PSU.  I bought the ASUS A8N32-SLI Deluxe and an Athlon 4400+ 89w X2 CPU and a Seasonic M12-700W PSU.

I put everything together and once experienced a random lock up.  The last time this happened it was due to a bad stick of memory.  I threw in Memtest and fired her up.  I noticed I could not change the settings to specify which test I wanted to perform using my Natural 4000.  After posting on a few message boards and newsgroups, I finally received a reply from someone on the official ASUS.com forum.  He said:

“Hi , I had the same problem with same keyboard this is what i did :- disable legacy usb disconnect your keyboard and connect a ps/2 then you can access memtest options ,when you installed windows you should have disabled the usb until  os was installed it caused me loads of problems with the acpi now i can use my keyboard in windows with or without legacy usb and it does not crash my system anymore”

So it’s safe to assume that this keyboard and motherboard combo doesn’t like to play nice unfortunately.  Just thought I’d post this just in case someone else in the future decides to try and fix this problem and can’t seem to fix it.