On an old HP DC5000, after running nicely for 85% of the estimated cycles, Einstein suddenly went to a status of "Waiting for Graphic Memory"
I do not have a capable video card, and as I said, was at 85% complete
This error lasted through a boot, and I finally had to abort the task
Anyone have any idea what was going on?
Copyright © 2025 Einstein@Home. All rights reserved.
Waiting for Graphic Memory
)
According to my brief research you have a variety of Intel Extreme 2 graphics controller within. Unless otherwise advised, I would deduce that your model is of 'Small Form Factor' ( otherwise you would know that you have an NVIDIA Quadro4 hanging off a PCI bus in the MicroTower version ). Follow up shows this product has Dynamic Video Memory Technology, which suggests a potential for fluctuant memory availability beyond usual concerns. I wouldn't expect that our executables have any capability to affect that ...
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
The message in question is a
)
The message in question is a fluke, a misnomer. It's caused by BOINC 6.12 which only has one scheduler that it uses for both CPU&GPU actions. It happens when BOINC reschedules the running of the task. Since it can't differentiate between whether it's running on a CPU or GPU, and in that client there's only the message about the GPU memory, it'll show you that message. BOINC can't show you a message it hasn't got.
So all that happened was that this task had exited due to unknown causes (e.g. anti-virus program locking it), and was being rescheduled to run again at a later stage. If you'd left it well alone, eventually, it should've restarted again.
Thanks, Ageless The reason
)
Thanks, Ageless
The reason I aborted the WU was this status had persisted through a boot and for more than two days, and was to the point that there was twice as much "time remaining" as wall clock time until the deadline
Mike,
BOINC Manager reports no usable GPUs when initializing
I've also now updated to
)
I've also now updated to v7.0.25, so this quirk shouldn't bite me again ;-)