Page 1 of 2 12 Last
  1. #1

    BSOD - Wifi? - Windows 7 x64

    Hi, Merry Christmas to everyone!

    I have a problem that bother me for quite some time and need your help. Hopefully this problem can be solved.

    Wifi of my laptop will suddenly unable to online, by using the "troubleshoot problems" will cause blur screen in the end when i wanted to restart/shut down laptop. Therefore sometimes i just restart my laptop (and the wifi can be connected again). These few days, even though i have restart many times still the wifi unable to be connected again. I suspect is the wireless adapter or driver problem,but unable to figure out more details.
    jcgriff2 had suggested me to open post and post the related info regarding my computer problems here. Wish to receive reply and solution for my problem. THANKS!!

    ∑ OS - Windows 7 64-bit
    ∑ Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? It is OEM version.
    ∑ Age of system (hardware) - 2009 until now
    ∑ Age of OS installation - have you re-installed the OS? No.

    ∑ Exact model number - aspire 4736G


    Attachment 18177
    Report.rar
    System.html
    Windbg Analysis.txt


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Jared's Avatar
    Join Date
    Feb 2014
    Age
    20
    Posts
    1,568
    • specs System Specs
      • Manufacturer:
        Custom
      • Motherboard:
        ASUS Maximus VII Ranger
      • CPU:
        i7 4790K @ 4.4GHz
      • Memory:
        Corsair Vengeance 16GB 1866MHz
      • Graphics:
        MSI Gaming 4G GTX 980
      • Sound Card:
        Creative Soundblaster ZxR
      • Hard Drives:
        Samsung 850 SSD 250GB
      • Disk Drives:
        Western Digital Black Caviar 2TB
      • Power Supply:
        Corsair RM650 Modular 650 Watts
      • Case:
        Fractal Design Define R5 Window
      • Cooling:
        Corsair H100i GTX
      • Display:
        Dell U2515H 25inch 2560x1440 + LG Flatron M2262D 22inch 1920x1080
      • Operating System:
        Windows 10 Professional x64

    re: BSOD - Wifi? - Windows 7 x64

    We'll need a Kernel dump from C:\Windows\MEMORY.dmp to investigate more.
    Upload it to a 3rd party file sharing site, as it is too large to upload here.

  3. #3

    re: BSOD - Wifi? - Windows 7 x64

    Quote Originally Posted by Jared View Post
    We'll need a Kernel dump from C:\Windows\MEMORY.dmp to investigate more.
    Upload it to a 3rd party file sharing site, as it is too large to upload here.
    Thanks for the reply. Is this the file? i have save it in small memory dump.

    Minidump.rar

  4. #4
    Jared's Avatar
    Join Date
    Feb 2014
    Age
    20
    Posts
    1,568
    • specs System Specs
      • Manufacturer:
        Custom
      • Motherboard:
        ASUS Maximus VII Ranger
      • CPU:
        i7 4790K @ 4.4GHz
      • Memory:
        Corsair Vengeance 16GB 1866MHz
      • Graphics:
        MSI Gaming 4G GTX 980
      • Sound Card:
        Creative Soundblaster ZxR
      • Hard Drives:
        Samsung 850 SSD 250GB
      • Disk Drives:
        Western Digital Black Caviar 2TB
      • Power Supply:
        Corsair RM650 Modular 650 Watts
      • Case:
        Fractal Design Define R5 Window
      • Cooling:
        Corsair H100i GTX
      • Display:
        Dell U2515H 25inch 2560x1440 + LG Flatron M2262D 22inch 1920x1080
      • Operating System:
        Windows 10 Professional x64

    re: BSOD - Wifi? - Windows 7 x64

    No, it has to be from the directory I said above.
    It's a few hundred mb in size.

  5. #5

    re: BSOD - Wifi? - Windows 7 x64

    Quote Originally Posted by Jared View Post
    No, it has to be from the directory I said above.
    It's a few hundred mb in size.
    Jared, i counldn't find the file due to the setting.
    BSOD - Wifi? - Windows 7 x64-memory-dump-png

  6. #6
    Jared's Avatar
    Join Date
    Feb 2014
    Age
    20
    Posts
    1,568
    • specs System Specs
      • Manufacturer:
        Custom
      • Motherboard:
        ASUS Maximus VII Ranger
      • CPU:
        i7 4790K @ 4.4GHz
      • Memory:
        Corsair Vengeance 16GB 1866MHz
      • Graphics:
        MSI Gaming 4G GTX 980
      • Sound Card:
        Creative Soundblaster ZxR
      • Hard Drives:
        Samsung 850 SSD 250GB
      • Disk Drives:
        Western Digital Black Caviar 2TB
      • Power Supply:
        Corsair RM650 Modular 650 Watts
      • Case:
        Fractal Design Define R5 Window
      • Cooling:
        Corsair H100i GTX
      • Display:
        Dell U2515H 25inch 2560x1440 + LG Flatron M2262D 22inch 1920x1080
      • Operating System:
        Windows 10 Professional x64

    re: BSOD - Wifi? - Windows 7 x64

    Okay, change the file size to Kernel memory dump, then restart and wait for the next crash.

  7. #7

    re: BSOD - Wifi? - Windows 7 x64

    Quote Originally Posted by Jared View Post
    Okay, change the file size to Kernel memory dump, then restart and wait for the next crash.
    Hi, Jared, here's the link.

    https://drive.google.com/file/d/0B8e...ew?usp=sharing

  8. #8

    Join Date
    Dec 2014
    Location
    Germany
    Posts
    179

    Unhappy re: BSOD - Wifi? - Windows 7 x64

    Quote Originally Posted by yen View Post
    Quote Originally Posted by Jared View Post
    Okay, change the file size to Kernel memory dump, then restart and wait for the next crash.
    Hi, Jared, here's the link.

    https://drive.google.com/file/d/0B8e...ew?usp=sharing

    Unfortunately, the permission don't allow to download, can you reshare or correct it?

    regards
    Michael

  9. #9
    Jared's Avatar
    Join Date
    Feb 2014
    Age
    20
    Posts
    1,568
    • specs System Specs
      • Manufacturer:
        Custom
      • Motherboard:
        ASUS Maximus VII Ranger
      • CPU:
        i7 4790K @ 4.4GHz
      • Memory:
        Corsair Vengeance 16GB 1866MHz
      • Graphics:
        MSI Gaming 4G GTX 980
      • Sound Card:
        Creative Soundblaster ZxR
      • Hard Drives:
        Samsung 850 SSD 250GB
      • Disk Drives:
        Western Digital Black Caviar 2TB
      • Power Supply:
        Corsair RM650 Modular 650 Watts
      • Case:
        Fractal Design Define R5 Window
      • Cooling:
        Corsair H100i GTX
      • Display:
        Dell U2515H 25inch 2560x1440 + LG Flatron M2262D 22inch 1920x1080
      • Operating System:
        Windows 10 Professional x64

    re: BSOD - Wifi? - Windows 7 x64

    My apologies I didn't reply sooner.
    I didn't get an email notifying me that you replied to the thread. For some reason Outlook likes to throw all Sysnative emails into the spam folder, not matter how many exceptions or rules I create to tell it otherwise.

  10. #10

    re: BSOD - Wifi? - Windows 7 x64

    Quote Originally Posted by MichaelB View Post

    Unfortunately, the permission don't allow to download, can you reshare or correct it?

    regards
    Michael



    Thanks, Micheal. I've changed the permission,please have a look.
    MichaelB says thanks for this.

  11. #11

    re: BSOD - Wifi? - Windows 7 x64

    Quote Originally Posted by Jared View Post
    My apologies I didn't reply sooner.
    I didn't get an email notifying me that you replied to the thread. For some reason Outlook likes to throw all Sysnative emails into the spam folder, not matter how many exceptions or rules I create to tell it otherwise.
    Is ok, thanks for your reply. May be you might want to change mailbox or check the spam folder?

    I've changed the permission, please have a look.

  12. #12

    re: BSOD - Wifi? - Windows 7 x64


  13. #13
    Jared's Avatar
    Join Date
    Feb 2014
    Age
    20
    Posts
    1,568
    • specs System Specs
      • Manufacturer:
        Custom
      • Motherboard:
        ASUS Maximus VII Ranger
      • CPU:
        i7 4790K @ 4.4GHz
      • Memory:
        Corsair Vengeance 16GB 1866MHz
      • Graphics:
        MSI Gaming 4G GTX 980
      • Sound Card:
        Creative Soundblaster ZxR
      • Hard Drives:
        Samsung 850 SSD 250GB
      • Disk Drives:
        Western Digital Black Caviar 2TB
      • Power Supply:
        Corsair RM650 Modular 650 Watts
      • Case:
        Fractal Design Define R5 Window
      • Cooling:
        Corsair H100i GTX
      • Display:
        Dell U2515H 25inch 2560x1440 + LG Flatron M2262D 22inch 1920x1080
      • Operating System:
        Windows 10 Professional x64

    re: BSOD - Wifi? - Windows 7 x64

    Code:
    //Thread that initiated the crash
    fffff800`04940498 fffff800`03163ea6 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`03cf6040 : nt!KeBugCheckEx
    fffff800`049404a0 fffff800`033163cc : 00000000`00000000 fffff800`00000000 00000000`00000000 fffff800`030e405a : nt!PnpBugcheckPowerTimeout+0x76
    fffff800`04940500 fffff800`030e7062 : fffff800`049405f0 00000000`00000000 00000000`402f1288 00000000`00000003 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
    fffff800`04940530 fffff800`030e6f06 : fffff880`0407a6d0 00000000`00011d2e 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`049405a0 fffff800`030e6dee : 00000002`a6d6f60f fffff800`04940c18 00000000`00011d2e fffff800`03250848 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`04940bf0 fffff800`030e6bd7 : 00000000`918e3fc2 00000000`00011d2e 00000000`918e3f1f 00000000`0000002e : nt!KiTimerExpiration+0x1be
    fffff800`04940c90 fffff800`030d336a : fffff800`0324de80 fffff800`0325bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`04940d40 00000000`00000000 : fffff800`04941000 fffff800`0493b000 fffff800`04940d00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    //The lock that is being waited on
    
    Resource @ nt!PiEngineLock (0xfffff800032d7440)    Exclusively owned
        Contention Count = 10
        NumberOfExclusiveWaiters = 2
         Threads: fffffa8003cf6040-01<*> 
         Threads Waiting On Exclusive Access:
                  fffffa8003d021a0       fffffa8007ed3b60
    
    //Here's the thread that held up the IRP
    
    0: kd> !thread fffffa8003cf6040
    THREAD fffffa8003cf6040  Cid 0004.0030  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
        fffff880035d9078  SynchronizationEvent
    IRP List:
        fffffa80040a97a0: (0006,01f0) Flags: 00000000  Mdl: 00000000
    Not impersonating
    DeviceMap                 fffff8a000008bc0
    Owning Process            fffffa8003c70990       Image:         System
    Attached Process          N/A            Image:         N/A
    Wait Start TickCount      34544          Ticks: 38462 (0:00:10:00.011)
    Context Switch Count      2596           IdealProcessor: 0  NoStackSwap
    UserTime                  00:00:00.000
    KernelTime                00:00:00.265
    Win32 Start Address nt!ExpWorkerThread (0xfffff800030e5910)
    Stack Init fffff880035d9d70 Current fffff880035d8d90
    Base fffff880035da000 Limit fffff880035d4000 Call 0
    Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`035d8dd0 fffff800`030e0992 : fffffa80`03cf6040 fffffa80`03cf6040 00000000`00000000 00000000`0000000f : nt!KiSwapContext+0x7a
    fffff880`035d8f10 fffff800`030e31af : fffffa80`0876e290 fffffa80`0876e290 fffffa80`00000000 fffff800`0324de80 : nt!KiCommitThreadWait+0x1d2
    fffff880`035d8fa0 fffff800`03137266 : 00000000`00000000 fffffa80`00000000 fffff880`01e6f900 fffff880`01b13200 : nt!KeWaitForSingleObject+0x19f //Here we sit in the loop, until the allotted time expires, then a context switch is perform to initiate the bugcheck
    fffff880`035d9040 fffff880`01d1657d : 00000000`00000100 0000000c`00000003 00000000`00000000 fffffa80`40010023 : nt! ?? ::FNODOBFM::`string'+0x13886
    fffff880`035d90b0 fffff880`01e40a7e : 00000000`c00000bb 00000000`00000008 fffff880`035d9230 fffff880`035d9230 : tcpip!FlPnpEvent+0x17d
    fffff880`035d9120 fffff880`01b28b2f : 00000000`c00000bb 00000000`00000008 00000000`c00000bb fffffa80`06dad1a0 : tcpip!Fl48PnpEvent+0xe
    fffff880`035d9150 fffff880`01b294b7 : fffffa80`0876a580 00000000`00000008 00000000`00000000 fffffa80`0876a580 : ndis!ndisPnPNotifyBinding+0xbf
    fffff880`035d91e0 fffff880`01b438e1 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`08395f20 : ndis!ndisPnPNotifyAllTransports+0x377
    fffff880`035d9350 fffff880`01b44c2b : 00000000`00000001 fffffa80`06dad1a0 fffffa80`06eda940 fffffa80`06dad050 : ndis!ndisCloseMiniportBindings+0x111
    fffff880`035d9460 fffff880`01adbe6a : fffffa80`06dad1a0 fffffa80`06dad1a0 fffffa80`040a97a0 fffff880`01a89300 : ndis!ndisPnPRemoveDevice+0x25b
    fffff880`035d9600 fffff880`01b385b2 : 00000000`00000000 fffffa80`06dad1a0 fffffa80`040a97a0 00000000`00000002 : ndis!ndisPnPRemoveDeviceEx+0xca
    fffff880`035d9660 fffff880`00e7093c : 00000000`00000001 fffffa80`040a98b8 fffffa80`06d06020 00000000`00000000 : ndis! ?? ::LNCPHCLB::`string'+0x7363
    fffff880`035d9700 fffff880`00e692ce : 00000000`00000001 fffff880`035d9810 fffff880`035d9800 fffffa80`06d06000 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
    fffff880`035d9730 fffff880`00e67dd6 : fffffa80`06ef0902 00000000`c00000bb 00000000`00000000 fffffa80`06d06020 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
    fffff880`035d97a0 fffff880`00e37245 : fffffa80`040a97a0 fffffa80`040a97a0 fffffa80`06cc1e20 fffffa80`06cc1e20 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
    fffff880`035d9810 fffff880`00e3714b : 00000000`00000003 fffffa80`040a97a0 00000000`c00000bb fffffa80`06cc1e20 : Wdf01000!FxDevice::Dispatch+0xa9
    fffff880`035d9840 fffff800`03347f29 : fffffa80`06cc1e20 00000000`c00000bb fffff880`035d9938 fffffa80`040a97a0 : Wdf01000!FxDevice::DispatchWithLock+0x93
    fffff880`035d9880 fffff800`034c2381 : fffffa80`046aa060 00000000`00000000 fffffa80`046a86e0 00000000`00000801 : nt!IopSynchronousCall+0xc5
    fffff880`035d98f0 fffff800`031d43e3 : fffff8a0`0e7063e0 fffff8a0`0e7063e0 00000000`00000016 00000000`00000000 : nt!IopRemoveDevice+0x101
    fffff880`035d99b0 fffff800`034c1ed4 : fffffa80`046a86e0 00000000`00000000 00000000`00000002 fffffa80`046aa060 : nt!PnpRemoveLockedDeviceNode+0x1a3
    fffff880`035d9a00 fffff800`034c1fe0 : 00000000`00000000 fffff8a0`0e6e5801 fffff8a0`0e685980 ffffe5db`9f6fd4fa : nt!PnpDeleteLockedDeviceNode+0x44
    fffff880`035d9a30 fffff800`03552e54 : 00000000`00000002 00000000`00000000 fffffa80`046a86e0 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
    fffff880`035d9aa0 fffff800`035534ac : fffff880`00000000 fffffa80`06f1f700 fffffa80`03cf6000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
    fffff880`035d9be0 fffff800`0343c6ac : 00000000`00000000 fffffa80`06f1f790 fffff8a0`0a33d640 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
    fffff880`035d9c10 fffff800`030e5a21 : fffff800`03346db8 fffff8a0`0e6e5830 fffff800`03278658 fffffa80`03cf6040 : nt! ?? ::NNGAKEGL::`string'+0x5cd3b
    fffff880`035d9c70 fffff800`03378cce : 0000059a`00000000 fffffa80`03cf6040 00000000`00000080 fffffa80`03c70990 : nt!ExpWorkerThread+0x111
    fffff880`035d9d00 fffff800`030ccfe6 : fffff880`009e8180 fffffa80`03cf6040 fffff880`009f2f40 0000059a`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`035d9d40 00000000`00000000 : fffff880`035da000 fffff880`035d4000 fffff880`035d9020 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    //The IRP that was held up
    
    0: kd> !irp fffffa80040a97a0
    Irp is active with 3 stacks 2 is current (= 0xfffffa80040a98b8)
     No Mdl: No System Buffer: Thread fffffa8003cf6040:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[IRP_MJ_PNP(1b), IRP_MN_REMOVE_DEVICE - (2)]
                0  0 fffffa8006dad050 00000000 00000000-00000000    
    	      *** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
     \Driver\NETwNs64
    			Args: 00000000 00000000 00000000 00000000
     [IRP_MJ_PNP(1b), IRP_MN_REMOVE_DEVICE - (2)]
                0  0 fffffa8006cc1e20 00000000 00000000-00000000    
    	       \Driver\vwifibus
    			Args: 00000000 00000000 00000000 00000000
    
    0: kd> lmvm NETwNs64
    Browse full module list
    start             end                 module name
    fffff880`04e18000 fffff880`056a0000   NETwNs64   (no symbols)           
        Loaded symbol image file: NETwNs64.sys
        Image path: \SystemRoot\system32\DRIVERS\NETwNs64.sys
        Image name: NETwNs64.sys
        Browse all global symbols  functions  data
        Timestamp:        Mon Jan 23 22:44:07 2012 (4F1DE2B7)
        CheckSum:         00845FA9
        ImageSize:        00888000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    It appears the lock was placed in an infinite loop, so the IRP was never processed, when the next thread tried to take control, because it never did.
    Your wireless adapter driver is out of date, you should update it.

  14. #14

    re: BSOD - Wifi? - Windows 7 x64

    Quote Originally Posted by Jared View Post
    Code:
    //Thread that initiated the crash
    fffff800`04940498 fffff800`03163ea6 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`03cf6040 : nt!KeBugCheckEx
    fffff800`049404a0 fffff800`033163cc : 00000000`00000000 fffff800`00000000 00000000`00000000 fffff800`030e405a : nt!PnpBugcheckPowerTimeout+0x76
    fffff800`04940500 fffff800`030e7062 : fffff800`049405f0 00000000`00000000 00000000`402f1288 00000000`00000003 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
    fffff800`04940530 fffff800`030e6f06 : fffff880`0407a6d0 00000000`00011d2e 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`049405a0 fffff800`030e6dee : 00000002`a6d6f60f fffff800`04940c18 00000000`00011d2e fffff800`03250848 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`04940bf0 fffff800`030e6bd7 : 00000000`918e3fc2 00000000`00011d2e 00000000`918e3f1f 00000000`0000002e : nt!KiTimerExpiration+0x1be
    fffff800`04940c90 fffff800`030d336a : fffff800`0324de80 fffff800`0325bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`04940d40 00000000`00000000 : fffff800`04941000 fffff800`0493b000 fffff800`04940d00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    //The lock that is being waited on
    
    Resource @ nt!PiEngineLock (0xfffff800032d7440)    Exclusively owned
        Contention Count = 10
        NumberOfExclusiveWaiters = 2
         Threads: fffffa8003cf6040-01<*> 
         Threads Waiting On Exclusive Access:
                  fffffa8003d021a0       fffffa8007ed3b60
    
    //Here's the thread that held up the IRP
    
    0: kd> !thread fffffa8003cf6040
    THREAD fffffa8003cf6040  Cid 0004.0030  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
        fffff880035d9078  SynchronizationEvent
    IRP List:
        fffffa80040a97a0: (0006,01f0) Flags: 00000000  Mdl: 00000000
    Not impersonating
    DeviceMap                 fffff8a000008bc0
    Owning Process            fffffa8003c70990       Image:         System
    Attached Process          N/A            Image:         N/A
    Wait Start TickCount      34544          Ticks: 38462 (0:00:10:00.011)
    Context Switch Count      2596           IdealProcessor: 0  NoStackSwap
    UserTime                  00:00:00.000
    KernelTime                00:00:00.265
    Win32 Start Address nt!ExpWorkerThread (0xfffff800030e5910)
    Stack Init fffff880035d9d70 Current fffff880035d8d90
    Base fffff880035da000 Limit fffff880035d4000 Call 0
    Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`035d8dd0 fffff800`030e0992 : fffffa80`03cf6040 fffffa80`03cf6040 00000000`00000000 00000000`0000000f : nt!KiSwapContext+0x7a
    fffff880`035d8f10 fffff800`030e31af : fffffa80`0876e290 fffffa80`0876e290 fffffa80`00000000 fffff800`0324de80 : nt!KiCommitThreadWait+0x1d2
    fffff880`035d8fa0 fffff800`03137266 : 00000000`00000000 fffffa80`00000000 fffff880`01e6f900 fffff880`01b13200 : nt!KeWaitForSingleObject+0x19f //Here we sit in the loop, until the allotted time expires, then a context switch is perform to initiate the bugcheck
    fffff880`035d9040 fffff880`01d1657d : 00000000`00000100 0000000c`00000003 00000000`00000000 fffffa80`40010023 : nt! ?? ::FNODOBFM::`string'+0x13886
    fffff880`035d90b0 fffff880`01e40a7e : 00000000`c00000bb 00000000`00000008 fffff880`035d9230 fffff880`035d9230 : tcpip!FlPnpEvent+0x17d
    fffff880`035d9120 fffff880`01b28b2f : 00000000`c00000bb 00000000`00000008 00000000`c00000bb fffffa80`06dad1a0 : tcpip!Fl48PnpEvent+0xe
    fffff880`035d9150 fffff880`01b294b7 : fffffa80`0876a580 00000000`00000008 00000000`00000000 fffffa80`0876a580 : ndis!ndisPnPNotifyBinding+0xbf
    fffff880`035d91e0 fffff880`01b438e1 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`08395f20 : ndis!ndisPnPNotifyAllTransports+0x377
    fffff880`035d9350 fffff880`01b44c2b : 00000000`00000001 fffffa80`06dad1a0 fffffa80`06eda940 fffffa80`06dad050 : ndis!ndisCloseMiniportBindings+0x111
    fffff880`035d9460 fffff880`01adbe6a : fffffa80`06dad1a0 fffffa80`06dad1a0 fffffa80`040a97a0 fffff880`01a89300 : ndis!ndisPnPRemoveDevice+0x25b
    fffff880`035d9600 fffff880`01b385b2 : 00000000`00000000 fffffa80`06dad1a0 fffffa80`040a97a0 00000000`00000002 : ndis!ndisPnPRemoveDeviceEx+0xca
    fffff880`035d9660 fffff880`00e7093c : 00000000`00000001 fffffa80`040a98b8 fffffa80`06d06020 00000000`00000000 : ndis! ?? ::LNCPHCLB::`string'+0x7363
    fffff880`035d9700 fffff880`00e692ce : 00000000`00000001 fffff880`035d9810 fffff880`035d9800 fffffa80`06d06000 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
    fffff880`035d9730 fffff880`00e67dd6 : fffffa80`06ef0902 00000000`c00000bb 00000000`00000000 fffffa80`06d06020 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
    fffff880`035d97a0 fffff880`00e37245 : fffffa80`040a97a0 fffffa80`040a97a0 fffffa80`06cc1e20 fffffa80`06cc1e20 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
    fffff880`035d9810 fffff880`00e3714b : 00000000`00000003 fffffa80`040a97a0 00000000`c00000bb fffffa80`06cc1e20 : Wdf01000!FxDevice::Dispatch+0xa9
    fffff880`035d9840 fffff800`03347f29 : fffffa80`06cc1e20 00000000`c00000bb fffff880`035d9938 fffffa80`040a97a0 : Wdf01000!FxDevice::DispatchWithLock+0x93
    fffff880`035d9880 fffff800`034c2381 : fffffa80`046aa060 00000000`00000000 fffffa80`046a86e0 00000000`00000801 : nt!IopSynchronousCall+0xc5
    fffff880`035d98f0 fffff800`031d43e3 : fffff8a0`0e7063e0 fffff8a0`0e7063e0 00000000`00000016 00000000`00000000 : nt!IopRemoveDevice+0x101
    fffff880`035d99b0 fffff800`034c1ed4 : fffffa80`046a86e0 00000000`00000000 00000000`00000002 fffffa80`046aa060 : nt!PnpRemoveLockedDeviceNode+0x1a3
    fffff880`035d9a00 fffff800`034c1fe0 : 00000000`00000000 fffff8a0`0e6e5801 fffff8a0`0e685980 ffffe5db`9f6fd4fa : nt!PnpDeleteLockedDeviceNode+0x44
    fffff880`035d9a30 fffff800`03552e54 : 00000000`00000002 00000000`00000000 fffffa80`046a86e0 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
    fffff880`035d9aa0 fffff800`035534ac : fffff880`00000000 fffffa80`06f1f700 fffffa80`03cf6000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
    fffff880`035d9be0 fffff800`0343c6ac : 00000000`00000000 fffffa80`06f1f790 fffff8a0`0a33d640 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
    fffff880`035d9c10 fffff800`030e5a21 : fffff800`03346db8 fffff8a0`0e6e5830 fffff800`03278658 fffffa80`03cf6040 : nt! ?? ::NNGAKEGL::`string'+0x5cd3b
    fffff880`035d9c70 fffff800`03378cce : 0000059a`00000000 fffffa80`03cf6040 00000000`00000080 fffffa80`03c70990 : nt!ExpWorkerThread+0x111
    fffff880`035d9d00 fffff800`030ccfe6 : fffff880`009e8180 fffffa80`03cf6040 fffff880`009f2f40 0000059a`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`035d9d40 00000000`00000000 : fffff880`035da000 fffff880`035d4000 fffff880`035d9020 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    //The IRP that was held up
    
    0: kd> !irp fffffa80040a97a0
    Irp is active with 3 stacks 2 is current (= 0xfffffa80040a98b8)
     No Mdl: No System Buffer: Thread fffffa8003cf6040:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[IRP_MJ_PNP(1b), IRP_MN_REMOVE_DEVICE - (2)]
                0  0 fffffa8006dad050 00000000 00000000-00000000    
              *** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
     \Driver\NETwNs64
                Args: 00000000 00000000 00000000 00000000
     [IRP_MJ_PNP(1b), IRP_MN_REMOVE_DEVICE - (2)]
                0  0 fffffa8006cc1e20 00000000 00000000-00000000    
               \Driver\vwifibus
                Args: 00000000 00000000 00000000 00000000
    
    0: kd> lmvm NETwNs64
    Browse full module list
    start             end                 module name
    fffff880`04e18000 fffff880`056a0000   NETwNs64   (no symbols)           
        Loaded symbol image file: NETwNs64.sys
        Image path: \SystemRoot\system32\DRIVERS\NETwNs64.sys
        Image name: NETwNs64.sys
        Browse all global symbols  functions  data
        Timestamp:        Mon Jan 23 22:44:07 2012 (4F1DE2B7)
        CheckSum:         00845FA9
        ImageSize:        00888000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    It appears the lock was placed in an infinite loop, so the IRP was never processed, when the next thread tried to take control, because it never did.
    Your wireless adapter driver is out of date, you should update it.
    Jared, my wireless adapter driver is "intel_proset_wireless_driver_16_100_win7_64bit" which is the latest for my wireless adapter i think? (although this updated version is also years ago)

    how to update again?

  15. #15
    Jared's Avatar
    Join Date
    Feb 2014
    Age
    20
    Posts
    1,568
    • specs System Specs
      • Manufacturer:
        Custom
      • Motherboard:
        ASUS Maximus VII Ranger
      • CPU:
        i7 4790K @ 4.4GHz
      • Memory:
        Corsair Vengeance 16GB 1866MHz
      • Graphics:
        MSI Gaming 4G GTX 980
      • Sound Card:
        Creative Soundblaster ZxR
      • Hard Drives:
        Samsung 850 SSD 250GB
      • Disk Drives:
        Western Digital Black Caviar 2TB
      • Power Supply:
        Corsair RM650 Modular 650 Watts
      • Case:
        Fractal Design Define R5 Window
      • Cooling:
        Corsair H100i GTX
      • Display:
        Dell U2515H 25inch 2560x1440 + LG Flatron M2262D 22inch 1920x1080
      • Operating System:
        Windows 10 Professional x64

    re: BSOD - Wifi? - Windows 7 x64

    https://downloadcenter.intel.com/dow...for-Windows-7-
    Choose the Ds64.exe download, second to top.

  16. #16

    re: BSOD - Wifi? - Windows 7 x64

    Jared, I just install it? Do i need to uninstall anything? Yesterday i just install it, but my wifi problem happens again(limited acess). Now i install it again [run as administrator].

  17. #17
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    15,839
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    re: BSOD - Wifi? - Windows 7 x64

    You have an Intel 5100 AGN wifi -
    Code:
        Driver                    : Intel(R) WiFi Link 5100 AGN
        Vendor                    : Intel Corporation
        Provider                  : Intel
        Date                      : 1/22/2012
        Version                   : 14.3.2.1
    Your driver is dated 2012. Download the second one - "Wireless 18.21.0_DS64.exe"

    https://downloadcenter.intel.com/dow...for-Windows-7-

    Be sure to reset your router as well.

    Regards. . .

    jcgriff2

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  18. #18

    re: BSOD - Wifi? - Windows 7 x64

    jcgriff2, reset router is that means i need to reset to the default factory setting?


  19. #19
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    15,839
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    re: BSOD - Wifi? - Windows 7 x64

    Hi. . .

    Yes - reset the router to factory default settings. Turn the router off, unplug it; wait for 30 seconds then plug it back in, then power it up.

    I make this suggestion because of the Internet problems you describe. It has nothing to do with the driver update, i.e., it's not a requirement to reset the router after a wifi driver update.

    Regards. . .

    jcgriff2

    p.s. I have the same Intel 5100 wifi in an older HP laptop here.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  20. #20

    re: BSOD - Wifi? - Windows 7 x64

    jcgriff2, I have followed all the instructions and reset the router to factory default settings, still the problem exists. I've attached the pictures, please have a look. Thanks.

    Between, did your hp laptop face the same issue?


    BSOD - Wifi? - Windows 7 x64-limited-acess-jpg BSOD - Wifi? - Windows 7 x64-network-connections-jpg

Page 1 of 2 12 Last

Similar Threads

  1. Replies: 0
    Last Post: 07-20-2015, 02:43 AM
  2. Wifi Disconnection Problem
    By kelese in forum Hardware
    Replies: 7
    Last Post: 09-19-2014, 12:46 PM
  3. Replies: 8
    Last Post: 02-23-2014, 09:33 AM
  4. Settings for wifi network when travelling
    By dee_can in forum Networking
    Replies: 19
    Last Post: 03-28-2013, 12:00 AM

Log in

Log in