LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

USB 6509 BSOD 0x24

Hi,

 

I am using a USB 6509 with labview in an ate environment. It performs a test with a pretty variable(15 minutes-1 hour) time length, and it continually writes to the 6509. For some reason after about 45 minutes of conducting the test the computer will bluescreen with a 0x24 error code, after working correctly the entire time.The program is written in labview 2009.

Is this a driver problem, a labview problem, a hardware problem, or something else(this never happens to the setup in question outside of this test)?

 

Thanks

0 Kudos
Message 1 of 4
(2,663 Views)

Are you doing something like continually create DAQ tasks in a loop?  Something that would bleed resources over time?

 

Is CPU usage or memory usage growing over time before it finally crashes?

Message 2 of 4
(2,655 Views)

I checked the memory usage, and it definently has some problems with it, but I am not sure if it is the main problem. After 40 minutes of testing it uses ~550 MB of RAM, while the computer has 2GB, and is nowhere near page thrashing. CPU usage is well below 20%. I discovered that I am using only stop task, and not clear task, to de-allocate the task being created in the loop, so memory is leaking. I will update it and check to see if it helps with the BSOD or just the memory problem.

0 Kudos
Message 3 of 4
(2,648 Views)

If you are creating the task in the loop and only stopping it, then you are leaking resources as you are continually creating new tasks.

 

Tasks should only be created before loops.  Start, acquire, stop as needed inside of loops.  Clear the task after the loop.

0 Kudos
Message 4 of 4
(2,630 Views)