Home > Disk Error > Disk Event 51 Error

Disk Event 51 Error


Curiously (is it significant?) the drive seems to frequently open and close of its own accord. I've been able to check the same tests outlined above with Samsung SATA drive and the error is still present. Current bandwidth usage: 326.30 kbit/s October 09 - 03:36am EDT Forums Product Prices Contents •Home •Reviews •Editorials •Columns •Home Theater •Forums •Price Search •Community •HWA Store Latest Topics The slave is a 16X DVD rom. navigate here

The data verification did freeze near 97%, and after 3 minutes I aborted the process and the event log reported this warning. For example, if the device path is \Device\Harddisk5\D and I have several drives installed or attached to my computer, which one is the actual Harddisk5? After removing the "/PAE" and the "/3GB" switches, the error has not been encountered under similar user loads. x 625 Michael Papalabrou If this disk is your system disk or a disk that contains sensitive data, consider taking regular backups and/or replacing this disk as soon as possible.

Event Viewer Disk Error

Sonora Sep 3, 2015 Tin Man Government, 101-250 Employees USB drive improperly removed. From a newsgroup post: "If you have Intel's Application Accelerator installed this is what can cause the error. By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member?

Seriously, there are other things that could possibly cause this. Follow the steps all the way through (and including) the reboot.e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as As mentioned, I have two identical ULTRA 320 IDE HD's running in a RAID 1 configuration. Event 51 Disk Server 2008 However, no after effects were noticed.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.) Do those settings you mentioned resolve this Event Viewer Disk Error 7 I finally found a pattern for us. For Windows 2000 and Windows XP, the idechndr.inf, IdeBusDr.sys, idechndr.sys, and Txtsetup.oem files need to be extracted. https://community.spiceworks.com/windows_event/show/230-disk-51 Giles Back to top #13 hamluis hamluis Moderator Moderator 50,618 posts OFFLINE Gender:Male Location:Killeen, TX Local time:02:36 AM Posted 17 November 2008 - 04:49 PM Well...the error indicates a hard

The problem resides in the IEEE 1394 (firewire) driver. Event 51 An Error Was Detected On Device I read it on Intel's web site. Style Default Style Contact Us Help Home Top RSS Terms and Rules Copyright © TechGuy, Inc. x 731 Mårten Edelbrink I received this error along with EventID 50 from source Ntfs (and EventID 11 from source disk and EventID 5 from source atapi), when I had the

Event Viewer Disk Error 7

My skills are not sufficient to work out why it does boot. If any MVP wants to point me a the correct reporting form, I'd be glad to ask Microsoft to earn the money I spent on their new OS and fix the Event Viewer Disk Error My drive died Next time I'll know, I lost everything. "Click of death" learn something new all the time. Event Viewer Disk Error 11 I'll try to run tests on the drive you suggest.

When I moved the paging file to another disk the errors stopped. check over here Have seen more than we'd like, but not THAT many. (considering how many disks we go through here...) bburgner Ars Centurion Registered: May 12, 2003Posts: 212 Posted: Tue Dec 18, 2007 I updated my IEEE 1394 (Firewire) controller driver from "LSI 1394 OHCI Compliant Host Controller" (1934ohci.sys ver 6.1.7600.16385 stock driver from Windows 7 64-bit) to "1394 OHCI Compliant Host Controller (Legacy)" parth20 replied Oct 9, 2016 at 1:47 AM Infected ! Event Log Disk Error

English: This information is only available to subscribers. Ultra ATA/133 9.3 ms Average Seek Time 2MB FDB Motors DAVE Jenkins Nov 09, 2004, 09:34am EST Reply - Quote - Report Abuse Private Message - Add to Buddy List Join the community Back I agree Powerful tools you need, all for free. his comment is here This information applies to the following Operating System(s): - Microsoft Windows 2000 - Microsoft Windows XP - Microsoft Windows Server 2003 - Microsoft Windows Vista - Microsoft Windows Server 2008 An

At the moment it is working and I have had no bad crashes or anything, but I am afraid that it might be a sign of something serious. Event Id 51 Disk Paging Operation Edson de Kort Oct 18, 2004, 08:08am EDT Reply - Quote - Report Abuse Private Message - Add to Buddy List >>Re: Event ID - 51 - An error was The error does not surface until after the mirroring has completed.

I haven't even run chkdsk since the last crash (takes forever I'll do it later) and it is both running and sounding fine.

I don't understand why there should be a paging operation on this device as it is used only as an external backup for the C: drive. What did it? What I also found interesting, is that I get the same error for my CDROM. Event Id 51 Disk Windows Server 2008 R2 Rather than using the full 8GB of RAM, we put the RAM into 4GB with mirroring instead.

I'm going to look at the diagnostic over the weekend. When some driver is being installed?http://support.packardbell.com/it/item/ind...;ppn=PB17B00706http://pcs.suite101.com/article.cfm/windows_xp_boot_sequenceI suppose that, in the face of such underwhelming evidence either way...the safe thing to do is assume that the drive is failing/faulty.I missed the most I installed it over the old broken in install of XP with sp1 at a time when it needed formatting anyway just so I could try it out, I might not weblink I think SP2 made my system unstable and my drive is actually fine, they must have snuck some of win98 back into XP through SP2, because that's what it is running

Share Delicious Digg Facebook Reddit StumbleUpon Twitter Print Email this page Recipient Email *Required Your Email *Required Your Name *Required Find Answers Contact Us Ask a Question Submit a question to It's the motherboard as the primary suspect, by default it seems. See ME830051 for a hotfix".