LINK, Event 51 Errors on nForce 4 mobos

[Cymbal Man Freq.]

http://forums.nvidia.com/lofiversion/index.php?t8171-0.html

Several of us have reported data corruption with nForce 4 based motherboards.
I'd like to share my experiences with you. I hope nVidia's experts read this
forum and finally offer us the right solution.

nForce 4 data corruption forum...at the link

 

[Cymbal Man Freq.]

http://www.hardwareanalysis.com/content/topic/12946/?o=0
This forum thread on Event ID 51 errors goes from 2003-4 thru very recently.

Somebody suggested to me that nVidia's ATA/IDE drivers are hosed across the
board, and that people should revert to the Microsft ATA/IDE drivers. However,
some people at the forum at the link above figure the problem can be solved by
using a Promise controller for IDE drives and also for SATA I or SATA II drives.

I believe the source of the problem is nVidia, but they take no responsibility
or interest in the problems discussed concerning Event ID 51 problems.
Alternatively, I could say it is all Microsofts' fault because Win XP has the
Event ID 51 error logging ability.

 

[Cymbal Man Freq.]

http://www.hardwareanalysis.com/content/topic/12946/?o=0
Nov 30, 2004, 04:12 PM
Re: Event ID - 51 - An error was detected on device \Device\Harddisk0\D during a
paging operation
It looks like this problem is related to Windows caching. I have some 2k servers
that connect to a novell network. My event log fills up with nwredir errors
(using MS netware client to attach). It seems from the descriptions above that
these Event 51 errors generally are showing up after paging or caching
operations which is what is causing my nwredir messages.

It seems that Windows is purging the cached information without updating the
cache index thus when the system goes back to look it finds nothing where it
thinks it should be something and generates this event noting that something was
missing.

Not sure if it can be fixed as it is just another undocumented feature of
Windows ;-)

Just my 2c

****************************************
PS., from CMF: after turning off Windows caching on my parents Dell Dimension
4300 two months ago, the SB Live! Value soundcard stopped stuttering profusely.

 

[Cymbal Man Freq.]

Apr 28, 2005, 05:07 AM
Post Edited On: Apr 29, 2005, 10:40 AM
http://www.hardwareanalysis.com/content/topic/12946/?o=80

Re: It looks like the problem is in a non NCQ/TCQ controller - NCQ/TCQ SATA hard
disk conflict
Here is my story.
I have P4P800MB on ICH5R controller and SATA Seagate 80GB disk plugged in SATA1
on one of the supported computers.
It all started quietly, sometimes (only sometimes) XP SP1 logged Controller
error problem and that was all. The system continued to work. It was strange but
it worked.
At the same time with installation of SP2 I updated BIOS for the latest version
and, since there was no more events like this, thought the problem is fixed.
Then all of a sudden the problem rose again, now it not only logged controller
error messages but the system would hang and the disk LED would burn continuosly
without actual disk activity. It looked like a hardware conflict and the further
system behavior - the system won't boot, not after the power cable is unplugged
or the switch on power supply is turned off - had backed my suspicion up.
I've done every possible thing with the system but with no success. The system
might work for a while but then some combination of concurrent file access would
happen and the system would hang again and won't boot till the power is
unplugged. New BIOS, drivers, configurations won't solve this bug completely.

Yet I have a theory, and only a theory, why this could happen with all of us. We
have different motheboards, chipsets, disks, etc. but the bug persists with all
of us. What is wrong?

I'll start from my case. Intel says that ICH5R controller which is built in
P4P800 MB doesn't support NCQ, yet my disk does support it. Read more about NCQ
here
http://techreport.com/reviews/2004q4/seagate-7200.7ncq/index.x?pg=1
What will happen if a seagate SATA disk with NCQ support is working on a
controller which doesn't support NCQ? I don't know but I assume it would fail
from time to time to communicate with hard drive by the reasons unknown for the
controller, and generating in its turn an error which system would log in the
system events as a controller error.

The assumption comes with agreement with:

1. WD supports TCQ instead, which is almost the same thing. ICH5R doesn't
support it either. So, changing the drive on WD shouldn't change the situation.

2. Promise controllers support TCQ&NCQ that's probably why some people reported
success after they have installed Promise SATA controller. Promise just
understands the drive and work with agreement while on borad controller is not.

