Windows Legacy OS forum

General discussion

Event ID 51 Error

by pcwiz100 / July 18, 2007 4:46 AM PDT


I am running Windows XP Pro SP2. I realize that everytime I start my computer, many Event 51 errors come up within a time frame of 3 seconds in the System log in the Event Viewer. However, the errors only come up in the log when Windows starts up. After that they don't come up. here is the log for the error:
Event Type: WarningEvent Source: Disk
Event Category: None
Event ID: 51
Date: 7/18/2007
Time: 11:31:54 AM
User: N/A
Computer: PC
An error was detected on device \Device\Harddisk0\D during a paging operation.

For more information, see Help and Support Center at
0000: 03 00 68 00 01 00 b6 00 ..h...

Discussion is locked
You are posting a reply to: Event ID 51 Error
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: Event ID 51 Error
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Another experience - another forum post
by pcwiz100 / July 18, 2007 5:00 AM PDT
In reply to: Event ID 51 Error


I found another person who had the same problem with the same HD model as me. Here is his post:


Hi all --

Just came across this post after having this same Event ID 51 problem myself. I built a new system this weekend with the following specs:

AMD x2 64 4800 Processor
(2x) Samsung SP2504C 250GB SATA 3G Drives with NCQ

In addition to the Event ID 51 problems, I was having intermitent problems with Windows taking a long time to boot. It was driving me MAD!!!

A big thank you to everyone with similar specs who solved the problem by disabling the command queueing on the controller in Device Manager. That seemed to work for me as well... I'll let this go a few more days but this appears to have fixed things.

Wondering if anyone has tried the 6.70 NForce4 drivers from NVidia and keeping command queueing ON. My current drivers are the 6.65 and these clearly don't work with NCQ.


It all seems to lead to nForce4 controllers that are incompatible with the model of HD. All my PATA and SATA controllers are nFore4 intel edition.


Collapse -
event error
by tomron / July 18, 2007 6:15 AM PDT
In reply to: Event ID 51 Error
Collapse -
Good news
by pcwiz100 / July 18, 2007 7:23 AM PDT
In reply to: event error


I have 3 Windows partitions. C:, the Windows XP partition, E: a Vista partition, and F:, a partition to store important documents and stuff. I only scanned C: because that's where the pagefile is and thats where the error occurs.

Like it said in that link you posted, I went to My Computer, right-clicked my HD partition, clicked properties, went to the Tools tab, and clicked Check Now. I selected both options (Automatically fix for file system error and Scan for and attempt recovery of bad sectors). It told me to restart and I did.

Checkdisk came up and it scanned the HD through a 5 step process. It took forever, but my computer restarted again and a screen came up saying MY DISK IS CLEAN. So that means its not a bad disk.

But someting weird did happen. After the computer restarted after the Checkdisk scan, the evnt 51 errors didn't come up this time in event Viewer. Weird.

Also, in that link, it says that the majority of problems is caused by NCQ (Native Command Queuing) technology. It said:


"NCQ is an innovation featured in SATA drives.

