Part deux in my “strange experiences while installing Vista” series 🙂
As mentioned earlier, I installed a clean copy of Vista after replacing the Motherboard and Video Card. The first time I booted up, my Windows Experience Index bottlenecked on the Video Card. Although I have an ATI Radeon X1950 Pro, drivers had not been loaded yet. This was to be expected. If winsat.exe determines that the graphics hardware does not support DirectX 9 (DX9) graphics, then the system receives a graphics score of 1.0 regardless of driver type. If the system supports DX9, but does not have a WDDM Driver (Windows Vista Display Driver Model) the system will then receive a graphics score of 1.9 at the most.
Without the driver loaded, that score will not change.
So… fired up my browser and downloaded/installed the latest Video driver from ATI. Rebooted, hit “Refresh Now”, ran through all the tests, and ended up with…
The same score.
I will save you the play-by-play of what I tried, and will just share the solution(s).
When Windows Vista boots for the first time, it tests all of the components and assigns the initial scores. The scores are stored here:
Every time you refresh your rating, the new ratings are stored in that folder, labeled with the date. These are XML files that you can open and look at if you’d like. They contain a bunch of cryptic information like:
<AdapterDescription>RADEON X600 Series (Microsoft Corporation – WDDM)</AdapterDescription>
<AdapterManufacturer>ATI Technologies Inc.</AdapterManufacturer>
Despite archiving previous winsat runs in this folder, the UI only displays the newest scores (as determined by the date)
The problem that I ran into with the score refreshing will ONLY happen if your clock is set to the future. In my case, this happened because it was a new motherboard, with the clock set at the factory to some random time/date. What that means is that the initial winsat run put a time/date of sometime in the future on the results file. Once Windows hit the desktop, it contacted a time server and reset the time/date to the correct…er… time and date.
This means that the winsat results file from the FUTURE was considered the most recent up until when I refresh my results AFTER passing that date.
The solution, then, is to do one of two things:
1. Wait until after the real date has passed that arbitrary wrong date that the computer clock was initially set to, then refresh your score.
2. Just delete the erroneous results file from C:\windows\Performance\WinSAT\DataStore. Refresh your score, and it will now display correctly. Hooray!