3. Changing MB, in my case on ICH6R which DOES support NCQ would solve the
problem. I've seen people changing the MB on almost identical one but with
different chipset would have succeeded in solving the problem. All the success
happened only if a new MB was built on a controller supporting NCQ (or TCQ)

4. One would only have 1 SATA disk with NCQ or TCQ support plugged in SATA
controller with doesn't have NCQ or TCQ support to have IDE problems or SATA
controller error etc.

5. If IDE disks do support NCQ/TCQ they should fail as well on a particular
controller.

I'm not sure at all in all this, but it might give some clues to the others.
Tell me if it helped.

--------------------------------------------------------------------------------
-----

Installing Promise SATAII TX2 has fixed the problem. There is no errors so far.
The weak place in NCQ theory is that Promise controller by default has NCQ/TCQ
switched off. And still it worked without any problems. I have enabled NCQ/TCQ
and still it worked. I found no reliability problems enabling or disabling
NCQ/TCQ on Promise controller.

Is it possible that NCQ/TCQ HDD itself can not work with non NCQ/ICQ
controllers?
I wonder if there is any difference in NCQ supporting controller handling NCQ
drives when NCQ is turned off? Does it know that it is working with NCQ drive
or, if NCQ is turned off, there is no difference between NCQ supporting
controller and non NCQ.

***************************************************************
Apr 28, 2005, 04:48 PM
Re: Event ID - 51 - An error was detected on device \Device\Harddisk0\D during a
paging operation
Having read the entire thread and contributed my own experiences and thoughts
I've come to the conclusion that there is no single answer to this problem, and
that for most of us it is pretty much a matter of trial and error to attempt to
isolate the source of the error within our particular configurations. I've got
SuSE 9.3 Pro and I'm going to install it over the weekend using my previous
config to see if I can replicate the error under Linux. Fundamentally though, I
reckon that because SATA1 technology was pretty new when most of us bought our
motherboards there have been some teething problems and they are probably a
combination of hardware and software issues - in short, we've all bought
unreliable technology.

For the moment I'll live with the workarounds but definitely won't be buying
another motherboard or hard drive until SATA2 is deployed as an on board, proven
feature. For that matter, my next MOBO will also be a 64 bit solution. What
surprises me is that the Internet is littered with a discussion of the issues
we've all experienced, however, I've not been able to find a single response
from a hardware vendor nor Microsoft. It's almost as if they collectively refuse
to acknolwedge the issue exists and is widespread.

Out of curiosity I even tried an extreme solution of rebuilding my own BIOS code
by removing the SI BIOS module, incorporating SI's latest BIOS for the 3112A
into the BIOS code and then flashing the MOBO. End result: lastest BIOS for the
3112A but no difference - as long as the 3112A is enabled in my BIOS (with or
without RAID support) I get the paging errors we've all so lovingly discussed
here.

Turning it off and using a PCI based Promise controller to provide additional
SATA channels solved the problem.
Post Edited On: Apr 28, 2005, 04:51 PM

**************************************************************
Apr 30, 2005, 05:26 AM
Installed a PCI-based Adaptec controller in January - Not a single error since

Please save yourself - if you're having this problem, go buy a new controller
and get on with your life!!
*************************************************************

 

[Guest]

Re: Event ID - 51 - An error was detected on device \Device\Harddisk0\D
during a paging operation

I solved the probem with event id 51. Or at least a work around. I noticed
that after cleaning out the prefetch folder I did not get any id 51 errors.
So I disabled it in the registry (see below) and have not had a problem for 3
weeks.
There are 4 options below that could be used to narrow the problem down. I
do not have time so I selected option 0


I hope this works for all you guys!
Later Mang

##################################>>>>>>>>>>>>>>>>>>#############################

To change the registry settings for prefetching, start the Registry Editor
by selecting Run from the Start menu, typing regedit in the Open text box,
and clicking OK. When the Registry Editor window opens, navigate through the
left pane until you get to this hive:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\PrefetchParameters

In the right pane, look for the key named EnablePrefetcher. The value of
this key represents how prefetch works on your system. Values you can choose
from include:
0—Disable
1—Application Launch Prefetch
2—Boot Prefetch
3—Prefetch everything

To change the value, double-click it. You'll then see the Edit DWORD Value
screen. Enter the value representing the level of prefetching you want in the
Value Data field.

As a general rule, if you're on a low-memory workstation, 128 MB or so, set
the value to 0. If your workstation has 512 MB of RAM or more, set it to 3.
Otherwise, you can choose the value as best suits your needs and observations