Windows Experience Index unknown error

[Zres]

I previously had vista installed and it performed smoothly.I did a Windows 7(x64) clean install and i kept getting the usual "cannot complete the assessment error".
I updated all BIOS-graphic card drivers and still no solution.

Heres my winsat log :

461170 (4160) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent 5fd3db46-6dc6-4446-84a8-eba83a197488
461185 (4160) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
461201 (4160) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE.
461232 (4160) - winsat\main.cpp:4585: Watch dog system enabled
461232 (4160) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds
462964 (4160) - winsat\main.cpp:2490: > DWM Running.
463198 (4160) - winsat\main.cpp:2497: > turning off DWM.
464960 (4160) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
464960 (4160) - winsat\main.cpp:2793: > power policy saved.
465148 (4160) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
465148 (4160) - winsat\main.cpp:2814: > power policy set to maximum.
465460 (4160) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance
465460 (4160) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
465460 (4160) - winsat\main.cpp:1775: > Run Assessment features
466068 (4160) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock
472183 (4160) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0
472261 (4160) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
474789 (4160) - winsat\processresults.cpp:0962: > Wrote cpu expression compression score to the registry 165
474789 (4160) - winsat\processresults.cpp:1004: Total physical mem available to the OS : 3,99 GB (4.293.320.704 bytes)
474820 (4160) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 520
474835 (4160) - winsat\processresults.cpp:1498: > Wrote random read disk score to the registry 1249
474929 (4160) - winsat\main.cpp:4736: ERROR: Unable to save validated results.
475147 (4160) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
475147 (4160) - winsat\main.cpp:2855: > Power state restored.
475147 (4160) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache.
475179 (4160) - winsat\watchdog.cpp:0311: Watch dog system shutdown
475179 (4160) - winsat\main.cpp:4909: > exit value = 1.

Any help much appreciated.

 

[simone87]

Windows Experience Index error solution Gigabyte P55

I had the same problem since I enabled AHCI mode for Sata controller on my GA-P55-UD3, a motherboard from Gigabyte with P55 chipset. I also had problems with other programs that analyse the pc configuration, like 3DMark Vantage, Fraps and Hardware Monitor.
The problem is probably due from the interaction from the OS, the drivers of the chipset and the bios. You can solve it by updating the bios of the motherboar to the newer version, published on the Gigabyte's site on 30 October.

 

[Flavius]

If anybody have Kaspersky Internet Security 2010 then surly this soft is responsible for this issue

Blocking Windows Experence Index on Windows 7 [Merged] - Kaspersky Lab Forum

 

[Saltgrass]

Watch dog system shutdown
475179 (4160) - winsat\main.cpp:4909: > exit value = 1.

Do you know where the Watch Dog system comes from or why it is running?

Do you have any logs for the anti-virus/spyware or firewall programs with entries around the time you did the scans?

 

[simone87]

I don't have Kaspersky, but AVG free. The problem was

winsat\main.cpp:4736: ERROR: Unable to save validated results.

probably for same error in the implementation of the driver and the bios of Gigabyte's motherboard. I solved it updating the bios from F3 to F4 version.
Watchdog timer is a function that prevents programs from remainig locked for same error: if the program can't run for same problem, the watchdog timer terminates the program.

 

[Bernard46]

Unfortunately I don't have Kapersky - I have McAfee (and had this under Vista with no problem). Also my machine is a Dell XPS420 which although only 18 months old is no longer sold and therefore the BIOS is not going to be updated. Since it worked OK under Vista I guess its most likely to be a Microsoft problem with their Windows 7 implementation, but how can i tell them about it?

 

[Flavius]

Unfortunately I don't have Kapersky - I have McAfee (and had this under Vista with no problem). Also my machine is a Dell XPS420 which although only 18 months old is no longer sold and therefore the BIOS is not going to be updated. Since it worked OK under Vista I guess its most likely to be a Microsoft problem with their Windows 7 implementation, but how can i tell them about it?

Although Vista and Win7 are very similar there are different systems - even if manufacturer declare full compatbility not always is fully true. I suggest to check it.

Of course classic method like update BIOS & drivers are also recommended in this issue

 

[Saltgrass]

probably for same error in the implementation of the driver and the bios of Gigabyte's motherboard. I solved it updating the bios from F3 to F4 version.

There was another post I saw where someone was getting pop-up messages from Gigabyte asking if he wanted it to make changes to his computer. There must be something in that bios that has more authority than I am used to.

 

[Tieske]

My windows 7 didnt recognize my Phentom x4 940 processor. It is a new PC. After i updated my bios the problem was solved.

 

[joeitalo]

Troubleshooting Here is the answer

 

[Bernard46]

Like I said before - if you don't have Kapersky installed then this isn't the answer :huh:

 

[luckman212]

I don't have Kaspersky, and never did.

I can't complete the WinSAT Experience Index either, Win7 x64. Tried with & without AHCI enabled in BIOS.

At this point I think this is a BIOS issue with Gigabyte motherboards. I have a GA-EP45-UD3P v1.6 and have tested BIOS "FC" as well as "FDa" beta. Neither one is working. grr.

 

[Bernard46]

My system has neither Kapersky anti-virus nor a Gigabyte motherboard (its a standard Dell XPS420), so neither of these are the basic cause of this problem - the issue must be something to do with the way that Microsoft has changed the testing it does to calculate the experience index - any idea how we report this to Microsoft?
Bernard