Windows Experience Index

[Caring1]

W.E.I. is meant to be a rough indicator of a systems performance, and I always run it to see how close I can get to the ideal 7.9.
Now the problem I am having is it won't run on a build I just completed last night, and I am wondering if it is due to my use of a Xeon Processor instead of a C2D in an old 775 system board.
The build runs perfectly and I even installed HWMonitor to keep an eye on temps and voltages, and installed the BOINC client which has been crunching all night with no issues @ 50C.
Does the Xeon architecture differ that much from the usual consumer CPU that would cause that, or would it be a software issue in Windows?

 

[Arjai]

hmmm...IDK that one!

 

[Octopuss]

Do you really care about these numbers? Jesus. You have much more serious problems than that it won't run.

 

[Scatler]

Might as well try this if you are not on a fresh install of windows http://answers.microsoft.com/en-us/...wont-run/2b078190-daf9-4bde-bdb3-38e90be05846.

 

[Toothless]

W.E.I. is meant to be a rough indicator of a systems performance, and I always run it to see how close I can get to the ideal 7.9.
Now the problem I am having is it won't run on a build I just completed last night, and I am wondering if it is due to my use of a Xeon Processor instead of a C2D in an old 775 system board.
The build runs perfectly and I even installed HWMonitor to keep an eye on temps and voltages, and installed the BOINC client which has been crunching all night with no issues @ 50C.
Does the Xeon architecture differ that much from the usual consumer CPU that would cause that, or would it be a software issue in Windows?

It said my GT220 was a 5.9. It's WAY outdated and probably isn't accurate either. Benching is probably your best bet.

 

[R-T-B]

I'd still be concerned something isn't right if it doesn't complete at all. Maybe run a sfc /scannow from an admin command prompt?

 

[FireFox]

Once Windows experience index didn't want to run on my main Machine, the problem? Due to a wrong Overclock

 

[Caring1]

Might as well try this if you are not on a fresh install of windows http://answers.microsoft.com/en-us/...wont-run/2b078190-daf9-4bde-bdb3-38e90be05846.

I followed those instructions and it still doesn't work.
It doesn't really matter as the system runs well, I just wanted to have a look at it's rating compared to my other systems.

 

[Caring1]

I'd still be concerned something isn't right if it doesn't complete at all. Maybe run a sfc /scannow from an admin command prompt?

Done that before I went into the registry, it said no errors.

 

[Caring1]

Once Windows experience index didn't want to run on my main Machine, the problem? Due to a wrong Overclock

It's a stock Acer Motherboard and there are no settings in the BIOS that allow overclocking, believe me i've looked.
It might have something to do with the CPU being a Xeon though, as that board doesn't list the one I am using in the compatibility list and I was told it wouldn't work by another forum.
Phht, I like to see for myself So far it's been crunching for over 48 hours straight and running cool.

 

[CAPSLOCKSTUCK]

I like WEI as a quick guide, it is useful, especially if you have a selection of bits to try out.
I dont think it was ever intended to be anything more than an interesting tool.



e.g

LOOK.... my Hd 5850 must be brilliant

I cant remember putting anything together that has caused it not to work.

It is on 8.1 if you know where to find it.

SEE BELOW

Starting with Windows 8.1, Microsoft decided to remove the graphical interface to the Windows Experience Index. The underlying benchmark utility, known as the Windows System Assessment Tool (WinSAT), is still there in Windows 8.1, however. To find your scores, you just need to type a couple of commands from the command line.

Step 1: Open a command prompt as administrator, then type "winsat prepop" and press Enter. This will run the benchmark and store the results on your PC as XML files.

Screenshot by Ed Rhee/CNET
Step 2: Open the Windows Powershell as administrator, then type "Get-WmiObject -Class Win32_WinSAT" and press Enter. This will analyze the results in the XML files, then present them as scores for each category.

Screenshot by Ed Rhee/CNET
CPUScore is the score for the processors on the PC.
D3DScore is the score for the 3D graphics capabilities of the PC.
DiskScore is the score for the sequential read throughput on the system hard disk.
GraphicsScore is the score for the graphics capabilities of the PC.
MemoryScore is the score for the memory throughput and capacity of the PC.

That's it. If you're looking for your base score, look at the number next to WinSPRLevel, which is just the lowest score of the five categories.

 

[Frick]

I like WEI as a quick guide, it is useful, especially if you have a selection of bits to try out.
I dont think it was ever intended to be anything more than an interesting tool.

Honestly IMO, it's not useful in any way, shape or form. It just presents you with a number that doesn't really mean anything, and you certinally can't use it to compare systems. You might as well write a list of numbers on a post-it and call it a day. IIRC it was meant to be tied to the Games For Windows thing that existed and in the long run it might've been able to tell you whether you'd be able to run certain games or not. I think that was the idea, but it didn't happen because reasons I no longer remember.

It might be interesting to find out why it doesn't work in this case, but I wouldn't sweat it, as people have already said.

 

[95Viper]

@Caring1... Does it give you an error message? If so, what is the message?

Try this:
To reset your WEI go to folder "C:\Windows\Performance\WinSat\DataStore"
In the DataStore folder, select all of the .xml files & delete them.
Now try running it.

 

[Caring1]

@Caring1... Does it give you an error message? If so, what is the message?

Try this:
To reset your WEI go to folder "C:\Windows\Performance\WinSat\DataStore"
In the DataStore folder, select all of the .xml files & delete them.
Now try running it.

There's no error message and I found those instructions online and looked in Win SAT, there's no DataStore in there. There was a few videos and a couple of files, but it wouldn't allow me to delete anything.

 

[95Viper]

That is odd... try creating a "DataStore" sub-folder in the WinSAT folder.

Then, open an elevated command prompt window, click Start, click All Programs, click Accessories, right-click Command Prompt, and click Run as administrator.

Type in command "winsat features" (without the quote marks)

See if it recognizes your processor and other components properly.

If it does; then, type the command "winsat cpu -encryption" (without the quote marks)

And, see if that will run properly, or, what error message it gives to you.

 

[Caring1]

...type the command "winsat cpu" (without the quote marks)

And, see if that will run properly, or, what error message it gives to you.

That last command gives me an "assessment mode not specified must be encryption or compression" message.

 

[95Viper]

That last command gives me an "assessment mode not specified must be encryption or compression" message.

I fixed it... I forgot the parameter... you could use -encryption or -encryption2.
If it recognized the CPU, I wanted you to run the second to see if the assessment would work at all.

Did it recognize your processor on the first command?

By the way, which Xeon model are you using?

 

[Caring1]

It recognized it the first time, it's a 3070
I'll run that again with the parameter corrected
Edit: It ran and did something although I have no idea what.
It did say it took about 12 secs to run and did AES256 Encryption at a rate of 81.93MB/s

 

[95Viper]

I don't believe it is your CPU which is the hold-up.
You can try running "winsat formal -v"
The v is for verbose and it should show you the tests as they are run.
So, you see where it runs into any difficulties.

 

[Caring1]

Ran that and it ran through perfectly, no errors.
Thanks for the help, it doesn't really matter if it runs, I was just wondering why.
I'll leave it as is and forget about it.