3 Replies Latest reply on May 19, 2015 10:24 AM by jonathan_intel

    BSOD Caused by Advanced-N 6235- Driver 8.1


      HW: Samsung ATIV Book 4 NP470R5E-K01UB running windows 8.1 64 bit

      Driver: Intel(R) Centrino(R) Advanced-N 6235- Driver version (latest)



      Whenever I attempt to connect to wifi I BSOD with error "kmode_exception_not_handled (Netwew01.sys)"



      • I've uninstalled the current drivers and installed new drivers directly from Intel® Download Center
      • I've also used DISM and SFC scan to try to clear up any potential issues with the system files.
      • Running the dmp files through WhoCrashed I received the following write-up 4 times:



      On Mon 5/18/2015 4:57:07 PM GMT your computer crashed
      crash dump file: C:\WINDOWS\Minidump\051815-34312-01.dmp
      This was probably caused by the following module: netwew01.sys (NETwew01+0x1703E9)
      Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8005C3C73E9, 0x0, 0x0)
      file path: C:\WINDOWS\system32\drivers\netwew01.sys
      product: Intel® Wireless WiFi Link Adapter
      company: Intel Corporation
      description: Intel® Wireless WiFi Link Driver
      Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
      A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwew01.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
      Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED


      The problem seems somewhat similar to this issue, except I'm not dealing with a WiFi hotspot, but with any connection to a wireless network.

      Re: Bug report: Advanced-N 6230- Driver + Win 8



      So what are my options at this point? All signs seem to point to the wireless adapter driver, but downloading new versions of the driver doesn't seem to help. Previous threads on the issue seem to indicate that enabling FIPS might help, but I'm not sure how to do that on Win 8.1.

      I can post one of the .dmp files if that would help.