The Process Forum - View Single Post - ITT: Tales of PC woe. Or why I hate MS (sometimes)!

TrunKated · 10-22-2008

Why, oh, why, doesn't microsoft (or some other part of my PC) give me a better error?

A couple of years ago, I started having problems with my old HD on my "main PC" because the HD was mounted on its side with only one loose screw. It would randomly make a racket and then the PC would freeze. I was able to replace the HD and secure it better.

Then months later I began to get problems with the new HD. Or so it seemed. Let me make a long story short. It now seems to be a memory error with the cheap upgrade memory I had bought a while back. But I only saw disk or file errors seemingly randomly but with increasing frequency. Like "Windows could not start because the following file is missing or corrupt: System32\Drivers\Ntfs.sys " It recommending repairing the file via Recovery Console. Well, guess, what. It was the bad memory not a file problem. I found the error on a discussion board and replacing or removing or reseating the memory was the remedy. So far the PC is working like a charm.

Lets hope it keeps doing so.

But, couldn't it have said something about the memory?

10-22-2008	#1
TrunKated AKA Kaytie. NOT Join Date: Jul 2005 Location: In my house. Posts: 5,597	ITT: Tales of PC woe. Or why I hate MS (sometimes)! Why, oh, why, doesn't microsoft (or some other part of my PC) give me a better error? A couple of years ago, I started having problems with my old HD on my "main PC" because the HD was mounted on its side with only one loose screw. It would randomly make a racket and then the PC would freeze. I was able to replace the HD and secure it better. Then months later I began to get problems with the new HD. Or so it seemed. Let me make a long story short. It now seems to be a memory error with the cheap upgrade memory I had bought a while back. But I only saw disk or file errors seemingly randomly but with increasing frequency. Like "Windows could not start because the following file is missing or corrupt: System32\Drivers\Ntfs.sys " It recommending repairing the file via Recovery Console. Well, guess, what. It was the bad memory not a file problem. I found the error on a discussion board and replacing or removing or reseating the memory was the remedy. So far the PC is working like a charm. Lets hope it keeps doing so. But, couldn't it have said something about the memory?