XPS 13 9370 WiFi issues after waking from sleep

Hey Justin, since I just discovered Intel is manufacturing the Wi-Fi cards for Killer Wireless, can anyone verify the 1435 is the same card as the Intel Wireless-ac 8265 used on the XPS 13 9365s?

If it were the same, I suppose using an Intel driver on the device is not possible?

Good day @Saltgrass,

All I can say regarding that is: each brand has a unique device ID and each driver pack only covers so many device IDs. Due to this, I suspect that each driver will not work with the other.

I suspect the wake/wifi issue discussed is strictly a coding issue between card and system BIOS but I'm speculating.

@DELL-Justin C, you might be right and it could be the coding issue you mention.  I was just wondering if there may be some Intel utility, such as a persistence module which help the system reconnect.

On my 9365, the wireless reconnects even before the desktop is fully available, and that is out of hibernation.  When the system comes out of Modern Standby, the wireless is already connected. 

Just like the problems being experienced with NVMe drives not being recognized on the 9360s, perhaps the folks working on the 9370 could get some help from the 9365 folks.

On a side note, I just replaced an Intel 8260 with a Killer Wireless 1535 and had no problems with drivers swapping over..

I stumbled across another command which creates a report for the wireless adapter.  Possibly the report would expose part of the process where the problem originates.

Open an Administrative command prompt and type the following.  When you check the report it would be good if you could keep in mind the status changes for the system so as to tie the report to those events.

netsh wlan show wlanreport

On one of the charts, you may see something like the following...

BIOS version 1.4.0 seems to be out.

Fixes:

Just got a nice shiny new XPS13 and experiencing this exact problem, although toggling the wi-fi off/on from the taskbar seems to sort it. I've messaged Dell on Twitter to see if we are indeed going to get a fix this month,

@quattrofan as I've posted above, the fix is already out for you to try. I've been running the fix since yesterday, but it's too early to say if it helps with the issue.

Where did you find the BIOS update?

When I run "Dell Update" it says the system is up to date. Found it!

Looks like the latest BIOS did not completely fix the issue.

Today I experienced a crashed WiFi card after returning from sleep.

The attachment was a screenshot of my event viewer showing the error after returning from sleep.

Here are the two relevant event log entries:

powercfg /a
The following sleep states are available on this system:
    Standby (S0 Low Power Idle) Network Disconnected
    Hibernate
    Fast Startup

The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Standby (S2)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Standby (S3)
        This standby state is disabled when S0 low power idle is supported.

    Hybrid Sleep
        Standby (S3) is not available.

    Standby (S0 Low Power Idle) Network Connected
        Connectivity in standby is not supported.

The link below describes the EventID 10317.  It seems the adapter is sent a request to power up but takes longer than 400 msec. to respond and generates the second error.  The link also mentions this happens often during transitional states.

I am guessing, for some reason, when this does happen nothing is repeating the wake request so your systems never connect.  The link is for Win 8 and does not mention Win 10 but might still be relevant.

https://support.microsoft.com/en-us/help/2981681/event-id-10317-is-logged-when-you-turn-on-a-mobile-broadband-device-or

Hopefully the folks who can effect this situation will.  But until then, I would like to ask, in modern standby, do you have your network set to disconnect never, always, or let Windows handle?  Also, how do you bring your system out of modern standby?

Right, the Bios update improved things somewhat, but I have had a couple of disconnects since I updated it.  I wonder how long we will have to wait for a real fix.

I contacted Killer support... here is what they said:

There is a newer driver available with the current Killer Control Center package that is optimized to run on Windows 10 1803. The driver version is 12.0.0.709. Are you on Windows 10 1803? You can check by clicking Start, then type winver and press Enter. A box will pop up, and it will likely say either Version 1709 or Version 1803. If you are on version 1803, I recommend updating to the version of the Killer Control Center that contains wireless driver 12.0.0.709, and which has been optimized to run on 1803. You can do that by following these steps:

1. Download our Killer Uninstaller Tool from here - https://www.killernetworking.com/support/KillerSoftwareUninstaller.exe
2. Download the version optimized for Windows 10 1803 from here - https://www.killernetworking.com/driver-downloads/item/kcc-uwd
3. Run the uninstaller tool and select Remove Killer Software. Wait for it to complete. It can take up to 5-10 minutes. It will say "RESTART REQUIRED" when it is finished.
4. Restart your computer by clicking Start > Power > Restart
5. Run the installer for the Killer Control Center that you downloaded earlier, following the prompts to complete the install.

If you are not on Windows 10 1803, I suggest updating to Windows 10 1803 to see if that resolves the issue, as this issue seems to be resolved with our test machines that are on 1803, and using the current driver with the current BIOS.

Same here :-/