locked
Windows 7 Blue Screen Crash RRS feed

  • Question

  • Hello, I recently have been getting a lot of blue screen crashes simultaneously. I haven't downloaded any games or anything. I just use this laptop for school work mostly. I already ran a memory diagnostic test and no problems found as well as restored my computer to a month back to when it wasn't having any problems. Anyways, this the problem details:

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.768.3
      Locale ID:    4105

    Additional information about the problem:
      BCCode:    3b
      BCP1:    00000000C0000005
      BCP2:    FFFFF88005CFC3BE
      BCP3:    FFFFF88009ACE4D0
      BCP4:    0000000000000000
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    768_1

    Files that help describe the problem:
      C:\WINDOWS\Minidump\103014-25318-01.dmp
      C:\Users\Mark\AppData\Local\Temp\WER-82087-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\windows\system32\en-US\erofflps.txt

    Hope that someone could help! Thanks!

    Thursday, October 30, 2014 5:04 PM

Answers

  • FS

    These were all Related to NETwNs64.sys Wireless WiFi Link Driver from Intel Corporation  (yours is 5 years old).  I would remove the current driver and install the newest driver available.

    If you continue to crash Remove McAfee and use MSE in its place.

    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\problem\103014-25318-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\symbols*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 Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`0360c000 PsLoadedModuleList = 0xfffff800`0384f890
    Debug session time: Thu Oct 30 12:54:00.869 2014 (UTC - 4:00)
    System Uptime: 0 days 0:01:07.181
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88005cfc3be, fffff88009ace4d0, 0}
    
    *** WARNING: Unable to verify timestamp for NETwNs64.sys
    *** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
    Probably caused by : NETwNs64.sys ( NETwNs64+2673be )
    
    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: fffff88005cfc3be, Address of the instruction which caused the bugcheck
    Arg3: fffff88009ace4d0, 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: 
    NETwNs64+2673be
    fffff880`05cfc3be 8b10            mov     edx,dword ptr [rax]
    
    CONTEXT:  fffff88009ace4d0 -- (.cxr 0xfffff88009ace4d0;r)
    rax=1004f250001ddd20 rbx=0000000000000000 rcx=0000000000060049
    rdx=000000000000002f rsi=fffffa800858f6b8 rdi=000000000000006b
    rip=fffff88005cfc3be rsp=fffff88009aceeb0 rbp=fffffa8008bf7618
     r8=0000000000000a70  r9=0000000000000000 r10=fffff8000360c000
    r11=fffff88009acecc0 r12=fffffa800a91d000 r13=0000000000000000
    r14=fffffa8008bf7fb0 r15=fffffa800af1c008
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    NETwNs64+0x2673be:
    fffff880`05cfc3be 8b10            mov     edx,dword ptr [rax] ds:002b:1004f250`001ddd20=????????
    Last set context:
    rax=1004f250001ddd20 rbx=0000000000000000 rcx=0000000000060049
    rdx=000000000000002f rsi=fffffa800858f6b8 rdi=000000000000006b
    rip=fffff88005cfc3be rsp=fffff88009aceeb0 rbp=fffffa8008bf7618
     r8=0000000000000a70  r9=0000000000000000 r10=fffff8000360c000
    r11=fffff88009acecc0 r12=fffffa800a91d000 r13=0000000000000000
    r14=fffffa8008bf7fb0 r15=fffffa800af1c008
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    NETwNs64+0x2673be:
    fffff880`05cfc3be 8b10            mov     edx,dword ptr [rax] ds:002b:1004f250`001ddd20=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  wlanext.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88005cfc3be
    
    STACK_TEXT:  
    fffff880`09aceeb0 00000000`00000000 : fffffa80`08bf7618 fffffa80`00000002 00000000`000000dc fffffa80`00001e37 : NETwNs64+0x2673be
    
    
    FOLLOWUP_IP: 
    NETwNs64+2673be
    fffff880`05cfc3be 8b10            mov     edx,dword ptr [rax]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  NETwNs64+2673be
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: NETwNs64
    
    IMAGE_NAME:  NETwNs64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d10df1b
    
    STACK_COMMAND:  .cxr 0xfffff88009ace4d0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_NETwNs64+2673be
    
    BUCKET_ID:  X64_0x3B_NETwNs64+2673be
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_netwns64+2673be
    
    FAILURE_ID_HASH:  {69744f93-8380-f8c7-a080-fedb60128a80}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Flipstep Monday, November 3, 2014 1:58 AM
    Saturday, November 1, 2014 2:17 AM

