locked
Windows Experience Index refresh has an error RRS feed

  • Question

  • Hi, is there anyone have some problem like me concering Windows Experience Index?

    When I finish setup Vista RTM Build 6000, my windows experience index was "Unrated".

    So I click this hypertext at computer properties page, "Performance Information and Tools" appeared from control pannel, I found exclmation mark at somewhere in this screen and it says "New hardware detected, Your Windows Experience Index needs to be refreshed".

    But I didn't recognize any new hardware in my computer, I don't know why this message was there, I click "Refresh Now" button anyhow.

    When I click this button, some Rating procedure screen was appered, and proceding meter was seems works well. But some message box was appeared when assesment procedure was just finished, it says...

    "Cannot complete assesment. The assessment or other operation did not complete successfully. This is due to an error being reported from the operating system, driver, or other component"

    Why this happen and how can I make index rating without error?

    I need some specialist's help...

    Sunday, December 3, 2006 3:37 AM

Answers

  • Hey, i had the same problem, with the Exp index, but found a solution on another forum, im not sure if its allowed to make a link to the post so ill quote the poster instead, all credits goes to him.

    Caleb wrote

    Try doing the following:

    Go to: %systemroot%\Performance\WinSAT\DataStore and try to delete everything but the most recent file... then try doing the reassesement.

     

     

    Wednesday, January 31, 2007 12:14 AM

All replies

  • I've got the same problem. When I try to refresh the rating the system goes through the complete checking cycle, but finishes with nothing done. I still have the 'Found new hardware' message.

    My machine is an Asus A7T laptop. I got almost all devices working under Vista build 6000, except the webcam, VID_174F&PID_A311, (D-Max?) which sometimes (!?!) gives an error in Device Manager, and an Unknown device VID_1180&DEV_0852 (that's Ricoh Co. Ltd), which might be a webcam, or a Memory-card reader. Maybe this is related...

     

    Tuesday, December 5, 2006 12:53 AM
  • Same problem here, although taking a look at the event log I get the following error displayed:

    The Desktop Window Manager was unable to start because WDDM is not in use

    I have checked my display adapter and it is set to:

    MOBILITY RADEON X700 (Microsoft Corporation - WDDM)

    Which is the correct adapter and presumably with WDDM.

    In what I consider the ultimate irony, this is on a Sony Vaio built for Windows, I have also just installed Vista on a Mini-Mac and it works perfectly, glass and all...

    Wednesday, December 6, 2006 7:29 AM
  • My VGA driver is nvidia 97.72 Guru3D version because of resolution problem.

    My Sound driver is not WDDM because I have SoundBlaster Audigy LS.

    Mu Scanner is HP Scanjet 3670 and it has not even driver yet...!

    But I had been success about Experience Index Refresh procedure when I use BillGates version of Vista RTM.

    Now my Vista is MSDN version, what is differences between this two version???

    When I use BillGates Vista, the Windows Experience Index hadn't any problem.

    It's very odd, maybe we have to wait retail...???

    Wednesday, December 6, 2006 8:13 PM
  • I'm having the same problem with the same Ati mobility X700 graphics card and the Ati drivers.

    When i click "refresh now" an event log "A request to disable the Desktop Window Manager was made by process (winsat.exe pid)" is created, followed by a couple of "The Desktop Window Manager was unable to start because composition was disabled by a running application" logs.

    The score however doesn't get changed, and the "new hardware detected" and "windows experience rating : not rated" messages remain.

    Thursday, December 14, 2006 5:04 PM
  • I have an Alienware m5500, the system analisys went fine, and the install went okay, but I am having the same problem. I also have a Dell Optiplex GX520 thich ran the Windows Experiance Index properly during install, but is generating the same message when I try to "Update My Score".

    I have found nothing in Event Viewer inidicating an error.

    Friday, December 15, 2006 6:08 PM
  • Built my first computer and installed Vista RC1 build 5600. Intel DG965Wh mother board "onboard graphics". Everything worked fine, my computer over all score was 3.6.

    Just installed EVGA GeForce 7950 GT KO. Windows detected it as a "Standard VGA Adapter" Lost the Aero glas capabilities. Computer resolution turned horrible, couldn't find any updated drivers from Nvidia other than one only for RC2 5744 or higher.

    Took out the graphics card and not I recieve the same error as you guys.

    ! New hardware detected.

    When I try to refresh my index, it doesn't finish and it reports and error.

    It seems to me "and I am not a techonolgy expert" That it has something to do with the Graphics card driver. I don't understand why don't they have them out yet?

    If any of you guys found a solution please email me I would really appreciate it.

    email: kinghaddad@hotmail.com

     

    Wednesday, December 20, 2006 2:32 AM
  • I am still getting the same error.

    In the C:\Widows\Performance\winSAT\winsat.txt log I keep getting the same error.

    winsat\main.cpp:1430: > Assessment FAILED due to an error

    When I run "winsat formal -v" I receive the below error.

    Error: Failed to properly assess the disk.
    The drive cannot locate a specific area or track on the disk.

    Thursday, December 21, 2006 12:50 AM
  • Thank you for pointing out to that log file. I get the following error:

    3843062 (3736) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 0'
    3843093 (3736) - winsat\main.cpp:1430: > Assessment FAILED due to an error

    I wonder what the problem is, because the disk seems to be operate fine.

    Thursday, December 21, 2006 9:42 AM
  • Well Ladies and Gentleman, I can proudly say that I have fixed all the problems with the experience index. It turned out to be that the problem was with the driver for the graphic card. I downloaded a beta driver from Nvidia's website and everything now works perfect. My computer scores:

    Processor (E6300): 4.8

    MEmory (2x1GB unbuffered 533) : 5.1

    Graphics (Geforce 7950 GT) : 5.9

    I guess most of those techinical issues are driver related (as always0

     

    Good luck everybody.

    Thursday, December 21, 2006 2:06 PM
  • I am having the same issue on my Dell Optiplex GX520 in the office, I am getting the same errors as I am with my notebook at home.
    Thursday, December 21, 2006 3:08 PM
  • Same problem for me although it was all ok after I first installed RTM 6000. I'm not sure but I suspect the problem occured either after I updated to the new Beta ATI drivers from 13th DEC 2006 or when I replaced two 512 RAM modules with 2 1GB modules.

    Specs.

    Z96JA built by Asus Core Duo T2400
    Intel® Core™ Duo processor T2400 (1.83GHz, 2MB cache, 667MHz FSB)
    ATI® Mobility™ Radeon® X1600 accelerator with up to 1024MB HyperMemory™
    120GB IDE hard drive (5400 rpm), 2GB (2 x 1024MB) DDR2 667 SDRAM

    Winsat logs.

    Ok the first one is the last log I got a rating from.

    124525078 (4576) - winsat\main.cpp:2295: --- START 2006 23:31:44 PM ---
    124525265 (4576) - winsat\main.cpp:2567: > IsFormal=TRUE  IsMoobe=FALSE.
    124525296 (4576) - winsat\main.cpp:1974: > DWM Running.
    124525515 (4576) - winsat\main.cpp:1987: > turning off DWM.
    124525671 (4576) - winsat\main.cpp:2051: > EMD device detected to be on.  EMD will be restored on exit.
    124525812 (4576) - mlib\syspowertools.cpp:0872: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
    124525968 (4576) - winsat\main.cpp:2108: > power policy saved.
    124526187 (4576) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    124526265 (4576) - winsat\main.cpp:2120: > power policy set to maximum.
    124527171 (4576) - winsat\main.cpp:2756: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE
    124527203 (4576) - winsat\main.cpp:1161: > Running Assessment: features ''
    124527796 (4576) - winsat\main.cpp:1436: > Assessment completed
    124527843 (4576) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'
    124573781 (4576) - winsat\main.cpp:1390: > DWM Assessment completed
    124573843 (4576) - winsat\processresults.cpp:2109: > Wrote video memory bandwidth to the registry 3372340
    124574031 (4576) - winsat\main.cpp:1408: > DWM Assessment results processing SUCCESS
    124574062 (4576) - winsat\main.cpp:1436: > Assessment completed
    124574078 (4576) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    124588562 (4576) - winsat\main.cpp:1436: > Assessment completed
    124588625 (4576) - winsat\main.cpp:1161: > Running Assessment: moobego ''
    124588656 (4576) - winsat\main.cpp:1161: > Running Assessment: mfmedia '-input {winsat.wmv} -nopmp'
    124593062 (4576) - winsat\main.cpp:1436: > Assessment completed
    124593109 (4576) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption'
    124603625 (4576) - winsat\main.cpp:1436: > Assessment completed
    124603687 (4576) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression'
    124613937 (4576) - winsat\main.cpp:1436: > Assessment completed
    124613984 (4576) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption2'
    124624203 (4576) - winsat\main.cpp:1436: > Assessment completed
    124624265 (4576) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression2'
    124634453 (4576) - winsat\main.cpp:1436: > Assessment completed
    124634515 (4576) - winsat\main.cpp:1161: > Running Assessment: mem ''
    124639593 (4576) - winsat\main.cpp:1436: > Assessment completed
    124639703 (4576) - winsat\main.cpp:1161: > Running Assessment: disk '-seq -read -n 0'
    124662375 (4576) - winsat\main.cpp:1436: > Assessment completed
    124662437 (4576) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 0'
    124662578 (4576) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    124662671 (4576) - winsat\processresults.cpp:0672: Total physical mem available to the OS : 1.99 GB (2,146,107,392 bytes)
    124663015 (4576) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'
    124663031 (4576) - winsat\main.cpp:2155: > Power state restored.
    124663062 (4576) - winsat\main.cpp:2171: > Successfully reenabled EMD.
    124663125 (4576) - winsat\main.cpp:2193: > Composition restarted
    124663171 (4576) - winsat\main.cpp:3216: > exit value = 0.

    This one failed to rate a brought up the error.



    063078 (1696) - winsat\main.cpp:2295: --- START 2007\1\1 18:36:26 PM ---
    067218 (1696) - winsat\main.cpp:2567: > IsFormal=TRUE  IsMoobe=FALSE.
    067250 (1696) - winsat\main.cpp:1974: > DWM Running.
    067421 (1696) - winsat\main.cpp:1987: > turning off DWM.
    067468 (1696) - winsat\main.cpp:2051: > EMD device detected to be on.  EMD will be restored on exit.
    067500 (1696) - mlib\syspowertools.cpp:0872: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
    067531 (1696) - winsat\main.cpp:2108: > power policy saved.
    067703 (1696) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    067781 (1696) - winsat\main.cpp:2120: > power policy set to maximum.
    068703 (1696) - winsat\main.cpp:2756: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE
    068843 (1696) - winsat\main.cpp:1161: > Running Assessment: features ''
    070718 (1696) - winsat\main.cpp:1436: > Assessment completed
    070843 (1696) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'
    118609 (1696) - winsat\main.cpp:1390: > DWM Assessment completed
    118843 (1696) - winsat\processresults.cpp:2109: > Wrote video memory bandwidth to the registry 3350560
    119234 (1696) - winsat\main.cpp:1408: > DWM Assessment results processing SUCCESS
    119265 (1696) - winsat\main.cpp:1436: > Assessment completed
    119296 (1696) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    119859 (1696) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    120062 (1696) - winsat\main.cpp:1161: > Running Assessment: moobego ''
    120125 (1696) - winsat\main.cpp:1161: > Running Assessment: mfmedia '-input {winsat.wmv} -nopmp'
    125546 (1696) - winsat\main.cpp:1436: > Assessment completed
    125765 (1696) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption'
    136437 (1696) - winsat\main.cpp:1436: > Assessment completed
    136500 (1696) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression'
    146734 (1696) - winsat\main.cpp:1436: > Assessment completed
    146765 (1696) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption2'
    156937 (1696) - winsat\main.cpp:1436: > Assessment completed
    156968 (1696) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression2'
    167156 (1696) - winsat\main.cpp:1436: > Assessment completed
    167203 (1696) - winsat\main.cpp:1161: > Running Assessment: mem ''
    172281 (1696) - winsat\main.cpp:1436: > Assessment completed
    172375 (1696) - winsat\main.cpp:1161: > Running Assessment: disk '-seq -read -n 0'
    192359 (1696) - winsat\main.cpp:1436: > Assessment completed
    192484 (1696) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 0'
    192531 (1696) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    192562 (1696) - winsat\processresults.cpp:0672: Total physical mem available to the OS : 1.99 GB (2,146,107,392 bytes)
    192812 (1696) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'
    192859 (1696) - winsat\main.cpp:2155: > Power state restored.
    192890 (1696) - winsat\main.cpp:2171: > Successfully reenabled EMD.
    192937 (1696) - winsat\main.cpp:2193: > Composition restarted
    193000 (1696) - winsat\main.cpp:3216: > exit value = 1.

    The problem appears to lie here:

    119296 (1696) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    119859 (1696) - winsat\main.cpp:1430: > Assessment FAILED due to an error

     

    Thursday, January 4, 2007 10:53 AM
  • Just to add to my above post I ran winsat from the cmd and saved to txt (winsat formal -v >> c:\winsat.txt). The trouble is here I think.

    > Run Time 00:00:44.78

    > Running: Media Decode/Encode Assessment v1.0.0.0 '-input C:\Windows\Performance\WinSAT\winsatencode.wmv -encode C:\Windows\Performance\WinSAT\\winsat.prx -v'

    Initializing COM.

    Creating temporary file for encoding output...

    Temporary output file "C:\Users\Tim\AppData\Local\Temp\wst45FF.tmp" created.

    Creating temporary file for ETW kernel trace...

    Temporary trace file "C:\Users\Tim\AppData\Local\Temp\wst4600.tmp" created.

    Creating filter graph.

    Loading encoder profile from "C:\Windows\Performance\WinSAT\\winsat.prx".

    Creating encoder, saving to temporary file.

    FAIL: mediaencode.cpp @ 572: 0xc00d0bc2 == Unknown

    ({AMGetErrorText() failed!})

    FAIL: mediatest.cpp @ 466: 0xc00d0bc2 == Unknown

    ({AMGetErrorText() failed!})

    Deleting temporary output file "C:\Users\Tim\AppData\Local\Temp\wst45FF.tmp"...

    Deleting temporary ETW trace "C:\Users\Tim\AppData\Local\Temp\wst4600.tmp"...

    > Run Time 00:00:00.41

    Any Ideas?

    Thursday, January 4, 2007 11:26 AM
  • anyone could fix this?
    Friday, January 12, 2007 10:35 PM
  • I'd be really interested in this as I've just finished building a new PC and now that I have all the hardware installed I'd like to refresh the WEI but it fails (although if I do a clean install on another partition the refresh works for some strange reason).  These are the points it fails:

    98099372 (2440) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'

    127343 (3176) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'

    I think this might be down to nVidia's drivers (I'm using the full release from Windows Update) but can't be certain.  The old machine (P4 3.2Ghz, GeForce 6800GT (AGP8x), ASUS P4C800-E Deluxe) used to refresh fine.  The new PC is a E6600 (Core 2 Duo), GeForce 7950GT, ASUS P5B Deluxe Wi-Fi.

    This one is really bugging me and as far as I can tell this is the only thread on this topic having searched Live & Google.

    Sunday, January 14, 2007 9:38 PM
  • No it isnt due to Nvidias drivers, I Clean uninstalled the drivers and then when windows installed the default one the test didnt work. Longview try using something called driver cleaner pro, it removes the nvidia card driver and then vista will install its own as default.

    What does it bring up when u use the verbose command in the command prompt?

    Mine is the same as the one mentioned above by Fr33 unknown error. This sucks.

     

    Thursday, January 18, 2007 7:25 PM
  • Well unfortunately I had to reformat, I had a feeling I was wrong and the nVidia beta drivers somehow damage the windows experience index. I asked the Reps from the Vista team but they did not know how it messed up either so it was the only way. Im no longer on the 64 bit version but the 32 (not that that makes a difference) but ill be running the test more often after program installs :)
    Sunday, January 21, 2007 12:55 AM
  • Thanks for the update and tips.  I've been getting a reboot roughly every 3 days so I'm trying to sort that out now which is more important to me than figuring out how to refresh the windows index.  I'm also having problems with sleep so I'm thinking that some software install or driver is causing some stability issues.  I'm thinking about a re-install too and if I go down that road I'll be trying to refresh the score and also enter sleep between each software and driver install.  Thanks again for the information and I'll report back if I get the index score to refresh.
    Friday, January 26, 2007 10:08 PM
  • Hey, i had the same problem, with the Exp index, but found a solution on another forum, im not sure if its allowed to make a link to the post so ill quote the poster instead, all credits goes to him.

    Caleb wrote

    Try doing the following:

    Go to: %systemroot%\Performance\WinSAT\DataStore and try to delete everything but the most recent file... then try doing the reassesement.

     

     

    Wednesday, January 31, 2007 12:14 AM
  • Well I shall if i experience that error again. Has anyone else tried it?
    Wednesday, January 31, 2007 12:20 AM
  • Well I have re-installed using my shiny new copy of Vista Ultimate and so far I've had no issues refreshing the index score so I guess some files got corrupted somewhere.  I wouldn't be surprised to see this issue fixed in either a hotfix or the SP1 scheduled for release late 2007.  If deleting some files is all that is needed then it makes sense to have the system self clean.
    Friday, February 2, 2007 10:22 AM
  • I deleted everything in %systemroot%\Performance\WinSAT\DataStore

    Did a reboot and then refreshed the rating.

    That FINALLY worked!

    I have an HP Laptop with an NVIDIA GO 7600. 

     

    Saturday, February 10, 2007 12:38 AM
  • Try doing the following:

    Go to: %systemroot%\Performance\WinSAT\DataStore and try to delete everything but the most recent file... then try doing the reassesement.

     this WORK FINE with me man thanks a lot

     

    Tuesday, February 13, 2007 6:38 PM
  • Hi Fr33


    Just wanted to ask if you solved the problem? I'm getting the exact same error.



    The problem appears to lie here:

    119296 (1696) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    119859 (1696) - winsat\main.cpp:1430: > Assessment FAILED due to an error


    looks like the WMV encoder cannot be initialized..therefore I'm thinking WMP11 is the culprit, but I know of no way to reinstall or repair it without a new install from Vista.... and I'm not going down that road again!

    Tuesday, February 20, 2007 7:07 PM
  • Hi jaddi01, No sorry still got the prob but I believe its something to to with the Vista Codecs. Have not had a chnace to delv further but will asap.
    Saturday, February 24, 2007 9:14 AM
  • Hello EveryOne witj WEI problems.

    I absolotely believe it's a codec problem and some display drivers installations make "defaults" for encoding/decoding

    I have used the WEI about 2 weeks with full function but now the winsat log says:
    793796 (4312) - winsat\main.cpp:1161: > Running Assessment: media '-input winsatencode.wmv -encode winsat.prx -v'
    794218 (4312) - winsat\main.cpp:1430: > Assessment FAILED due to an error

    If I run it in the console:
    Run: Utvärdering av kodning och avkodning av media v1.0.0.0 '-input winsatencode.wmv -encode winsat.prx -v'
    Initializing COM.
    (Im swedish so im trying to translate the above line: Evaluation of encoding and decoding of media v1.0.0.0 '-input winsatencode.wmv -encode winsat.prx -v' )

    Creating temporary file for encoding output...
    Temporary output file "E:\Users\JONNYA~1\AppData\Local\Temp\wstED34.tmp" created.
    Creating temporary file for ETW kernel trace...
    Temporary trace file "E:\Users\JONNYA~1\AppData\Local\Temp\wstED35.tmp" created.
    Creating filter graph.
    Loading encoder profile from "winsat.prx".
    Creating encoder, saving to temporary file.
    FAIL: mediaencode.cpp @ 572: 0xc00d0bc2 == Unknown      
        ({AMGetErrorText() failed!})
    FAIL: mediatest.cpp @ 466: 0xc00d0bc2 == Unknown   
       ({AMGetErrorText() failed!})

    It is possible to run "winsat media..." without the "-encode winsat.prx" and then there is no error but the WEI will not run correctly.

    The only thing i have installed after the successfully runs are: VLC mediaplayer, DivX 6.5.1 Codecs (from MS site) and the DreamScene Preview (KB929327) update for Vista Ultimate.

    I have also of course tried to reinstall and update my ATI drivers for the my graphics card without any success.


    I hope SomeOne SOON can reply to all these post with som kind of solution.

    /jonny

    Monday, February 26, 2007 8:27 PM
  • Well mine was because of the nvidia BETA drivers (the RC2 ones) Fr33 did you install these drivers? Or any other  beta graphics drivers?
    Monday, February 26, 2007 8:41 PM
  • Anyone got a "codec checkup/cleaning utilty" for Vista?
    Monday, February 26, 2007 9:11 PM
  • Gazza Im using ATI but yeh it was working with the WDMs and I installed ATI beta and it still worked sometime after that it stopped. I install the first full release and codec since. Im not interested in doing a restore. I have looked at all the stuff I have installed but I really cant put a finger on it. I really would like to just fix it if I can without going back. Its no really bothering me yet.
    Tuesday, February 27, 2007 6:48 AM
  • Indeed i have got the same problem with the codecs. I think it began after i installed the new nvidia forceware drivers (WCQL)

    I even have Windows Media Encoder installed to encode a webcam stream. that doesn't work anymore.
    also the windows Movie maker etc. isn't working anymore. does anyone has the same problem.

    all of this seems to me pointing to a codec problem. is there a way to refresh / reinitialze the default codec settings?

    in waht way does the nvidia driver infuence the codecs?? is that possible?

     

     

    Wednesday, February 28, 2007 10:09 AM
  •  LongView_UK wrote:

    These are the points it fails:

    98099372 (2440) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'

    127343 (3176) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'

    I think this might be down to nVidia's drivers (I'm using the full release from Windows Update) but can't be certain.  The old machine (P4 3.2Ghz, GeForce 6800GT (AGP8x), ASUS P4C800-E Deluxe) used to refresh fine.  The new PC is a E6600 (Core 2 Duo), GeForce 7950GT, ASUS P5B Deluxe Wi-Fi.

    This one is really bugging me and as far as I can tell this is the only thread on this topic having searched Live & Google.

     

    I am having the same issue with almost the same set up.  

    E 6600, xfx 7950 xtreme,

    Motherboard 975xbx2   It would seem that the native Intel codecs should be fine but the Windows Media Center isn't playing nice with WEI.  When booting my sound gets delayed about 2 seconds.  It's a windows issue.   

    Any solutions?   

    Wednesday, February 28, 2007 2:38 PM
  • This is soo frustrating...I have tried to check what codecs is fault by using "gspot" but its says nothing bad.

    the errorcodes from winsat says:
    FAIL: mediaencode.cpp @ 572: 0xc00d0bc2 == Unknown
          ({AMGetErrorText() failed!})
    FAIL: mediatest.cpp @ 466: 0xc00d0bc2 == Unknown

    i have tried to figure out what thiserror is and it point to a codec problem i think.

    I bet it solved by unregister /u "wrong-thing" and then re-register "right-thing it again.....but...but...but

    And im not convinced a repair or reinstall of Vista will solve it....so....just try and try and hopefully SomeOne out here will solve it!

    Wednesday, February 28, 2007 5:13 PM
  • I have the same issue and a reinstall will fix it until media center gets reactivated. 

    32 bit home premium

    e6600, 975XBX 2

    XFX 7950 xtreme

     

    Wednesday, February 28, 2007 6:01 PM
  • power1,

    Does the problem started after installing the nvidia display drivers?
    or do you still use the default windows vista display drivers?

    hope to hear from you!

     

     

    Thursday, March 1, 2007 11:56 AM
  •  BigBas wrote:

    power1,

    Does the problem started after installing the nvidia display drivers?
    or do you still use the default windows vista display drivers?

    hope to hear from you!

     

     

    I am using the XFX forceware driver 97.41 and WEI is currently updating correctly.  I completed a reinstall to make WEI work again.  The issue doesn't seem to be with my Nvidia.  When WEI stops working, again I will post any changes or updates that could be causing the problem. 

     

    Power1

    Friday, March 2, 2007 5:00 PM
  • I also now have a fully working WEI after a re-install when I received my retail version of Vista Ultimate so it does seem that something is getting messed up.  In my case I believe it was the fact that my computer blue screened during the initial WEI that Vista calculates at the end of the install.  If the solution posted here (deleting some files) works then it does seem that WEI needs to do some cleaning up should a refresh of the score not complete.  I never tested that out since I went for the full install.  I've now solved my instability issues which was down to a faulty PSU.
    Friday, March 2, 2007 11:47 PM
  • Some solutions yet?

    anybody?

    Monday, March 19, 2007 7:22 PM
  • I've found my way to resolve this by deleting my pinnacle studio software completely. Maybe this can help to somebody!

    You know, want my wise? Place some time (several hours) to make clean installation of Windows Vista (even without cd-key, you won't need it) on some other HDD and do tests of WEI, installing software one by one till it makes an error! Thus you can figure out what is bad. So this way helped me already!

     

    Wish luck!

    Wednesday, March 21, 2007 4:34 PM
  • Same problem here. Same video driver as when it last worked, so.... Latest results:

    1713842 (4896) - winsat\main.cpp:2295: --- START 2007\4\9 11:25:46 AM ---
    1714372 (4896) - winsat\main.cpp:2567: > IsFormal=TRUE  IsMoobe=FALSE.
    1714388 (4896) - winsat\main.cpp:1974: > DWM Running.
    1714716 (4896) - winsat\main.cpp:1987: > turning off DWM.
    1714872 (4896) - winsat\main.cpp:2051: > EMD device detected to be on.  EMD will be restored on exit.
    1714918 (4896) - mlib\syspowertools.cpp:0872: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
    1715012 (4896) - winsat\main.cpp:2108: > power policy saved.
    1715293 (4896) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    1715355 (4896) - winsat\main.cpp:2120: > power policy set to maximum.
    1716151 (4896) - winsat\main.cpp:2756: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE
    1716166 (4896) - winsat\main.cpp:1161: > Running Assessment: features ''
    1717555 (4896) - winsat\main.cpp:1436: > Assessment completed
    1717586 (4896) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'
    1822356 (4896) - winsat\main.cpp:1390: > DWM Assessment completed
    1822528 (4896) - winsat\processresults.cpp:2109: > Wrote video memory bandwidth to the registry 1724490
    1822653 (4896) - winsat\main.cpp:1408: > DWM Assessment results processing SUCCESS
    1822668 (4896) - winsat\main.cpp:1436: > Assessment completed
    1822684 (4896) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    1823745 (4896) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    1823807 (4896) - winsat\main.cpp:1161: > Running Assessment: moobego ''
    1823838 (4896) - winsat\main.cpp:1161: > Running Assessment: mfmedia '-input {winsat.wmv} -nopmp'
    1831638 (4896) - winsat\main.cpp:1436: > Assessment completed
    1831779 (4896) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption'
    1835367 (4896) - winsat\main.cpp:1436: > Assessment completed
    1835757 (4896) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression'
    1846459 (4896) - winsat\main.cpp:1436: > Assessment completed
    1846505 (4896) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption2'
    1849688 (4896) - winsat\main.cpp:1436: > Assessment completed
    1849735 (4896) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression2'
    1859984 (4896) - winsat\main.cpp:1436: > Assessment completed
    1860015 (4896) - winsat\main.cpp:1161: > Running Assessment: mem ''
    1865147 (4896) - winsat\main.cpp:1436: > Assessment completed
    1865272 (4896) - winsat\main.cpp:1161: > Running Assessment: disk '-seq -read -n 0'
    1886052 (4896) - winsat\main.cpp:1436: > Assessment completed
    1886067 (4896) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 0'
    1886161 (4896) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    1886317 (4896) - winsat\processresults.cpp:0672: Total physical mem available to the OS : 0.98 GB (1,063,071,744 bytes)
    1886332 (4896) - winsat\processresults.cpp:0732: Physical memory available to the OS is less than or equal to 1.5GB - limit mem score to 4.5
    1886535 (4896) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'
    1886551 (4896) - winsat\main.cpp:2155: > Power state restored.
    1886566 (4896) - winsat\main.cpp:2171: > Successfully reenabled EMD.
    1886582 (4896) - winsat\main.cpp:2193: > Composition restarted
    1886629 (4896) - winsat\main.cpp:3216: > exit value = 1.

    HELP!

    Monday, April 9, 2007 3:51 PM
  • I had the same problem with my new install of vista and a sony vaio. The reason you cant run winsat correctly is because your machine will not play back wmv files correctly, I found that when i run /windows/performance/winsat/winsat.wmv or winsatencode.wmv manually it will not play back in media player.  Winsat i presume plays these files in the background as a test so that it can get an idea of frame rates etc.  I have had endless trouble trying to find a ati mobility driver for my card as amd has bought over ati and no longer supports the mobility chipsets, they say goto your manufacturer which mostly are unsure themselves.

     

    The solution is to install the ati drivers produced before the amd takeover, they can be downloaded from here.

     

    http://drivers.softpedia.com/get/GRAPHICS-BOARD/ATI/ATI-Catalyst-Video-Driver-Beta-Vista-RC1.shtml

     

    Hope this helps you, it worked perfectly for me.


    Friday, April 20, 2007 6:03 PM
  • This is somewhat very late reply but eventually it works fine.

    Thanks for your dig, I hope it will help the others who have same problem.

    Sunday, April 22, 2007 7:05 PM
  • Well I had this issue resurface after fixing it with a re-install.  I started to refresh the score then realised I had something big still running which would have affected the score so I cancelled it.  Then each time I tried to run it again it crashed just like before.  I followed the advice posted here earlier about deleting all files in the drive:\Windows\Performance\WinSat folder and as soon as I did that it worked again.

     

    I think there really is an issue with the process that calculates the score in that it doesn't tidy up after itself correctly if the process is cancelled or it fails.  I'm sure a fix for this will be in the first service pack as it must be an easy one to fix.  Just clean out the folder after each run of the WEI process regardless of if it fails or succeeds.  Alternatively clean out that folder just before it runs each time.

    Sunday, April 22, 2007 7:34 PM
  • Getting the same WMV Encoding problem too. Gonna try and uninstall graphics drivers and see if it works.

    EDIT:

    Doesn't do anything, I noticed this WMV Encoding thing stopped me from running PCMark05 too but I could get a rating on WEI. Only now it affects both.
    Monday, April 23, 2007 7:54 PM
  • I'm sure that if you follow the advice I gave above about deleting the files you'll have it working again.
    Monday, April 23, 2007 8:45 PM
  • i tried that too. now i have no wei Stick out tongue
    ill reinstall when i get my new cpu soon.
    Monday, April 23, 2007 8:54 PM
  • Oops! Perhaps you need to keep the wmv files and the winsat.prx file since these are all dated 2nd November 2006 on my system.
    Tuesday, April 24, 2007 7:36 PM
  • yea i did, still didnt work. anyway, i installed ntune for vista, which seemed to cause it to mess up and not boot, quick reinstall and its working now. Smile
    Tuesday, April 24, 2007 7:57 PM
  • try installing or re-installing your drivers, and then do this:

    http://wiki.cdyne.com/index.php/Windows_Experience_Index_refresh_has_an_error

     

    it may or may not work for you, but it did for me!

     

     

    Tuesday, April 24, 2007 9:21 PM
  • the same error

    214968 (3368) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    215796 (3368) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    270406 (3368) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 1'
    270593 (3368) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    ---------------------------------------------------------------------------------------------------------

    in open winsat.prx in notepad

     

    <profile version="589824"
                 storageformat="1"
                 name="WinSAT Test Profile"
                 description="A test profile designed for use by WinSAT as part of formal assessments.">
                       <streamconfig majortype="{73646976-0000-0010-8000-00AA00389B71}"
                       streamnumber="1"
                       streamname="Video Stream"
                       inputname="Video409"
                       bitrate="2638200"
                       bufferwindow="5000"
                       reliabletransport="0"
                       decodercomplexity="AU"
                       rfc1766langid="en-us"
     >
                         <videomediaprops maxkeyframespacing="50000000"
                                         quality="85"/>
                 <wmmediatype subtype="{33564D57-0000-0010-8000-00AA00389B71}" 
                       bfixedsizesamples="0"
                       btemporalcompression="1"
                       lsamplesize="0">
           <videoinfoheader dwbitrate="2638200"
                            dwbiterrorrate="0"
                            avgtimeperframe="416666">
            <rcsource left="0"
                      top="0"
                      right="1920"
                      bottom="1080"/>
            <rctarget left="0"
                      top="0"
                      right="1920"
                      bottom="1080"/>
                <bitmapinfoheader biwidth="1920"
                                  biheight="1080"
                                  biplanes="1"
                                  bibitcount="24"
                                  bicompression="WMV3"
                                  bisizeimage="0"
                                  bixpelspermeter="0"
                                  biypelspermeter="0"
                                  biclrused="0"
                                  biclrimportant="0"/>
           </videoinfoheader>
                </wmmediatype>
                </streamconfig>
        </profile>

    ----------------------------------------------------------------------------

    if open regedit I can't find 33564D57-0000-0010-8000-00AA00389B71 and find only 73646976-0000-0010-8000-00AA00389B71

    I think problem in absent 33564D57-0000-0010-8000-00AA00389B71 , but don't know how to repair...

    can't setup HALO 2 ... can't refresh index

    Sunday, June 10, 2007 7:14 AM
  • Deleting the C:\Windows\Performance\WinSAT\DataStore folder worked for me!

     

    Thanks!

     

    Friday, August 17, 2007 6:07 AM
  • hi!

     

    i had the same problem with the error message:

     

    Code Block

    2931165 (11040) - winsat\main.cpp:2295: --- START 2007\12\28 13:30:38 ---
    2931180 (11040) - winsat\main.cpp:2567: > IsFormal=TRUE  IsMoobe=FALSE.
    2931180 (11040) - winsat\main.cpp:1974: > DWM Running.
    2931352 (11040) - winsat\main.cpp:1987: > turning off DWM.
    2931383 (11040) - winsat\main.cpp:2051: > EMD device detected to be on.  EMD will be restored on exit.
    2931383 (11040) - mlib\syspowertools.cpp:0872: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
    2931399 (11040) - winsat\main.cpp:2108: > power policy saved.
    2931555 (11040) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    2931555 (11040) - winsat\main.cpp:2120: > power policy set to maximum.
    2932381 (11040) - winsat\main.cpp:2756: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE
    2932491 (11040) - winsat\main.cpp:1161: > Running Assessment: features ''
    2933099 (11040) - winsat\main.cpp:1436: > Assessment completed
    2933115 (11040) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'
    2975485 (11040) - winsat\main.cpp:1390: > DWM Assessment completed
    2975500 (11040) - winsat\processresults.cpp:2109: > Wrote video memory bandwidth to the registry 2959620
    2975500 (11040) - winsat\main.cpp:1408: > DWM Assessment results processing SUCCESS
    2975500 (11040) - winsat\main.cpp:1436: > Assessment completed
    2975500 (11040) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    2975906 (11040) - winsat\main.cpp:1430: > Assessment FAILED due to an error

    2975906 (11040) - winsat\main.cpp:1161: > Running Assessment: moobego ''
    2975906 (11040) - winsat\main.cpp:1161: > Running Assessment: mfmedia '-input {winsat.wmv} -nopmp'
    2978901 (11040) - winsat\main.cpp:1436: > Assessment completed
    2978901 (11040) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption'
    2989072 (11040) - winsat\main.cpp:1436: > Assessment completed
    2989072 (11040) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression'
    2999290 (11040) - winsat\main.cpp:1436: > Assessment completed
    2999290 (11040) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption2'
    3009508 (11040) - winsat\main.cpp:1436: > Assessment completed
    3009508 (11040) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression2'
    3019758 (11040) - winsat\main.cpp:1436: > Assessment completed
    3019758 (11040) - winsat\main.cpp:1161: > Running Assessment: mem ''
    3024906 (11040) - winsat\main.cpp:1436: > Assessment completed
    3024952 (11040) - winsat\main.cpp:1161: > Running Assessment: disk '-seq -read -n 0'
    3036793 (11040) - winsat\main.cpp:1436: > Assessment completed
    3036793 (11040) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 0'
    3036980 (11040) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    3037027 (11040) - winsat\processresults.cpp:0672: Total physical mem available to the OS : 1,99 GB (2.144.677.888 bytes)
    3037105 (11040) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'
    3037105 (11040) - winsat\main.cpp:2155: > Power state restored.
    3037105 (11040) - winsat\main.cpp:2171: > Successfully reenabled EMD.
    3037105 (11040) - winsat\main.cpp:2193: > Composition restarted
    3037121 (11040) - winsat\main.cpp:3216: > exit value = 1.

     

     

    you can see that mine stopped with the encode stuff as well. based on the great information in this thread i just started deleting some applications. i started with pinnacle studio 10. after that i was running the test again and it WORKED.

     

    thanks a lot!

    Friday, December 28, 2007 12:55 PM
  • It works definitely! Previous WEI can't be performed after upgrading my RAM. Now it works again!!

    Thanks a lot!

     

    Again, Microsoft should test their OS more throughtly rather than providing never ending hotfix and service pack!!!!!!!

    Tuesday, March 4, 2008 11:39 AM
  • guys, are you using Pinncle Studio? I have heard that this is the cause.

    I use Pinnacle and I have the same problem.

     

    Tuesday, July 15, 2008 11:58 AM
  • I have removed Pinnacle Studio 11 and it did not help.

     

    when I do winsat manually, I get this error:

     

    Loading encoder profile from "C:\Windows\Performance\WinSAT\\winsat.prx".

    Creating encoder, saving to temporary file.

    FAIL: mediaencode.cpp @ 572: 0xc00d1b5e == Unknown
     ({AMGetErrorText() failed!})

    FAIL: mediatest.cpp @ 466: 0xc00d1b5e == Unknown
     ({AMGetErrorText() failed!})

     

    Any solutions?? why is Microsoft silent around this problem??

     

    I am using all up to date drivers

    > Operating System                        : 6.0 Build-6001

    > Processor                               : Intel(R) Core(TM)2 CPU  6600 @ 2.40GHz

    > TSC Frequency                           : 2400400000

    > Number of Processors                    : 1

    > Number of Cores                         : 2

    > Number of CPUs                          : 2

    > Number of Cores per Processor           : 2

    > Number of CPUs Per Core                 : 1

    > Cores have logical CPUs                 : NO

    > L1 Cache and line Size                  : 32768  64

    > L2 Cache and line Size                  : 4194304  64

    > Total physical mem available to the OS  : 1,98 GB (2.129.063.936 bytes)

    > Adapter Description                     : NVIDIA GeForce 8800 GT

    > Adapter Manufacturer                    : NVIDIA

    > Adapter Driver Version                  : 7.15.11.7783

    > Adapter Driver Date (yy/mm/dd)          : 2008\8\2

    > Has DX9 or better                       : Yes

    > Has Pixel shader 2.0 or better          : Yes

    > Has LDDM Driver                         : Yes

    > Dedicated (local) video memory          : 1013.94MB

    > System memory dedicated as video memory : 0.00MB

    > System memory shared as video memory    : 759.59MB

    > Primary Monitor Size                    : 1680 X 1050  (1764000 total pixels)

    > WinSAT is Official                      : Yes

     

     

    Friday, August 15, 2008 10:24 AM