Random BSODs W7, guessing driver issue

By pooh5858
Oct 31, 2010
Post New Reply
  1. Hello, I am suffering from daily BSOD issue on W7.
    I'm using HP laptop dv8t and using it for a simple home studio purposes. I have external MIDI controller (Novation SL MK II) and audio interface for Pro Tools (MBox MINI II and Pro Tools 8.0.4 drivers). Interestingly, it does not have blue screen issues whenever I am producing. But during web surfing, playing games and at random moments, blue screen comes up repeatedly. Most of them are as DRIVER IRQL NOT LESS OR EQUAL error, but sometimes it involves Win32k.sys errors. Though I'm guessing faulty driver on pro tools 8.0.4, I would love to hear other opinions as well. Below are some of my dump files. Please help !






    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {28, 2, 0, fffff88005334264}

    Probably caused by : ntkrnlmp.exe ( nt!IopAllocateIrpPrivate+cb )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88005334264, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800037000e0
    0000000000000028

    CURRENT_IRQL: 0

    FAULTING_IP:
    +6536306135303264
    fffff880`05334264 80792905 cmp byte ptr [rcx+29h],5

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from fffff800037e26b6 to fffff800034d678b

    STACK_TEXT:
    fffff880`0c5ed9b0 fffff800`037e26b6 : 00000000`0001202f fffffa80`08cda500 fffff880`0c5edca0 fffff800`03642e80 : nt!IopAllocateIrpPrivate+0xcb
    fffff880`0c5eda10 fffff800`037e3156 : fffff880`0c5edbf8 00000000`000004c0 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x3c6
    fffff880`0c5edb40 fffff800`034c67d3 : fffffa80`08d7c620 00000000`0171f768 fffff880`0c5edbc8 fffff880`0c5edc00 : nt!NtDeviceIoControlFile+0x56
    fffff880`0c5edbb0 00000000`7751f6ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0171f618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7751f6ca


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!IopAllocateIrpPrivate+cb
    fffff800`034d678b 498bcc mov rcx,r12

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!IopAllocateIrpPrivate+cb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c42e3

    FAILURE_BUCKET_ID: X64_0xD1_nt!IopAllocateIrpPrivate+cb

    BUCKET_ID: X64_0xD1_nt!IopAllocateIrpPrivate+cb

    Followup: MachineOwner
    ---------









    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 3B, {c000001d, fffff960000b4b60, fffff8800503e700, 0}

    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+4c0 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c000001d, Exception code that caused the bugcheck
    Arg2: fffff960000b4b60, Address of the instruction which caused the bugcheck
    Arg3: fffff8800503e700, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {

    FAULTING_IP:
    +6536306135303264
    fffff960`000b4b60 488bc4 mov rax,rsp

    CONTEXT: fffff8800503e700 -- (.cxr 0xfffff8800503e700)
    Unable to read context, Win32 error 0n30

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff8000347a1e0 to fffff88006bd8c61

    STACK_TEXT:
    fffff800`00b9cca8 fffff800`0347a1e0 : 00000000`0017c970 fffffa80`078bcd40 fffff800`035e7e80 fffff800`03477ddc : 0xfffff880`06bd8c61
    fffff800`00b9ccb0 fffff800`03474ecc : fffff800`035e7e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x4c0
    fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


    FOLLOWUP_IP:
    nt!PoIdle+4c0
    fffff800`0347a1e0 0fba25a02418000f bt dword ptr [<Unloaded_Unknown_Module_00000000`00000000>+0x1824a0 (00000000`001824a0)],0Fh

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!PoIdle+4c0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c42e3

    STACK_COMMAND: .cxr 0xfffff8800503e700 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_nt!PoIdle+4c0

    BUCKET_ID: X64_0x3B_nt!PoIdle+4c0

    Followup: MachineOwner
    ---------











    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffff680007e30c2, 2, 0, fffff88001ba674f}

    Probably caused by : ndis.sys ( ndis!NdisSendNetBufferLists+4f )

    Followup: MachineOwner
    ---------

    6: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff680007e30c2, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88001ba674f, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b70e0
    fffff680007e30c2

    CURRENT_IRQL: 2

    FAULTING_IP:
    ndis!NdisSendNetBufferLists+4f
    fffff880`01ba674f f7433040010000 test dword ptr [rbx+30h],140h

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: fffff88004b5a010 -- (.trap 0xfffff88004b5a010)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000d501 rbx=0000000000000000 rcx=fffff88001b4ed00
    rdx=fffffa80045b2030 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001ba674f rsp=fffff88004b5a1a0 rbp=0000000000000000
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
    r11=fffffa8003ed281e r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    ndis!NdisSendNetBufferLists+0x4f:
    fffff880`01ba674f f7433040010000 test dword ptr [rbx+30h],140h ds:ddb0:00000000`00000030=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff8000347dae9 to fffff8000347e580

    STACK_TEXT:
    fffff880`04b59ec8 fffff800`0347dae9 : 00000000`0000000a fffff680`007e30c2 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`04b59ed0 fffff800`0347c760 : 00000000`00000000 fffff680`007e30c2 fffff880`0161f900 fffff680`007e3092 : nt!KiBugCheckDispatch+0x69
    fffff880`04b5a010 fffff880`01ba674f : fffffa80`03f5ddb0 fffff880`04b5a2f0 ffff0000`0563ce28 fffff880`04b5a1f0 : nt!KiPageFault+0x260
    fffff880`04b5a1a0 fffff880`01c6861e : 00000000`00000000 00000000`0000000e fffffa80`0837c010 00000000`00000001 : ndis!NdisSendNetBufferLists+0x4f
    fffff880`04b5a200 fffff880`01c69b9f : fffff880`01d6b9a0 00000000`00000000 00000000`00000000 00000000`01d60800 : tcpip!IppFragmentPackets+0x39e
    fffff880`04b5a320 fffff880`01c65aa5 : 00000000`00000000 00000000`00140005 00000000`00000000 fffffa80`0582b858 : tcpip!IppDispatchSendPacketHelper+0x8f
    fffff880`04b5a3b0 fffff880`01c673f3 : 00000000`00000006 fffff880`01aea200 00000000`00000014 fffff880`00000000 : tcpip!IppPacketizeDatagrams+0x2d5
    fffff880`04b5a4d0 fffff880`01c6c0fe : 00000000`0000ffff fffff880`01c86407 fffff880`01d6b9a0 fffffa80`03f5ddb0 : tcpip!IppSendDatagramsCommon+0x753
    fffff880`04b5a7a0 fffff880`01c7d370 : fffffa80`05820a00 fffffa80`083cf190 fffffa80`0000001c fffffa80`03f5ddb0 : tcpip!IpNlpSendDatagrams+0x3e
    fffff880`04b5a7e0 fffff880`01c779c6 : 00000000`00000000 fffffa80`05976201 fffff880`01d65128 fffffa80`00000000 : tcpip!TcpTcbSend+0xc19
    fffff880`04b5aa60 fffff880`01c8058c : fffff880`08cf8a00 00000000`00000000 00000000`00000000 fffff880`01c61900 : tcpip!TcpFlushDelay+0x316
    fffff880`04b5ab40 fffff880`01c608f7 : fffffa80`05978000 fffffa80`0598b3a0 fffffa80`058234a1 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x20c
    fffff880`04b5abf0 fffff880`01c609b5 : 00000000`00000006 fffff880`04b5ad70 00000000`00000006 00000000`00000000 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`04b5acb0 fffff880`01c60ee9 : 00000000`00000006 00000000`00000000 fffff880`01d6bd08 fffff880`01d6b9a0 : tcpip!IppProcessDeliverList+0x45
    fffff880`04b5ad10 fffff880`01c5fd40 : 00000000`3201a8c0 fffffa80`05978000 fffff880`01d6b9a0 00000000`0837c001 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`04b5adf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IpFlcReceivePackets+0x650


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    ndis!NdisSendNetBufferLists+4f
    fffff880`01ba674f f7433040010000 test dword ptr [rbx+30h],140h

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: ndis!NdisSendNetBufferLists+4f

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ndis

    IMAGE_NAME: ndis.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4bb6aab0

    FAILURE_BUCKET_ID: X64_0xD1_ndis!NdisSendNetBufferLists+4f

    BUCKET_ID: X64_0xD1_ndis!NdisSendNetBufferLists+4f

    Followup: MachineOwner
    ---------
  2. Macboatmaster

    Macboatmaster TechSpot Member Posts: 79

    The most likely cause is memory or as you say a driver issue.

    What is shown as the failures and causes on your Problem reports see this

    http://www.sevenforums.com/tutorials/4566-problem-reports-solutions-view-history-details.html

    You have not overclcked the processor have you. That can also be a cause of some of these errors.

    I would do three things.
    1. I would check for any driver issues. Are there any warnings against drivers. Graphics is a favourite.

    2. I would a chkdsk and a system file check. See this for System File Checker
    http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    and I am sure you know but see this for chkdsk
    http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    3. If still not resolved I would run a memory test.

    4. I would install Who crashed and see if it gives a better idea.
    http://www.resplendence.com/whocrashed

    5. Can you tie down the start of these errors to any particular installation or event..

    I


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.