IIRC Seagate ( drives were the first to bring it in.

Seagate/Intel have a great joint whitepaper(in PDF) ( they released which is a nifty little overview of the process.

I usually describe NCQ a SATA drives ability to remember and execute multiple commands with greater efficiency as it remembers the position of the drive head and is able to select the next data transfer to minimize seek/rotational latencies.

Indeed, NCQ has a bearing on pagefile as it is an interaction if read/write on the disk. Please note that the event ID that was being generated in this instance is a generic one - indicating that an i/o(in/out) process isnt agreeing with windows virtual memory.

Unless you went exploring into hex error codes it is reallyhard to tell what the *specific* problem was. As NCQ is a modified way of achieving i/o process, it is not unreasonable at all that this could be perhaps causing your problem.

MS has more info on optimising pagefiles (;en-us;314482) but it seems you have a good grasp on that.

Another really important thing to consider here are transfer rates. SATA can achieve 3gbps. If a 3gpbs drive is being used at 1gbps this event error can also be generated. Most SATA drives come with little jumpers to 'dumb them down' to 1.5gbps if the drive is having trouble talking to the mboard.

In any event, a variety of solutions seem to work for people with different mboards/chipsets - though the A8n seems to be a common thread. I myself have an a8n but have never had a problem...perhaps my components have the most recent firmware in them ?? who knows !!

Still, disabling NCQ has solved the problem for many people, but you need to remembert that the drives capability to perform in its most efficient capacity is being disregarded when you do its not really a 'fix' in a true sense, but a workaround.

Nice work though stoffe Wink Let us now if you have any more probs with this error."


My drive is an NCQ drive so that might be it. What do you think?


Collapse -
Error fixed 4 now---what fixed it?
by pcwiz100 / July 18, 2007 9:03 AM PDT
In reply to: Good news

I ran CHKDSK (checkdisk) on my HD and it came out clean. Then after my computer restarted, I checked the Event Viewer and this time, the error didn't come up when the computer started. I restarted again and still no error. At first I thought that CHKDSK fixed it but then I remembered that right before I ran CHKDSK, I uninstalled a program called MSI Live Update. It is a program that was on my graphics card utility CD that is supposed to update the VGA Drivers with one click.

The program has been nothing but trouble to me on my computer. I have had previous experiences where the program causes (different) warnings in Event Viewer related to security threats and stuff. The program sometimes causes missing DLL error messages too, so I got tired of it and completely uninstalled it. Anyway, if I need new drivers, i'd much rather use MSI Live Update Online (its the same as Live Update except you run it on the web so no modifications to your computer are made.

Anyway, I don't know what fixed it (for now), Checkdisk or Uninstalling MSI Live Update. I'm still not 100% sure the problem's gone though. I'll post back if it comes back.

Thanks for all the help Happy

Collapse -
(NT) Your welcome,thanx for posting back
by tomron / July 18, 2007 10:38 AM PDT
Collapse -
It came back :(
by pcwiz100 / July 19, 2007 2:57 AM PDT


After leaving the computer off overnight, when it started up this morning the Event 51 errors came back. So, hoping it works (Which it probably won't), I switched the page file to a "System managed size". If nothing works, I think I'll just ignore it for now.

Also, I don't know if this is normal, but I realize that even though I have 400MB of unused physical memnory (RAM) out of my total 1GB of RAM, 700MB of the page file is being used. I just thought that the page file was only supposed to be used if the system runs out of physical memory... Any thoughts on that?


Collapse -
by tomron / July 19, 2007 5:00 AM PDT
In reply to: It came back :(

You can adjust the page file,LINK,this link has pictures you can click on to expand.


Collapse -
What should I do?
by pcwiz100 / July 19, 2007 5:11 AM PDT
In reply to: OK

Thanks Tom,

There was a lot of good stuff on that page. Which ones specifically should I follow do you think? Moving the pagefile is not an option for me because I don't have a second (physical) hard drive.

Thanx again

Collapse -
by tomron / July 19, 2007 8:19 AM PDT
In reply to: What should I do?

I was referring to "Have the initial size be at least 1.5 times bigger than the amount of physical RAM. Do NOT make the Pagefile smaller than the amount of physical RAM you've got installed on your system."

Increase the size on your HD,check the first picture there that you expand.


Collapse -
Pagefile size seems to be OK/Problem FIXED for now
by pcwiz100 / July 20, 2007 3:03 AM PDT
In reply to: pcwiz100


The pagefile size on the system managed option is around 2450MB so thats more than enough (1024 x 1.5 = 1536).

Anyway, after changing the pagefile option to "System managed", the problem SEEMED to go away. The computer was left off all night and when in started up this morning, there were no errors in the log. I'll post back if there are any more developments.


Popular Forums
Computer Help 51,912 discussions
Computer Newbies 10,498 discussions
Laptops 20,411 discussions
Security 30,882 discussions
TVs & Home Theaters 21,253 discussions
Windows 10 1,672 discussions
Phones 16,494 discussions
Windows 7 7,855 discussions
Networking & Wireless 15,504 discussions


Meet the drop-resistant Moto Z2 Force

The Moto Z2 Force is really thin, with a fast processor and great battery life. It can survive drops without shattering.