Experience index for your system could not be computed

I am unable to rate my computer performance index. This is a Fujitsu Lifebook A6110 series laptop. It has been upgraded to 4GB of RAM and has an SSD drive installed. This is a clean install of Windows 8 pro where I booted from the install CD and deleted the old partition with Windows vista on it and installed from scratch. I have not had any errors or issues since installing a couple of days ago. I have barely even used it and not installed any software yet.

Is there any reason I should be getting an error "The Windows Experience index for your system could not be computed. Cannot complete assessment"?

When running the test is sits for the longest time on "Running the Direct3D 10 Texture Load Assessment" before giving the above error. I checked device manager and it has the Intel Mobile 965 driver (10/1/2012 8.15.10.2697) installed, which I believe is correct. Intel site has no drivers available for Windows 8, so I don't think I really have another choice.

Any idea how I would check to see why the index score cannot be calculated? error log or something?

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hi DonDallas,

You want to rate your computer performance index. I will help you with this issue.

Method 1.

Let’s test the issue in clean boot and check if the issue persists.

 

Step 1:

a) Press the ‘Windows + R’ key on the keyboard.

b) In the ‘Run’ windows type ’MSCONFIG’ and click ‘Ok’.

c) Click the ‘Boot’ tab and uncheck ‘Safe Boot’ option.

d) On the ‘General’ tab, click to select the option ‘Selective startup’, and then click to clear the option Load startup items check box.

e) On the ‘Services’ tab, click to select the ‘Hide all Microsoft services’ check box, and then click ‘Disable all’.

f) On the ‘StartUp’ tab, click ‘Open Task Manager’. In the Task Manager window under startup tab, right click on each startup item which are enabled and select ‘Disable’.

g) Click ‘OK’, and then click Restart.

 

Step 2: Enable half of the services
a.
Follow steps 1a and 1b to start the System Configuration utility.
b. Click the Services tab, and then click to select the Hide all Microsoft services check box.
c. Click to select half of the check boxes in the Service list.
d. Click OK, and then click Restart.

 

Step 3: Determine whether the problem returns
If the problem still occurs, repeat step 1 and step 2. In step 2, click to clear half of the check boxes that you originally selected in the Service list.
If the problem does not occur, repeat step 1 and step 2. In step 2, select only half of the remaining check boxes that are cleared in the Service list. Repeat these steps until you have selected all the check boxes.
If only one service is selected in the Service list, and you still experience the problem, the selected service causes the problem. Go to step 6. If no service causes this problem, go to step 4.

 

Step 4: Enable half of the Startup items
If no startup item causes this problem, a Microsoft service most likely causes the problem. To determine which Microsoft service may be causing the problem, repeat step 1 and step 2 without selecting the Hide all Microsoft services check box in either step.

 

Step 5: Determine whether the problem returns
If the problem still occurs, repeat step 1 and step 4. In step 4, click to clear half of the check boxes that you originally selected in the Startup Item list.
If the problem does not occur, repeat step 1 and step 4. In step 4, select only half of the remaining check boxes that are cleared in the Startup Item list. Repeat these steps until you have selected all the check boxes.
If only one startup item is selected in the Startup Item list, and you still experience the problem, the startup item that is selected in the list is the service that is causing the problem. Go to step 6.
If no startup item causes this problem, a Microsoft service most likely causes the problem. To determine which Microsoft service may be causing the problem, repeat step 1 and step 2 without selecting the Hide all Microsoft services check box in either step.

 

Step 6: Resolve the problem
After you determine the startup item or the service that causes the problem, contact the program manufacturer to determine whether the problem can be resolved. Or, run the System Configuration utility, and then click to clear the check box for the problem item.

 

Step 7:

Note: After you have finished troubleshooting, follow these steps to boot to normal startup.

a) Press the ‘Windows + R’ key on the keyboard.

b) In the ‘Run’ windows type ’MSCONFIG’ and click ‘Ok’.

c) On the ‘General’ tab, click the ‘Normal Startup’ option, and then click ‘OK’.

d) When you are prompted to restart the computer, click ‘Restart’.

 

Method 2.

