Home > Error Was > Disk Error 51

Disk Error 51


From ME324916: "The Iomega Zip 250 drive does not support requests by the operating system to turn off write caching. 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 This event might have generated during swapping operation ( memory manager either swapped a page out of memory to your external disk or retrieved a page from your external disk ) So the It really really ANNOYS the heck out of me that the error message talks about "during paging" on drives that don't even participate in virtual memory pagefile.sys's, I can only presume Check This Out

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/Windows_7/Q_26182013.html 0 Message Author Comment by:Jsmply2010-07-01 We wanted to update this to anyone else facing this issue. My skills are not sufficient to work out why it does boot. I only hope my drive is still in fine working order! see ya mac damnxp damnms Dec 04, 2004, 12:27pm EST Reply - Quote - Report Abuse Private Message - Add to Buddy List >>Re: Event ID - 51 - An

Error Was Detected On Device During A Paging Operation

I've seen these errors caused by bad ATA cables (usually non-standard lengths, and/or "rounded" cables). we are done a complete DISSERVICE when it turns out the errors are a "opps a mistake" "oh gee are we accidentally trowing abunch of disk errors gee just ignore those" This then fixes some errors and then i can load windows again.

See MSW2KDB for more details on this event. Stats Reported 7 years ago 17 Comments 53,437 Views Other sources for 51 Symantec AntiVirus cdrom disk Cdrom OFADriver Sfloppy Print Removable Storage Service See More Others from Disk 11 7 Check Microsoft articles ME123747 and ME197379 to learn more about page file and performance. An Error Was Detected On Device During A Paging Operation Cdrom x 75 Anonymous Event shows on Server 2008 R2 when backing up Hyper-V volumes holding VMs with either Windows Backup or Shadowprotect.

Moto Guzzi Dec 05, 2004, 02:09am EST Reply - Quote - Report Abuse Private Message - Add to Buddy List >>Re: Event ID - 51 - An error was detected An Error Was Detected On Device Device Harddisk1 D During A Paging Operation What if it wasn't brand new and it was a 3 year old 160gb disk? Thanks! 0 Question by:Jsmply Facebook Twitter LinkedIn Google LVL 46 Active today Best Solution bynoxcho I think this part of the support kb article refers to your problem exactly Quote: "An https://social.technet.microsoft.com/Forums/office/en-US/f0f319f8-1af8-4957-b188-e4126e0d871d/an-error-was-detected-on-device-deviceharddisk0-during-a-paging-operation?forum=winservergen I believe that was all the questions.

Not a member? An Error Was Detected On Device Device Cdrom0 During A Paging Operation Hence I/O errors to ANY file get reported as "paging errors," even though the page file is not involved. Back to top BC AdBot (Login to Remove) BleepingComputer.com Register to remove ads #2 hamluis hamluis Moderator Moderator 50,689 posts ONLINE Gender:Male Location:Killeen, TX Local time:07:43 PM Posted 04 So, I suggest one avenue of investigation would be for you to check your virtual memory management settings (Computer, right click Properties (or Control Panel, System) Advaced tab, Performance Settings, (yet

An Error Was Detected On Device Device Harddisk1 D During A Paging Operation

If these events are logged regularly on a primary system drive, replace the device. This method is available for Microsoft* Windows* NT* 4.0, Windows 2000, and Windows XP. (For Windows NT 4.0, the TXTSETUP.OEM, INTELATA.INF, and INTELATA.SYS files need to first be extracted from the Error Was Detected On Device During A Paging Operation We can try a restore to similar hardware though or another hdd. An Error Was Detected On Device Device Harddisk2 Dr13 During A Paging Operation In these particular cases, you can safely ignore the log entries, and no additional action is required." You mentioned that you did swap some devices while one of them stayed connected

I've also now been able to run the full diagnostic utility from Samsung Site for this drive - on 5/5 cycles including the full surface scan no errors present drive is his comment is here That being said, I do believe I have seen the same error from a Seagate drive that had it's own power adapter on a Windows 2000 Server box in the past. To identify it, open the Disk Management applet (diskmgmt.msc) and select a volume on the list displayed in the top panel. EricDoing a job RIGHT the first time gets the job done. An Error Was Detected On Device During A Paging Operation Usb

The drives are not being written to at this time (at least through nothing intentionally running). 0 LVL 46 Overall: Level 46 Storage Hardware 30 Windows XP 13 PCs Do you think my apps should remain unaffected by the repair? If these are USB powered, they may be losing access for just enough time to lose paging capability whilst keeping connection. this contact form I've been able to check the same tests outlined above with Samsung SATA drive and the error is still present.

We started with two brand new servers with 8GB of RAM, using Windows 2003 Enterprise Server. An Error Was Detected On Device During A Paging Operation Usb Drive See ME834910 for a hotfix. I'm presently dealing with what may be a similar issue with Event 11 (the driver detected a controller error on \Device\Harddisk6\DR6) errors in the event log but seemingly normal drive operation.

And that's evidence of a failing drive.

The search continues! I already had three instances of IE 6 going, I already had an MP3 playing on media player 10 and was 3/4 way through a 10 minute song, all running fine, Is this something we should be concerned about? An Error Was Detected On Device Device Harddisk0 I have the Knack. ** If I haven't replied in 48 hours, please send me a message.

I'm not using the "latest" via drivers because I dont' have the "latest" hardware, I'm using the optimal via drivers for my chipset. Not so fast , my friend. Join & Ask a Question Need Help in Real-Time? http://smartphpstatistics.com/error-was/error-encountered-while.html but unfortunately the budget is very small and even this new machine (with RAID) was a stretch and took a while.

Turns out, there were "irreconcilable differences" between BIOS, disk controller embedded on the motherboard, and NVIDIA chipset drivers for same; "dumbing" it down to using the generic IDE controller mode and They should have more information on these Event ID's for you. You're right on what you say.Based on some related MS articles, the problem doesn't have to be the disk itself.Besides the faulty wiring, it might be a slow or problematic controller Pete 0 Message Author Comment by:Jsmply2010-05-16 Interesting, this machine is a Dell precision also (different model though). 0 Message Author Comment by:Jsmply2010-05-24 Well, this particular error did dissapear when

Seriously, there are other things that could possibly cause this. Concepts to understand: What is a paging operation? The system is XP home, AMD 3000+. We did that, and it's still throwing the paging errors right now.

Featured Post Find Ransomware Secrets With All-Source Analysis Promoted by Recorded Future Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat See the link to "Abit Forum Thread" for some other useful information. DriverGuru Senator et Subscriptor Tribus: somewhere in nonpaged pool Registered: Mar 21, 2001Posts: 19651 Posted: Tue Apr 13, 2010 3:50 am Quote:Maybe the driver wasn't ready and the operation had to Service pack 2 is new.

I will gladly test it though, but would need to be on-site. If it's noteworthy, all the machines we've seen with these paging errors have been Windows XP and Dell desktops with the OEM image. An isolated event 51 warning is harmless if not accompanied by an actual error event, because obviously if the event is isolated in time, the retry was successful." 0 Message Under it, the list of drives and their number is displayed and you can match the hard disk number shown there with the one listed in the event description.

Unfortunately I have no idea what was done except that the fault was cleared. The weird thing is that the explanation from MS fits in almost all points and they announced the article at the beginning of november..