Windows 10: (New built) IRQL NOT LESS OR EQUAL, Random BSODs

Page 1 of 3 123 LastLast

  1. Posts : 14
    Windows 10 64 bit
       20 Dec 2016 #1

    (New built) IRQL NOT LESS OR EQUAL, Random BSODs


    Hi,

    After every few random days I am getting BSOD with the title mentioning "IRQL NOT LESS OR EQUAL. FYI, This is a completely new built and only 2 months in use. Currently not using for gaming so no graphics card in it. Using Windows 10.

    My initial findings of the dump files is that mostly are related to HDAudBus.SYS error and 2 dumps are of Netio.SYS error.


    I have attached the required logs ZIP FILE for your through review.

    Really appreciate your help.

    PC Info:
    Asus z170 Pro gaming, mITX
    16 GB Crucial
    kingston 250 GB SSD
    500 GB HDD
    600 Watts PSU



    (New built) IRQL NOT LESS OR EQUAL, Random BSODs Attached Files
      My ComputerSystem Spec


  2. Posts : 5,089
    Windows 10 Pro X64 15063.138
       20 Dec 2016 #2

    The most recent dump indicates a problem with Qcamain10x64.sys.

    Code:
    ffff8600`4a19a270  fffff809`4874f552*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Qcamain10x64.sys
     Qcamain10x64+0x14f552
    This belongs to your Qualcomm Atheros QCA61x4A Wireless Network Adapter. The one currently installed is dated 2/24/2016 12:20:49 PM.

    See if there is a newer version available.
      My ComputersSystem Spec


  3. Posts : 14
    Windows 10 64 bit
    Thread Starter
       20 Dec 2016 #3

    Sure i'll check it and update..

    But what about the other dumps which have caused the most crashes? Any advise for that
      My ComputerSystem Spec


  4. Posts : 5,089
    Windows 10 Pro X64 15063.138
       20 Dec 2016 #4

    Code:
    fffff801`3a3473a8  fffff80a`d8d289fd*** WARNING: Unable to verify timestamp for Qcamain10x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Qcamain10x64.sys
     Qcamain10x64+0x1289fd
    Qualcomm Atheros QCA61x4A Wireless Network Adapter

    Code:
    fffff801`3a347758  fffff80a`d8f54c14*** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
     igdkmd64+0x84c14
    Intel Graphics Accelerator Drivers for Windows
    Code:
    Code:
    BugCheck A, {0, 2, 0, fffff803ec87b248}
    
    Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::NotificationDpc+1f1 )
    All over the place, Wireless, Video and Audio. Check your PSU voltages. You can usually do this in BIOS Setup.

    Remove all over clocking, CPU and RAM.
      My ComputersSystem Spec


  5. Posts : 14
    Windows 10 64 bit
    Thread Starter
       19 Jan 2017 #5

    Hi...a bit late in reply..was busy..

    I checked my PSU voltages in my BIOS. I have attached pictures of my PSU specs and BIOS Voltage details. I am new into analyzing voltages. Voltages were observed to be stable monitored for a minute or so. No fluctuation observed. Is there anything else i should do or know regarding this? Also is my PSU OK??? Secondly, i used 'Drive Easy' tool to check my drivers, it showed similar driver issues related to audio, video & wireless and suggested updating them. So can i rely on this info to troubleshoot my issues? For any other info kindly ask me
    Click image for larger version. 

Name:	20170120_080342.jpg 
Views:	6 
Size:	1.98 MB 
ID:	117779Click image for larger version. 

Name:	20170120_080358.jpg 
Views:	3 
Size:	621.2 KB 
ID:	117780
      My ComputerSystem Spec


  6. Posts : 5,089
    Windows 10 Pro X64 15063.138
       20 Jan 2017 #6

    Voltages look okay. Only way to tell if a PSU is bad is to replace it but I don't think that is warranted in this case.

    I would not use Drive Easy. Better to find and download updates manually.

    Also would be a good idea to test your ram. For 16GB it can take 10 to 14 hours so run it overnight.
    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.


    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.
      My ComputersSystem Spec


  7. Posts : 14
    Windows 10 64 bit
    Thread Starter
       23 Jan 2017 #7

    Here's the memtest result. As shown 12 passes. No issues observed with RAM,
    FYI, i checked my BIOS, newer versions are available for stability. So from here on what can be done next for these random crashes. I think we are left with faulty drivers. But still you know better and will advise better analyzing the dumps.
    Click image for larger version. 

Name:	20170123_075320.jpg 
Views:	3 
Size:	1.99 MB 
ID:	118139
      My ComputerSystem Spec


  8. Posts : 5,089
    Windows 10 Pro X64 15063.138
       25 Jan 2017 #8

    If there are newer BIOS versions available, update to the latest one. Won't hurt, may help.

    You can try enabling Driver Verifier, see if that gives us any better idea of the cause of these problems.

    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to
    PART TWO
    and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it.
      My ComputersSystem Spec


  9. Posts : 14
    Windows 10 64 bit
    Thread Starter
       06 Feb 2017 #9

    Dumps (after using Driver verifier)


    Before updating BIOS, I have went through the driver verifier procedure as advised.

    Got 2 immediate BSOD one after the other, after rebooting the PC. Have attached the dumps in the thread for your reference.
    Other than these last 2 dumps generated by the driver verifier, I believe rest of the dumps of earlier times will also give you some idea.
    (New built) IRQL NOT LESS OR EQUAL, Random BSODs Attached Files
      My ComputerSystem Spec


  10. Posts : 5,089
    Windows 10 Pro X64 15063.138
       07 Feb 2017 #10

    The 2/7 4:11Pm dump shows this:

    Code:
    BugCheck C9, {21f, fffff80a3061b174, ffff840c90996570, 0}
    *** WARNING: Unable to verify timestamp for ScpVBus.sys
    *** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys
    Probably caused by : memory_corruption
    Known to cause BSODS, see an post I made awhile ago here: Error code c0000005 - Not a BSOD
      My ComputersSystem Spec


 
Page 1 of 3 123 LastLast

Related Threads
I don't remember for sure if it said ndis.sys, but I'm almost positive it was. Anyways, I get this BSOD at random times, it usually happens while I'm streaming a video on YouTube or Netflix but I'm not sure if there's any correlation since that's...
Solved Błąd IRQL NOT LESS OR EQUAL in BSOD Crashes and Debugging
An error occurred while browsing web pages.
Random Bsods since i built my new pc, Help? in BSOD Crashes and Debugging
built this new pc and it works well but randomly has bsod, here are dump files. dont remember what i was doing for most of the bsods but more than likely it was gaming. if not it would be browsing the web or streaming Thanks in advance Kookta
IRQL Not Less or Equal in BSOD Crashes and Debugging
I've been having problems with a BSOD, but I can't get the debugger in Visual Studio to read the Minidump .dmp file to find out what the problem is. I've updated my BIOS to the newest version. It reboots itself numerous times per day, sometimes...
Random BSODs, Driver IRQL ETD.sys in BSOD Crashes and Debugging
Hello, I have been getting random BSODs for weeks now and I am totally clueless on what to do. The BSOD Message is : DRIVER_IRQL_NOT_LESS_OR_EQUAL (ETD.sys) Recently updated to windows 10. I cant seem to remember if the BSODs begun before I...
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 09:56.
Find Us