To run the System File Checker you will need to open an elevated Command Prompt. This can be done by:

  • Enter the Start screen
  • Press Windows key + C on your keyboard to show the Charms bar. (If you are using a touch screen: touch the right edge of the screen and swipe your finger toward the center of the screen to show the Charms bar)
  • Click Search
  • Type Command Prompt into the Search field
  • Right click Command Prompt (If you are using a touch screen: Touch and hold your finger to the Command Prompt, slide your finger down until you see an outline around the tile, and finally release your finger from the screen.)
  • Click Run as administrator
  • Enter the command: sfc /scannow
    Note: If you are using a touch screen you can open the touch keyboard for the Command Prompt by tapping the keyboard icon displayed on your Taskbar near the System tray.

 

Please try these steps and let us know the status. We will be glad to help you further.

Thanks.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

    I've been having the same issue.  I installed Windows 8 Pro on a Acer Aspire 5315 which has the same 965 Express Graphics as your Fujitsu and I have the same Driver loaded for it.  WEI errors out at the same point during the Direct3D 10 Texture Load Assessment.
    The Acer has been upgraded to an Intel T7300, 3 Gb RAM, Intel 6235 WiFi/BT, & 160 Gb Hitachi hard drive replacing stock equipment.
     My assumption is that either the given graphics driver isn't supporting whatever the test is trying to do (It's only WDDM 1.1 not 1.2) or because of the age of the chipset, it is too slow and creating a divide by zero error because the resulting value is too small.  We may just have to wait until Intel makes drivers of their own.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yea, the only way I have been able to get it to complete is to uninstall the display driver and let it use a default generic one. Of course this will give a terrible score. I tried downloading the latest driver from the Intel website (Win 7 64bit), but it is version 8.15.10.1930 whereas the Intel driver included with windows 8 is newer at 8.15.10.2697. According to the driver details for 8.15.10.2697 it is in fact provided by Intel (not Microsoft), just included in the Windows 8 install. Even after downgrading to the older one from the Intel site it still will not run. The experience index worked fine on Windows Vista, just not Windows 8. I guess it is testing more than Vista did or has a little bug in it.

I even booted from the Win 8 CD and deleted my partition and installed from scratch a second time. Still no luck, so I am pretty sure it is the display driver, or something Windows 8 is trying to do with the display driver.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Using method 1, I disabled ALL services and Startup programs. The only non-MS service was for my SD card slot driver. The only Startup program was related to my Touchpad driver. I was able to disable ALL service (even MS) except the following:

These would automatically re-enable after a reboot:
Background Task Infrastructure
Group Policy Client
Local Session Manager
RPC Endpoint Mapper
System Events Broker
Task Scheduler
Time Broker
Windows Installer
Windows Store Service

This one was required for the WEI to even start
Power

With only the above enabled, the result of the WEI was the same.

I had actually already tried Method 2. The result was "Windows Resource Protection did not find any integrity violations". Running it had no effect on the WEI, as it still failed in the same spot.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I'm also having the same problem and cannot get the WEI score to run, I've followed all the steps above and still get the same error. 

Here is the log file and there's an error message at the bottom that I'm not sure how to repair.


159296 (6704) - exe\logging.cpp:0841: --- START 2012\11\7 20:46:22 PM ---
159296 (6704) - exe\main.cpp:4659: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent 080f1cb6-3c9f-42fe-9ebb-65f6a8fd9398
159296 (6704) - exe\main.cpp:4766: WinSAT registry node is created or present
159296 (6704) - exe\main.cpp:4450: INFO: The axe results path environment variable is not set. Assuming we aren't running under AXE.
159296 (6704) - exe\main.cpp:4786: INFO: Winsat is not running in AXE mode.
159296 (6704) - exe\processwinsaterror.cpp:0146: ERROR: tried to read resource strings, unknown exception occured
159328 (6704) - exe\main.cpp:4878: > IsFormal=TRUE IsMoobe=FALSE.
159328 (6704) - exe\watchdog.cpp:0113: WatchDogThreadProc Launched with priority 0
159375 (6704) - exe\main.cpp:4997: Watch dog system enabled
159375 (6704) - exe\main.cpp:5012: Main watch dog timer set to 600.0 seconds
159375 (6704) - common\winsatutilities.cpp:1153: PNPID from DX9 call = PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
159375 (6704) - common\winsatutilities.cpp:1219: Index [0]: PNPID = PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
159375 (6704) - common\winsatutilities.cpp:1243: Matching device PnPID is PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
159375 (6704) - common\winsatutilities.cpp:1219: Index [1]: PNPID = ROOT\BasicDisplay
159421 (6704) - exe\main.cpp:2617: > DWM Running.
159421 (6704) - exe\main.cpp:2628: > leaving DWM on.
159421 (6704) - exe\syspowertools.cpp:0983: > Read the active power scheme as '512a6ac6-efc1-4441-85c9-cccf29b69cd2'
159421 (6704) - exe\main.cpp:2925: > power policy saved.
159453 (6704) - exe\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
159453 (6704) - exe\main.cpp:2946: > power policy set to maximum.
160281 (6704) - exe\main.cpp:0868: > WinSAT info: Version=V6.2 Build-9200.16420

