Windows wont shutdown always proberly, error with DWM.exe.

writhziden · 19 Jan 2012

ChronoRunner said:

Here´s pick about end of Vipre scan

http://img600.imageshack.us/img600/8282/viprescan.png

Currently i´m running full scan with malwarebytes

Edit: Malwarebytes didn´t find anything.

proceeding to next step.

i´ve now done also Fakerean removal.

I will do to disk checks after i come back from school witch is approximately after 4 hours from now on.

Glad that some threats were cleaned up by VIPRE Rescue and Malwarebytes came up clean after. Once you get the AIR uninstalled and the errors cleaned up using the links I provided, hopefully the problems will be gone.

ChronoRunner · 19 Jan 2012

Here is now Check disck reports from C: (SSD 80GB for OS) SATA II and D: (HDD 250GB for programs)
I also have 1000gb storage hdd but didn´t include it here yet.

CheckDisk.evtx

writhziden · 19 Jan 2012

Run the disk check again on C: since "Windows has made corrections to the file system."; keep running the disk check on C: until you receive the message that "Windows has checked the file system and found no problems" for the C: drive. Your D: drive already indicated the second message.

ChronoRunner · 19 Jan 2012

Here is the results of the second check for C = SSD

CheckDiskSecondCheckC.evtx

i also ran SFC /SCANNOW Command three times in a row and it didn´t find anything. XD i sure hope everything is now okay. o.o Would it have been possible that my ssd caused this before it was fixed with disc check?

XD i hope the problems are gone now.

Sorry for my bad english.

writhziden · 19 Jan 2012

Looks good. No worries about the English. See if your system is more stable now. If not, proceed to the clean startup step.

kool018 · 23 Jan 2012

I also have this exact same problem. It started a week or so ago. Did you ever get it to shut down properly again?

ChronoRunner · 26 Jan 2012

kool018 said:

I also have this exact same problem. It started a week or so ago. Did you ever get it to shut down properly again?

I did, i followed the instructions given me in this topic post them again for you.
These helped me alot:

"Download and install the free version of Malwarebytes :
Free anti-malware, anti-virus and spyware removal download (do not start the trial)
and make sure it is updated. Do not run a scan yet.

Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet

Download the Fakerean removal tool but do not run it yet.

0 Start your computer in Safe Mode
1 Unzip VIPRE Rescue and let it run.
2 Run a full scan with Malwarebytes.
3 Run the fakerean removal tool.

Run Disk Check with both boxes checked for all HDDs and with Automatically fix file
system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk)
- Read Event Viewer Log
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors.
Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.
Troubleshoot Application Conflicts by Performing a Clean Startup"

Some hotfixes

Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2 to remedy the errors.

Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server.

writhziden · 26 Jan 2012

Glad to see your problem was resolved, ChronoRunner.

If you would like, you can mark this thread as solved by clicking the green button Mark as Solved next to the orange button Post Reply either at the top or bottom of the thread. :)

sirrichard · 11 Sep 2014

writhziden said:

Glad to see your problem was resolved, ChronoRunner.

If you would like, you can mark this thread as solved by clicking the green button Mark as Solved next to the orange button Post Reply either at the top or bottom of the thread. :)

Sorry to hijack an old thread, but having the same problem as the OP I have learned that nowadays Fakerean seems to be a virus instead of a removal tool - so I thought it would be a good idea to issue a warning on that one.

Win32/FakeRean