Frustrating instability on new PC

OK, I've just built myself a brand new PC. First off, here are the specs:

ASUS A7V8X Motherboard
256MB PC3200 RAM (Corsair)
WinXP Pro (SP-1)
WD 80GB HD (special edition w/ 8MB cache)
Gainward GeForce4 ti 4200 (128MB ver.)
CL Audigy2 Platinum
Samsung 16X DVD-ROM
TDK VeloCD 48X CD-RW

The problem is I keep getting these strange crashes and so far I haven't been able to solve it. It usually happens when I'm multitasking. These crashes take on two different forms, but according to the event log they're caused by the same problem. Either:

1. My PS/2 ports disappear causing my mouse and keyboard to stop responding (rest of the system seems fine and I am able to recover by plugging in a USB mouse).

Or:

2. The exact opposite happens and my entire system stops responding but the keyboard and mouse is OK (you can click on things but there's no response). There is no graceful way out of this state and it always requires a hard reboot.

In either case, here is what the event viewer has to say:

"The device, \Device\Harddisk1\D, is not ready for access yet."

The BIOS and all relevant drivers have already been updated to the latest versions. I'm assuming it's hardware since I've already tried reformatting and reinstalling.

This thing is driving me bananas! Any ideas?

Thanks...

Run chkdsk and get the diagnostic program for your hard drive to check the installation. I have also seen bad ram cause this.

By relevant drivers I hope you also include the latest 4in1 drivers form VIA.

To quote Steve Martin, "Does the pope poop in the woods"? I'm paraphrasing of course! :D

Given the nature of the errors, those are the first drivers I tried. As a matter of fact, I just updated to the new Hyperion drivers (4.45) yesterday. No dice.

I'm with Noo Noo... I'm starting to suspect the RAM. I've been frequenting the ASUS forums and newsgroups and the A7V8X/Corsair pairing seems to be a troublesome combo for quite a few people. There may be a slight incompatibility there. I think I may try a different vendor.

New behavior -

Desktop icons and taskbar suddenly disappear and PC becomes totally non-responsive.

New error message -

"The instruction at "ox77F53B37" referenced memory at
"0x00000000".

The memory could not be "read"."

Same cause -

"The device, \Device\Harddisk1\D, is not ready for access yet."

Sure sounds like the RAM, doesn't it? Problem is I ran several complete passes of memtest86 and it came up clean as a whistle.

Because this is such a new motherboard with a new chipset, it's entirely possible that the hardware is fine, but I'm not sure and there lies the problem. Part of me says wait for a BIOS release and all will be solved, and another part says start the RMA process.

I'm really divided here (and more than a little confused), so any and all input would be GREATLY appreciated!

Thanks...

Run a thorough hard disk check too.

I had similar problems pop up a couple of weeks ago on my intel based system
I run a p 4 1.6 gig cpu on the Asus p4b 266, I have two sticks of ddr ram totaling 512 megs, One was a Micron stick the other was a generic stick
I also have a P3 1 gig system on the Asus cuv 266 board with a really cheap stick of ddr ram
I would reinstall XP home and run into problems, I ran memtest 86 and had no errors, I was thinking my power supply was at fault since my slave drive would not be detected the odd time
I pulled my promise controller and connected the drives to the mother board
My memory reported no errors on the Intel chipset but once I tested the two sticks on my cuv 266 ( via chipset )I have 402 errors on the micron stick and an address error on the generic
I tested the really cheap stick thinking my cuv 266 had a problem.
That stick passed the test
I installed it into my problematic computer alone, reinstalled Windows and it works fine now
If you can test your ram in another system, or Try another power supply

Like noo noo said "RAM" Ram Ram Ram!!! seen it 3 times now!!!!

RAM

Yes

RAM

This is what I suspected as well, so I guess it's unanimous.

It's pretty ironic though, that I've always gone the generic route as far as memory is concerned and never had a problem, and then the very first time I decide to spring for the good stuff (Corsair XMS) I wind up with a bad stick. :(

Quote:

---

Originally posted by mrwilhelm
This is what I suspected as well, so I guess it's unanimous.

It's pretty ironic though, that I've always gone the generic route as far as memory is concerned and never had a problem, and then the very first time I decide to spring for the good stuff (Corsair XMS) I wind up with a bad stick. :(

---

I know what you mean. Last year when I upgraded my system, I bought Crucial for the first time and within a couple months had one of the two sticks go bad on me. Was my first time buying namebrand RAM and had heard nothing but good about Crucial. Unfortunately I wasn'y able to RMA it because it was bought through a third party with a 30 day RMA policy. Replacement I bought directly from Crucial.

Also, you stated you tested the RAM with some program.....my understanding was that the only sure way to test RAM was on a RAM testing device.......

I just got my RMA'd RAM back and my system still has the same problem. I'm beside myself. There's nothing more exhasperating than a computer tech not being able to fix his own PC or more frustrating than being the proud owner of a $1200 paperweight. :(

Of course the system I tinkered together using spare parts, duct tape, spit, and bailing wire to fill in for this paragon of stability has run flawlessly in it's absence. :mad:

I'm quickly running out of ideas. Unless someone here knows something else to try I guess my next move is to RMA the CPU/MB combo. Yuk!

Any ideas?

If the cause always mentions the hard drive, why do you think it's the RAM?

Did you try another hard drive?