160281 (6704) - exe\main.cpp:1008: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
160281 (6704) - exe\main.cpp:4261: > Power 'execution' request successfully set.
160281 (6704) - exe\main.cpp:1853: > Run Assessment features
160281 (6704) - common\winsatutilities.cpp:1153: PNPID from DX9 call = PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
160281 (6704) - common\winsatutilities.cpp:1219: Index [0]: PNPID = PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
160281 (6704) - common\winsatutilities.cpp:1243: Matching device PnPID is PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
160281 (6704) - common\winsatutilities.cpp:1219: Index [1]: PNPID = ROOT\BasicDisplay
160281 (6704) - exe\main.cpp:1853: > Run Assessment media -input C:\Windows\Performance\WinSAT\winsatencode.wmv -encode C:\Windows\Performance\WinSAT\winsat.prx
160281 (6704) - media\mediaop.cpp:0590: ps_MediaWorkerThread Launched with priority 0
162468 (6704) - exe\main.cpp:1853: > Run Assessment moobego
162468 (6704) - exe\main.cpp:1853: > Run Assessment cpu -encryption -up
162484 (6704) - exe\winsatop.h:1133: Adjusted the priority to 2
162484 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
162500 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
172546 (6704) - exe\main.cpp:1853: > Run Assessment cpu -compression -up
172546 (6704) - exe\winsatop.h:1133: Adjusted the priority to 2
172546 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
172562 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
182656 (6704) - exe\main.cpp:1853: > Run Assessment cpu -encryption2 -up
182656 (6704) - exe\winsatop.h:1133: Adjusted the priority to 2
182656 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
182671 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
192671 (6704) - exe\main.cpp:1853: > Run Assessment cpu -compression2 -up
192671 (6704) - exe\winsatop.h:1133: Adjusted the priority to 2
192671 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
192687 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
202750 (6704) - exe\main.cpp:1853: > Run Assessment cpu -encryption
202750 (6704) - exe\winsatop.h:1133: Adjusted the priority to 2
202750 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
202750 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
202750 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
202750 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
202750 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
202750 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
202750 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
202750 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
202781 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
202781 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
202781 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
202781 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
202781 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
202781 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
202781 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
202781 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
212937 (6704) - exe\main.cpp:1853: > Run Assessment cpu -compression
212937 (6704) - exe\winsatop.h:1133: Adjusted the priority to 2
212937 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
212937 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
212937 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
212937 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
212937 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
212937 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
212937 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
212937 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
212953 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
212953 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
212953 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
212953 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
212953 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
212953 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
212953 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
212953 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
223187 (6704) - exe\main.cpp:1853: > Run Assessment cpu -encryption2
223187 (6704) - exe\winsatop.h:1133: Adjusted the priority to 2
223187 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
223187 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
223187 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
223187 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
223187 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
223187 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
223187 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
223187 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
223203 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
223203 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
223203 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
223203 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
223203 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
223203 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
223203 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
223203 (6704) - cpu\encryption.cpp:0164: CPU Encryption thread priority changed to 15
233359 (6704) - exe\main.cpp:1853: > Run Assessment cpu -compression2
233359 (6704) - exe\winsatop.h:1133: Adjusted the priority to 2
233359 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
233359 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
233359 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
233359 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
233359 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
233359 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
233359 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
233359 (6704) - exe\winsatop.h:0819: CPU ThreadEntryPoint Launched with priority 0
233375 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
233375 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
233375 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
233375 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
233375 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
233375 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
233375 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
233375 (6704) - cpu\compression.cpp:0180: CPU Compression thread priority changed to 15
243546 (6704) - exe\main.cpp:4300: > Power request 'execution' successfully cleared.
243562 (6704) - exe\processresults.cpp:1076: > Wrote cpu expression compression score to the registry 261
243562 (6704) - exe\main.cpp:0868: > WinSAT info: Version=V6.2 Build-9200.16420

