Wow....I did not realize just how many of you actually had this motherboard!
Based on the string length here....and the 20 or 30 separate email I've
gotten just in the last hour and a half......its seems this mobo is more
prolific among the sim community members than I realized. I guess this
makes sense....since it accommodates the P3 Intel chips from around 450 to
800-1000 mHz. That's probably were a lot of you are at....if you have not
upgraded your systems yet for N4 or for a GF3 video card.
This "bug" is real....and it is prolific on all the ASUS P3V4X
boards......running BIOS 1.005 or 1.004, or 1.003. There is this mysterious
BIOS version 1.006 (not on the ASUS website)....that some of you have. If
you have this BIOS version....you don't have the bug. Therefore, it would
be reasonable to assume that it was fixed on this BIOS version.
If you want to confirm you "have the bug" or don't....here's a procedure
that works well:
1. Try to run any "video memory" intensive application....3DMark2000 is a
good one (not 3DMark 2001...unless you have a GF3 video card...only!). This
"bug" exists with all video applications (WMP 7.1 for example).....but you
may not have noticed your mpegs running slow....or unless you run a lot of
them back-to-back...you may have not encountered a system crash. In my
case, the bug is bad enough that I can't even run GPL on this system. What
happens, is when selecting a "track"....GPL tries to initialize the replay
system. That is a video application and windows (on my system) says to
GPL....."I have no memory to allocate to that function." ....so GPL reports
the error, "Can Not Initialize Replay System.....aborting race weekend!"
2. If when attempting to run 3DMark2000 benchmark....you get a bad score,
slow FPS or a crash/abort on the first texture screen load......then go to
the next step.....which will confirm the problem is this ASUS mobo "bug."
3. After a video crash...if you can recover to your desktop.....do so! If
not....shutdown and reboot....let scandisk run and take you back to your
desktop. In either case, once back to your desktop...perform the following
procedure: Hold down the Shift key....permanently. Then, go to "Shut
Down - Restart" ....still holding down the shift key. When the screen says,
"Returning to Windows........" you can release the shift key and the system
will boot normally to your desktop. Now run 3DMark2000 again......you
should find you get either "no crash"....or a much higher score! If this
happens...you have the "bug."
I have no clue "why" holding down the shift key works to get around this
bug. However, I do remember having to do this with some of the "crashes" we
used to get when I was beta testing Internet Explorer 4.0 for MS a few years
back (something about IE not releasing resources after a crash). My
"guess"....and this is only a guess....is that holding the shift key forces
Windows to poll the devices on the mobo......and get a "report" from
them....not just accepting the BIOS generated report during a normal boot up
sequence. If we have some Windows gurus among us....maybe they could shed
some light on this for us?
I'm now going to go attempt to flash the EPROM on this mobo....and see if
this fixes this bug! Of course, then I'd still have the unstable AGP4x
issue to deal with! Nice mobo ASUS....got anymore like this one? I'd want
three more please........that way I'd have "one" to bury......and the other
two to use as "dirt" to cover up the first one! .......lol......
See ya....
Tom