locked
Connecting to a secure network causes BSOD RRS feed

  • Question

  • I'm having difficulties with one secured network in particular. I have tried connecting my computer (HP Pavilion dv6) to other secure wireless networks, and have experienced no bluescreens or other problems. Same goes for unsecured networks. However, when I connect to one specific secured network, I can browse the internet for 5-30 minutes, then my computer bluescreens abruptly. I can't really mess around with the network to see if that is causing my problems, as the network is school provided. Any suggestions to fix this?

    .dmp file = http://rapidshare.com/share/09B5F0BF3ACB588ED2F223036687EA43

    Thanks in advance!

    Wednesday, April 2, 2014 4:41 PM

Answers

  • Hi,

    Here is the dump analyze file:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88001a9453b, fffff8800ac117c0, 0}
    
    Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+57b4 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff88001a9453b, Address of the instruction which caused the bugcheck
    Arg3: fffff8800ac117c0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    tcpip! ?? ::FNODOBFM::`string'+57b4
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx]
    
    CONTEXT:  fffff8800ac117c0 -- (.cxr 0xfffff8800ac117c0;r)
    rax=0000000000000000 rbx=fffffa8005d6deb0 rcx=0000000000000000
    rdx=0000000000000001 rsi=00000000fffffa9c rdi=fffffa8009f628c0
    rip=fffff88001a9453b rsp=fffff8800ac121a0 rbp=0000000000000000
     r8=0000000000000000  r9=00000000000000d0 r10=fffff88003172e80
    r11=fffffa8009f62980 r12=fffffa8005d6deb0 r13=fffffa800bd8fba0
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffffa8005d6deb0 rcx=0000000000000000
    rdx=0000000000000001 rsi=00000000fffffa9c rdi=fffffa8009f628c0
    rip=fffff88001a9453b rsp=fffff8800ac121a0 rbp=0000000000000000
     r8=0000000000000000  r9=00000000000000d0 r10=fffff88003172e80
    r11=fffffa8009f62980 r12=fffffa8005d6deb0 r13=fffffa800bd8fba0
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  firefox.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88001a9453b
    
    STACK_TEXT:  
    fffff880`0ac121a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x57b4
    
    
    FOLLOWUP_IP: 
    tcpip! ?? ::FNODOBFM::`string'+57b4
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  tcpip! ?? ::FNODOBFM::`string'+57b4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: tcpip
    
    IMAGE_NAME:  tcpip.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  522bced8
    
    IMAGE_VERSION:  6.1.7601.18254
    
    STACK_COMMAND:  .cxr 0xfffff8800ac117c0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_tcpip!_??_::FNODOBFM::_string_+57b4
    
    BUCKET_ID:  X64_0x3B_tcpip!_??_::FNODOBFM::_string_+57b4
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_tcpip!_??_::fnodobfm::_string_+57b4
    
    FAILURE_ID_HASH:  {5f01c931-bac7-82e0-1f17-fc6af91ddc3c}
    
    Followup: MachineOwner
    ---------
    
    2: kd> .cxr 0xfffff8800ac117c0;r
    rax=0000000000000000 rbx=fffffa8005d6deb0 rcx=0000000000000000
    rdx=0000000000000001 rsi=00000000fffffa9c rdi=fffffa8009f628c0
    rip=fffff88001a9453b rsp=fffff8800ac121a0 rbp=0000000000000000
     r8=0000000000000000  r9=00000000000000d0 r10=fffff88003172e80
    r11=fffffa8009f62980 r12=fffffa8005d6deb0 r13=fffffa800bd8fba0
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffffa8005d6deb0 rcx=0000000000000000
    rdx=0000000000000001 rsi=00000000fffffa9c rdi=fffffa8009f628c0
    rip=fffff88001a9453b rsp=fffff8800ac121a0 rbp=0000000000000000
     r8=0000000000000000  r9=00000000000000d0 r10=fffff88003172e80
    r11=fffffa8009f62980 r12=fffffa8005d6deb0 r13=fffffa800bd8fba0
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    2: kd> lmvm tcpip
    start             end                 module name
    fffff880`01a00000 fffff880`01bff000   tcpip      (pdb symbols)          d:\symbols\tcpip.pdb\36C7D038792A4163AC632412CF2882992\tcpip.pdb
        Loaded symbol image file: tcpip.sys
        Mapped memory image file: d:\symbols\tcpip.sys\522BCED81ff000\tcpip.sys
        Image path: \SystemRoot\System32\drivers\tcpip.sys
        Image name: tcpip.sys
        Timestamp:        Sun Sep 08 09:11:52 2013 (522BCED8)
        CheckSum:         001E0A26
        ImageSize:        001FF000
        File version:     6.1.7601.18254
        Product version:  6.1.7601.18254
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.6 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     tcpip.sys
        OriginalFilename: tcpip.sys
        ProductVersion:   6.1.7601.18254
        FileVersion:      6.1.7601.18254 (win7sp1_gdr.130907-1536)
        FileDescription:  TCP/IP Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
     

    Most of the dump files indicated that the cause of the BSOD is the driver tcpip.sys.

    For the information regarding Bugcheck 3B, please takea look at the MSDN article below:

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    In the above article ti told this error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

    Please take a check with your graphics drivers, also make sure we have enough virtual memory(Change the size of virtual memory), in case to manage large video files.

    Best regards


    Michael Shao
    TechNet Community Support

    • Proposed as answer by ZigZag3143x Thursday, April 3, 2014 8:42 PM
    • Marked as answer by arnavsharma Monday, April 14, 2014 9:28 AM
    Thursday, April 3, 2014 7:57 AM

