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

n30_mkii · 15 Apr 2006 at 13:23

Couple of questions, i have started to get this error since i got my new WD 320GB Sata 2 drive, couple of weeks ago i did a fresh install of winxp sp2 on it. I also have to pata drives as well, but the sata has windows on it

how can i tell which hard disk it is refering to?

And is it more than likely a bad drive? or something that needs to be disabled on the device? I have the latest nvidia drivers for my mainboard

Is this a common problem or something i should worry about?

Replies ASAP thanks

I also downloaded the WD utility for checking the drive and all came up ok...

Toytown · 15 Apr 2006 at 14:38

If you right click on "MY COMPUTER" and select manage, then you can get access to the disk management (its in the storage part). Here it will show you all the harddrives and which number they are referred by.

An error during a paging operation is "normally" the sign of a bad harddrive. Although in some cases it can be down to the SATA cable or controller.

n30_mkii · 15 Apr 2006 at 15:10

Yes that confirms that it is talking about my new sata drive.

It is only these paging errors that are apprearing, and the WD Data Lifeguard reports no problems.....Shouldnt it find anything on the extended run?

Could it be a driver related problem?

Goberpiles316 · 23 Apr 2006 at 13:14

I have been having this problem on and off since I brought my new pc November, everything was ok for the first 6-8 weeks in jan I sent the whole lot back for testing and it was returned with all the parts passing the tests, I put everything back togather and it worked fine again for 3-4 weeks and then again the problems started, I have now purchased a second Hard drive an 80gig and install all the bits their and use the 250gb as storage.

The drives concerned are both Samsung spinpoint sata 2 drives.

n30_mkii · 23 Apr 2006 at 14:03

Well i found out after doing a little more googling that there is a problem with the nforce 4 chipset and sata2 disks (If the os is installed on it) i only ever got these at startup, not sure if ures is the same, but if you do a search in google, to solve the problem you need to disable enable command queuing on the sata controller.... This is a know bug apparently and should be solved in the nvidia drivers at some point.....Hope this helps!