When I didn't do it that way either the CUDA WU's stuff up ( typically reported as in error, but occasionally not and then proceeding through to not validating in the quorum ) and/or I get funny visual behaviours in the game. Richard had earlier pointed out to me an issue with driver swapping ( regarding remote sessions into CUDA running machines ) - perhaps that is relevant here.
you can not use windows remote desktop or switch users while running cuda-jobs!
SUPPOSEDLY there is a new Boinc version coming out that works around this problem, I am using the latest released version and it is not mentioned though.
It's better to identify BOINC by the actual version number, rather than using relative terms like "the latest" which may mean something different for readers coming back to this thread in the future.
All your computers here were using v6.10.58 (one v6.10.56) when they last contacted the servers around 11 April 2011. Since then, "the latest" recommended version for Windows has gone up to v6.12.26
I'm not sure that v6.12.26 is entirely bug-free (what computer software ever is?), but it has some improvements. It may schedule your ATI GPUs more effectively, and it does handle the RDP/user switch problem better. Not a complete solution - that would require support from Microsoft and nVidia/AMD - but GPU tasks are now paused and can be resumed later, rather than failing with an error.
6.12.16 had the workaround: client: Fast User Switching does not change the session protocol to RDP when the active session is put into the background and a new one is brought into the foreground. It appears it is safe to use the connected state in addition to the protocol to detect when the session is no longer capable of processing GPU work.
This means it's included in 6.12.26/.28
Any other fixes or workarounds will be coming in BOINC 7.
When I didn't do it that way either the CUDA WU's stuff up ( typically reported as in error, but occasionally not and then proceeding through to not validating in the quorum ) and/or I get funny visual behaviours in the game. Richard had earlier pointed out to me an issue with driver swapping ( regarding remote sessions into CUDA running machines ) - perhaps that is relevant here.
you can not use windows remote desktop or switch users while running cuda-jobs!
SUPPOSEDLY there is a new Boinc version coming out that works around this problem, I am using the latest released version and it is not mentioned though.
It's better to identify BOINC by the actual version number, rather than using relative terms like "the latest" which may mean something different for readers coming back to this thread in the future.
All your computers here were using v6.10.58 (one v6.10.56) when they last contacted the servers around 11 April 2011. Since then, "the latest" recommended version for Windows has gone up to v6.12.26
I'm not sure that v6.12.26 is entirely bug-free (what computer software ever is?), but it has some improvements. It may schedule your ATI GPUs more effectively, and it does handle the RDP/user switch problem better. Not a complete solution - that would require support from Microsoft and nVidia/AMD - but GPU tasks are now paused and can be resumed later, rather than failing with an error.
Sorry...I am STILL using v6.10.58 on most of my pc's but have upgraded two of them to v6.12.26. I COULD still be using v6.10.56 on one or two pc's, I have 15 running and it is a pain to keep each at the latest version. Most are Boinc only machines and as long as they are working it is easier to leave them be.
That's probably because Microsoft doesn't care too much about CUDA. It's a driver with the WHQL (Windows Hardware Quality Labs) logo, meaning that the drivers will run perfectly fine under Windows, nothing more.
"Products that pass the WHQL tests get to use a "Certified for Windows" logotype, which certifies that the hardware or software has had some share of testing by Microsoft to ensure compatibility. The actual logo used depends on the version of Microsoft Windows.
For device drivers passing the WHQL tests, Microsoft creates a digitally signed certification file that, when included in the driver installation package allows installation on 64 bit versions of Windows and prevents 32 bit versions of Vista and all versions of Windows XP from displaying a warning message that the driver has not been certified by Microsoft."
That's probably because Microsoft doesn't care too much about CUDA. It's a driver with the WHQL (Windows Hardware Quality Labs) logo, meaning that the drivers will run perfectly fine under Windows, nothing more.
you are running XP - the problem with user-switching does not affect it.
Not sure where you got this bit of information from, but it isn't true. The fast-user switching on all Windows versions that can do fast-user switching have the problem that hardware drivers will switch to a Windows driver. These Windows drivers do not have explicits like CUDA support, OpenGL support and such and one cannot update these Windows drivers.
This driver switching is what causes the problem of the GPU going missing.
I think what you're confused with is that BOINC under XP can be installed as a service, where it cannot be done so under Vista and 7, as these Windows versions split the driver layers. The user accounts do not run in the same layer as the drivers, and as such BOINC cannot find the drivers --and thus not the GPUs-- when BOINC is installed as a service under Vista and 7.
Under XP the user accounts run at the same layer as the drivers, and as such here BOINC has no problem finding the GPU at all times. Well, but for when you switch users fast. ;-)
RE: RE: RE: When I
)
It's better to identify BOINC by the actual version number, rather than using relative terms like "the latest" which may mean something different for readers coming back to this thread in the future.
All your computers here were using v6.10.58 (one v6.10.56) when they last contacted the servers around 11 April 2011. Since then, "the latest" recommended version for Windows has gone up to v6.12.26
I'm not sure that v6.12.26 is entirely bug-free (what computer software ever is?), but it has some improvements. It may schedule your ATI GPUs more effectively, and it does handle the RDP/user switch problem better. Not a complete solution - that would require support from Microsoft and nVidia/AMD - but GPU tasks are now paused and can be resumed later, rather than failing with an error.
6.12.16 had the
)
6.12.16 had the workaround:
client: Fast User Switching does not change the session protocol to RDP when the active session is put into the background and a new one is brought into the foreground. It appears it is safe to use the connected state in addition to the protocol to detect when the session is no longer capable of processing GPU work.
This means it's included in 6.12.26/.28
Any other fixes or workarounds will be coming in BOINC 7.
RE: RE: RE: RE: When
)
Sorry...I am STILL using v6.10.58 on most of my pc's but have upgraded two of them to v6.12.26. I COULD still be using v6.10.56 on one or two pc's, I have 15 running and it is a pain to keep each at the latest version. Most are Boinc only machines and as long as they are working it is easier to leave them be.
Thanks Jord for the update.
ok, nvidia has published a
)
ok, nvidia has published a new driver version for windows - 275.33 with WHQL logo.
and of course the downclock bug still strikes.. :(
That's probably because
)
That's probably because Microsoft doesn't care too much about CUDA. It's a driver with the WHQL (Windows Hardware Quality Labs) logo, meaning that the drivers will run perfectly fine under Windows, nothing more.
"Products that pass the WHQL tests get to use a "Certified for Windows" logotype, which certifies that the hardware or software has had some share of testing by Microsoft to ensure compatibility. The actual logo used depends on the version of Microsoft Windows.
For device drivers passing the WHQL tests, Microsoft creates a digitally signed certification file that, when included in the driver installation package allows installation on 64 bit versions of Windows and prevents 32 bit versions of Vista and all versions of Windows XP from displaying a warning message that the driver has not been certified by Microsoft."
RE: That's probably because
)
i know...
Actually I do do a lot of
)
Actually I do do a lot of user switching sometimes. I'll look into upgrading to 6.12.10. Does this limitation apply to 'run as...'
32bit Windows XP Home
AMD Opteron 180
ASUS A8N-SLI Motherboard
Nvidia 450GTS GPU
4GB DDR 400 Memory
RE: Actually I do do a lot
)
you are running XP - the problem with user-switching does not affect it.
only win 6.x (aka vista, win7 and the coresponding server versions) got that problem.
How about my swap files? I
)
How about my swap files?
I have two hard drives. My main one with my OS and stuff like BOINC on it is an IDE drive. I set it to have a 2 gig swap file.
My second drive, which I use to hold games and large files for storage is a high speed SATA drive. It has around a 6gb swap file on it.
Would increasing the swap file size on my IDE drive help E@Home?
32bit Windows XP Home
AMD Opteron 180
ASUS A8N-SLI Motherboard
Nvidia 450GTS GPU
4GB DDR 400 Memory
RE: you are running XP -
)
Not sure where you got this bit of information from, but it isn't true. The fast-user switching on all Windows versions that can do fast-user switching have the problem that hardware drivers will switch to a Windows driver. These Windows drivers do not have explicits like CUDA support, OpenGL support and such and one cannot update these Windows drivers.
This driver switching is what causes the problem of the GPU going missing.
I think what you're confused with is that BOINC under XP can be installed as a service, where it cannot be done so under Vista and 7, as these Windows versions split the driver layers. The user accounts do not run in the same layer as the drivers, and as such BOINC cannot find the drivers --and thus not the GPUs-- when BOINC is installed as a service under Vista and 7.
Under XP the user accounts run at the same layer as the drivers, and as such here BOINC has no problem finding the GPU at all times. Well, but for when you switch users fast. ;-)