World community grid boinc manager12/9/2023 It has a two-core AMD A-6 6400 APU with Radeon(TM) HD Graphics and a Gigabyte motherboard, 8 gigs of RAM and a 1TB hard drive. However, the computer does not have an Intel GPU. I think it's probably best for you to withdraw your computer from the iGPU part of the project for the time being, and watch out for any new version announcements on the WCG project forums. Otherwise, the Scripps programmers are going to have to redesign their application pretty substantially. So I'm not going to post details in public: if anyone else understands Windows internals enough to deduce what I'm alluding to, feel free to use your own judgement as to whether it's safe in your environment. It is possible to disable the Windows watchdog, but it's dangerous: depending on what else you use the computer for, you could encounter other problems far worse than this one. I think they're all too busy to work on it yet. There are several possible courses of action, but most of them would need to be carried out by the WCG project staff working with the Scripps Institute science team. The app continues to run, but isn't actually using the GPU any longer. But for those affected - it's mainly the i5 range of processors and below - the WCG iGPU is simply too slow, and triggers a safeguard/watchdog in Windows. Not every iGPU is affected, which is why they haven't turned off the supply entirely. What follows only applies to that combination: if your situation is different, please stop reading here and post back with details of your GPU. I'm guessing that you're running an Intel GPU (iGPU) under Windows. Sadly, this is a known problem which the WCG team are aware of, but haven't yet addressed. ![]() The computer could be doing some good research crunching, but is not. It's wasting my computer time and interfering with my other projects and is pissing me off. Why would BOINC repeatedly send me tasks my computer can't process? Somebody said that perhaps my GPU was not compatible with these tasks. Stuff like this has happened several times in the past two weeks. Yesterday I aborted a running task because the time remaining was increasing instead of decreasing, and it was up to 3 days, 17+ hours with no progress being made. The task shown below has been stuck at 01:48:50, occasionally showing 01:48:49 then back to 01:48:50
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |