System freezes, HDD fails, Event 51 "error during paring operation"

[bulletng]

System freezes, HDD fails, Event 51 "error during paging operation"

For the past few weeks I've been having this strange issue with my computer. I would be doing something like browsing the internet or playing a game. Then I would go to access some media files such as music or video's on my media drive and my computer would start acting up. The symptoms I would get is the sound would buzz and scratch, the screen would freeze and stutter, and repeat this every few seconds until my hard drive fails and loses connection all-together.

Then I would have to restart my computer to get my drive back and POST displays that BOOTMGR is missing. I would have to go into BIOS to reset the Boot Order to get my system to boot up and I would get my media drive back.

At first I thought my hard drive was dying, so I took it out and plugged it into another computer to troubleshoot it. Everything seemed to work fine. I even went to the lengths of purchasing a new hard drive, but have yet to install it. I then realized that my video drivers started to act up and crash so I updated those. I believed I had a beta driver and once I got a WHQL driver the problem went away. At least until now...

A week later I was on facebook listening to some music and I went to browse my media drive and to my surprise it instantly started stuttering and freezing again. I'm at the point where I don't know what else to do except replace the drive which I'll probably end up doing this weekend.

I've attached several Event Viewer logs. I could also try capturing it on video if that would help at all. I've never seen this happen before. Any ideas?

EDIT:
I just rebooted my system after I lost my drive again and this time it didn't loose the boot order, so I'm not exactly sure why that's different now than before.

I should also mention that I like to set my icons for the shortcuts on my desktop to be blank (No I didn't do the 'remove the arrow hack'). Although recently they've been showing up as black icons. I had this issue several years back and iirc it was an old driver or something. Not sure if this could be related? I've attached the driversquery to this as well just in case.

 

[TVeblen]

First, change the title of your post. That should be PAGING, not PARING. A lot of people will skip the post not knowing what that is.

All errors indicate a dying hard drive as you suspected. The fact that it works without error in another PC raises the possibility that you may have power supply problems (insufficient power to the drives will produce the same errors), bad cables, or a problem with the SATA controller on the motherboard.

How many physical hard drives do you have in this PC? (Not to be confused with partitions on the same hard drive). If more than one physical hard drive, which one is the problem drive?

 

[bulletng]

Oh crap thank you..I didn't notice that haha.

I have four drives, two are SSD two are HDD. I have them separated by two modular power cables. I haven't changed anything physical and it has been running fine for years. I'm sure my 800W PSU can handle it but you could be right that the cables could be bad.

Concerning the SATA Controller I believe I had a problem with related drivers a few years back. I can try swapping the SATA port along with a new cable.

The problem drive only contains media. I have the OS and software on my other drives. There's no RAID setup or anything fancy. It's just a hard drive.

Thank you btw

 

[TVeblen]

A failing hard drive can mess up the whole system. If you disconnect that drive and the system runs without a hiccup then that would pretty much ice it.

First order of business regardless: back up any data on that drive before doing anything else. You do not know how long you will have until total failure. If it is not the drive you will only have lost some time.

 

[bulletng]

A failing hard drive can mess up the whole system. If you disconnect that drive and the system runs without a hiccup then that would pretty much ice it.

First order of business regardless: back up any data on that drive before doing anything else. You do not know how long you will have until total failure. If it is not the drive you will only have lost some time.

I am pretty good with backing up my data. That's the first thing I did when I encountered this issue.

I will swap the hard drive this weekend and see what happens.

 

[bulletng]

Well I got around to throwing in my new hard drive the last week, and it's been working fine for awhile until today. It just happened again. I got a similar event viewer error that says, "The device, \Device\Ide\iaStor0, did not respond within the timeout period."

The only thing I haven't done yet is a new SATA/power cable. Hopefully it's not the motherboard. I really don't know what else to do!

 

[TVeblen]

Have you attempted running it with only one hard drive (the OS drive) connected?
Also try it with any optical drive disconnected.

 

[bulletng]

Once my E:\ drive disconnects the system runs fine, besides not being able to access my media... Also I have no optical media drives connected. I have bad luck with them so I just don't use them at all.

EDIT:
Also I went ahead and swapped the SATA cable, used another modular power cable just for that drive, and disconnected some extra peripherals I had.

 

[TVeblen]

So let's focus on that E drive.

Which one is it? the Vertex 2, the WD Black, or the WD Green?

 

[bulletng]

It's a brand new WD Black FAEX 2TB drive. The one I had before it was a WD Black FALS 1TB. Both of them produce the same issue so I'm not so sure it's the HDD anymore. I have yet to encounter the issue since I swapped the cables, but I'll keep you posted.

I'm thinking about checking my drivers soon because I'm having another minor issues as well possibly unrelated to this...Some of my desktop icons I like to select the transparent icons so it just has the labels only. Well for the past few months they've been showing up as black squares now. I've had this issue several years back and I think it was an old storage driver causing the issue or something I don't remember.