WiFi Driver issue with Acer Predator Helios Neo 16 PHN16-71

nandhakumar95
nandhakumar95 Member Posts: 3 New User

I'm experiencing frequent wifi driver crash in my new laptop PHN16-71, after updating the drivers to 22.250.10.1. Everytime I need to reinstall the killer network suite to get it fixed.

Tried to clean install the drivers as well, nothing helped. Can any one provide me the solution for this issue.

Currently running the version- 22.170.0.3.

Thank you.

Answers

  • nandhakumar95
    nandhakumar95 Member Posts: 3 New User

    Hi, As suggested, I'm using the older version (Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) - 22.170.0.3), with which the laptop shipped. But again I'm getting the Wifi driver error.

    Tried doing a clean boot, uninstalled it in device manager and reinstalled the drivers from Acer's drivers page and rebooted. It worked for a while, But again it crashed. Device manger throws the below error message.

    Windows has stopped this device because it has reported problems. (Code 43)

    I have also checked the event viewer and got this below error,

    Device PCI\VEN_8086&DEV_7A70&SUBSYS_16521A56&REV_11\3&11583659&0&A3 had a problem starting.

    Driver Name: oem1.inf
    Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
    Service: Netwtw10
    Lower Filters:
    Upper Filters: vwifibus
    Problem: 0x0
    Problem Status: 0xC00000E5

    This issue has become persist now. Can anyone please provide a solution for it.

    I even tried to reset the system, nothing worked.

  • Muhil
    Muhil Member Posts: 511 Skilled Practitioner WiFi Icon

    @nandhakumar95 just uninstall in device manager and then reboot connect to internet and let windows installl the driver

  • shubh_kukreti
    shubh_kukreti Member Posts: 1 New User
    edited July 27

    this issue is happening with me also for quite some time . I contacted acer support earlier , then they made me clean install windows and drivers . Worked fine for a bit and now again i have the same issue .
    Anyone with the fix to this issue ?

    @nandhakumar95 did you resolve your issue ?