Error 51 since upgrade

Upgraded my motherboard and graphics card about 1 month ago. Have 1 WDC harddisk which is partitioned into a C: and D: drive, as well as a linux partition which is now dormant. Reformatted C: when upgrading motherboard. Twice in the past month, I've received multiple instances of the following error in the event log over a period of about 20 minutes, after which it then disappears.

Event Type:      Warning
Event Source:      Disk
Event Category:      None
Event ID:      51
Date:            2/10/2008
Time:            6:27:29 AM
User:            N/A
Computer:      SYSTEM
Description:
An error was detected on device \Device\Harddisk1\D during a paging operation.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 01 68 00 01 00 b6 00   ..h...¶.
0008: 00 00 00 00 33 00 04 80   ....3..€
0010: 2d 01 00 00 0e 00 00 c0   -......À
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 05 d4 10 00 00 00 00 00   .Ô......
0030: ff ff ff ff 01 00 00 00   ÿÿÿÿ....
0038: 40 00 00 08 00 00 00 00   @.......
0040: ff 20 0a 12 4c 02 20 40   ÿ ..L. @
0048: 00 00 00 00 0a 00 00 00   ........
0050: 00 00 00 00 c0 27 2e 85   ....À'.…
0058: 00 00 00 00 08 a0 ca 85   ..... Ê…
0060: 00 00 00 00 58 79 02 00   ....Xy..
0068: 28 00 00 02 79 58 00 00   (...yX..
0070: 08 00 00 00 00 00 00 00   ........
0078: 00 00 00 00 00 00 00 00   ........
0080: 00 00 00 00 00 00 00 00   ........
0088: 00 00 00 00 00 00 00 00   ........

There are some known issues with the nvidia nforce drivers. I receved the following error right after installing them when I selected the install of the nvidia IDE SW drivers, back when I first upgraded about a month ago. That day, I removed these drivers [I hope completely] and have never received this second error since. This error is:

Event Type:      Error
Event Source:      nvata
Event Category:      None
Event ID:      4
Date:            1/18/2008
Time:            10:58:21 PM
User:            N/A
Computer:      SYSTEM
Description:
Device slot returned an invalid status value. See data for detailed information.
Data:
0000: 1b 00 0c 00 01 00 60 00   ......`.
0008: 00 00 00 00 04 00 de c0   ......ÞÀ
0010: 00 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 01 01 09 00 53 00 de 10   ....S.Þ.
0030: ff 00 00 00               ÿ...    

So I'm wondering: What might be causing the first error? Further problems with the nvidia drivers lingering? I've never received the error for the C: drive, and have run chkdsk without any bad sectors or errors found.

Also, I would imagine that removing the dormant linux patition might be a good idea, after removing data I might need. Maybe this is complicating things? I mention this because ever since I created the linux partition, I have an "F:" drive in My Computer, which appears as empty, both before and after the upgrade, which I imagine corresponds to the linux partition.

Specs as follows:
Windows:                  Windows XP5.1 (Build 2600) Service Pack 2
Internet Explorer:        6.0.2900.2180
Memory (RAM):             1024 MB
CPU:                      AMD Athlon(tm) 64 Processor 3700+
CPU Speed:                2208.2 MHz
Sound card:               NVIDIA(R) nForce(TM) Audio
Display Adapters:         NVIDIA GeForce 7600 GT  | NetMeeting driver | RDPDD Chained DD
Screen Resolution:        1280 X 1024 - 32 bit
:                         
Network Adapters:         Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller - Packet Scheduler Miniport | NVIDIA nForce Networking Controller - Packet Scheduler Miniport
CD / DVD Drives:          E: LG      CD-ROM CRD-8400B
:                         
COM Ports:                COM1
LPT Ports:                LPT1
Mouse:                    8 Button Wheel Mouse Present
Hard Disks:               C:  32.2GB | D:  67.4GB | F:  0.0MB
Hard Disks - Free:        C:  15.7GB | D:  31.2GB | F:  0.0MB
USB Controllers:          2 host controllers.
Firewire (1394):          Not Detected
:                         
Manufacturer:             Phoenix Technologies, LTD
Product Make:             System Product Name
:                         
AC Power Status:          OnLine
BIOS Info:                ATAT COMPATIBLE  102105  Nvidia  42302e31
Time Zone:                Eastern Standard Time
Battery:                  No Battery
Motherboard:              ASUSTeK Computer INC. A8N-SLI Premium
Modem:                    Not detected
phoebusAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
pheidiusConnect With a Mentor Commented:
Actually, I meant ata vrs pata.  There are so many "fixes" out there it is dizzying. but first you would need to find the all the files and dll's that go wth the nvidia driver and remove them(or move rename). Since you just installed them, you should have a disk and can open them up on the cd and look at them so you know what you need to find. If this is at all tricky you can probably do a custom install and see where the drivers want to go. Next, I would say that you would unstall the pata nvidia controller in device manager.  Then when you reboot MS should not find the nvidia drivers and instal its own instead. If this works then all you would need to do is make sure the drives are not really running in pio mode(that would be slooow). Then just use puter and see if  the problem has gone away.
0
 
pheidiusCommented:
Apparently, you are nowhere near alone with an amd chipset on this one. One solution offered "I disabled tagged queuing and disabled synchronous tranfers for my hard drive and rebooted my computer. I haven't gotten a single error in Event Viewer ever since. It's been only 2 days now but I believe my \Device\Harddisk0\D problem is gone for good. I will report back to you guys after another week to confirm my fix.

For anyone who wants to try my fix, you can disable tagged queuing and synchronous transfers by accessing your hard drive's properties page in device manager, selecting the SCSI Properties tab, and clicking on the two appropriate boxes. Reboot your computer, and hopefully, your \Device\Harddisk0\D headaches are gone too. Thank you to everyone here for their advice!"
That was , there others on this page
 http://www.hardwareanalysis.com/content/topic/12946/?o=120
In fact, there are two years of posts on this issue in this forum. I wish I had a better answer.
0
 
phoebusAuthor Commented:
Thanks phedius. I did find MANY similar results when I googled the problem prior to posting to ee, but all of the posts that I read referred to SATA, rather than the old fahsioned [? parallel] ATA which is what I am using. When I go to the properties page of "nVidia Parallel ATA Adaptor" I find 'enable read caching' and 'enable write caching' rather than 'tagged queuing' and 'synchronous transfers.' I did notice in the last post from the link you listed:

"what I did for me (since I use the nVidia IDE Drivers) is to uninstall the PATA portion of the drivers and revert back to the Microsoft IDE drivers. Problem solved for me."

Perhaps I should try that - I am using ATA rather than SATA? I'm not knowledgable enough to understand if this is relevant to my situation [ATA rather than SATA] or if it is a bad idea. Thanks for your help.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
pheidiusCommented:
It would not hurt to try. pata vrs sata is  a very small difference in real world anyway.
0
 
phoebusAuthor Commented:
This drive doesn't support sata, so I'm stuck with the old fashioned ATA, so I was wondering whether the solution seemed applicable. Right now the drivers listed under IDE ATA/ATAPI controlelrs are:

NVIDIA nForce4 Parallel ATA Controller
NVIDIA nForce4 Serial ATA Controller
NVIDIA nForce4 Serial ATA Controller
[yup, two of the SATA ones]

As expected, both SATA Controllers list 'no device' under primary and secondary channels. PATA lists the WDC drive as Master for Primary Channel, and the LG CD-ROM as Master on Secondary Channel. What would you recommend I do at this point?

0
 
phoebusAuthor Commented:
Thanks for your continued help pheidius. Unfortunately the damn installer is an exe that I downloaded from nvidia.com rather than a CD [needed updated version, mobo was from a friend so was without the cd]. So its pretty tough to tell all the junk it puts on the drive. Would it be safe to bypass that part, and use device manager to uninstall the pata controller in the device manager, or perhaps 'roll-back' the driver?

Also how do I check to see if they are running in pio mode [don't know what that is heh]?

Thank you for your ongoing help.
0
 
pheidiusCommented:
Well if your ide controller looses its drivers or they get corrupt then it reverts to pio mode which is glacial slow. in other owrds not ATA tranfer rates. You will be able to check that in Device manager. Well if the installer is an exe when you click it does it give you the coise of a custom installation. If it does, then you can watch where the stuff goes and perhaps even be given a choice as to which drivers to be installed.
0
 
phoebusAuthor Commented:
Okay...I've already uninstalled completely then reinstalled the NVIDIA drivers back when I was removing the problematic IDE SW driver about a month ago. Should I completetly remove and reinstall again and watch where the files go, or just install again over the old installation and try to watch where the files go?

Also, I take it that rolling back wouldn't be a way to test it rather than trying the uninstall route?
0
 
pheidiusCommented:
Well, I assume that the nvdia ata drivers were the stock ones for this particular chipset so while you might want to try  rolling back but Yes I was thinking of just running a reinstall over the existing installation and see if their is a custom option that allows you to pick which files you want and see where they go. If you can just see the folders they go to, you may be able to just rename them to hide them from Windows after a device uninstall.
0
 
phoebusAuthor Commented:
Thank you for your ongoing help pheidius. I ran a reinstall of the nForce drivers, but there was no custom option. I let the installation continue to see if I could see the location the files were going to, but could not. I did make sure to select NO when asked whether I wanted to install Nvidia IDE SW drivers. I then rebooted. In the device manager, under nVidia Parallel ATA Controller, I selected 'rollback driver.' I was then warned the driver I would be rolling back to wouldn't be digitally signed...anyway I then rebooted and now see in my device manager:

IDE ATA/ATAPI controllers
NVIDIA nForce4 Serial ATA Controller
NVIDIA nForce4 Serial ATA Controller
Primary IDE Channel
Secondary IDE Channel
Standard Dual Channel PCI IDE Controller

The drivers for the last 3 entries [which have apparently replaced the 1 entry: nForce4 Parallel ATA Controller] are published by Microsoft, dated 2001. Wierd that they weren't 'digitally signed' ....

So...couple of questions to wrap things up?

1 - Should I be worried that supposedly Microsoft drivers weren't digitally signed - thought all MS drivers were, only 3rd party drivers weren't

2- Have I successfully replaced all drivers which I should have?

3 - How do I make sure I'm not in PIO mode?

Thanks again for your help.
0
 
pheidiusCommented:
http://forum.digital-digest.com/showthread.php?t=61905 Here is a very clear description of the process. Your device manager results look good though. So if you are running the right level of dma that match your drives rating then hopefully you will have fixed the problem.
0
 
phoebusAuthor Commented:
Great thank you for the link. The primary IDE channel shows DMA on both Device 0 and 1. On Device 0 the mode is Ultra DMA Mode 5.

 The secondary IDE channel shows PIO only on Device 0 and 'DMA if available' on Device 1.

My HDD is on the primary channel, CD rom on secondary channel.

I googled and found that windows uses PIO by default with CD-ROM drives. I guess 'Ultra DMA Mode 5' is the correct setting for my HDD - it was set that way without my doing anything and the drive seems to be working ok?

Anything else for me to check or are we all set? Thanks again for your help.
0
 
pheidiusCommented:
No, just knock on wood as this error code covered a lot of territory. Hopefully, you have seen the last of it.
0
 
phoebusAuthor Commented:
Thank you for your help :)
0
 
phoebusAuthor Commented:
Okay :) Thank you!
0
All Courses

From novice to tech pro — start learning today.