Recently, my computer has been getting the BSOD, but only when performing certain operations. Whenever I try to run Eusing Free Registry Cleaner, Lavasoft's Ad-Aware, or Avira's Rootkit scanner, at around the same time in each scan (usually early on), I get a BSOD. I do not run into this problem when running Spybot Search & Destroy, A-Squared Free, or any portion of CCleaner (both the file cleaner and regsitry cleaner). HiJackThis also ran fine, and there are no programs unaccounted for. Spyware/malware/viruses don't seem to be the culprit here, but I suppose it is possible.
The BSOD error variates a little bit, but for the most part it goes like this:
0X00000050: 0XE414A000, 0x00000000, 0x8063FF94, 0X00000001 (sorry if I dropped a zero anywhere, I did my best). The first bit after the colon sometimes changes, I've seen and written down 0XE182A000 as well. Searching the Microsoft website didn't come up with anything helpful, at least not in the first few pages. Google was not of much help either.
I'll list the specs of my computer here, everything has been tested at stock.
Intel Core 2 Duo E6600
Gigabyte GA-P965 DS3 rev 1.0 board with F10 BIOS
2x1GB G.Skill DDR2 800 RAM @ 1.9v (recommended voltage according to G.Skill)
HIS Radeon X1900XT 256MB
Seagate 7200.10 320GB SATA 3.0Gb/s hard drive
Creative X-Fi XtremeMusic sound card
Corsair HX520w power supply
Windows XP Professional (Multilingual edition) w/SP3 (problem started with SP2)
I'm pretty sure those are the only pertinent specs for this problem, I can list the rest upon request.
This problem came up a few months ago, I tried running everything at stock to make sure it wasn't an instability problem, and tested my CPU for 12 hours using Prime95, my memory for 6 hours with Memtest86, and my graphics card with ATITool's artifact scanner for 4 hours. I used S.M.A.R.T., but didn't come up with anything significant (my hard drive came out with flying colors at 98% healthy), and Chkdsk /f /r didn't come up with anything significant either (a few minor errors). I reseated my RAM and checked the sticks one at a time, no change. I've also double-checked and triple-checked all connections, both power and data. Swapping SATA ports did not work either (and yes, I'm not using the purple RAID ports on my board). I also re-installed Windows, but have not gone so far as to format my drive yet. All drivers are either up-to-date or have been on the same version for much longer than the problem has existed (I can't stand trying to update the Creative drivers).
When I was building my computer back in October of 2006, I dropped the hard drive and knocked a bit of ceramic off a little electrical...thing on the bottom of the hard drive. I'm almost positive this is the problem, but I like being sure before I spend money on new components. The drive ran just fine for over a year, so I'm not sure if this is directly related or not, but I definitely feel the need to let you all know about this incident.
I guess I'm just having a last-ditch wishful bit of thinking that the drive might not actually be damaged (well, as far as data goes, I know there's a damaged bit on the bottom). I'm loathe to reformat, not because I don't have any backed-up data, but because if I do reformat and the drive itself is bad, I might not be able to get it working again and will be mostly without a computer until I can get a new drive (probably around a week or so).
I guess my questionis this: Should I just go ahead and get a new hard drive, or is it possible I screwed up my registry somehow (probably with a utility like CCleaner or Eusing) and this is causing the issue?
The BSOD error variates a little bit, but for the most part it goes like this:
0X00000050: 0XE414A000, 0x00000000, 0x8063FF94, 0X00000001 (sorry if I dropped a zero anywhere, I did my best). The first bit after the colon sometimes changes, I've seen and written down 0XE182A000 as well. Searching the Microsoft website didn't come up with anything helpful, at least not in the first few pages. Google was not of much help either.
I'll list the specs of my computer here, everything has been tested at stock.
Intel Core 2 Duo E6600
Gigabyte GA-P965 DS3 rev 1.0 board with F10 BIOS
2x1GB G.Skill DDR2 800 RAM @ 1.9v (recommended voltage according to G.Skill)
HIS Radeon X1900XT 256MB
Seagate 7200.10 320GB SATA 3.0Gb/s hard drive
Creative X-Fi XtremeMusic sound card
Corsair HX520w power supply
Windows XP Professional (Multilingual edition) w/SP3 (problem started with SP2)
I'm pretty sure those are the only pertinent specs for this problem, I can list the rest upon request.
This problem came up a few months ago, I tried running everything at stock to make sure it wasn't an instability problem, and tested my CPU for 12 hours using Prime95, my memory for 6 hours with Memtest86, and my graphics card with ATITool's artifact scanner for 4 hours. I used S.M.A.R.T., but didn't come up with anything significant (my hard drive came out with flying colors at 98% healthy), and Chkdsk /f /r didn't come up with anything significant either (a few minor errors). I reseated my RAM and checked the sticks one at a time, no change. I've also double-checked and triple-checked all connections, both power and data. Swapping SATA ports did not work either (and yes, I'm not using the purple RAID ports on my board). I also re-installed Windows, but have not gone so far as to format my drive yet. All drivers are either up-to-date or have been on the same version for much longer than the problem has existed (I can't stand trying to update the Creative drivers).
When I was building my computer back in October of 2006, I dropped the hard drive and knocked a bit of ceramic off a little electrical...thing on the bottom of the hard drive. I'm almost positive this is the problem, but I like being sure before I spend money on new components. The drive ran just fine for over a year, so I'm not sure if this is directly related or not, but I definitely feel the need to let you all know about this incident.
I guess I'm just having a last-ditch wishful bit of thinking that the drive might not actually be damaged (well, as far as data goes, I know there's a damaged bit on the bottom). I'm loathe to reformat, not because I don't have any backed-up data, but because if I do reformat and the drive itself is bad, I might not be able to get it working again and will be mostly without a computer until I can get a new drive (probably around a week or so).
I guess my questionis this: Should I just go ahead and get a new hard drive, or is it possible I screwed up my registry somehow (probably with a utility like CCleaner or Eusing) and this is causing the issue?