for anyone else out there experiencing problems with the LOW MEM algo, you can change I=4 to I=3 in the bat file. It stops the DAG from going over 4 which was another problem I was having, some coins' DAG size is under 4 but close enough that variables in DAG size cause errors.

Whatever change you made, now it is saying a new error "out of memory"

something definitely very wrong here

So far so good after a few hours this morning. Will let you know problem returns. Thank you.

Thank goodness I am not the only one. When the low mem algo works, it works great. When it stops working, in the dashboard it populates a huge amount of extra workers connected to the name of my 4GB cards that cannot connect and I have to refresh the screen to try to get them to disappear. Its a hea...

I sent an email, I do not have a ticket number. Can you please let me know how you will contact me. I think you should also write the solution here to help people with this problem, as I have noticed others have been confused about how to write the bat file etc in the past

Here is what I am using for GMiner 2.78, Please let me know if this is right.
Otherwise the low mem ethash is just extremely unstable?

miner.exe --algo ethash --server prohashing.com:3358 --user myusername --pass l=4,n=1650,a=ethash-lowmemory
pause

I have had two of my cards with 4GB running fine on the Low Memory Ethash algo, then yesterday those two units keep getting kicked off the server saying "Connection Error: Connection Closed". Now today I am getting the same result. Sometimes works, sometimes doesn't. I have not adjusted th...