1. #1

    BSOD caused by WiFi drivers maybe?

    Hello folks,

    I have a Dell E7240 laptop that keeps BSODing. I've updated the drivers and BIOS from the Dell site, but the problem has persisted.

    I suspect it's a problem with WiFi drivers because it seems OK at some locations, but crashes more when connected to a specific WiFi network. There's also another WiFi network it won't connect to - even though other devices can.

    I've tried to analyse the minidump, but I don't have the knowledge to interpret it fully.

    The laptop runs Windows 7 x64 and was installed in Jan 2016.

    I've run the Sysnative BSOD Dump + System File Collection App and attached the zip file.

    Thanks in advance for your help!

    Paul
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor
    axe0's Avatar
    Join Date
    May 2015
    Location
    The Netherlands
    Age
    22
    Posts
    664
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB & 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24" Liyama ProLite XB2483HSU-B2 & 24" Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: BSOD caused by WiFi drivers maybe?

    Hi PaulChuckle,

    Your USB chipset drivers are dated, update them from Dell.
    Code:
    Bugcheck code 0000009F
    Arguments 00000000`00000003 fffffa80`07371910 fffff800`00b9a3d8 fffffa80`037120e0
    Debug session time: Fri Nov 10 08:58:52.899 2017 (UTC + 1:00)
    System Uptime: 0 days 0:20:17.983
    
    0: kd> !irp fffffa80037120e0 1
    Irp is active with 5 stacks 4 is current (= 0xfffffa8003712288)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
    Flags = 00000000
    ThreadListEntry.Flink = fffffa8003712100
    ThreadListEntry.Blink = fffffa8003712100
    IoStatus.Status = 00000000
    IoStatus.Information = 00000000
    RequestorMode = 00000000
    Cancel = 00
    CancelIrql = 0
    ApcEnvironment = 00
    UserIosb = 00000000
    UserEvent = 00000000
    Overlay.AsynchronousParameters.UserApcRoutine = 00000000
    Overlay.AsynchronousParameters.UserApcContext = 00000000
    Overlay.AllocationSize = 00000000 - 00000000
    CancelRoutine = 00000000   
    UserBuffer = 00000000
    &Tail.Overlay.DeviceQueueEntry = fffffa8003712158
    Tail.Overlay.Thread = 00000000
    Tail.Overlay.AuxiliaryBuffer = 00000000
    Tail.Overlay.ListEntry.Flink = fffff80003276be0
    Tail.Overlay.ListEntry.Blink = fffff80003276be0
    Tail.Overlay.CurrentStackLocation = fffffa8003712288
    Tail.Overlay.OriginalFileObject = 00000000
    Tail.Apc = 00000000
    Tail.CompletionKey = 00000000
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
                0  0 fffffa8007371910 00000000 fffff880081a3b08-fffffa8007cf71b0    
    	      *** WARNING: Unable to verify timestamp for iusb3xhc.sys
    *** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
     \Driver\iusb3xhc	iusb3hub
    			Args: 00000000 00000000 00000000 00000000
    >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 fffffa8007cf7060 00000000 00000000-00000000    pending
    	       \Driver\iusb3hub
    			Args: 00000000 00000001 00000001 00000000
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-fffffa800f1a8100    
    
    			Args: 00000000 00000000 00000000 00000000
    
    0: kd> lmvm iusb3hub
    Browse full module list
    start             end                 module name
    fffff880`08199000 fffff880`081f8000   iusb3hub T (no symbols)           
        Loaded symbol image file: iusb3hub.sys
        Image path: iusb3hub.sys
        Image name: iusb3hub.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Mar 26 12:05:37 2014 (5332B481)
        CheckSum:         0005D3B8
        ImageSize:        0005F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

  3. #3

    Re: BSOD caused by WiFi drivers maybe?

    Many thanks axe0.

    I've installed the USB chipset drivers from here Intel USB eXtensible Host Controller Driver Driver Details | Dell UK

    Fingers-crossed that will fix things - I'll let you know if it works.

Similar Threads

  1. BSOD - Wifi? - Windows 7 x64
    By yen in forum BSOD, Crashes, Kernel Debugging
    Replies: 35
    Last Post: 02-09-2016, 05:28 AM
  2. Replies: 0
    Last Post: 07-20-2015, 02:43 AM
  3. [SOLVED] BSOD - caused by a driver but I'm not sure which
    By holaboo in forum BSOD, Crashes, Kernel Debugging
    Replies: 10
    Last Post: 09-21-2014, 12:44 PM
  4. Replies: 8
    Last Post: 02-23-2014, 09:33 AM
  5. BSOD, caused by software?
    By FallDown in forum BSOD, Crashes, Kernel Debugging
    Replies: 7
    Last Post: 07-28-2012, 08:49 AM

Log in

Log in