random bluescreens Bug Check Code : 0x00000133


  1. Posts : 47
    Windows 10
       #1

    random bluescreens Bug Check Code : 0x00000133


    I am new here so if anything is wrong with how this is posted let me know.

    Anyway I bought a acer laptop about a month ago exact model Aspire E5-774G-52W1. This just started happening today out of the blue but here are some exported logs from bluescreenview I managed to get before it bluescreened again. I will try and run the dm log collector however I can't guarantee I will be able to before I get another bluescreen.

    ==================================================
    Dump File : 121616-8390-01.dmp
    Crash Time : 12/16/2016 9:25:00 PM
    Bug Check String :
    Bug Check Code : 0x00000133
    Parameter 1 : 00000000`00000001
    Parameter 2 : 00000000`00001e00
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : pci.sys
    Caused By Address : pci.sys+5386
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+14a6f0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\121616-8390-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 14393
    Dump File Size : 527,772
    Dump File Time : 12/16/2016 9:25:53 PM
    ==================================================

    ==================================================
    Dump File : 121616-7203-01.dmp
    Crash Time : 12/16/2016 9:32:03 PM
    Bug Check String :
    Bug Check Code : 0x00000133
    Parameter 1 : 00000000`00000001
    Parameter 2 : 00000000`00001e00
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+14a6f0
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+14a6f0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\121616-7203-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 14393
    Dump File Size : 513,700
    Dump File Time : 12/16/2016 9:32:39 PM
    ==================================================
    ==================================================
    Dump File : 121616-7281-01.dmp
    Crash Time : 12/16/2016 9:36:41 PM
    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x000000d1
    Parameter 1 : 00000000`00000000
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff809`42104670
    Caused By Driver : tcpip.sys
    Caused By Address : tcpip.sys+104670
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+14a6f0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\121616-7281-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 14393
    Dump File Size : 514,868
    Dump File Time : 12/16/2016 9:37:23 PM
    ==================================================
    ==================================================
    Dump File : 121616-9609-01.dmp
    Crash Time : 12/16/2016 9:53:15 PM
    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x000000d1
    Parameter 1 : 00000000`0000000a
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff805`5c36c9cc
    Caused By Driver : tcpip.sys
    Caused By Address : tcpip.sys+2c9cc
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+14a6f0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\121616-9609-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 14393
    Dump File Size : 514,596
    Dump File Time : 12/16/2016 9:53:56 PM
    ==================================================


    Also I am getting weird things like this in my event viewer. I don't know if it is related but it's an issue none the less. The WHEA logger events are happening non stop it seems. It seems to be tied to pci express root port but I am not sure what ti do about it and it seems to have started on december 3rd




    Last edited by mikee286; 17 Dec 2016 at 14:30.
      My Computers


  2. Posts : 654
    windows 10 Pro
       #2

    Please use the BSOD posting instruction to provide the Dumpfile BSOD - Posting Instructions - Windows 10 Forums
      My Computer


  3. Posts : 47
    Windows 10
    Thread Starter
       #3

    **original post updated**
      My Computers


  4. Posts : 545
    seL4
       #4

    Hi Mikee286,

    It is looking like the issue is with your wifi driver. From the crashdumps you posted, I'm seeing:

    wdiwifi.sys (Miniport framework driver)
    netio.sys (Network Input Output driver)
    qcamain10x64.sys (Qualcomm Atheros Wifi driver)
    nwifi.sys (NativeWiFi Miniport Driver).

    You currently have the latest Wifi driver installed, 12.0.0.230, per Acer's Driver page. Does device manager give you the option to rollback the driver? It would certainly be worth a shot.

    There is also a BIOS update, version 1.18 (you are currently running 1.12) - while unlikely - it could increase the stability of your system with regards to the PCI slot. You should of course only update your BIOS while being plugged in to A/C power and have >50% battery left.

    For reference your wifi card is a Qualcomm Atheros NFA435 QCA9377.

    However I did see that there has been a release for 12.0.0.278 that was posted on Softpedia, I agree this does seem sketchy however sigcheck shows that is a signed release by Microsoft from 10/9/2016. This is a .cab file so you will want to extract it using 7zip or similar, and then update your drive by going to device manager and selecting the driver for your wifi card manually.

    Let me know how it goes.
    Last edited by Spectrum; 18 Dec 2016 at 11:33.
      My Computer


  5. Posts : 47
    Windows 10
    Thread Starter
       #5

    Spectrum said:
    Hi Mikee286,

    It is looking like the issue is with your wifi driver. From the crashdumps you posted, I'm seeing:

    wdiwifi.sys (Miniport framework driver)
    netio.sys (Network Input Output driver)
    qcamain10x64.sys (Qualcomm Atheros Wifi driver)
    nwifi.sys (NativeWiFi Miniport Driver).

    You currently have the latest Wifi driver installed, 12.0.0.230, per Acer's Driver page. Does device manager give you the option to rollback the driver? It would certainly be worth a shot.

    There is also a BIOS update, version 1.18 (you are currently running 1.12) - while unlikely - it could increase the stability of your system with regards to the PCI slot. You should of course only update your BIOS while being plugged in to A/C power and have >50% battery left.

    For reference your wifi card is a Qualcomm Atheros NFA435 QCA9377.

    However I did see that there has been a release for 12.0.0.278 that was posted on Softpedia, I agree this does seem sketchy however sigcheck shows that is a signed release by Microsoft from 10/9/2016. This is a .cab file so you will want to extract it using 7zip or similar, and then update your drive by going to device manager and selecting the driver for your wifi card manually.

    Let me know how it goes.
    Sorry for the late reply. I just figured I would follow up. I did end up RMAing the laptop but I got a new identical one and the same issue came right back up with the WHEA Logger flood in event viewer. I did find a post on acers support forum about this same issue on a similar model and the solution was to select driver manually from a list of drivers in device manager and select the 2015 driver 9.1.404 .2015 for the realtek PCIe GBE Family Controller (ethernet port) and the events went away. I only get 2 WHEA logger warnings in event viewer after a boot up or resume from sleep but other than that the event viewer is not being flooded and I have yet to see another BSOD. So thank you for pointing me in the right direction.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:51.
Find Us




Windows 10 Forums