Seems to be a driver problem. Weird, never seen this before..
Maybe because of the DAG generation fails? It makes sense if the memory remain "occupied" by the failed DAG generated. 8gb - DAG size, then rounded is 3gb as I see in the list.
This can also explain why I can fix only when I reboot the rig