Waiting for memory lock 'memlock-0'

[Ludoplh-van-Ceulen]

Hi, I am stuck for last hours in GPUowl. When finishing the exponent PRP test to 100.00%, GPUowl is always frozen on this message:
Waiting for memory lock 'memlock-0'
and nothing is happening after that. I already manually tested one exponent with GPUowl at the beginning of Feb 2025 - and I had no problems. results.txt was updated, worktodo.txt cleared and .\proof folder contains 175 MB binary file. Manually uploading the results on GIMPS page went OK and everything was verified.
But within this 2nd exponent, nothing is happening, no files are being created. Its frozen after calculation reaches 100.00% with this message:
Waiting for memory lock 'memlock-0'

OS: Win11 24H2
Driver: Adrenalin 24.12.1 (WHQL Recommended)
GpuOwl VERSION v7.5-10-g61a08e2
GPU: AMD Radeon RX 7900XT
CPU: AMD Ryzen9 9900X
RAM: 64 GiB (conservative 6000 MT/s, CL36, 1.35V)
M.2 SSD 4 TB

My last saved calculation state is at 99.92%, so I was trying everything possible starting calculation from this 99.92% point (about 3 minutes of calculation to 100.00%), but nothing helped.

VGA has only 3 GiB of VRAM occupied of 20 GiB during calculation
RAM has only 12 GiB occupied of 64 GiB during calculation
SSD has only 1.7 TB occupied of 4 TB
Playing with hiberfil.sys, pagefile.sys. Executing the command in CMD as Admin.
Given full rights to GPUowl installation dir (and all files/sub-dirs. in it) to ordinary system users.
Computer restarted.

Where can be the problem? Especially when the first exponent went really OK. Both exponents (the 1st OK and this 2nd problematic one) are very similar in range 140M-150M.

[selroc]

Hi,
you have to delete the memlock file manually, it is located in a subdirectory of your worktodo directory.

[Ludoplh-van-Ceulen]

Hi, thanks for ans, but directory ".\GPUowl\memlock-0" is empty - I checked that when the error 1st time occurred.
.\GPUowl is my worktodo dir. Any other ideas are really appreciated.

[selroc]

Then delete the directory memlock-0.

[Ludoplh-van-Ceulen]

WOW it helped 👌
Many thanks 😉
But this seems to be a quite ugly bug in GPUowl 🤔

[Ludoplh-van-Ceulen]

solved 😊