SFC/Corrupted Files

Night Hawk · 21 Feb 2010

With the extent of the problems and the "not knowing" about any backups the solution is... "Take No Chances"! and go for broke with a clean install fresh. Once an installation becomes too far polluted with errors it's time for a wipe and start over fresh!

Since you are unable to find root cause for the BSODs you may have been infected with a rootkit form of malware being revealed lately! That will require a drive wipe to get rid of the malware. Microsoft says rootkit caused Windows blue screens

Frostmourne · 21 Feb 2010

This isn't difficult - the dynamic link library in the log in the first post is a transparency component of DWM. Uninstall your current drivers with driver sweeper and install new ones that are WDDM 1.1 certified.

seekermeister · 21 Feb 2010

Frostmourne said:

This isn't difficult - the dynamic link library in the log in the first post is a transparency component of DWM. Uninstall your current drivers with driver sweeper and install new ones that are WDDM 1.1 certified.

Uninstall what? As I recall, Driver Sweeper is only designed to remove video drivers, chipset drivers and a couple of others that I can't remember at the moment, but isn't DWM a OS function?

Frostmourne · 21 Feb 2010

seekermeister said:

Frostmourne said:

This isn't difficult - the dynamic link library in the log in the first post is a transparency component of DWM. Uninstall your current drivers with driver sweeper and install new ones that are WDDM 1.1 certified.

Uninstall what? As I recall, Driver Sweeper is only designed to remove video drivers, chipset drivers and a couple of others that I can't remember at the moment, but isnn't DWM a OS function?

DWM relies on your GPU - get new drivers for them and use Driver Sweeper to clean up the debris.

Night Hawk · 21 Feb 2010

I would advise running a good security sweep of the system perhaps with an online scanner even to see if the problems are stemming from what you haven't been looking for. Secunia has one free of charge at OSI - Consumer - Products

I've been putting 7 through the mill for the last year from beta to retail and have yet to see any blue screen! Have had a few lockups and hard boots even a memory dump or two without any BSODs! Just the same you may want to start looking at other then driver related sources in case you did get winged by something like the rootkit flosting around.

seekermeister · 21 Feb 2010

Frostmourne said:

DWM relies on your GPU - get new drivers for them and use Driver Sweeper to clean up the debris.

Forgive me if I'm being dense, but to be clear on what you are saying, you are talking about the video driver...yes? I have the latest installed, but if it has corrupted, I will reinstall it as suggested.

Frostmourne · 21 Feb 2010

seekermeister said:

Frostmourne said:

DWM relies on your GPU - get new drivers for them and use Driver Sweeper to clean up the debris.

Forgive me if I'm being dense, but to be clear on what you are saying, you are talking about the video driver...yes? I have the latest installed, but if it has corrupted, I will reinstall it as suggested.

Yes, the CBS log points to a DWM error, reinstall the GPU drivers. I would also scan with Sophos Anti-Rootkit, as Night Hawk has pointed out.

Night Hawk · 21 Feb 2010

I had to point that possibility out since there have been a few alerts about those lately for not only BSODs but unexplained system restart problems on 7 machines as well. The Microsoft Security Response Center (MSRC)

seekermeister · 21 Feb 2010

I know that this is a bit of a tangent, but before reinstalling the video driver, I thought it would be good to replace the video card also, because the Vcore 1 voltage is only 1.14v, instead of 1.39volts as set. However, the card that I tried to use was worse, because it wouldn't boot with it, and I got some BIOS beeps, which seem strange (AMI 1 long, 3 shorts), because when I looked it up, it says that it is about a fault in memory above 64MB.

Thinking that I might have dislodged a RAM stick, I reinstalled them and swapped positions, but that had no effect. When I went back to the original video card there were no more beeps and it booted. I undersand that the card that I tried to use is no good, but why would that produce a memory error?

karlsnooks · 21 Feb 2010

cbs.log is an accumulative file. Before I run SFC I always:
Run CMD.EXE as administrator.
Cd \windows\logs\cbs
del cbs.log
exit