|27 Oct 2009||#1|
| || |
Problems with WEI + standby issues
I've been reading around on this for months now, and was experiencing the same issue in the RC. I was hoping that the problem would be resolved with the RTM, but after doing a clean install once I received my retail copy in the mail, the problems persists.
One of the issues I'm experiencing is coming out of standby, where it can take up to 30-40 seconds before I get a response, if at all. I understand that this is a common issue, but was wondering if anyone had come up with a solution for this? It's frustrating when my desktop is on 24/7, as it's used as a media server streaming content throughout the house, as well as recording live tv etc.
The main issue that i'm having is the WEI refusing to complete. I have recently upgraded my system, and have found that although the WEI seems to complete, it comes up with a generic 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, driver, or other component"
The device manager shows no issues, DXDIAG report no conflicts and I have manually updated drivers for my motherboard, graphics card, sound card, network card the works.
I have run the elevated WEI from command prompt, under admin using the winsat formal command, and found it completes but then comes up with an error about writing to the disc at the end. I have also done all the other known tricks, and precautions, such as not using kapersky, deleting all the performance logs and starting a clean slate etc.
The winsat log shows the following errors (i have attached the full log):
042151 (0872) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
045209 (0872) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance
058344 (0872) - winsat\main.cpp:4736: ERROR: Unable to save validated results.
Any help would be greatly appreciated, its frustrating, and if it's a hardware issue i'd like to know so I can get it sorted.
|My System Specs|
|27 Oct 2009||#2|
| || |
Problem solved- anyone who is experiencing a similar issue with a gigabyte motherboard (apparantly this is a common issue) there is a new beta bios available from the gigabyte website as of the 23rd of October.
You will need to manually download the bios file, and use the @bios utility to update from file (as it will not automatically detect and download the update, due to it being a beta).
I tried absolutely everything, and it was an issue with the way the sata ide/raid/ahci function worked in the bios.
I also noticed that the firewire port detected and installed in Windows 7, which was something I hadn't noticed until it fixed itself.
|My System Specs|
|Similar help and support threads for2: Problems with WEI + standby issues|
|Comp wont standby...(few problems since using W7 Manager)||Hardware & Devices|
|Intel workstation board standby issues S5520SC||General Discussion|
|BSOD problems after standby or sleep||BSOD Help and Support|
|BSOD problems with standby and sleep||BSOD Help and Support|
|Standby Issues||Network & Sharing|
|Keyboard and monitor standby issues||General Discussion|
|Problems going to standby TWICE||BSOD Help and Support|