Do these chkdsk messages mean that I need to replace the drive?

OK, I'll post the specs. New build with quality parts as of this spring. I got a fairly discounted 500W CoolerMaster PSU which I thought would be more than adequate (only have one mid-low-grade Nvidia GT 240 GPU), and I did an online calc that said with some periphs plugged in I should use about 200W, so recommended at least 260W PSU (approx).

Also, I had everything unplugged for a while and was having problems, but that was probably my failed RAM that then seems likely to have corrupted the filesystem?

The two drives connected are 1 each AC/powered older Iomega and Seagate drives, and a USB-poweered newer USB iomega e-something.

I'll post specs in a sec but from what I have said, does it sound like it still would be power? I was under the impression that 400W would likely be more than I need, and I'm at 500.

OK I posted specs. I have a 500W CoolerMaster PSU that was pretty inexpensive (bad sign?). But I did an online power-req calculator and it said I was probably using 200W, and recommended like a 260W PSU. So shouldn't 500W be more than enough?

Also, I had everything unplugged when the first minor issues began, but of course they could be causing current problems. Basically all I have had plugged in is two fairly old 300GB drives that have A/C power, and a newer Iomega eGo portable USB drive with 2 USB plugs (no AC). Does that really sound like enough to cause issues?

Found some info using vssadmin list shadows. Looks like this shadow copy, which is the last remaining one that continuously throws ntfs errors, was from the 19th, right about when things started to go south....

Almost definitely going to reinstall on Thursday when I have more time. I have one restore point pre-12/19, and I might think about rolling back to that one just to see what happens. I'm backed up and planning to reinst anyway...

Anyone know of a way to remove just this one shadow copy?

Contents of shadow copy set ID: {04028ce9-9c14-41e0-898d-a2073de046a9}
Contained 2 shadow copies at creation time: 12/19/2010 3:39:07 PM
Shadow Copy ID: {73f35717-2ef3-4a90-8a02-a646bee42a58}
Original Volume: (C:)\\?\Volume{2c3d4e5a-79c7-11df-a8e3-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
Originating Machine: megatron
Service Machine: megatron
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Also, that one happens to be at the same time as a Windows Backup I made. Here is a screenshot of the restore points.

I looks like that deleting my restore points would at least get rid of the ntfs error. And if that is the cause of superfetch failing, then there you go, that fixes my original problem. I am worried I still have a jacked up drive though, and might have corrupt files that I will not discover for a long time, so I probably should reinst anyway.

Before I do though, I want to either try Sys Restoring all the way back or removing the restore points, just to see if either one fixes at least some things or fail catastrophically. Torn between giving Sys Restore a shot vs just removing all shadow copies. Either one probably doesn't do me a whole lot of good, but I'd do it just pre-reinstall.

Any opinions on that?