nforce4 - warning messages in event viewer

[spyork]

Ok everyone here's the problem. I recently built a new system with the following specs:
MSI Neo4 Platinum w/ nforce4 chipset
AMD 3500+ Winchester core
Corsair XMS TwinX1024
WD Raptor 72GB
Seagate 160GB 7200.7 w/ NCQ
LiteOn DVD Rom
LiteOn DVD Writer
MSI Geforce 6600GT

The problem that I'm noticing is that occassionally I'm receiving the following warning in the event viewer:

An error was detected on device \Device\Harddisk0\D during a paging operation.

When this error does occur it will be logged about 10 times consecutively in the event logs. I've run memtest86+, Prime95 torture test(~4 hours), SuperPi, and SiSoft Sandra tests without any problems. So it would appear that the CPU and memory seem to be in good working order. I've also run the windows diagnostic utility from Western Digital and both the quick and extended tests ran successfully without error. So the question is should I worry about this error if it really doesn't happen that often? Could this be an Nvidia SW IDE driver problem?

I would appreciate any feedback that anyone can provide? Thanks...

 

[FastEddie]

Try to resolve the issue. Do you have your memory voltage set up manually or is your vdimm set to AUTO? When set to AUTO, the bord sets the memory to run at 2.5v, which isn't enough voltage, especially for Corsair modules. Try setting your memory voltage to 2.75v and see if the problem goes away.

 

[spyork]

Thanks for the advice FastEddie...The only memory settings i changed are the CAS latency, tras, trcd, etc to match the recommended timings for my memory 2.5-3-3-6. I haven't changed any of the memory voltage settings yet. I can give that a try tonight, but the problem is that there is no real way to reproduce the problem.

 

[FastEddie]

If you are running the Corsair modules at AUTO voltage, then I'm 99.9999% sure that is your problem. You might not be able to reproduce the error, but not having it pop up after you manually set the vdimm is indicitative that was the problem to begin with.

 

[spyork]

I'll definitely up the voltages tonight and see what happens, but I'm still curious about something. If the memory is not getting enough voltage wouldn't memory intensive programs such as Prime95 or memtest generate errors?

 

[Peter]

Dude, this is a harddisk error.

 

[spyork]

I've run the basic and extended harddrive diagnostic tools from WD and the drive passes all tests. The drive doesn't have any bad sectors and is not making any bad noises either.

 

[Peter]

So? Nonetheless, Windows isn't able to read or write to it. Yes this might be a cabling issue or a driver problem just as well, but it very much points to a hardware failure. Might even be the power supply.

 

[spyork]

I already changed out the cables and the power supply is brand new and has excellent readings on all rails. The power supply is a Cooler Master Real Power 450W. It seems the problem only occurs on bootup. Over on another forum(http://217.115.198.3/content/topic/12946/) several people have had the same problems, but with different platforms and chipsets.

 

[FastEddie]

Paging error, from memory to hardisk. Set your vdimm manually as like I said, AUTO sets the Corsair modules up at 2.5v, which isn't enough voltage.

 

[spyork]

I'll make that vdimm change when I get off of work, and hopefully that will solve my problems. FastEddie, do you recommend the SW IDE drivers or the default MS drivers?

 

[FastEddie]

Default MS. The NV SW ide drivers still have problems with some optical drives and large file transfers. There is nothing wrong with the MS ide drivers. If you have SATA drives that allow for NCQ, then install the NV driver pack (which enables NCQ by default) then simply roll back the IDE Controllers to the MS controllers.

 

[spyork]

Hey FastEddie, before setting my vdimm to 2.75v I noticed that Core Center was displaying that my memory was already running at 2.70v. Is 2.70v the correct stock setting or is it 2.5v like you said above? I bumped the vdimm up to 2.75v. Is there any danger in bumping up the vdimm? I've always built and ran my systems at stock settings, so I've never messed with the vdimm settings before. Oh..and thanks for all of the suggestions You know now that I think about it I think I remember you posting on the amdzone.com forums back in the days when the Epox 7KXA Slot A was first released. Man that board really brings back some memories, some really awful ones