Amd link connection timeout windows#
There are new registry keys for Vista and Windows 7. I think that was the key for Windows XP 64-bit.
(outdated again, see the updates below for the most recent information) The registry key above is out-of-date. in gpu local memory you just have some command buffers complete occasionally, to prove to the OS that you're not stuck in an infinite loop.įinally, GPUs are fast, so if your application is not able to do useful work in that 5 or 10 seconds, I'd take that as a sign that something is wrong. You should not have to read all of your data back and forth across the PCIX bus on every time slice you can leave your textures, etc. In the AMD Stream SDK, a long sequence of operations can be broken up into multiple time slices by explicitly flushing the command queue with a CtxFlush() call. The basic unit that has to fit within the time slice is not your entire application, but the execution of a single command buffer. I.e., instead of computing 1,000,000 output pixels in one fell swoop, issue 10 commands to the gpu to compute 100,000 each. Ideally, you should be able to break your kernel operations up into multiple passes over your data to break it up into operations that run in the time limit.Īlternatively, you can divide the problem domain up so that it's computing fewer output pixels per command. Look for some reference to "VPU Recovery" in the CUDA docs. You may also need to do something in the NVidia control panel. To disable it, you need to regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog\Display\DisableBugCheck, create a REG_DWORD and set it to 1.
You can disable the Windows watchdog timer, but that is highly not recommended, for reasons that should be obvious. I'm not a CUDA expert, - I've been developing with the AMD Stream SDK, which AFAIK is roughly comparable.
0 kommentar(er)
