Two threads on one gpu?

Author	Message
Tom M Volunteer tester Send message Joined: 28 Nov 02 Posts: 5124 Credit: 276,046,078 RAC: 462	Message 1980200 - Posted: 14 Feb 2019, 0:45:00 UTC Last modified: 14 Feb 2019, 0:45:21 UTC This is the 2nd time this has happened. under Windows 10 I had a Amd R5 2400G and one time when I installed Amd video drivers, the install caused Boinc Manager to think I had 2 gpus. The task manager didn't think I had two gpus and it didn't show processing in some other locations of the Gpu. So I re-installed the Amd drivers and the problem went away. I have just experienced the same issue only this time it was with Nvidia cards. And one card is busy, the other is not. Boinc Manager is convinced I have 2 gpus. Only one is showing busy under the windows task manager/gpu z and the other is not busy. But Boinc Manager shows 2 gpus running. And neither is approaching the 7 minutes per task on SOG apps that it used to. Odd. :( Tom A proud member of the OFA (Old Farts Association). ID: 1980200 ·

Tom M Volunteer tester Send message Joined: 28 Nov 02 Posts: 5124 Credit: 276,046,078 RAC: 462	Message 1980216 - Posted: 14 Feb 2019, 3:18:28 UTC - in response to Message 1980200. This is the 2nd time this has happened. under Windows 10 I had a Amd R5 2400G and one time when I installed Amd video drivers, the install caused Boinc Manager to think I had 2 gpus. The task manager didn't think I had two gpus and it didn't show processing in some other locations of the Gpu. So I re-installed the Amd drivers and the problem went away. I have just experienced the same issue only this time it was with Nvidia cards. And one card is busy, the other is not. Boinc Manager is convinced I have 2 gpus. Only one is showing busy under the windows task manager/gpu z and the other is not busy. But Boinc Manager shows 2 gpus running. And neither is approaching the 7 minutes per task on SOG apps that it used to. Odd. :( Tom I back graded slightly on the 2400G box and I have backgraded to version 3.97 of the Nvidia drivers and all is well. At least both gpus are showing they are loaded/working. And the run times are beginning to look "normal" for Windows/SOG instead of more than double what it "used" to be. Tom A proud member of the OFA (Old Farts Association). ID: 1980216 ·

Keith Myers Volunteer tester Send message Joined: 29 Apr 01 Posts: 13160 Credit: 1,160,866,277 RAC: 1,873	Message 1980222 - Posted: 14 Feb 2019, 3:30:37 UTC Last modified: 14 Feb 2019, 3:32:04 UTC I think the API's for both AMD and Nvidia are getting ahead of themselves. Numerous issues lately for both camps. The latest drivers should be considered "beta" and at least you can roll back to older, stabler drivers. Until you get caught in a Catch-22 for needing the latest drivers to support the latest hardware. The two cards shown instead of one has other posts in other projects. So you are not alone or unique. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) ID: 1980222 ·

Richard Haselgrove Volunteer tester Send message Joined: 4 Jul 99 Posts: 14571 Credit: 200,643,578 RAC: 874	Message 1980251 - Posted: 14 Feb 2019, 7:50:34 UTC We had a problem like this reported on the BOINC dev boards recently. In the end, after a lot of red herrings, the user came up with this answer for himself: https://boinc.berkeley.edu/forum_thread.php?id=12830&postid=90033#90033 Long story short, a driver installation hadn't removed the old driver completely. So he had two drivers, and that looked to BOINC like two GPUs. Thorough eradication of all drivers, and clean re-installation of just one of them, solved his problem. ID: 1980251 ·

©2023 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.