Windows Client TechCenter >
Windows 7 IT Pro Forums
>
Windows 7 Miscellaneous
>
Can't compute Windows Experience Index
Can't compute Windows Experience Index
- Hi,
I'm having a weird problem on my system (Athlon 64 3800+ running Windows 7 RC 32-bit version--yes I realize I'm using a 64 bit processor, but that shouldn't matter, right?). I am unable to get Windows to compute my Windows Experience Index. When I go to compute it, it goes all the way through the tests, but after it's done, it tells me that it could not compute my score. I get this vague error message:
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, driver, or other component.
It does this every time. It goes all the way through the tests and then gives me that message at the end.
I've tried reinstalling Windows 7, but it still has the problem. I have all the latest drivers installed for my graphics card (GeForce 8600 GT) and motherboard from Windows Update. My hard drive (SATA) has two partitions: partition 1 is my current Windows XP install, and partition 2 is the Windows 7 install, about 50 GB in size. I've installed Windows 7 RC on another computer (MacBook Pro with an Intel Core Duo T2600) from the same DVD I burned, and it has no problems getting the experience index.
I've tried manually running winsat from an administrator command prompt to see if it can do anything. No matter what I tell it to do (for example: winsat features), it runs the test I ask for and then I always get this stuff at the end of the output:
Error: Failed to load XML
An invalid character was found in text content.
winsat\main.cpp(1041)
Unable to process XML file.
....
ERROR: cannot process assessment results
cannot load XML data from a string
An invalid character was found in text content.
From Interface msxml6.dll:IXMLDOMDocument2
On my other working Windows 7 RC computer, this error message does not appear when I type the same command, and it completes successfully. So I'm assuming this XML error is the root cause of the problem, but I have no idea what XML it's talking about.
My C:\Windows\Performance\WinSAT\DataStore directory is empty, so it's not anything in there that it's choking on.
Any ideas what might be causing this? I'm totally at a loss. I've googled everything, particularly the XML error messages, but I haven't found anyone else who had that error message when they ran WinSAT.
Thanks for any help!
Doug
All Replies
- Doug -
I have a similar enough system - it's got an Athlon 64 3400+ chip, and a GeForce 7300 GS based video card and I'm also running the 32 bit version of the RC. I'm also running Win 7 from a SATA drive. So no, the hardware itself isn't a problem. My system managed to chug through the experience index without problems.
The error mesages seem to indicate there's an "invalid character" in the XML file somewhere. If we coudl find the file(s) in question, that would be helpful... Maybe we can track down the source of that invalid character... Doug -
I have a similar enough system - it's got an Athlon 64 3400+ chip, and a GeForce 7300 GS based video card and I'm also running the 32 bit version of the RC. I'm also running Win 7 from a SATA drive. So no, the hardware itself isn't a problem. My system managed to chug through the experience index without problems.
The error mesages seem to indicate there's an "invalid character" in the XML file somewhere. If we coudl find the file(s) in question, that would be helpful... Maybe we can track down the source of that invalid character...
Hi Wolfie2k6,
Yeah, I would agree--the hardware isn't the problem--there have to be tons of people out there with similar systems and no problem :) I'm just trying to think of any differences between my two systems that might explain it.
For sure, it must have to do with either an XML file somewhere. I did a search for XML files on my hard drive and there are a ton of them (no surprise there, haha). I haven't a clue where to begin. It could even be a temporary one that it's creating that contains the test results...who knows.
Anyway, this is definitely a weird problem. Thanks for replying!
Doug- Hello,
I have got the same exact problem on my Lenovo ThinkPad X200 Tablet PC (7448-CTO). It seems that winsat.exe is simply unable to write or create the XML file, even it I force it a location. I think it is unable to read it at the end because the file was simply not created at all. This is my asumption, and I'll validate this up with filemon utility.
Now this problem happens on both x86 and x64 versions of Windows 7 RC. I tried running "winsat memformal" to quickly check access to the xml file, and even this fails. I tried to run it before applying any driver or system update, and it fails the same way. I have no idea of what the problem be. As soon as RTM is available on MSDN, I'll try it and check if it solves the problem.
Doug, by any chance, did you managed to solve the problem? I'll be pleased to know.
Thanks
Vince Hi,
Note:
I'm having a weird problem on my system (Athlon 64 3800+ running Windows 7 RC 32-bit version--yes I realize I'm using a 64 bit processor, but that shouldn't matter, right?).
I am writing this reply on a AMD Athlon 64 3500+ processor on win7 32-bit with a Geforce 8500GT and I can't tell you how many times I have re-run the assessment to try to get the processor to get a better score. (and determine a better final score because it is the lowest one at 4.2)
The 64 just means that the comp is able to run 64-bit windows, it does not mean that you have to use 64-bit Windows.
Hello! Please try every solution given to your problem...and reply back with its results...
Click here for my thread on Win7 min. requirements
- JoelbX- I have exactly the same problem. Please post if u have the answer. 10x.
- I recall having that problem. It was fixed by a re-install... Sorry. I doubt that a rescue rebuild or whatever would do anything.
I think it had to do with running WEI before activating, and then activating, and then WEI wouldn't complete correctly.
Since then, if I do a re-install, I activate before I run WEI.
Hope that helps. - The acls for windows\performance may be restricting the .xml creation. Try taking ownership of the windows\performance folder
- Proposed As Answer byMThd Friday, August 21, 2009 3:11 PM
- Hi,
I have found the solution to my problem. My laptop have been repaired (new system board) just before I install Windows 7 on it. Then I found out that the technician who repaired my machine forgot to enter the model number and serial number in the EEPROM of the new system board. Once the correct info was entered in the EEPROM, the performance assessment have been able to run correctly.
I hope this can help other folks who may have the same problem as I had.- Proposed As Answer byDEFCON 1® Friday, August 21, 2009 3:17 PM
- Hi, Doug.
If your BIOS has the item "Quick Boot" (Memory Check), then set it to "Enable" and try to get WEI again.
It seems to me the specification of Memory management on Windows 7 has changed. it became more rely on BIOS,
but VISTA does not so in the case of computing WEI.
Based on the fact, on Windows 7, Memory description in the system information is totally different when "Quick Boot: Enable" or "Disable".
This is just my guess but Windows 7 heavily relies on the memory upper limit information by BIOS.
hope this might be helpful for you,
Kazuyuki,- Proposed As Answer bytanfather Monday, October 26, 2009 3:12 PM
- I have run into this problem several times and each time it was caused by a reset bios with incorrect date and time settings. I simply corrected the date and time in the control panel and re ran the assessment and it worked fine. The same thing happen with windows update, if the date and time are wrong it will fail. Hope this helps.
- Proposed As Answer bypaulypav Saturday, January 16, 2010 5:33 PM
- Thank You so much.
I went to the bottom right hand cormer of my screen, right clicked it and updated the time and date and it was able to do it.
Thanks Alot
