Random BSODs bccode d1


  1. Posts : 2
    Windows 7 Ultimate x64
       #1

    Random BSODs bccode d1


    Hello, been getting BSOD almost daily for past couple of weeks. Sometimes two times a day and sometimes it will go two or more days with no BSOD.

    No pattern that I can detect as far as the same program triggering it. Looking back at program install dates in Add/Remove Programs, I see Bitdefender and Steam were installed about the time the BSOD started.

    DM Log Collector attached, thanks for any help.
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #2

    It looks like your Malwarebytes is causing the problem or conflicting with other software (probably an antivirus). Try turning off Malwarebytes and then report back. Based upon your post I would say a conflict between Bitdefender and MB.
      My Computer


  3. Posts : 2
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Ok I disabled Malwarebytes and I'll head over to their forums to see if there is any info.

    Out of curiosity, which log file contained the info that you needed to see the problem?

    Many thanks!
      My Computer


  4. Posts : 17,796
    Windows 10, Home Clean Install
       #4

    Code:
     Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\richa\AppData\Local\Temp\Temp1_SRV1-Wed_05_25_2016_112021_39 (3).zip\052516-15740-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
    Machine Name:
    Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`0324e730
    Debug session time: Wed May 25 05:11:40.244 2016 (UTC - 4:00)
    System Uptime: 1 days 17:25:10.570
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {0, 2, 0, fffff88001c9556b}
    
    *** WARNING: Unable to verify timestamp for mwac.sys   
    *** ERROR: Module load completed but symbols could not be loaded for mwac.sys
    Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferList+86 )
    
    Followup: MachineOwner
    ---------
    
    1: 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: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88001c9556b, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b8100
    GetUlongFromAddress: unable to read from fffff800032b81c8
     0000000000000000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    tcpip! ?? ::FNODOBFM::`string'+57b4
    fffff880`01c9556b 488b01          mov     rax,qword ptr [rcx]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  mbamservice.ex
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    TRAP_FRAME:  fffff880143c5030 -- (.trap 0xfffff880143c5030)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa80176f0420 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa80176f0421 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001c9556b rsp=fffff880143c51c0 rbp=0000000000000000
     r8=fffffa80176f0420  r9=00000000000000d0 r10=fffff88003500e80
    r11=fffffa80155d8220 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01c9556b 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000307a9a9 to fffff8000307b400
    
    STACK_TEXT:  
    fffff880`143c4ee8 fffff800`0307a9a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`143c4ef0 fffff800`03079620 : fffff880`143c5360 fffff880`143c5380 00000000`00000002 fffffa80`156b82a0 : nt!KiBugCheckDispatch+0x69
    fffff880`143c5030 fffff880`01c9556b : fffffa80`156b82a0 fffff880`0c2f2002 00000000`206c644d fffffa80`2000e8c0 : nt!KiPageFault+0x260
    fffff880`143c51c0 fffff880`01b07316 : fffffa80`156b82a0 00000000`01c5baaa 00000000`00000000 fffff880`01b05d4b : tcpip! ?? ::FNODOBFM::`string'+0x57b4
    fffff880`143c5210 fffff880`01b06a72 : 00000000`00000000 fffffa80`238763e0 00000000`00000000 00000000`00000011 : NETIO!NetioDereferenceNetBufferList+0x86
    fffff880`143c5240 fffff880`01c5b232 : 00000000`00000000 fffffa80`23876500 fffff880`143c53a0 fffff880`143c5360 : NETIO!NetioDereferenceNetBufferListChain+0x332
    fffff880`143c5310 fffff880`01c58d4f : 00000000`4b4b4b4b fffff880`01d6e9a0 fffff880`01d6e9a0 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x3c3
    fffff880`143c53f0 fffff880`01d376a2 : fffffa80`15523220 00000000`00000000 fffffa80`1b23fe01 fffffa80`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`143c55f0 fffff880`01b98b16 : fffffa80`1d2d1002 fffffa80`1d2d1010 00000000`00000002 00000000`00000000 : tcpip!IppInspectInjectReceive+0xf2
    fffff880`143c5630 fffff880`0c2ef1b0 : fffffa80`1a1379f0 00000000`00000000 00000000`00000000 fffffa80`1b23fe80 : fwpkclnt!FwpsInjectTransportReceiveAsync0+0x256
    fffff880`143c56e0 fffffa80`1a1379f0 : 00000000`00000000 00000000`00000000 fffffa80`1b23fe80 fffffa80`1b230002 : mwac+0x61b0
    fffff880`143c56e8 00000000`00000000 : 00000000`00000000 fffffa80`1b23fe80 fffffa80`1b230002 fffffa80`00000001 : 0xfffffa80`1a1379f0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    NETIO!NetioDereferenceNetBufferList+86
    fffff880`01b07316 4885ff          test    rdi,rdi
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  NETIO!NetioDereferenceNetBufferList+86
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: NETIO
    
    IMAGE_NAME:  NETIO.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5294760d
    
    IMAGE_VERSION:  6.1.7601.18327
    
    FAILURE_BUCKET_ID:  X64_0xD1_NETIO!NetioDereferenceNetBufferList+86
    
    BUCKET_ID:  X64_0xD1_NETIO!NetioDereferenceNetBufferList+86
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xd1_netio!netiodereferencenetbufferlist+86
    
    FAILURE_ID_HASH:  {b03a5328-38ca-1e4a-8e26-dcd45efb9256}
    
    Followup: MachineOwner
    ---------
    This is from your file. There was one report for each BSOD. They were all consistent which is rare. I think that we nailed the problem, but lets wait and see. If the problem is solved you can set up Malwarebytes to ignore your anti virus and then do the same for your antivirus to ignore Malwarebytes. I have bolded the appropriate passage.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:31.
Find Us