Scannow to fix BSODs

[philnolan3d]

I built this computer last Sept, just over a year ago. For a few months it was perfect, then it started crashing (BSOD) at least once a day, 2-3 times is the average, but 11 times is the most I counted. So of course I've been trying to fix this for about a year now, I've updated all drivers, replaced parts, checked memory both with memtest86+ and by removing one stick at a time, and of course been through multiple long threads on forums. So finally yesterday one of the BSODs mentioned the file USBHUB.SYS which I had never seen mentioned before, so I Googled it and came up with a thread in this forum suggesting the poster should run ScanNow. So I did that and it surprisingly found and fixed some files. However it said some files could not be fixed and I would find more info in the CBS.log. I looked in the log but don't understand a word of it. I was wondering if someone here would know enough about it to look at it and figure out what I need to do. Thank you.

 

[garysgold]

Hello Phil,

I don't know how to read them either, but there are links to tell you how in the tip box here. http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html?filter[11]=Performance%20Maintenance

You could also do a repair install if you have the proper disk. Info here if needed: http://www.vistax64.com/tutorials/88236-repair-install-vista.html

Hope that helps.
Gary

 

[philnolan3d]

Thanks I'll look at that. I think I have done the repair install. If you're talking about inserting the Vista disc and clicking Repair, then yes, I have.

 

[philnolan3d]

Well that's annoying, those instructions don't work. I typed in what it said in a command prompt (as admin.), hit Enter, and nothing happened, I just got another C:\ prompt So I typed in the next part ans it tells me "edit" isn't a recognized command.

Edit: OK I searched for that string manually and found the damaged files. They are all named similarly to this one "NlsData0045.dll" so I googled that and came across this site:
http://www.corruptedfilerepair.com/...ws-Operating-System-Microsoft-Corporation.asp

Anyone know if that site is trustworthy?

 

[garysgold]

Sorry Phil, but I don't see where the command 'edit' is mentioned anywhere. I'm assuming that your talking about the SFC command. Make sure you have a space between the sfc and the /scannow. If that fails, then try it in safe mode. Also if you are in an elevated (admin) prompt it should read 'C:\Windows\system32>'.

Please keep us posted.
Gary

 

[philnolan3d]

It's step 3 on that Microsoft link you gave me
3. Type the following command, and then press ENTER:
edit sfcdetails.txt

Actually you gave me a link to this forum, that page had the MS link

As I said in the first post I already did the scannow, I'm just reading the results now.

 

[garysgold]

Ah. Sorry about that. I hadn't read the MS link so didn't know that command. Learn something new everyday.

Gary

 

[RichFrogg]

Phil,

When I opened up my own cbs.log file I just did a search for "cannot" and/or "repair" to find all the lines that mentioned whether or not a file was repaired.

Richard

 

[philnolan3d]

Yeah thanks, that's what I did too. Now I just need to know where to get those damaged files, like I said in post #4 I found a site but I wonder how trustworthy it is.

 

[Barman58]

Hello Phil,

If your not sure about the other site this one is , as far as I know, OK

DLL-files.com - Download all your missing dll-files.

 

[philnolan3d]

Thanks it looks like that site doesn't list them but I found more info on them from that other site. Turns out they are related to a Crysis demo I had installed like 8 months ago and it never worked right anyway so I'm just uninstalling it, then I'll run Scannow again.

 

[philnolan3d]

Not the Crysis demo, don't know what that site was talking about. So I downloaded the files and replaced them. Scannow still said they were bad. Then I crashed, twice! Back to the drawing board. Thanks for the help.