DAQmxResetDevice never returns. PC must be rebooted

Question

We have a problem where our program never returns from a call to DAQmxResetDevice(). The program cannot be stopped via task manager. Trying to shutdown the PC frequently results in a blue screen of death (BSOD). Sometimes the Windows won't even shut down and we must resort to physically powering off the PC.
This is the code that gets called when the program starts and when it tries to recover from an error such as the USB cable is removed and reinserted. Is there some precondition that should be checked before calling DAQmxResetDevice? Or should it ALWAYS be safe to call it? Note that some of the args and error handling has been removed so you can see the sequence of calls.
            err = DAQmxResetDevice( m_device );   <= hangs on this statement
            if (err != 0)
                DAQmxGetErrorString(err, errorString, 1024);
                Log(errorString);
            if( DAQmxCreateTask( "", &m_analogTaskHandle ) == 0)
                err = DAQmxCreateAIVoltageChan( ... m_analogTaskHandle ... );
                if( err == 0 )
                    DAQmxStartTask( m_analogTaskHandle );
Thanks for any ideas, we're getting close to product release and we don't want our customers having to reboot their PC just because of glitch in the NI code.
Hardware is a USB6008 connected to PC via an external
hub. Sometimes we have two of these systems (two hubs, two USB6008 cards)
connected to one PC. But it will happen when only one is currently conected.
Win7 64
DAQmx 9.2
Mitch

Answer 1

Additional Info. This is the WinDbg analysis of the minidump file created when the BSOD happens during shutdown. Note that the probable cause is nipalk.sys.
0: kd> !analyze -v
*                        Bugcheck Analysis                                    *
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006d58680, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510
Debugging Details:
DRVPOWERSTATE_SUBCODE:  4
FAULTING_THREAD:  fffffa8006d58680
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002ad5992 to fffff80002ad45da
STACK_TEXT:  
`00000000 : nt!KiSwapContext+0x7a
`08e5ca90 : nt!KiCommitThreadWait+0x1d2
`8002de00 : nt!KeWaitForSingleObject+0x19f
`009b2180 : nipalk+0x8e784
`00024010 : 0xfffff8a0`14132000
`03569460 : 0xfffff800`00000000
`03a3d7b5 : 0xffff0000`00020000
`03569460 : 0x8002de00
`03a78488 : 0xfffff880`009b2180
`00000000 : 0xfffff8a0`00024010
`000e0082 : 0xfffff880`03569460
`00000000 : nimxdfk+0xb7b5
`ffffffff : 0xfffff880`03569460
`00000020 : nimxdfk+0x46488
BugCheck 1000009F, {4, 258, fffffa8006d58680, fffff80000b9c510}
Unable to load image \SystemRoot\System32\drivers\nipalk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nipalk.sys
*** ERROR: Module load completed but symbols could not be loaded for nipalk.sys
Unable to load image \SystemRoot\system32\DRIVERS\nimxdfk.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nimxdfk.dll
*** ERROR: Module load completed but symbols could not be loaded for nimxdfk.dll
Probably caused by : nipalk.sys ( nipalk+8e784 )
BSODs are really unacceptable. Thanks for your help.
Mitch