They're trying to run Memtest86+ but they're getting, for want of a better description, a screen error. I finally found a pattern for us. That's all the light I can shed on it after looking through my event logs, I have a few of those too, but no errors anywhere else. After a bit of fooling around I uninstalled the Intel Storage Manager and boom, everything is fine again, chkdsk is happy and no more error 51 in the event log. We've just been using Windows Server Backup included with Windows Server backing up to a local drive.
Can anyone help with how to solve the following hard disc error please? If you own a desktop computer, connect the hard disk to another port e. . Is one or both of your discs getting low in free space. When some driver is being installed? From now on, I'll be avoiding Seagate drives like the plague. . Had a look at the little proggy from Geeks.
If the problem disappears, you'll know this was what it was. This did not fix the problem either. Make sure to right-click on the installer and choose to Run as Administrator. If Windows cannot find an updated driver, then navigate to the manufacturer's support site and look for an updated Chipset driver and install all other recommended drivers for the Storage controllers. These are generally, but not always, generated after a reboot.
Using that information proceed and find which physical disk has the problem. Yes errors are at every startup. I would say that overall timeup times are the same. Huh, so it's safe to assume that it's from a bad Bitdefender update? I missed the most important info that you posted, my apologies. Ruled out a bad motherboard. I've carried out the page changes as suggested - no change. I've replaced the hard drive and am getting the same error.
Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them. I'm thinking these errors may be generated while these drives are being dismounted or something. Neither one of my drives are even close to running out of space, they're both at over 90% free space. I've even had to temporarily hook up the offending drive to my system to obtain some information from the properties sheets. Z 0060: 00 00 00 00 47 00 5e 00. And I think I've proven it. An incompatibility problem somewhere, yes.
If yes what is the recommended way to rescue data? Not surprising since the error 51 seems to be only reported on booting. . It took 7 hours but all was well at this point. The problems started just over 2 weeks ago after a couple of months of problem free usage. Hi, This may be of help.
I'm keeping my fingers crossed. What do you suggest now please? Open an Command Prompt as Administrator. Finally found a place within the drive management software Seagate Manager, not SeaTools , where I can completely disable the power-saving mode. I've also included the system log - perhaps this may shed some light? In fact, the harddisk1 designation had nothing to do with my hard drive at all, since I only have one hard drive, which is indicated as Harddisk0. If you're unsure how to do this, see the Perform these steps on the problem machine. Besides which, I tried to switch it back manually toggeling them but it wouldn' work.
An error detected on device HardDisk during paging operation. I use Bitdefender, maybe an update from that could have caused it? That's why we recommend using a hard drive diagnostic from the manufacturer of that drive. If you need more information just point me in the right direction and I will post it. Dear all, This is my first post. If you own a laptop computer, disconnect the hard disk from its cable and connect it again or replace its cable.
I also saw that this error happens with Shadowprotect users as well. My skills are not sufficient to work out why it does boot. A few weeks after solving this I put together a pc for a friend and that one also had the 51 error which also got solved with another cable. Contrary to what you may have been told, that message is not the kiss of death. I thought maybe there was a corruption in windows files or third party app causing the error.
Both drives are half empty in my case. I've attached the actual error report - all are the same. Can I add another piece of info? 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 Wrong. A paging operation is defined as anytime the operating system writes or reads data from memory to drive, or reads from the hard drive and writes to memory. Maybe there is still some part running and causing the problem. An oddball screensaver can also affect turn on, wake up from suspend Shut that down also. It just sets the parameters that I set through the registry.