All replies

  •  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask

    If you are using Blue screen view, who crashed, or a similar application, don't.  They are wrong at least as often as they are correct

    Wanikiya and Dyami--Team Zigzag

    Thursday, October 30, 2014 5:05 PM
  • I have compressed the DMP files. The link for the files is down below. Thanks for the help Zigzag!

    https://onedrive.live.com/redir?resid=44175BDDB243022D%21132

    Friday, October 31, 2014 6:34 AM
  • FS

    These were all Related to NETwNs64.sys Wireless WiFi Link Driver from Intel Corporation  (yours is 5 years old).  I would remove the current driver and install the newest driver available.

    If you continue to crash Remove McAfee and use MSE in its place.

    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\problem\103014-25318-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\symbols*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 Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`0360c000 PsLoadedModuleList = 0xfffff800`0384f890
    Debug session time: Thu Oct 30 12:54:00.869 2014 (UTC - 4:00)
    System Uptime: 0 days 0:01:07.181
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88005cfc3be, fffff88009ace4d0, 0}
    
    *** WARNING: Unable to verify timestamp for NETwNs64.sys
    *** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
    Probably caused by : NETwNs64.sys ( NETwNs64+2673be )
    
    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: fffff88005cfc3be, Address of the instruction which caused the bugcheck
    Arg3: fffff88009ace4d0, 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: 
    NETwNs64+2673be
    fffff880`05cfc3be 8b10            mov     edx,dword ptr [rax]
    
    CONTEXT:  fffff88009ace4d0 -- (.cxr 0xfffff88009ace4d0;r)
    rax=1004f250001ddd20 rbx=0000000000000000 rcx=0000000000060049
    rdx=000000000000002f rsi=fffffa800858f6b8 rdi=000000000000006b
    rip=fffff88005cfc3be rsp=fffff88009aceeb0 rbp=fffffa8008bf7618
     r8=0000000000000a70  r9=0000000000000000 r10=fffff8000360c000
    r11=fffff88009acecc0 r12=fffffa800a91d000 r13=0000000000000000
    r14=fffffa8008bf7fb0 r15=fffffa800af1c008
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    NETwNs64+0x2673be:
    fffff880`05cfc3be 8b10            mov     edx,dword ptr [rax] ds:002b:1004f250`001ddd20=????????
    Last set context:
    rax=1004f250001ddd20 rbx=0000000000000000 rcx=0000000000060049
    rdx=000000000000002f rsi=fffffa800858f6b8 rdi=000000000000006b
    rip=fffff88005cfc3be rsp=fffff88009aceeb0 rbp=fffffa8008bf7618
     r8=0000000000000a70  r9=0000000000000000 r10=fffff8000360c000
    r11=fffff88009acecc0 r12=fffffa800a91d000 r13=0000000000000000
    r14=fffffa8008bf7fb0 r15=fffffa800af1c008
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    NETwNs64+0x2673be:
    fffff880`05cfc3be 8b10            mov     edx,dword ptr [rax] ds:002b:1004f250`001ddd20=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  wlanext.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88005cfc3be
    
    STACK_TEXT:  
    fffff880`09aceeb0 00000000`00000000 : fffffa80`08bf7618 fffffa80`00000002 00000000`000000dc fffffa80`00001e37 : NETwNs64+0x2673be
    
    
    FOLLOWUP_IP: 
    NETwNs64+2673be
    fffff880`05cfc3be 8b10            mov     edx,dword ptr [rax]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  NETwNs64+2673be
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: NETwNs64
    
    IMAGE_NAME:  NETwNs64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d10df1b
    
    STACK_COMMAND:  .cxr 0xfffff88009ace4d0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_NETwNs64+2673be
    
    BUCKET_ID:  X64_0x3B_NETwNs64+2673be
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_netwns64+2673be
    
    FAILURE_ID_HASH:  {69744f93-8380-f8c7-a080-fedb60128a80}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Flipstep Monday, November 3, 2014 1:58 AM
    Saturday, November 1, 2014 2:17 AM
  • Thank you for the help ZigZag! I really appreciate it!
    Monday, November 3, 2014 1:58 AM
  • FS

    Happy to help and let us know if the problem re-appears


    Wanikiya and Dyami--Team Zigzag

    Monday, November 3, 2014 2:03 AM