Odd issues with PC.

eronenris

Honorable
Aug 16, 2014
60
0
10,630
I am not positive which section to post this in, where I think it may be a gpu or ssd issue, I am going to post it in Graphics cards. Sorry if that is wrong.

So every morning I start my computer when I get to work. Most days it starts just fine, but every now and again, it will shut off within a few seconds of posting. I then turn it back on, and everything is fine, then it won't do it again for a week or so.

My other issue is, again intermittent. Sometimes my computer will completely lock up for 1-2 minutes, and then resume whatever it is that I was doing, like nothing happened.

I have tried updating my graphics drivers, they are the newest ones, I always update when needed through geforce experience. Also my SSD is only like 2 years old, so I really hope that is not the issue. I also recently cleaned out my computer, because where I work gets kinda dirty. It was not as dirty as I had thought it would be.

These are not life changing problems, I can deal with them, but I would just like to figure it out before whatever it is completely fails and then I am stuck buying new parts.

Any help is great, thanks.
 

eronenris

Honorable
Aug 16, 2014
60
0
10,630


No, nothing. It just goes back to what it was doing, like nothing happened.
 

eronenris

Honorable
Aug 16, 2014
60
0
10,630


So checked my event viewer after it did it today, it did it twice today.

This is what it says.

taskhostw (7316,D,0) WebCacheLocal: A request to write to the file "C:\Users\Cloudnine\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 135168 (0x0000000000021000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

taskhostw (7316,D,0) WebCacheLocal: A request to write to the file "C:\Users\Cloudnine\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 135168 (0x0000000000021000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Two separate errors at the same time today. Not sure what they mean, It says it may be a hardware issue, but it doesn't tell me which hardware....
 


This looks like a storage issue. Actually I'm a little embarrassed to say I had the exact same thing happen to me over ten years ago and I didn't think of it until you posted your last message. I would have a long pause and it would come back, no error. It happened right after doing a clean install of Windows. It wasn't doing it prior. I suspect the stress placed on the drive from doing a clean install pushed it over the edge. To make a long story short after troubleshooting it and finding nothing (even used WD's tools to test the drive), I emailed WD with the info, and immediately got an RMA number even though I wasn't asking for one at that point. I could hear a faint click from the drive when it would freeze.
 

eronenris

Honorable
Aug 16, 2014
60
0
10,630


That sucks, This is an expensive SSD that is only like 2 years old.
 

eronenris

Honorable
Aug 16, 2014
60
0
10,630


PNY 960gb
Damn thing retails for $350, from Best Buy.

Luckily I just found out that it has a 3 year warranty and it is not even 2 years old. So I am going to try that route today and hope for the best.
 

eronenris

Honorable
Aug 16, 2014
60
0
10,630


This is a new one today. I have hundreds of instances of this error. It just keeps popping up.

The driver detected a controller error on \Device\Ide\IdePort0.

 

eronenris

Honorable
Aug 16, 2014
60
0
10,630
Ok, so it has been a week since I tried what I tried. And the issue seems to have gone away. SO I now feel comfortable calling it fixed, hopefully more than temporarily.

I switched the sata cable to a new one, and changed the port that the drive was plugged into on the mobo, and the problem has gone away.

Now I am not one hundred percent sure if both steps were necessary, but with where my computer sits at work, it is not something I wanted to have to take apart again and again. My guess is, replacing just the cable would have done the trick, but I tried both just for the hell of it, and it worked.

Thanks all for your help and suggestions, hopefully this post can help future people with this issue.