the dreaded nforce4/diamondmax10 problem

[xtknight]

ok, i decided to update to the latest bios from asus's website just to see if this problem is gone. even the a8n-sli deluxe last beta 1012.003 didn't fix it. has this problem been resolved by some other way to this day? all i can do is shut my pc off completely and turn it on in a couple hours and hope it turns on. writing from my old p4 now. also it happened right after my pc crashed, probably due to me changing command rate to 1t from its default 2t...

also my PC takes quite a bit longer to boot even when the hard disk was detected under the new BIOS. what gives?

 

[mattburk]

I had the same problem. Not too impressed with all the glitches.
I uninstalled the nvidia ide drivers, and now my maxtor works fine. Did you do that yet?

 

[xtknight]

Originally posted by: mattburk
I had the same problem. Not too impressed with all the glitches.
I uninstalled the nvidia ide drivers, and now my maxtor works fine. Did you do that yet?

First I turned it off for about 10 minutes, then I flashed to 1001 from a CD and Windows 98 startup floppy. All is well...sort of. Before that I tried to flash to 1008 and got graphics glitches when trying to do safe mode in WinXP.

Looks like I'm stuck using the very BIOS my board shipped with originally (1001). This board is starting to piss me off. So I flashed it to 1001, and am using the accelerated NVIDIA SATA drivers and everything's fine. Guess this gives new meaning to 'if it ain't broke, don't fix it'. But, it was broke. The PCI-E locks didn't work on the original BIOS. Oh well I guess I won't be overclocking this thing.

Also half the time it doesn't show any graphics until Windows is at the login screen. :roll: Occasionally the graphics glitch, pre-Windows, also.

With 1008 bios nvcchflt and nvatabus drivers failed and BSOD'd windows. I tried disabling them and Windows wouldn't boot at all so I flashed to 1001 BIOS and I could boot into safe mode without graphics glitches then I uninstalled, reinstalled NV SATA drivers.

The odd thing is, it worked absolutely flawlessly until I decided to update my BIOS to 1012.003 beta, or any other BIOS for that matter, even 1002.