BSOD Ntoskrnl.exe and ndistapi.sys

Hello and welcome to SF :) .

The problem seem to originate in your USB audio solution.

A driver is in an inconsistent or invalid power state. Typically occurs during events that involve power state transitions,
such as shutting down, or moving into or out of standby or hibernate mode.

Code:

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80085c8bf0, Physical Device Object of the stack
Arg3: fffff80001f1a3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8008af5010, The blocked IRP

Code:

!irp fffffa8008af5010 1
IoStatus.Status = c00000bb
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa8008590e10 00000000 00000000-00000000    
           \Driver\NvnUsbAudio
            Args: 00016600 00000001 00000004 00000006
 [ 16, 2]   0 e1 fffffa80083e3d00 00000000 00000000-00000000    pending
           \Driver\ksthunk
            Args: 00016600 00000001 00000004 00000006
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800973c3a0    

            Args: 00000000 00000000 00000000 00000000

Code:

!error c00000bb
Error code: (NTSTATUS) 0xc00000bb (3221225659) - The request is not supported.

By using the lmvm command we can get more information about the driver;

Code:

lmvm NvnUsbAudio
start             end                 module name
fffff880`04bcc000 fffff880`04bdc000   nvnusbaudio T (no symbols)           
    Loaded symbol image file: nvnusbaudio.sys
    Image path: nvnusbaudio.sys
    Image name: nvnusbaudio.sys
    Timestamp:        Wed Oct 05 14:46:33 2011

• Driver Reference Table - nvnusbaudio.sys

We see that the driver is very old.
Please update the driver .:: Download ::.

Please follow this tutorial and disable the USB selective suspend setting;

• USB Selective Suspend - Turn On or Off

---

The second bugcheck is a double fault, which means that one exception was being processed
and while that was ongoing a second exception occurred;

Code:

BugCheck 7F, {8, 80050033, 406f8, fffff880071d87ee}

*** WARNING: Unable to verify timestamp for MAudioFastTrackPro.sys
*** ERROR: Module load completed but symbols could not be loaded for MAudioFastTrackPro.sys
Probably caused by : MAudioFastTrackPro.sys ( MAudioFastTrackPro+147ee )

• Driver Reference Table - MAudioFastTrackPro.sys

Usually to debug this sort of bugcheck we need a a Kernel dump at least but in this case
it's pretty consistent with the previous bugcheck in being a USB Audio device.

Again this driver is pretty old;

Code:

lmvm MAudioFastTrackPro
start             end                 module name
fffff880`071c4000 fffff880`071f4000   MAudioFastTrackPro T (no symbols)           
    Loaded symbol image file: MAudioFastTrackPro.sys
    Image path: MAudioFastTrackPro.sys
    Image name: MAudioFastTrackPro.sys
    Timestamp:        Wed Dec 08 01:37:01 2010

Please update the driver .:: Download ::.

Even by looking at the raw stack we can see that the driver has entered a loop
here is a small snip;

Code:

0xfffff880063e93d8 : 0xfffff800020e99cc : nt!IopFreeIrp+0x11c
0xfffff880063e9448 : 0xfffff800020dc5d1 : nt!IopfCompleteRequest+0x341
0xfffff880063e9488 : 0xfffff800020dc5d1 : nt!IopfCompleteRequest+0x341
0xfffff880063e94d8 : 0xfffff88003e952b2 : usbhub!UsbhIncPdoIoCount+0xda
0xfffff880063e9518 : 0xfffff88003e952b2 : usbhub!UsbhIncPdoIoCount+0xda
0xfffff880063e9578 : 0xfffff88003e95baa : usbhub!UsbhPdoInternalDeviceControl+0x18e
0xfffff880063e95c8 : 0xfffff88003e63fb7 : usbhub!UsbhGenDispatch+0x57
0xfffff880063e97b8 : 0xfffff800020e99cc : nt!IopFreeIrp+0x11c
0xfffff880063e9828 : 0xfffff800020dc5d1 : nt!IopfCompleteRequest+0x341
0xfffff880063e9868 : 0xfffff800020dc5d1 : nt!IopfCompleteRequest+0x341
0xfffff880063e98b8 : 0xfffff88003e952b2 : usbhub!UsbhIncPdoIoCount+0xda
0xfffff880063e98f8 : 0xfffff88003e952b2 : usbhub!UsbhIncPdoIoCount+0xda
0xfffff880063e9958 : 0xfffff88003e95baa : usbhub!UsbhPdoInternalDeviceControl+0x18e
0xfffff880063e99a8 : 0xfffff88003e63fb7 : usbhub!UsbhGenDispatch+0x57
0xfffff880063e9b40 : 0xfffff800022696c0 : nt!ExpScratchBufferLookasideList
0xfffff880063e9b48 : 0xfffff8000220971e : nt!MiAllocatePoolPages+0x9e
0xfffff880063e9b98 : 0xfffff800020e99cc : nt!IopFreeIrp+0x11c
0xfffff880063e9c08 : 0xfffff800020dc5d1 : nt!IopfCompleteRequest+0x341
0xfffff880063e9c48 : 0xfffff800020dc5d1 : nt!IopfCompleteRequest+0x341
0xfffff880063e9c78 : 0xfffff80002268580 : nt!NonPagedPoolDescriptor
0xfffff880063e9c98 : 0xfffff88003e952b2 : usbhub!UsbhIncPdoIoCount+0xda
0xfffff880063e9cd8 : 0xfffff88003e952b2 : usbhub!UsbhIncPdoIoCount+0xda
0xfffff880063e9d38 : 0xfffff88003e95baa : usbhub!UsbhPdoInternalDeviceControl+0x18e
0xfffff880063e9d88 : 0xfffff88003e63fb7 : usbhub!UsbhGenDispatch+0x57
0xfffff880063e9f78 : 0xfffff800020e99cc : nt!IopFreeIrp+0x11c

Post back with the results !

Serikiito said:

Hi there,

Thank you for your help! Much appreciated. I've uninstalled the Novation driver and installed the latest from their website, I'm pretty sure I had the latest one.

With the M-Audio driver, I'm on the latest driver. They haven't updated their drivers in a few years. I thought my m-audio interface would be a problem. (Been a bit sketchy in the past). So I've brought a new reliable audio interface (that updates their drivers regularly) and that should be with me in the next week.

I've disabled the USB selective suspend, what will this do? I know it disables suspending USB ports to save power but how will it help me?

Thank you for your time and help

Hi, thanks for the feedback :) .
The first bugcheck (0x9F) is a power transition failure which happens when a device driver fails
to switch between power states; suspending or resuming from standby mode, suspending or resuming from hibernation, shutting down.
Or in other words the device was idle then an interrupt was sent to "wake it up", the device failed to return the packet within the time limit in order to allow the next IRP to pass through.
So by disabling the selective suspension of the USB hubs we are not allowing them to switch power state
when the PC is at idle and the chance to create a problem in the future.