STARTED OVER

Have you tried to use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file? To do this, follow these steps: Open an elevated command prompt. To do this, click Start, clickAll Programs, clickAccessories, right-clickCommand Prompt, and then clickRun as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or clickAllow. Type the following command, and then press ENTER: sfc /scannow Thesfc /scannowcommand scans all protected system files and replaces incorrect versions with correct Microsoft versions. Regards, MCP MCTS MCITP

Ronald, You can examine the WinSAT log to get some context and detailed information: C:\Windows\Performance\WinSAT\winsat.log Post here the contents and we will take a look.Microsoft MVP Windows Expert Consumer | http://blogs.msmvps.com/dmartin/ | http://www.wintecnico.com

This issue can be caused by your antivirus. For example: Windows Experience Index Cannot Compute http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/cbdf8e05-c958-4022-8f80-301f654dac8d/Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Did that and no files were corrupt.Ronald Banfield

Using Microsoft Security Essentials alone. No problems reported.Ronald Banfield

Done, no problems.Ronald Banfield

I have the winsat.log on my desktop and cannot figure out how to send it to be looked at.Ronald Banfield

I will definitely do that when my problem is solved.Ronald Banfield

Checked DxDiag and everything is enabledRonald Banfield

Dit the sfc/scannow and no system integrity violations.Ronald Banfield

This is what is in the C:\Windows\Performance\WinSAT\winsat.log: 2003910 (0856) - winsat\logging.cpp:0815: --- START 2012\1\20 6:35:23 AM --- 2003910 (0856) - winsat\main.cpp:2861: > no need to restore power state (no saver object). 2003910 (0856) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache. 2003910 (0856) - winsat\main.cpp:4909: > exit value = 4. 3533001 (5316) - winsat\logging.cpp:0815: --- START 2012\1\28 10:12:03 AM --- 3533017 (5316) - winsat\main.cpp:2861: > no need to restore power state (no saver object). 3533017 (5316) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache. 3533017 (5316) - winsat\main.cpp:4909: > exit value = 4. 3555247 (5316) - winsat\logging.cpp:0815: --- START 2012\1\28 10:12:25 AM --- 3555247 (5316) - winsat\main.cpp:2861: > no need to restore power state (no saver object). 3555247 (5316) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache. 3555247 (5316) - winsat\main.cpp:4909: > exit value = 4.Ronald Banfield

Running Microsoft Security Essentials completely updated. Find no problems here.Ronald Banfield

Have eliminated any software problems, There were none, Now I must go to Hardware. So off I go, Thanks for all the help, RonRonald Banfield

Have eliminated the possibility of software causing the problem. Now I must turn to the Hardware, so here I go. Thanks for all the help, RonRonald Banfield