Can't rate system in windows experience

Edebarudo · 13 Oct 2009

xyxer said:

same problem same error intel p55 gigabyte p55m-ud4 windows 7 x64 . Seems to me like something with intel matrix storage driver or chipset driver is wonky. My wife's X58 system
completes the WEI perfectly with nearly same hardware except chipset. On the other hand the p55 has failed me with acronis of x58 + new drivers and fresh brand new from scratch install. Shucks MS has dropped the ball here it seems.

Ahhh... Crapzorz! It seems like that error of yours extends to x86, since that's what I'm running...

Oh, so what to do now? Wait until Gigabyte releases new drivers that will be compatible?

Thanks for the help!

ickymay · 13 Oct 2009

I think those drivers are the responsibility of the motherboard manufacturer aren't they ?

I would say yes if the only issue is not being able to run the WEI then it's worth waiting for gigabyte to catch up

Edebarudo · 13 Oct 2009

Aaah... Okey, so I think I'll wait then.

Or, since the WEI worked when I first installed Win 7, should I go back to the Win 7 proprietary drivers?

Since they seemed to work, I mean...

Cheers, and thanks for all the major help guys!!!

BobD · 25 Oct 2009

I had the same problem. It is from a failure of winsat.exe (the engine computing the Windows Experience Index (WEI) in Win7) to play the file Clip_1080_5sec_10mbps_h264 in the Windows/Performance/WinSAT folder (the other clips in the folder play fine for me). This file is played during the WEI phase "Tuning Media Decoding". When it fails, the computer appears to lock up, but it really still running, updating the desktop at about 1 frame per second. This makes if very difficult to move the mouse or to get out of windows even by using the ctl-alt-delete method. But it can be done if you are patient enough to do so. Or you can try and wait out the 600 second deadman timer that weisat.exe uses to bail out. After 10 minutes (or so), the graphics interface is still extremely slow, so you have to get out and reboot to clear it.

I have exactly the same problem with either the ATI 4670 or new ATI HD5850 graphics card. It occurs with the Win7 RTM Home Premium drivers (in the case of the 4670) or the latest Win7 catalyst drivers from the AMD (ATI) site for both the cards.

AMD.com | Support & Downloads

I agree with the above posts that it is probably an issue with the Gigabyte motherboard driver, as I ran WEI fine on a different motherboard, Core 2 CPU E7400 and DDR2 memory.

In my case, after countless hours of swapping hardware, reinstalls of various Win7 software, the only solution I have found with the GA-P55M-UD2 motherboard setup, is to eliminate the Win 7 Aero mode by using a non-Aero Theme. To do so, right Click on the desktop, select "Personalize" and pick a Basic and High Contrast theme - like Windows 7 Basic.

You will lose the AERO features, but WEI will run - at least on my machine!

Hopefully either an update to Win7 or the appropriate drivers will resolve the issue soon.

Bare Foot Kid · 25 Oct 2009

Hello BobD, welcome to Seven Forums; thanks for the info.

michael123 · 27 Oct 2009

Hi guys, just to let you know I had this exact problem on Gigabyte's P55-UD2 chipset, and they've now released a newer BIOS (as of the 22nd Oct) which fixed the issue for me. As it's beta I don't think @BIOS, the bundled program I use to update, installs it automatically, so you'll have to go to the website and download it manually.

Sarezar · 28 Oct 2009

Hello

I got my Windows 7 copy a few days ago and had the same problem. I am mostly playing around to see if I can fix this, not because I care about the score, so I bumped into this thread.

My log mentions the same thing:

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

At the same time, it shows that some of the results are saved in the registry, e.g.:

475615 (2240) - winsat\processresults.cpp:0962: > Wrote cpu expression compression score to the registry 270
476052 (2240) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 590
476068 (2240) - winsat\processresults.cpp:1498: > Wrote random read disk score to the registry 1699

I had a look at the Event Viewer and I get this everytime I run the Windows System Assessment Tool:

Event ID 9010: A request to disable the Desktop Window Manager was made by process (Windows System Assessment Tool)
Event ID 9013: The Desktop Window Manager was unable to start because composition was disabled by a running application

At the end of the tests and just before it stops with an error, it logs this:

Event ID 903: The Software Protection service has stopped.

First, I tried stoppping the dwm.exe before running the Index tool, but it didn't help. Weird thing is that after ending the dwm.exe, every time I tried to restart it, I got this:

Event ID 9009: The Desktop Window Manager has exited with code (0x80070224)

So, I wanted to ask if people think this may be causing the problem. The tests seem to crash at the end when the monitor flashes, so maybe it's because the Desktop Window Manager cannot load (or unload?) properly.

If not, then maybe the Software Protection service has something to do with it, although after running the test 5 times, it only happened twice (at the end), so I'm not so sure it is relevant (and I have no idea why the service stops running)

Finally, I was wondering where are those score settings saved. The log says 'registry', but does it mean Windows registry or some file it creates?

Thanks for reading

GumbyDamnit · 28 Oct 2009

I had the same problem with my P55M-UD2 board w/ F3 bios. I even tried a new Windows 7 re-install -- still had the same problems (could not get the WEI to finish).

I was getting this error: "ERROR: Unable to save validated results." I am using an ATI 4890 card with 9.10 drivers.

I re-flashed to the beta F4g bios from Gigabyte's web site and that fixed the problem! Thanks for the direction you guys gave on this thread!!

thedriver · 14 Nov 2011

GumbyDamnit said:

I was getting this error: "ERROR: Unable to save validated results."
I re-flashed to the beta F4g bios from Gigabyte's web site and that fixed the problem.

Sorry to rehash an old thread, but I wanted to contribute. I had the same problem.

When running the WEI, I was getting the following error:

The Windows Experience Index for your system could not be computed.
Cannot complete assessment.
The assessment or other operation did not complete successfully. This is due to an error being reported from the operating system, drive or other component.

I have read a bunch of info online and clearly a lot of people are or have been affected by this. Although I've tried a lot of supposed fixes, I haven't been able to resolve it.

I'm running Win7 Ultimate x64 (not a Nor KN version) on a Gigabyte GA-EP45-UD3P rev1.6 motherboard (with latest non beta BIOS). Once upon a time the WEI ran, but seemingly not anymore.

The log (C:\Windows\Performance\WinSAT\winsat.log) file is as follows:

3542548 (0712) - winsat\logging.cpp:0815: --- START 2011\11\15 11:35:59 AM ---
3542548 (0712) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent 1e558820-d421-49a4-a9e8-6857a91299e4
3542548 (0712) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
3542548 (0712) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE.
3542595 (0712) - winsat\main.cpp:4585: Watch dog system enabled
3542595 (0712) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds
3542595 (0712) - winsat\main.cpp:3115: A failure occured while trying to read partial assessments from the datastore. Running full assessment
3542595 (0712) - winsat\main.cpp:2490: > DWM Running.
3542860 (0712) - winsat\main.cpp:2497: > turning off DWM.
3542860 (0712) - winsat\main.cpp:2470: > EMD service will be restored on exit.
3543219 (0712) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
3543219 (0712) - winsat\main.cpp:2793: > power policy saved.
3543266 (0712) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
3543266 (0712) - winsat\main.cpp:2814: > power policy set to maximum.
3544186 (0712) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance
3544186 (0712) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
3544186 (0712) - winsat\main.cpp:1775: > Run Assessment features
3544373 (0712) - 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
3556853 (0712) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 5009980
3556869 (0712) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS
3556869 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
3563265 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
3569661 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3
3578850 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3
3587882 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
3594044 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
3600237 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3
3610206 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3
3617865 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname GeomF4 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 150;200;241 -batchcnt C(50);C(200);C(300) -objs C(12);C(26);C(45) -noalpha -geomf4shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1
3626695 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname GeomV8 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75;100;120 -batchcnt C(25);C(100);C(150) -objs C(8);C(17);C(29) -noalpha -geomv8shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1
3634792 (0712) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname CBuffer -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75 -batchcnt C(25) -objs C(8) -rendertotex 6 -rtdelta 3 -texpobj C(1) -cbuffershader -cbufa 2 -cbuff 5 -cbufp 6
3640860 (0712) - winsat\main.cpp:1775: > Run Assessment mfmedia -input C:\Windows\Performance\WinSAT\winsat.wmv -nopmp
3642888 (0712) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_MPEG2_HD_15mbps.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
3649409 (0712) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_VC1_15mbps.wmv -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
3655462 (0712) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480i_5sec_6mbps_new.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
3661920 (0712) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480p_5sec_6mbps_new.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
3668316 (0712) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_10mbps_h264.mp4 -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
3674478 (0712) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480_5sec_6mbps_h264.mp4 -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
3680515 (0712) - winsat\main.cpp:1775: > Run Assessment media -input C:\Windows\Performance\WinSAT\winsatencode.wmv -encode C:\Windows\Performance\WinSAT\winsat.prx
3689829 (0712) - winsat\main.cpp:1775: > Run Assessment moobego
3689829 (0712) - winsat\main.cpp:1775: > Run Assessment cpu -encryption -up
3699906 (0712) - winsat\main.cpp:1775: > Run Assessment cpu -compression -up
3709984 (0712) - winsat\main.cpp:1775: > Run Assessment cpu -encryption2 -up
3720031 (0712) - winsat\main.cpp:1775: > Run Assessment cpu -compression2 -up
3730093 (0712) - winsat\main.cpp:1775: > Run Assessment cpu -encryption
3740311 (0712) - winsat\main.cpp:1775: > Run Assessment cpu -compression
3750529 (0712) - winsat\main.cpp:1775: > Run Assessment cpu -encryption2
3760653 (0712) - winsat\main.cpp:1775: > Run Assessment cpu -compression2
3770902 (0712) - winsat\main.cpp:1775: > Run Assessment mem
3773071 (0712) - winsat\main.cpp:1775: > Run Assessment disk -seq -read -n 1
3775957 (0712) - winsat\main.cpp:1775: > Run Assessment disk -ran -read -n 1
3776331 (0712) - winsat\main.cpp:1775: > Run Assessment disk -scen 2009 -drive C:
3828748 (0712) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 5009980
3828763 (0712) - winsat\processresults.cpp:0962: > Wrote cpu expression compression score to the registry 160
3828763 (0712) - winsat\processresults.cpp:1004: Total physical mem available to the OS : 7.99 GB (8,588,148,736 bytes)
3828763 (0712) - winsat\processresults.cpp:1253: Skipping StdDefPlayback limit check.
3828763 (0712) - winsat\processresults.cpp:1265: Skipping StdDefPlayback limit check.
3828763 (0712) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 760
3828763 (0712) - winsat\processresults.cpp:1498: > Wrote random read disk score to the registry 190760
3828779 (0712) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
3828779 (0712) - winsat\main.cpp:4736: ERROR: Unable to save validated results.
3828826 (0712) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'
3828826 (0712) - winsat\main.cpp:2855: > Power state restored.
3828826 (0712) - winsat\main.cpp:2870: > Successfully reenabled EMD.
3828826 (0712) - winsat\main.cpp:2896: > Composition restarted
3828826 (0712) - winsat\watchdog.cpp:0311: Watch dog system shutdown
3828826 (0712) - winsat\main.cpp:4909: > exit value = 1.[/SIZE]

The line highlighted in Red seemed to be the problem but I couldn't find an answer.

I tried:

Checked event logs - no errors anywhere that related to the running of WEI.
Reset and restored default power plans - Power Plan - Restore Default Settings - Windows 7 Forums.
Reset WEI and delete previous WEI scores - Windows Experience Index - Reset - Windows 7 Forums.
Not running any Kaspersky software.
Not running any Comodo software.
Updated ATI Radeon drivers to latest (11.10).
Updated BIOS to latest (FE).
Disable MS Security Essentials
Uninstall MS Security Essentials
Uninstall Granola Miserware
Disable MalwareBytes AntiMalware

Resolution:
Finally I updated the BIOS to the FFb beta version and after a reboot, the WEI worked first time. I'm not sure why this is the case, but it did work (for me at least) when all else failed.

Thanks for the help of others.

Can't rate system in windows experience

Aaah?

Fixed WEI Problem!