Wait (TimeInterval) takes too long to execute

[dug9000]

To see if this really is the problem referred to by the MSDN help. Is it possible to disable one of the cores in your BIOS (check your BIOS settings on bootup)? If so please try that and see if the problem goes away. I know it's not a good solution, but it will at least let us know if this is really the hardware/BIOS bug referred to by Microsoft.

 Also, what OS are you using, incase it makes a difference?

Thanks, 

-Doug 

Message Edited by dug9000 on 09-04-2008 10:28 AM

Message Edited by dug9000 on 09-04-2008 10:28 AM

[dug9000]

Just wondering if you've had a chance to test with only one core enabled, or have otherwise been able to narrow down this problem. We tried to reproduce this on a pentium D machine, but were unable to, however we do not have the exact same model machine as you. Thanks for any info.

-Doug 

[Alan_Bentz]

I have not been able to run with one-core yet on the problem PC.  I'm going to try reloading TestStand.

I tried this same timing test on my desktop, which is the identical model to the problem PC, a Dell Optiplex GX620. TestStand timing worked perfectly.

[dug9000]

Hmm, I was thinking it could be some sort of third party software or driver installed on the machine that's interfering with the timing, perhaps overclocking software or something similar. If you can, you might try either uninstalling any unusual 3rd party software you don't need or reinstalling the OS. Just a guess though.

Thanks for the update,

-Doug 

[Alan_Bentz]

More news:

I got called in this afternoon because the test times were WAY too long. I ran the simple Wait time test sequence as before, and TS was waiting 11x as long as programmed. (was 1.5x last week). Shutting down and restarting TS did not change the situation. Powered down the PC and tried again. Now TS is back to its original 1.5X too long.

I still need to try some of your suggestions.

[dug9000]

Interesting. I strongly suspect a hardware or 3rd party software issue with that machine. It could also perhaps be an unusual bios setting. You might want to see if you have any non-default bios settings related to CPU speed or the CPU in general. Also, a clean install of the OS would help narrow down whether or not 3rd party software is to blame, though I'm not sure how practical that would be for you if you are actively using that machine. Have you seen this problem on any other machines? This is really the first time we've ever heard of this problem happening.

-Doug 

[Anders_Swe]

You seems to have the same problem that I have!

I think I now the root of cause of this problem, please check my findings in my thread:

http://forums.ni.com/ni/board/message?board.id=330&thread.id=23221

Regards

Anders 

[Anders_Swe]

dug9000 found the solution to this problem, please check my thread.

Regards

Anders