Bsod / irql_not_less_or_equal


  1. Posts : 19
    Windows 10 Pro
       #1

    Bsod / irql_not_less_or_equal


    Computer was idling web open web browser when this BSOD appears suddenly.
    Attachment 55702
      My Computer


  2. Posts : 14,897
    Windows 10 Pro
       #2




    Diagnostic Test

     CPU TEST


    Run Prime95 and IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

    Note   Note
    If you're overclocking anything, please stop it and set everything back to default while troubleshooting

    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.


    Code:
    0: kd> !errrec ffffe000021be028===============================================================================
    Common Platform Error Record @ ffffe000021be028
    -------------------------------------------------------------------------------
    Record Id     : 01d136f8106fa4df
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 12/16/2015 18:57:28 (UTC)
    Flags         : 0x00000000
    
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000021be0a8
    Section       @ ffffe000021be180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000206a7
    Processor ID  : 0x0000000000000000
    
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000021be0f0
    Section       @ ffffe000021be240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : a7 06 02 00 00 08 10 00 - bf e3 9a 1f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    
    Proc. Info 0  @ ffffe000021be240
    
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000021be138
    Section       @ ffffe000021be2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Error         : Internal timer (Proc 0 Bank 3)
      Status      : 0xbe00000000800400
      Address     : 0x00003802383d42bf
      Misc.       : 0x000000000003ffff
      My Computers


  3. Posts : 19
    Windows 10 Pro
    Thread Starter
       #3

    axe0 said:


    Diagnostic Test

     CPU TEST


    Run Prime95 and IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

    Note   Note
    If you're overclocking anything, please stop it and set everything back to default while troubleshooting

    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.


    Code:
    0: kd> !errrec ffffe000021be028===============================================================================
    Common Platform Error Record @ ffffe000021be028
    -------------------------------------------------------------------------------
    Record Id     : 01d136f8106fa4df
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 12/16/2015 18:57:28 (UTC)
    Flags         : 0x00000000
    
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000021be0a8
    Section       @ ffffe000021be180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000206a7
    Processor ID  : 0x0000000000000000
    
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000021be0f0
    Section       @ ffffe000021be240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : a7 06 02 00 00 08 10 00 - bf e3 9a 1f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    
    Proc. Info 0  @ ffffe000021be240
    
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000021be138
    Section       @ ffffe000021be2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Error         : Internal timer (Proc 0 Bank 3)
      Status      : 0xbe00000000800400
      Address     : 0x00003802383d42bf
      Misc.       : 0x000000000003ffff
    Thank you for repply!

    I have already tested with Prime95 Blend test 8 hours and system was stable, not even errors. Same with Intel Burn Test, stable. I don't have any over clocks with CPU, GPU or RAMs. I have also tested my RAM sticks with memtest86 overnight and it did not give any errors.
    Maybe my mobo or CPU is dying then.

    I gues what i can do, is bump cpu voltage a bit and disable some C power savings in bios and see if it does anything. As you can see my posts i've had several BSOD:s with same system righ after upgrading Windows 10.
    Last edited by RoopeSeta; 29 Dec 2015 at 15:27.
      My Computer


  4. Posts : 14,897
    Windows 10 Pro
       #4

    What were the temps of the CPU while testing and what are the temps of the CPU when under other load (like gaming or something).
      My Computers


  5. Posts : 19
    Windows 10 Pro
    Thread Starter
       #5

    axe0 said:
    What were the temps of the CPU while testing and what are the temps of the CPU when under other load (like gaming or something).

    CPU max +50-60c during AVX Prime, GPU was also cool. My system never crashes during havy gaming, every crash was under ligh load or idling.
      My Computer


  6. Posts : 14,897
    Windows 10 Pro
       #6

    Please run driver verifier for the 0xA(irql_not_less_or_equal), the CPU part (not completely ruled out) was for the 0x124(WHEA_UNCORRECTABLE_ERROR) that happened 2 weeks ago.




    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  7. Posts : 19
    Windows 10 Pro
    Thread Starter
       #7

    axe0 said:
    Please run driver verifier for the 0xA(irql_not_less_or_equal), the CPU part (not completely ruled out) was for the 0x124(WHEA_UNCORRECTABLE_ERROR) that happened 2 weeks ago.




    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

    Thanks, i will test that.
      My Computer


 

  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 20:39.
Find Us




Windows 10 Forums