+- +-
Say hello if visiting :) by Gecko
11 Jan 2023, 07:43:05 pm

Seti is down again by Mike
09 Aug 2017, 10:02:44 am

Some considerations regarding OpenCL MultiBeam app tuning from algorithm view by Raistmer
11 Dec 2016, 06:30:56 am

Loading APU to the limit: performance considerations by Mike
05 Nov 2016, 06:49:26 am

Better sleep on Windows - new round by Raistmer
26 Aug 2016, 02:02:31 pm

Author Topic: Nvidia just released new drivers  (Read 12865 times)

Maik

  • Guest
Re: Nvidia just released new drivers
« Reply #15 on: 09 Jan 2009, 08:00:33 pm »
Oh WTF ?!?
First time i got a blue screen ....
All written down here.

Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
Re: Nvidia just released new drivers
« Reply #16 on: 10 Jan 2009, 01:45:31 am »
Yes, as I said already new driver doesn't fix VLAR driver crash bug. Have strong considerations that this bug connected with 2-3 seconds limit for execution time for single CUDA kernel. This limitation exists in CUDA itself - OS just restart driver when there is no respond from it for few seconds. Probably the single way to eliminate this bug for now is to split affected kernel on few CUDA calls.

Offline Devaster

  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 653
  • I like Duke !!!
Re: Nvidia just released new drivers
« Reply #17 on: 10 Jan 2009, 05:39:40 am »
its a watchdog problem on primary display  in windows core - it  happens on  devices where is a primary display extended .  windows core is waiting for device response in 5 seconds max intervals if nothing happens it crashed to BSOD in xp or restart devce driver in vista. so if kernel take more execution time as 5 secs this is problem for
windows core. on  devices without primary display u can run kernels with any execution times ....

Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
Re: Nvidia just released new drivers
« Reply #18 on: 10 Jan 2009, 05:46:02 am »
its a watchdog problem on primary display  in windows core - it  happens on  devices where is a primary display extended .  windows core is waiting for device response in 5 seconds max intervals if nothing happens it crashed to BSOD in xp or restart devce driver in vista. so if kernel take more execution time as 5 secs this is problem for
windows core. on  devices without primary display u can run kernels with any execution times ....

Very likely, BUT there is too little number of such non-primarily devices available. And I personally have no one (actually have one PC with dual GeForce but it's x64 host and there are other troubles - it gives computational errors always it seems :( )
So, if you have such setup (CUDA GPU with no primarily display), please, try to redo VLAR tests from this thread: http://lunatics.kwsn.net/gpu-crunching/wus-that-cuda-mb-cant-do-correctly.0.html.
And report results. It would be helpfull for debugging I think.

 

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?
Members
Total Members: 97
Latest: ToeBee
New This Month: 0
New This Week: 0
New Today: 0
Stats
Total Posts: 59559
Total Topics: 1672
Most Online Today: 48
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 40
Total: 40
Powered by EzPortal