New
#1
9500GT not working properly in Windows 7?
I am coming to Windows 7 from Vista 64bit Ultimate. On Vista I was able to get aero enabled and my system scored a 4.7 on the winsat tests. When I did a clean install and went to Windows 7 Ultimate 64bit, my aero doesn't want to initiate. I also cannot complete my winsat test because when it gets to hard disk it says could not measure storage performance.
I put in the latest drivers form nvidia's website and I got aero for a few seconds at start up only for it to change back to basic. I have tried forcing aero with those registry edits. I have also tried the troubleshooting transparency and aero effects and it gives me aero for a sec then goes back to basic. The problem it lists is the Desktop Windows Manager to be disabled. I have tried stopping and restarting the Desktop Windows Manager but it only does the same thing as the troubleshooter. I have also tried putting it to high performance in power options and setting it to best visuals but no dice.
My system:
XPS 200 w/ pentium D 2.8ghz with an upgraded 9500GT and 2GB RAM
This was just cleanly installed so application compatibility problems is not likely. I have done all windows updates.
I already have the latest Windows 7 driver installed from Nvidia's website. Themes and DWM Session Manager are both running and are set to automatic.
I created a test account and the same thing happens.
Here is the winsat log:
1987577 (1964) - winsat\logging.cpp:0815: --- START 2010\8\20 18:04:33 PM ---
1987577 (1964) - winsat\main.cpp:4301: Command Line = winsat disk
1987577 (1964) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
1987780 (1964) - winsat\main.cpp:2505: > DWM not running.
1987780 (1964) - winsat\main.cpp:2470: > EMD service will be restored on exit.
1988185 (1964) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
1988185 (1964) - winsat\main.cpp:2793: > power policy saved.
1988419 (1964) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
1988419 (1964) - winsat\main.cpp:2814: > power policy set to maximum.
1988747 (1964) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance
1988747 (1964) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=FALSE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
1988747 (1964) - winsat\main.cpp:1775: > Run Assessment features
1988965 (1964) - winsat\main.cpp:1775: > Run Assessment disk -seq -read -n 0
1995970 (1964) - winsat\main.cpp:1775: > Run Assessment disk -ran -read -n 0
2009027 (1964) - winsat\main.cpp:1775: > Run Assessment disk -scen 2009 -drive C:
2088962 (1964) - winsat\main.cpp:1775: > Run Assessment disk -seq -write -drive C:
2103345 (1964) - winsat\main.cpp:1775: > Run Assessment disk -flush -drive C: -seq
2110833 (1964) - winsat\main.cpp:1775: > Run Assessment disk -flush -drive C: -ran
2126590 (1964) - winsat\main.cpp:1775: > Run Assessment disk -hybrid -ran -read -n 0 -ransize 4096
2126636 (1964) - winsat\main.cpp:1775: > Run Assessment disk -hybrid -ran -read -n 0 -ransize 16384
2126792 (1964) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 530
2126808 (1964) - winsat\processresults.cpp:1498: > Wrote random read disk score to the registry 1300
2126870 (1964) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
2126870 (1964) - winsat\main.cpp:2855: > Power state restored.
2126870 (1964) - winsat\main.cpp:2870: > Successfully reenabled EMD.
2127136 (1964) - winsat\main.cpp:4909: > exit value = 0.
This was just form the disk test and not the whole log since it is too long to post here
Also, I noticed this in Even Viewer:
Log Name: Application
Source: Desktop Window Manager
Date: 8/20/2010 5:39:01 PM
Event ID: 9020
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
The Desktop Window Manager has encountered a fatal error (0x8898009b)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event ">
<System>
<Provider Name="Desktop Window Manager" />
<EventID Qualifiers="49152">9020</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-20T21:39:01.000000000Z" />
<EventRecordID>1113</EventRecordID>
<Channel>Application</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>0x8898009b</Data>
</EventData>
</Event>
then this
Log Name: Application
Source: Desktop Window Manager
Date: 8/20/2010 5:39:02 PM
Event ID: 9009
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer:
Description:
The Desktop Window Manager has exited with code (0x8898009b)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event ">
<System>
<Provider Name="Desktop Window Manager" />
<EventID Qualifiers="16384">9009</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-20T21:39:02.000000000Z" />
<EventRecordID>1114</EventRecordID>
<Channel>Application</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>0x8898009b</Data>
</EventData>
</Event>
(Took out pc name)
and looking at the service in services it is set that if it fails to restart and do this the second time also then if it happens a third time to do nothing. So what happens is for some reason it fails and gets restarted giving me basic for a split second then going back to aero then doing the same thing then stopping and staying in basic mode until I start the system again.
Also, whenever I start up the computer I have aero. I left it sitting there for 15 minutes and it stayed the same. Once I open any program up it reverts back to basic immediately.
Thanks for reading! The help is greatly appreciated!
Quote