Windows 10: Blue screen of death IRQL_NOT_LESS_OR_EQUAL, PC keeps restarting to a blue screen.

Discus and support Blue screen of death IRQL_NOT_LESS_OR_EQUAL, PC keeps restarting to a blue screen. in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello guys, Reinstalling windows doesn't help me fix that problem, my pc bluescreens right before windows should come up with this error message.... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Shiran Shushan, Mar 27, 2021.

  1. Blue screen of death IRQL_NOT_LESS_OR_EQUAL, PC keeps restarting to a blue screen.


    Hello guys,


    Reinstalling windows doesn't help me fix that problem, my pc bluescreens right before windows should come up with this error message.

    Tried analyzing the file with WinDbg Preview, this is what comes up when I analyze the file "MEMORY.DMP" in windows folder.

    It's important for me to say that I tried scanning my memory through that windows thing and it said that no problems have been found.


    In WinDbg it says in the threads window "nt!KiSwapContext+0x76 fffff802`805fc9d6" tried googling it and it said "DRIVER_POWER_STATE_FAILURE"


    Is there any chance it might be cause cause of BIOS version? when I updated it the last time I installed a beta version

    This thing is driving me crazy as every time I install a Windows update and it has to restart I get like 3-4 BSODs in a row I just got 9 in a row lol


    Here are the files from my minidump folder + the MEMORY.DMP one uploaded to google drive

    https://drive.google.com/file/d/1tOqxCmEYxk2IsUlr25qgJEaPpBJBClbi/view?usp=sharing


    Any help will be so much appreciated


    MEMORY.DMP analyzed through windbg preview down below

    [COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff802`80200000 PsLoadedModuleList = 0xfffff802`80e2a490Debug session time: Sun Mar 28 00:53:14.604 2021 UTC + 3:00System Uptime: 0 days 0:00:09.212Loading Kernel Symbols.........................................................................................................................................................Loading User SymbolsLoading unloaded module list.......For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff802`805f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb083`cc73eb10=000000000000000a2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL aAn attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: ffffb5871028b010, memory referencedArg2: 00000000000000ff, IRQLArg3: 0000000000000073, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation only on chips which support this level of statusArg4: fffff80280608bd3, address which referenced memoryDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3828 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 3848 Key : Analysis.Init.CPU.mSec Value: 218 Key : Analysis.Init.Elapsed.mSec Value: 5639 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1BUGCHECK_CODE: aBUGCHECK_P1: ffffb5871028b010BUGCHECK_P2: ffBUGCHECK_P3: 73BUGCHECK_P4: fffff80280608bd3WRITE_ADDRESS: ffffb5871028b010 Paged poolPROCESS_NAME: SystemTRAP_FRAME: ffffb083cc73ec50 -- [/COLOR][COLOR=rgba0, 0, 255, 1].trap 0xffffb083cc73ec50[/COLOR][COLOR=rgba30, 30, 30, 1]NOTE: The trap frame does not contain all registers.[/COLOR][COLOR=rgba0, 0, 255, 1]Some register values may be zeroed or incorrect.[/COLOR][COLOR=rgba30, 30, 30, 1]rax=ffffb5871028b010 rbx=0000000000000000 rcx=ffffb5871028b020rdx=ffffffffffde4e90 rsi=0000000000000000 rdi=0000000000000000rip=fffff80280608bd3 rsp=ffffb083cc73ede8 rbp=ffffb083cc73f279 r8=000000000000001c r9=0000000000000001 r10=ffffb5871006fea0r11=ffffb5871006ff0c r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up di pl nz na pe ncnt!memcpy+0x113:fffff802`80608bd3 0f2941f0 movaps xmmword ptr [rcx-10h],xmm0 ds:ffffb587`1028b010=????????????????????????????????Resetting default scopeLOCK_ADDRESS: fffff80280e44c00 -- !locks fffff80280e44c00Resource @ nt!PiEngineLock 0xfffff80280e44c00 Exclusively owned Contention Count = 5 Threads: ffff8a817a40d240-01<*> 1 total locksPNP_TRIAGE_DATA: Lock address : 0xfffff80280e44c00 Thread Count : 1 Thread address: 0xffff8a817a40d240 Thread wait : 0x24dSTACK_TEXT: ffffb083`cc73eb08 fffff802`80607b69 : 00000000`0000000a ffffb587`1028b010 00000000`000000ff 00000000`00000073 : nt!KeBugCheckExffffb083`cc73eb10 fffff802`80603e69 : 00000000`0000007c fffff802`80bb1094 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69ffffb083`cc73ec50 fffff802`80608bd3 : fffff802`8045c08b ffffb587`101e0e50 ffffb587`1006fe90 00000000`00000000 : nt!KiPageFault+0x469ffffb083`cc73ede8 fffff802`8045c08b : ffffb587`101e0e50 ffffb587`1006fe90 00000000`00000000 00000000`00001000 : nt!memcpy+0x113ffffb083`cc73edf0 fffff802`8081b053 : 00000000`00000001 ffffb587`10201160 ffffb083`cc73efe0 00000000`00000000 : nt!CmpDoQueryKeyName+0x23bffffb083`cc73ef30 fffff802`807d9ae3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt!CmpQueryKeyName+0x13ffffb083`cc73ef80 fffff802`807d96da : ffffb587`101e0e50 ffffb587`1028b000 00000000`00001000 ffffb083`cc73f0f4 : nt!ObQueryNameStringMode+0xd3ffffb083`cc73f0a0 fffff802`809267ea : ffffffff`800019c4 ffffffff`800019c4 ffff8a81`7a40d240 fffff802`00001000 : nt!NtQueryObject+0x18affffb083`cc73f1f0 fffff802`80925af9 : fffff802`7e020000 ffff8a81`7a40d240 ffffffff`00000000 00000000`00000000 : nt!IopQueryRegistryKeySystemPath+0xdaffffb083`cc73f2e0 fffff802`809232c0 : fffff802`7e020000 fffff802`7e020000 00000000`00000000 00000000`00000000 : nt!IopBuildFullDriverPath+0xc1ffffb083`cc73f3a0 fffff802`80923228 : fffff802`7e020000 00000000`00000000 ffffffff`800019c4 ffffb587`0dff8b10 : nt!PpCheckInDriverDatabase+0x40ffffb083`cc73f400 fffff802`80926215 : ffffb083`cc73f580 fffff802`7e0200d8 fffff802`80e45a80 00000000`00000000 : nt!PnpPrepareDriverLoading+0x6cffffb083`cc73f480 fffff802`80927e06 : 00000000`00000000 00000000`00000000 00000000`00000004 ffffb083`00000004 : nt!IopLoadDriver+0x27dffffb083`cc73f650 fffff802`80927b16 : fffff802`8020af01 00000000`00000000 ffff8a81`7ace8410 ffffffff`800019a4 : nt!PipCallDriverAddDeviceQueryRoutine+0x1beffffb083`cc73f6e0 fffff802`809274d4 : 00000000`00000000 ffffb083`cc73f7f0 00000000`6e657050 fffff802`0000000e : nt!PnpCallDriverQueryServiceHelper+0xdaffffb083`cc73f790 fffff802`80926c67 : ffff8a81`7ba18c70 ffffb083`cc73f9d1 ffff8a81`7ba18c70 00000000`00000000 : nt!PipCallDriverAddDevice+0x41cffffb083`cc73f950 fffff802`8091fd96 : ffff8a81`7ba18c00 ffff8a81`7ce89701 ffffb083`cc73fa70 fffff802`00000000 : nt!PipProcessDevNodeTree+0x333ffffb083`cc73fa20 fffff802`8056c31a : 00000001`00000003 ffff8a81`7ba18c70 00000000`00000000 ffff8a81`7ce89780 : nt!PiRestartDevice+0xbaffffb083`cc73fa70 fffff802`80425975 : ffff8a81`7a40d240 ffff8a81`74287a20 fffff802`80e435a0 ffff8a81`00000000 : nt!PnpDeviceActionWorker+0x46affffb083`cc73fb30 fffff802`80517e85 : ffff8a81`7a40d240 00000000`00000080 ffff8a81`742ce040 000fe067`b4bbbdff : nt!ExpWorkerThread+0x105ffffb083`cc73fbd0 fffff802`805fd2a8 : ffffe500`d0b47180 ffff8a81`7a40d240 fffff802`80517e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55ffffb083`cc73fc20 00000000`00000000 : ffffb083`cc740000 ffffb083`cc739000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: nt!KiPageFault+469MODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]nt[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 469FAILURE_BUCKET_ID: AV_CODE_AV_nt!KiPageFaultOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {22c06795-f62b-154a-eb13-05cdd373e37e}Followup: MachineOwner---------[/COLOR]

    :)
     
    Shiran Shushan, Mar 27, 2021
    #1
  2. akshay tripathi, Mar 27, 2021
    #2
  3. vPizzas Win User
    Blue screen of death keeps restarting

    Need help because my pc keeps getting a blue screen of death saying it will collect error info, the percentage goes to 100%, and then it restarts the whole process. Stop code CRITICAL_SERVICE FAILED
     
    vPizzas, Mar 27, 2021
    #3
  4. J-Man Win User

    Blue screen of death IRQL_NOT_LESS_OR_EQUAL, PC keeps restarting to a blue screen.

    Blue screen of death?

    If anyone happens to know the error called "DRIVE_IRQL_NOT_EQUAL_OR_LESS" please let me know. It says that on the blue screen of death I call it.
     
    J-Man, Mar 27, 2021
    #4
Thema:

Blue screen of death IRQL_NOT_LESS_OR_EQUAL, PC keeps restarting to a blue screen.

Loading...
  1. Blue screen of death IRQL_NOT_LESS_OR_EQUAL, PC keeps restarting to a blue screen. - Similar Threads - Blue screen death

  2. IRQL_NOT_LESS_OR_EQUAL a Blue Screen of Death

    in Windows 10 Gaming
    IRQL_NOT_LESS_OR_EQUAL a Blue Screen of Death: Hello there. For the past few days I have been experiencing the same blue screen error of 'IRQL_NOT_LESS_OR_EQUAL', and I am unsure what could be the cause of this. Minidump file will be listed below:...
  3. IRQL_NOT_LESS_OR_EQUAL a Blue Screen of Death

    in Windows 10 Software and Apps
    IRQL_NOT_LESS_OR_EQUAL a Blue Screen of Death: Hello there. For the past few days I have been experiencing the same blue screen error of 'IRQL_NOT_LESS_OR_EQUAL', and I am unsure what could be the cause of this. Minidump file will be listed below:...
  4. Blue screen of death and keep restarting

    in Windows 10 Gaming
    Blue screen of death and keep restarting: I updated my PC 2days ago after that it keep on restarting and showing BSOD.So help me how to fix it. https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-of-death-and-keep-restarting/3de4db66-d8dd-4f28-bf63-830706cf3c49
  5. Blue screen of death and keep restarting

    in Windows 10 Software and Apps
    Blue screen of death and keep restarting: I updated my PC 2days ago after that it keep on restarting and showing BSOD.So help me how to fix it. https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-of-death-and-keep-restarting/3de4db66-d8dd-4f28-bf63-830706cf3c49
  6. Blue Screen of Death with IRQL_NOT_LESS_OR_EQUAL error

    in Windows 10 Gaming
    Blue Screen of Death with IRQL_NOT_LESS_OR_EQUAL error: Problem signatureProblem Event Name: BlueScreenCode: aParameter 1: ffffd98ab4b0ecc0Parameter 2: 2Parameter 3: 0Parameter 4: fffff8035bc004f2OS version: 10_0_19044Service Pack: 0_0Product: 768_1OS Version: 10.0.19044.2.0.0.768.101Locale ID: 2057Extra information about the...
  7. Blue Screen of Death with IRQL_NOT_LESS_OR_EQUAL error

    in Windows 10 Software and Apps
    Blue Screen of Death with IRQL_NOT_LESS_OR_EQUAL error: Problem signatureProblem Event Name: BlueScreenCode: aParameter 1: ffffd98ab4b0ecc0Parameter 2: 2Parameter 3: 0Parameter 4: fffff8035bc004f2OS version: 10_0_19044Service Pack: 0_0Product: 768_1OS Version: 10.0.19044.2.0.0.768.101Locale ID: 2057Extra information about the...
  8. Blue Screen of Death with IRQL_NOT_LESS_OR_EQUAL error

    in Windows 10 BSOD Crashes and Debugging
    Blue Screen of Death with IRQL_NOT_LESS_OR_EQUAL error: Problem signatureProblem Event Name: BlueScreenCode: aParameter 1: ffffd98ab4b0ecc0Parameter 2: 2Parameter 3: 0Parameter 4: fffff8035bc004f2OS version: 10_0_19044Service Pack: 0_0Product: 768_1OS Version: 10.0.19044.2.0.0.768.101Locale ID: 2057Extra information about the...
  9. Blue Screen of Death with IRQL_NOT_LESS_OR_EQUAL error

    in Windows 10 Drivers and Hardware
    Blue Screen of Death with IRQL_NOT_LESS_OR_EQUAL error: My brand new computer keeps crashing, was looking to get an answer to why? Thanks! I've compressed the DMP file, it will be in the link below. https://1drv.ms/f/s!AjXoDqTW3RxUghbKSAr7oaHxGqem The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a...
  10. Blue screen of death keeps restarting

    in Windows 10 BSOD Crashes and Debugging
    Blue screen of death keeps restarting: Need help because my pc keeps getting a blue screen of death saying it will collect error info, the percentage goes to 100%, and then it restarts the whole process. Stop code CRITICAL_SERVICE FAILED...