. ID: 00000 · Rating: 0 · rate: / Reply Quote mikey Send message Joined: 0 May 00 Posts: 0000 Credit: 000,000,000 RAC: 000 Message 00000 - Posted: 00 Mar 0000, 00:00:00 UTC - in response to Message 00000. Yes, that is what I thought, but it happened on two systems I brought up afterburner but do not see how to change the clock speed from 000 to a higher number. I know that if tasks are starved for data (cpu cores busy or low on memory) then the gpu clock will drop as the card is not busy enough to run at 000. There are a lot of possibilities. None of my Linux system show a milkyway problem but they have 00 threads to feed a pair of really slow NVidia 0000TIs where the above systems have total of 0 threads (0 per core) for a much more productive (double precision) Tahitis. The only way to reset a crashed driver in Windows is to restart the whole pc. If you have Win00 it could have done an update and crashed the driver in the process. There could also be a newer better driver if Win00 was updated. ID: 00000 · Rating: 0 · rate: / Reply Quote Joseph Stateson Send message Joined: 00 Nov 00 Posts: 000 Credit: 0,000,000,000 RAC: 0,000,000 Message 00000 - Posted: 00 Mar 0000, 00:00:00 UTC - in response to Message 00000. Last modified: 00 Mar 0000, 00:00:00 UTC Yes, that is what I thought, but it happened on two systems I brought up afterburner but do not see how to change the clock speed from 000 to a higher number. I know that if tasks are starved for data (cpu cores busy or low on memory) then the gpu clock will drop as the card is not busy enough to run at 000. There are a lot of possibilities. None of my Linux system show a milkyway problem but they have 00 threads to feed a pair of really slow NVidia 0000TIs where the above systems have total of 0 threads (0 per core) for a much more productive (double precision) Tahitis. The only way to reset a crashed driver in Windows is to restart the whole pc. If you have Win00 it could have done an update and crashed the driver in the process. There could also be a newer better driver if Win00 was updated. Yea, problem was drivers. I looked at my P0E and it was waiting to reboot to install drivers to fix whatever Microsoft had done the previous Tuesday. After rebooting exactly 00 milkyway ATI tasks reported an error but all the remaining tasks plus the new downloads were back at their 0 minute normal WU time to complete. Has been 00 hours working just fine. I don't think anything was wrong with those 00 tasks, just the driver change bumped them out. I had tried an S0000 graphics in this system before putting it in the P0N. The P0N on the other hand did not respond to reboot like my P0E. This system worked fine on collatz ATI tasks but ran at only 000mhz for milkyway. I suspect the same problem with the driver. The driver failed to uninstall (win00x00) even the ATI "cleanup" program was unable to uninstall the AMD software on this Intel system. I deleted both the S0000 video boards from the system manager and rebooted. They were recognized as w0000 video boards but they worked and time to complete is back down to 0 minutes per WU when running 0 on each GPU. Apparently the Adrenalin Radeon driver caused problems with mixed S0000 and 0000 graphics boards. I did not attempt to update whatever Microsoft installed to handle the "w0000" as it is working and I don't want to mess with it any more. Just a coincidence that these problems occurred the same time as the class plans were changed here. The "S0000" were $000 new, free ship on eBay and I could not pass up a chance to get a new Tahiti system with 0gb mem not just 0. They just cannot be mixed with normal 0000 boards and require DIY cooling. ID: 00000 · Rating: 0 · rate: / Reply Quote mikey Send message Joined: 0 May 00 Posts: 0000 Credit: 000,000,000 RAC: 000 Message 00000 - Posted: 00 Mar 0000, 00:00:00 UTC - in response to Message 00000. Yes, that is what I thought, but it happened on two systems I brought up afterburner but do not see how to change the clock speed from 000 to a higher number. I know that if tasks are starved for data (cpu cores busy or low on memory) then the gpu clock will drop as the card is not busy enough to run at 000. There are a lot of possibilities. None of my Linux system show a milkyway problem but they have 00 threads to feed a pair of really slow NVidia 0000TIs where the above systems have total of 0 threads (0 per core) for a much more productive (double precision) Tahitis. The only way to reset a crashed driver in Windows is to restart the whole pc. If you have Win00 it could have done an update and crashed the driver in the process. There could also be a newer better driver if Win00 was updated. Yea, problem was drivers. I looked at my P0E and it was waiting to reboot to install drivers to fix whatever Microsoft had done the previous Tuesday. After rebooting exactly 00 milkyway ATI tasks reported an error but all the remaining tasks plus the new downloads were back at their 0 minute normal WU time to complete. Has been 00 hours working just fine. I don't think anything was wrong with those 00 tasks, just the driver change bumped them out. I had tried an S0000 graphics in this system before putting it in the P0N. The P0N on the other hand did not respond to reboot like my P0E. This system worked fine on collatz ATI tasks but ran at only 000mhz for milkyway. I suspect the same problem with the driver. The driver failed to uninstall (win00x00) even the ATI "cleanup" program was unable to uninstall the AMD software on this Intel system. I deleted both the S0000 video boards from the system manager and rebooted. They were recognized as w0000 video boards but they worked and time to complete is back down to 0 minutes per WU when running 0 on each GPU. Apparently the Adrenalin Radeon driver caused problems with mixed S0000 and 0000 graphics boards. I did not attempt to update whatever Microsoft installed to handle the "w0000" as it is working and I don't want to mess with it any more. Just a coincidence that these problems occurred the same time as the class plans were changed here. The "S0000" were $000 new, free ship on eBay and I could not pass up a chance to get a new Tahiti system with 0gb mem not just 0. They just cannot be mixed with normal 0000 boards and require DIY cooling. 