WEI - The Windows Experience Index for your system could not be computed.

Anonymous
2009-10-23T22:29:38+00:00

Hi,

Ive installed a clean copy of Windows7 64bit, on a formatted HD. I am unable to run WEI.

I updated the BIOS for my M3A79-T DELUXE to the latest (1303 rev). Installed all latest drivers for the hardware and latest Windows update.

I have ran c: CHKDSK /F /R /X (Ive seen on a website this has resolve the issue for one person) 

checked all hardware is installed ok and there are no conflicts in device manager.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2009-10-24T11:13:49+00:00

Windows Experience Index has a log file "%SystemRoot%\Performance\WinSAT\winsat.log". That may give some relevant details.

I had the same error message and, in my case, the log file reported "Unable to save". It appears to have been Kaspersky Internet Security 2010 which was blocking WEI from saving the results. The complete WEI test ran OK and even flashed-up the 'completed' message but this was then immediately replaced with the "assessment could not be completed" message ... because it could not *save* the results.

Can I suggest you try another AV package? If you disconnect the network cable you could safely uninstall your existing AV package and see if WEI works again. If that resolves it, perhaps you need a different AV package from now on.

Personally, I found that Microsoft Security Essentials appears to not have this issue and I can now get my rating again. But I may try some other (try before you buy) packages to see what's best.

Worth a try?

Keith.

Was this answer helpful?

30+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2009-11-05T17:14:05+00:00

Hello Everyone,

For those with Kaspersky and this issue, an article was recently released by Kaspersky with their fix for the issue:

http://support.kaspersky.com/faq/?qid=208280937

Thanks!

If you find that my answer was what you were looking for, please remember to click the "mark as answer" box below!

Was this answer helpful?

2 people found this answer helpful.
0 comments