243562 (6704) - exe\main.cpp:1008: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
243562 (6704) - common\winsatutilities.cpp:1153: PNPID from DX9 call = PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
243562 (6704) - common\winsatutilities.cpp:1219: Index [0]: PNPID = PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
243562 (6704) - common\winsatutilities.cpp:1243: Matching device PnPID is PCI\VEN_10DE&DEV_0FD4&SUBSYS_21151043&REV_A1
243562 (6704) - common\winsatutilities.cpp:1219: Index [1]: PNPID = ROOT\BasicDisplay
243578 (6704) - exe\processresults.cpp:4577: > Wrote video memory bandwidth to the registry 16516300
243578 (6704) - exe\processresults.cpp:5370: > Wrote random read disk score, from the profiler, to the registry 310312
243578 (6704) - exe\processresults.cpp:5370: > Wrote random read disk score, from the profiler, to the registry 1044
243593 (6704) - exe\processresults.cpp:1076: > Wrote cpu expression compression score to the registry 261
243593 (6704) - exe\processresults.cpp:1121: Total physical mem available to the OS : 15.9 GB (17,130,483,712 bytes)
243593 (6704) - exe\processresults.cpp:1222: > Wrote memory throughput to the registry 20453
243593 (6704) - exe\processresults.cpp:1421: Skipping HighDefPlayback limit check.
243593 (6704) - exe\processresults.cpp:1559: Using D3D10 subscore for final D3D score.
243593 (6704) - exe\processresults.cpp:1648: > Wrote random read disk score (throughput) to the registry 310312
243593 (6704) - exe\processresults.cpp:1674: > Wrote sequential read disk score (throughput) to the registry 520131
243593 (6704) - exe\processresults.cpp:2076: > Wrote CRS score to the registry 72
243593 (6704) - exe\processresults.cpp:2097: > Wrote memory score to the registry 78
243593 (6704) - exe\processresults.cpp:2116: > Wrote cpu score to the registry 78
243593 (6704) - exe\processresults.cpp:2137: > Wrote DWM score to the registry 72
243593 (6704) - exe\processresults.cpp:2157: > Wrote D3D score to the registry 72
243593 (6704) - exe\processresults.cpp:2177: > Wrote disk score to the registry 81
243593 (6704) - exe\main.cpp:4376: ERROR: 0X80004005 DataStore::BuildFormalFromMostRecentPartialAssessments failed.
243593 (6704) - exe\main.cpp:5148: ERROR: Unable to save validated results.
243593 (6704) - exe\processwinsaterror.cpp:0298: Unspecified error 46 occured.
243593 (6704) - exe\processwinsaterror.cpp:0319: Writing exit code, cant msg and why msg to registry
243625 (6704) - exe\syspowertools.cpp:1015: > Set the active power scheme to 512a6ac6-efc1-4441-85c9-cccf29b69cd2'
243625 (6704) - exe\main.cpp:2987: > Power state restored.
243625 (6704) - exe\main.cpp:3005: > Not necessary to reenable EMD cache.
243640 (6704) - exe\watchdog.cpp:0339: Watch dog system shutdown
243640 (6704) - exe\main.cpp:5341: > exit value = 46.


Your help is greatly appreciated.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I was able to get it to run this time.

I went to the C:\Windows\Performance\WinSAT\DataStore folder and deleted all the files and then re-ran the assessment and it worked perfectly.

Also before deleting the files I put them into a temporary folder for testing just in case.

Hopefully this works for anyone else having this same problem

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks for your answer, but in my case the test eventually times out according to the log (600 seconds is all that is allowed).  For some reason the D3D 10 Texture Load Assessment will not run correctly.  It could be a bug in the test or an incompatibility with the 965 Express Graphics driver.

I noticed from your log file that tests were completing, so you must have had some corrupt data file which deleting those files helped with.

Thanks again.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi, I was getting the same problem with the latest win7 drivers. In the end I downloaded the vista driver (7.15.10.1666) which is out of date but did allow WEI to run through. The graphics score was only 3.1 which is probably about right for the 965 express graphics. Hope that helps.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I manually ran all the tests except the d3d texture test that was failing from the command line using the newest drivers.  So WEI is now displayed with the graphics score about the same as yours, 3.2.  Of course the graphics subsystem is the slowest component. :)

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

hi chrisH_747 how did u ran the test manually coz im having the same problem wei could not be computed? tnx Mateo Arnol

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated March 5, 2020 Views 3,694 Applies to: