Vista64 BSOD - Driver, Hardware, Software?

[richc46]

Its getting late, here.
If you want to save your stuff, try this
Use Ubuntu Live CD to Backup Files from Your Dead Windows Computer - How-To Geek

If you can get to your documents, normally, just back it up.

 

[mitchellb]

I'm sorry but what exactly would you/me be saving?

 

[mitchellb]

Oh, I have done that already. Thanks, for everything.

 

[mitchellb]

Rich, I restored from the recovery drive and all is set to factory settings. I ran an SFC scan and the errors are still there. What do you suggest?

 

[richc46]

My first thought is that you think you ran factory settings, but did not. If you did it would be like the day that you took it home. There may be problems but not the same that you had.

How do you know that factory settings worked?

 

[mitchellb]

Well, programs that I've never installed or used are installed.

 

[richc46]

And your programs are gone?

 

[mitchellb]

Yes, ones I've downloaded and installed are gone.

 

[richc46]

I have never heard of this. Upload the file to us and I will give this to our resident expert on SFC files (they are actually called cbs files)

 

[mitchellb]

Here's the log.

 

[richc46]

This is the report after the factory restoration?

 

[mitchellb]

Yes, is there a problem?

 

[richc46]

No problem, just wanted to be sure we check the correct report. Our specialist in this area is from another land and time zone. He should be around by early tomorrow at the latest.
It is 3PM here.

 

[mitchellb]

Ok, I'll be waiting. Thanks.

 

[richc46]

I noted hes still on line. Hope he explains what happened, so I can understand, too.

 

[richc46]

OK its done, the errors will not affect your problem.

 

[niemiro]

Hello!

Sorry for the delay.

Actually, there is no problem

The only corruption shown in settings.ini

This occurs when a system manufacturer modifies the Windows Sidebar using the sysprep tool. This changes the settings.ini file, so it comes up as corrupt in SFC, although actually it is perfectly valid, and not a problem at all. You can read more about this here: The SFC.exe command reports Settings.ini file errors in the CBS.log file after you add gadgets to the Windows Vista Sidebar by using the Sysprep tool and an Autounattend.xml file

I wish Microsoft would just whitelist this file, because 50% of my work is this one "not-corruption" alone

Your system before the reinstall had this changed sidebar. Sometimes just running sysprep is enough, so you may not have even noticed any additional gadget. But is was there.

When you reinstalled, your OEM reinstall disk contained factory modifications, including sysprep.exe modifications, and this new sidebar.ini. So your SFC log came back.

So, what does this mean? It is not a problem. Any settings.ini corruption on any computer can be safely ignored. Because your manufacturer used sysprep, you will always have this "corruption". But is isn't a problem. Just ignore it. And since there are no other files mentioned, your SFC log is completely clean

Have a great day!

(Another) Richard

 

[mitchellb]

Alright, that's good to hear. Thanks rich. Now I can continue using my pc without errors. Thanks again, and your friend too.

 

[richc46]

LOL hes rich too. If you get another BSOD post. Actually, I think that you will. The corruption shown on those reports do not show hardware, drivers, etc.
Possible causes of BSOD

 

[mitchellb]

Ok, any new errors will be posted here.

How should I install new downloaded software?

Should it be:


[Option 1] Log in Admin account > right click .EXE > run as ADMIN

OR

[Option 2] Log in Standard account > right click .EXE > run as ADMIN