Solved Driver causing BSOD while running Labview need help debugging

[squiggy]

BSOD running Labview for long periods of time. The error seems to be tied to a USB driver error. I am unable to determine what driver is causing it. I will post the dump.dmp files.
Pretty much need help in debugging the crashes.

The devices being used are an LDT-5940C, Coherent PowerMAX USB PS19, and NI DAQmx 6341.

Thanks for any help.

 

[centaur78]

Could you use this tool to post all the files here..

Yes all the BSOD's does point to usbser.sys.... but based on the hardware that you have mentioned here.... alll are usb based..

So please upload all the files i will have a look

 

[squiggy]

All files using the SF Diagnostics tool

Centaur78 ,

I have attached the files that the GRAB ALL button copied.

 

[Sir George]

BSOD running Labview for long periods of time. The error seems to be tied to a USB driver error. I am unable to determine what driver is causing it. I will post the dump.dmp files.
Pretty much need help in debugging the crashes.

The devices being used are an LDT-5940C, Coherent PowerMAX USB PS19, and NI DAQmx 6341.

Thanks for any help.

You may get better assistance by posting this at;

BSOD Help and Support - Windows 7 Help Forums

HTH

 

[centaur78]

It looks like the driver for NI DAQ is causing this usbser.sys to wait for task completion.. are you using the latest drivers for the NI DAQ modem or communication ??

 

[squiggy]

Thanks,

I did download the NI DAQmx drivers not too long ago I will re-download the drivers and install them again to see if this solves the issue.

 

[centaur78]

Any update or feedback

 

[squiggy]

I ran the VI for two 24 hour periods with success. And then I restarted the computer and did a 12 hour runtime with the program it crashed about 6 hours in.
I am upgrading to the new VISA for labview, and repairing the DAQmx driver. After this I will run for another 12 hour run and see if it crashes like it did the last 12 hour run.

I can upload the new crash files but I it looks like the system crashed for the same reasons it crashed previously.

 

[squiggy]

Actually after reviewing the data the crash for the 12 hour run was 87 minutes in.

I have attached the crash files.

 

[centaur78]

Alright

I will wait for your feedback...

Just on the sidenote.... Not sure if this is relevent.. but if you running the 32bit drivers for NI DAQ... the issue is still not resolved in 2012 SP1.... Look here for more info and workaround

View attachment 268801

But its worth a try update Labview and the NI DAQ drivers for 64 bit and testing again...

If the issue is resolved do mark the thread as closed and REP those helped...

 

[centaur78]

squiggy

I think this is the latest version for NI DAQmx 9.7 with 64bit support....

Check and let me know

 

[squiggy]

That is the recent DAQmx driver.

I have installed the Labview 2012 x64 version, and installed the recent drivers for all devices being used.
After running the program for 9.5 hours the computer crashed due to the same reasons as before.
I am rearranging the code to see if this may eliminate this scenario from occurring.

 

[centaur78]

Did you install the SP1 for Labview 2012 ???

 

[squiggy]

Yes I did install the Labview 2012 SP1 as well as the f2 patch.

 

[centaur78]

Any update ??

 

[squiggy]

Sorry,

After installation I ran the program for 24 hours with success. I then restarted the computer and ran the computer on another 24 hour test, but it crashed at 9.5 hours into the run. After the crash I did another run to see if it would crash at around the same amount of time, but it ran for the full 24 hours. After the crash it ran for 3 full 24 hour test runs. This is something we can work with for now until NI figures out what part of their driver is causing this lockup and BSOD.

But this success was not accomplished until the x64 LabVIEW was installed and the drivers updated or repaired.

Thanks
Squiggy

 

[centaur78]

You are welcome Squiggy... Let me know if you need any more help.. and thanks for the feedback.