All replies

  • Hi,

    Here is the dump analyze file:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88001a9453b, fffff8800ac117c0, 0}
    
    Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+57b4 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff88001a9453b, Address of the instruction which caused the bugcheck
    Arg3: fffff8800ac117c0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    tcpip! ?? ::FNODOBFM::`string'+57b4
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx]
    
    CONTEXT:  fffff8800ac117c0 -- (.cxr 0xfffff8800ac117c0;r)
    rax=0000000000000000 rbx=fffffa8005d6deb0 rcx=0000000000000000
    rdx=0000000000000001 rsi=00000000fffffa9c rdi=fffffa8009f628c0
    rip=fffff88001a9453b rsp=fffff8800ac121a0 rbp=0000000000000000
     r8=0000000000000000  r9=00000000000000d0 r10=fffff88003172e80
    r11=fffffa8009f62980 r12=fffffa8005d6deb0 r13=fffffa800bd8fba0
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffffa8005d6deb0 rcx=0000000000000000
    rdx=0000000000000001 rsi=00000000fffffa9c rdi=fffffa8009f628c0
    rip=fffff88001a9453b rsp=fffff8800ac121a0 rbp=0000000000000000
     r8=0000000000000000  r9=00000000000000d0 r10=fffff88003172e80
    r11=fffffa8009f62980 r12=fffffa8005d6deb0 r13=fffffa800bd8fba0
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  firefox.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88001a9453b
    
    STACK_TEXT:  
    fffff880`0ac121a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x57b4
    
    
    FOLLOWUP_IP: 
    tcpip! ?? ::FNODOBFM::`string'+57b4
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  tcpip! ?? ::FNODOBFM::`string'+57b4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: tcpip
    
    IMAGE_NAME:  tcpip.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  522bced8
    
    IMAGE_VERSION:  6.1.7601.18254
    
    STACK_COMMAND:  .cxr 0xfffff8800ac117c0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_tcpip!_??_::FNODOBFM::_string_+57b4
    
    BUCKET_ID:  X64_0x3B_tcpip!_??_::FNODOBFM::_string_+57b4
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_tcpip!_??_::fnodobfm::_string_+57b4
    
    FAILURE_ID_HASH:  {5f01c931-bac7-82e0-1f17-fc6af91ddc3c}
    
    Followup: MachineOwner
    ---------
    
    2: kd> .cxr 0xfffff8800ac117c0;r
    rax=0000000000000000 rbx=fffffa8005d6deb0 rcx=0000000000000000
    rdx=0000000000000001 rsi=00000000fffffa9c rdi=fffffa8009f628c0
    rip=fffff88001a9453b rsp=fffff8800ac121a0 rbp=0000000000000000
     r8=0000000000000000  r9=00000000000000d0 r10=fffff88003172e80
    r11=fffffa8009f62980 r12=fffffa8005d6deb0 r13=fffffa800bd8fba0
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffffa8005d6deb0 rcx=0000000000000000
    rdx=0000000000000001 rsi=00000000fffffa9c rdi=fffffa8009f628c0
    rip=fffff88001a9453b rsp=fffff8800ac121a0 rbp=0000000000000000
     r8=0000000000000000  r9=00000000000000d0 r10=fffff88003172e80
    r11=fffffa8009f62980 r12=fffffa8005d6deb0 r13=fffffa800bd8fba0
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    tcpip! ?? ::FNODOBFM::`string'+0x57b4:
    fffff880`01a9453b 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    2: kd> lmvm tcpip
    start             end                 module name
    fffff880`01a00000 fffff880`01bff000   tcpip      (pdb symbols)          d:\symbols\tcpip.pdb\36C7D038792A4163AC632412CF2882992\tcpip.pdb
        Loaded symbol image file: tcpip.sys
        Mapped memory image file: d:\symbols\tcpip.sys\522BCED81ff000\tcpip.sys
        Image path: \SystemRoot\System32\drivers\tcpip.sys
        Image name: tcpip.sys
        Timestamp:        Sun Sep 08 09:11:52 2013 (522BCED8)
        CheckSum:         001E0A26
        ImageSize:        001FF000
        File version:     6.1.7601.18254
        Product version:  6.1.7601.18254
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.6 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     tcpip.sys
        OriginalFilename: tcpip.sys
        ProductVersion:   6.1.7601.18254
        FileVersion:      6.1.7601.18254 (win7sp1_gdr.130907-1536)
        FileDescription:  TCP/IP Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
     

    Most of the dump files indicated that the cause of the BSOD is the driver tcpip.sys.

    For the information regarding Bugcheck 3B, please takea look at the MSDN article below:

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    In the above article ti told this error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

    Please take a check with your graphics drivers, also make sure we have enough virtual memory(Change the size of virtual memory), in case to manage large video files.

    Best regards


    Michael Shao
    TechNet Community Support

    • Proposed as answer by ZigZag3143x Thursday, April 3, 2014 8:42 PM
    • Marked as answer by arnavsharma Monday, April 14, 2014 9:28 AM
    Thursday, April 3, 2014 7:57 AM
  • I checked my memory, and everything is working out fine there. How do I go about checking my graphics card drivers? Anything in particular I should be looking for? Sorry, I'm not so good with this sort of thing...
    Thursday, April 3, 2014 2:59 PM
  • M

    The most recent DMP file is from november 2013.  For us to accurately find your current issue we need current DMP files.  Are they still enabled?


    Wanikiya and Dyami--Team Zigzag

    Thursday, April 3, 2014 8:45 PM