Forum > GPU crunching
WUs that CUDA MB can't do correctly
Raistmer:
Another damaged online result with good standalone ones.
It seems OS reboot after driver crash/"snow" screen is required indeed although there is no visible memory leak.
AR =0.437128
ADDON: added another such result.
[attachment deleted by admin]
Maik:
I noticed not every WU-crash leads into a gfx-memoryleak.
Very often -after my script killed a stucking task- they run normal to 100% without any loss of memory.
It seems that the memoryleak isn't indicated from stucking WU.
My assumption:
There must be an instruction (send from cuda-app) that run inside the shaders in a neverending loop.
Maybe you know, an instruction is given with a special task to the first shader-unit, it complete it gives with next special task to the next shader-unit and so on until the instruction is handled. (ok, thats for grafic calculation, dont know how cuda works)
Is there a fault, maybe the instructions runs from shader-unit to shader-unit without completing it, it is blocking the gfx to work correctly (snow on screen, jumping pixel, grafic-errors, chrash of gfx).
I had this error one time. Tryied driver-reset via RivaTuner -> nothing happend. If you have this error, you have to reboot your host ... :(
Raistmer:
Maybe...
There is no evidences of memory leak still.... Now I have driver crashed and restarted, "snow" on screen so will try to run task again to see if initial free memory will be less or not.
And here is "classic" VLAR AR~0.009 (edited)
It crashes videodriver with "snow" visual effect on screen.
ADDON:
No memory leak. Just usual amount of free GPU memory.
And many CUDA errors in log, ended with overflow.
[attachment deleted by admin]
Maik:
will do a stand alone test with 23ap08aa.4504.481.10.11.187 at my host ... done
-results AK_v8_win_SSE41.exe -> equivalent to yours (3 Pulse)
-MB_6.06r380mod_CUDA.exe -> task (WinTaskManager) goes stuck, after 30 sec i kicked them
'--> no video-errors.
Maik:
--- Quote from: Maik on 04 Jan 2009, 08:03:49 pm ----MB_6.06r380mod_CUDA.exe -> task (WinTaskManager) goes stuck, after 30 sec i kicked them
'--> no video-errors.
--- End quote ---
I was really wrong. After restarting BM i noticed first Cuda-Wu wont work (stuck). -> reboot -> now it runs ... reporting back ->done
WU true angle range is : 2.722583 (Triplet count: 2), normally run through ... must be a driver crash from past task
I'v been warned now. Next WU's i get with AR below 0.00 i'll abort bevore bm trys to crunch them *grrr >:(
edit: found one ... AR: 0.0078554334964187 wanna have it? -> attachment ;) (not tested yet!)
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version