BSOD error 0x3b most frequently. Randomly occurring while browsing net


  1. Posts : 3
    Windows 7 Professional x64
       #1

    BSOD error 0x3b most frequently. Randomly occurring while browsing net


    Hi there,

    Lately, i've been receiving a lot of these blue screen errors, especially when browsing the internet (ie YouTube etc.), but not during playing games. Could someone please help me out here? it's driving me crazy.

    I've attached multiple dump files, looking at the dump files it seems like ntoskml.exe is being problematic? There is also the occasional nVidia driver issue. I really don't know what to do though.

    I have attached the minidump files relevant in the zip.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Yes, it is some issues with the networking.

    Symantec Heuristics Driver is failing continuously. It causes issues with network.
    Code:
    fffff880`0a8cb958  fffff880`07b2c743Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_20.2.0.19\Definitions\BASHDefs\20131101.003\BHDrvx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BHDrvx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
     BHDrvx64+0x10e743
    Description here: Driver Reference Table - BHDrvx64.sys

    Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    Also, Realtek PCIe GBE Family Controller is failing, too.
    Code:
    fffff880`0e905a88  fffff880`07e23edbUnable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     Rt64win7+0x7edb
    Update it from Realtek ... Win7 and WinServer 2008 R2 Auto Installation Program dated 2013/9/24.

    Let us know the results.
      My Computer


  3. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #3

    Thanks for you reply Arc, have done want you suggested and will test the stability of the system today :) Thanks again!
      My Computer


  4. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #4

    Hi again, i got another blue screen, this time it was a 0x1e error.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff8800c3777a0, 0, 0}
    
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    Probably caused by : Rt64win7.sys ( Rt64win7+1b7da )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800c3777a0, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b9100
    GetUlongFromAddress: unable to read from fffff800032b91c0
     ffffffffffffffff 
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    +0
    fffff880`0c3777a0 c886370c        enter   3786h,0Ch
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff88001a05fe9 to fffff88001ac3eb7
    
    CONTEXT:  fffff8800c377f20 -- (.cxr 0xfffff8800c377f20)
    rax=0004000000000000 rbx=fffff88001b68128 rcx=fffffa800d095000
    rdx=fffffa800d095000 rsi=0000000000000014 rdi=fffffa800d095000
    rip=fffff88001ac3eb7 rsp=fffff8800c378908 rbp=fffff8800c378af0
     r8=0000000000000000  r9=0000000000000001 r10=0000000000000000
    r11=fffff8800c378a00 r12=fffffa800f571670 r13=fffff8800c378a00
    r14=0000000000000000 r15=fffff88001b68128
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    tcpip! ?? ::FNODOBFM::`string'+0x3f877:
    fffff880`01ac3eb7 48ffe0          jmp     rax {00040000`00000000}
    Resetting default scope
    
    STACK_TEXT:  
    fffff880`0c378908 fffff880`01a05fe9 : fffff880`01b68128 00000000`00000014 00000000`00000014 fffffa80`0f571670 : tcpip! ?? ::FNODOBFM::`string'+0x3f877
    fffff880`0c378910 fffff880`01a06254 : fffff880`01b6e9a0 fffffa80`0fd30080 fffffa80`0d095000 00000000`00000000 : tcpip!Icmpv4pHandleError+0x1d9
    fffff880`0c378a80 fffff880`01a5bf7e : fffffa80`0cf4ea00 00000000`00000000 fffff880`01b6e9a0 fffff880`0c378cf0 : tcpip!Icmpv4ReceiveDatagrams+0x164
    fffff880`0c378b30 fffff880`01a5ba8a : 00000000`00000000 fffff880`01b6e9a0 fffff880`0c378cf0 fffffa80`0f5665e0 : tcpip!IppDeliverListToProtocol+0xfe
    fffff880`0c378bf0 fffff880`01a5b089 : fffff880`01b6e9a0 fffffa80`0f55af00 fffff880`0c378ca0 fffff880`0c378ce0 : tcpip!IppProcessDeliverList+0x5a
    fffff880`0c378c90 fffff880`01a58d2f : fffffa80`040a5c76 fffff880`01b6e9a0 fffff880`01b6e9a0 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`0c378d70 fffff880`01a58302 : fffffa80`0ca09380 00000000`00000000 fffffa80`0f6f2401 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`0c378f70 fffff880`01a5772a : fffffa80`0f6f2400 fffff880`0c3790a0 fffffa80`0f6f2400 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`0c379050 fffff800`0308d878 : fffffa80`0f571670 00000000`00004800 fffffa80`10ea0060 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`0c3790a0 fffff880`01a57e22 : fffff880`01a57650 00000000`00000018 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0c379180 fffff880`018f80eb : fffffa80`0f6f4010 00000000`00000000 fffffa80`0f1681a0 00000000`00000286 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`0c3791f0 fffff880`018c1ad6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`0c379260 fffff880`0183bac1 : fffffa80`0f1681a0 00000000`00000002 00000000`00000001 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    fffff880`0c3796e0 fffff880`078877da : fffffa80`0f34b000 00000000`00000000 00000000`00000000 fffffa80`0f571670 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
    fffff880`0c379730 fffffa80`0f34b000 : 00000000`00000000 00000000`00000000 fffffa80`0f571670 fffff800`00000001 : Rt64win7+0x1b7da
    fffff880`0c379738 00000000`00000000 : 00000000`00000000 fffffa80`0f571670 fffff800`00000001 00001f80`00040201 : 0xfffffa80`0f34b000
    
    
    FOLLOWUP_IP: 
    Rt64win7+1b7da
    fffff880`078877da ??              ???
    
    SYMBOL_STACK_INDEX:  e
    
    SYMBOL_NAME:  Rt64win7+1b7da
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Rt64win7
    
    IMAGE_NAME:  Rt64win7.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  521c41ce
    
    STACK_COMMAND:  .cxr 0xfffff8800c377f20 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_Rt64win7+1b7da
    
    BUCKET_ID:  X64_0x1E_c0000005_R_Rt64win7+1b7da
    
    Followup: MachineOwner
    ---------
    
    4: kd> lmvm Rt64win7
    start             end                 module name
    fffff880`0786c000 fffff880`07946000   Rt64win7 T (no symbols)           
        Loaded symbol image file: Rt64win7.sys
        Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Tue Aug 27 11:36:06 2013 (521C41CE)
        CheckSum:         000D9BD8
        ImageSize:        000DA000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Something is there that is still making the network fail. If the BSOD occurs again, post it following the Blue Screen of Death (BSOD) Posting Instructions.
      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 19:09.
Find Us