66 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2009-10-24T11:41:03+00:00

    Hi Keith,

    I can see the 'Assessment compelte' this flashes up after 7 seconds from starting the rating then as you mentioned it is replaced with the error.

    I have tried turning off kaspersky 2010, I get the same error message.

    Here is a copy of the WINSAT.LOG file

    I dont know why on the second line its showing the command line = D:\Windows\system32\winsat.exe

    as windows is installed on C:

    There is no d:\windows folder

    ==================================================================

    030201 (0844) - winsat\logging.cpp:0815: --- START 2009\7\13 22:08:30 PM ---

    030232 (0844) - winsat\main.cpp:4301: Command Line = "D:\Windows\system32\winsat.exe" moobe -cancelevent 849bd0b4-8fa1-4e71-8c56-8fdbbf2e34d1 -moobegoevent 27423f94-1309-49e2-9e93-e31a7cd77d2f

    030232 (0844) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured

    030357 (0844) - winsat\main.cpp:4474: > IsFormal=TRUE  IsMoobe=TRUE.

    030420 (0844) - winsat\main.cpp:4585: Watch dog system enabled

    030420 (0844) - winsat\main.cpp:4592: Main watch dog timer set to 60.0 seconds

    030638 (0844) - winsat\main.cpp:2505: > DWM not running.

    031746 (0844) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'

    031761 (0844) - winsat\main.cpp:2793: > power policy saved.

    031886 (0844) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'

    031902 (0844) - winsat\main.cpp:2814: > power policy set to maximum.

    032307 (0844) - d3d\dx9misc.cpp:1030: HRESULT = 8876086a

    032323 (0844) - d3d\dx9misc.cpp:1030: Error: Unable to create the D3D device

    032323 (0844) - d3d\dx9misc.cpp:1030: Error: Unable to check the capabilities of the video card because a d3d device could not be created

    032463 (0844) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance

    032463 (0844) - winsat\main.cpp:0948: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=TRUE  RanOverTs=FALSE  RanOnbatteries=FALSE

    032479 (0844) - winsat\main.cpp:1775: > Run Assessment features

    033009 (0844) - 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

    033150 (0844) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment.

    033446 (0844) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0

    033462 (0844) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS

    033524 (0844) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0

    033540 (0844) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability

    033540 (0844) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0

    033571 (0844) - winsat\main.cpp:0948: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=TRUE  RanOverTs=FALSE  RanOnbatteries=FALSE

    033680 (0844) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability

    033696 (0844) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0

    033696 (0844) - common\winsatutilities.cpp:1382: cannot access the winast API registry key; 2 The system cannot find the file specified.

    033789 (0844) - winsat\main.cpp:2339: > Finalized MOOBE key

    033836 (0844) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'

    033836 (0844) - winsat\main.cpp:2855: > Power state restored.

    033852 (0844) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache.

    033945 (0844) - winsat\main.cpp:2899: INFO: DwmpRestartComposition() did not return OK!

    033961 (0844) - winsat\watchdog.cpp:0311: Watch dog system shutdown

    033977 (0844) - winsat\main.cpp:4909: > exit value = 0.

    =======================================================================

    I will try uninstalling Kaspersky I will let you know the outcome.

    Thanks

    Dave

    Was this answer helpful?

    0 comments
  2. Anonymous
    2009-10-24T11:33:57+00:00

    Hi Deadman,

    I tried SFC /SCANNOW

    It came completed ok with the below message.

    =======================================

    Beginning verification phase of system scan.

    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations

    =======================================

    Tried again and I get the same error message.

    Thanks

    Dave

    Was this answer helpful?

    0 comments
  3. Anonymous
    2009-10-24T11:30:37+00:00

    umm, I read:

    ....

    375697 (4316) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 42076500

    375697 (4316) - winsat\processresults.cpp:0962: > Wrote cpu expression compression score to the registry 159

    375697 (4316) - winsat\processresults.cpp:1004: Total physical mem available to the OS : 3,99 GB (4.290.207.744 bytes)

    375697 (4316) - winsat\processresults.cpp:1253: Skipping StdDefPlayback limit check.

    375697 (4316) - winsat\processresults.cpp:1265: Skipping StdDefPlayback limit check.

    375697 (4316) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 740

    375697 (4316) - winsat\processresults.cpp:1498: > Wrote random read disk score to the registry 136222

    375712 (4316) - winsat\main.cpp:0948: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE

    375712 (4316) - winsat\main.cpp:4736: ERROR:  Unable to save validated results.

    375728 (4316) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'

    375728 (4316) - winsat\main.cpp:2855: > Power state restored.

    375728 (4316) - winsat\main.cpp:2870: > Successfully reenabled EMD.

    375728 (4316) - winsat\main.cpp:2896: > Composition restarted

    375744 (4316) - winsat\watchdog.cpp:0311: Watch dog system shutdown

    375744 (4316) - winsat\main.cpp:4909: > exit value = 1.

    ...

    But i am pretty sure when i tried to install it on the 60GB SSD I just ran WEI as soon as I installed win 7, also I am sure I gave it a try with this installation as soon as I finished installation; and in both case it was not working.

    PS, Now I look at the log and I see the first 2 attempts gave this results:

    033150 (0844) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment.

    033446 (0844) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0

    033462 (0844) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS

    033524 (0844) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0

    033540 (0844) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability

    033540 (0844) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0

    033571 (0844) - winsat\main.cpp:0948: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=TRUE  RanOverTs=FALSE  RanOnbatteries=FALSE

    033680 (0844) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability

    033696 (0844) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0

    033696 (0844) - common\winsatutilities.cpp:1382: cannot access the winast API registry key; 2 The system cannot find the file specified.

    033789 (0844) - winsat\main.cpp:2339: > Finalized MOOBE key

    033836 (0844) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'

    033836 (0844) - winsat\main.cpp:2855: > Power state restored.

    033852 (0844) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache.

    033945 (0844) - winsat\main.cpp:2899: INFO: DwmpRestartComposition() did not return OK!

    033961 (0844) - winsat\watchdog.cpp:0311: Watch dog system shutdown

    033977 (0844) - winsat\main.cpp:4909: > exit value = 0.

    Since I had no updated dsrivers installed.

    So I now have Vipre installed as antivirus, I try to remove it and see what happens

    Was this answer helpful?

    0 comments