IRQL_NOT_LESS_OR_EQUAL, KMODE_EXCEPTION_NOT_HANDLED, DRIVER_POWER_STATE_FAILURE


Ghira24

Member
Local time
12:34 AM
Posts
2
OS
Windows11
Hi, for some time I have been experiencing BSOD, but they were just once in a while and it was not annoying and even though I was not able to repair them I just let them be. However lately they started happening really often, as well as Black Screens, so I reinstalled Windows 11 completely. This solved the issue for two days and started happening again. I ran everything from Windows Memory Diagnostic to Driver Verifier (which for some reason does not yield any dump), sfc /scannow and so on. Finally I ran DISM /Online /Cleanup-Image /RestoreHealth, this repaired my system for approximately 4 days and now it started giving BSOD again. The issue persists even in Clean Boot, even though MyAsus and all the systems can't find any issue. Any clues why this might happen? This is the link to V2 log results: DESKTOP-SAI6G4L-(2024-04-13_23-10-44).zip. My system is around 4 years old, I do not think there is anything left in warranty.

Thank you!
 
Windows Build/Version
Windows 11
Last edited:

My Computer

System One

  • OS
    Windows11
    Computer type
    Laptop
    Manufacturer/Model
    ASUS TUF GAMING A15
    CPU
    AMD Ryzen 7 4800H with Radeon Graphics 2.90 GhZ
    Motherboard
    ASUSTeK COMPUTER INC. FA506IU 1.0
    Memory
    16.0GB RAM
    Graphics Card(s)
    NVIDIA GeForce GTX 1660 Ti, AMD Radeon Graphics Processor
    Monitor(s) Displays
    built-in
    Screen Resolution
    1920x1080
    Hard Drives
    SSD KINGSTON OM8PcP3512F-AB
Hello sir,
Rich (BB code):
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80611729425, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: fffffc8557afb508, Parameter 1 of the exception

The crash occurs when the error handler fails to catch the exception. parameter 1 describes the exception. Let's look at the ntstatus codes,

0xC000001D
STATUS_ILLEGAL_INSTRUCTION
{EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
Nothing much will come of this, because if a security breach occurs as a result of this exception, a blue screen is an inevitable fact.
Code:
kd> !prcb
PRCB for Processor 10 at fffff780ffff0000:
Current IRQL -- 0
Threads--  Current ffff8b0fbd618040 Next 0000000000000000 Idle ffff8b0fbd618040
Processor Index 10 Number (0, 10) GroupSetMember 400
Interrupt Count -- 00e06214
Times -- Dpc    00000013 Interrupt 00000004
         Kernel 0000affc User      000000d7
So let's look at the core stacks. We have the stacks in core 10.
Code:
kd> k
 # Child-SP          RetAddr               Call Site
00 ffffc100`d05f70e8 fffff806`1195a6fa     nt!KeBugCheckEx
01 ffffc100`d05f70f0 fffff806`11837642     nt!HvlpVtlCallExceptionHandler+0x22
02 ffffc100`d05f7130 fffff806`117013c3     nt!RtlpExecuteHandlerForException+0x12
03 ffffc100`d05f7160 fffff806`116d141e     nt!RtlDispatchException+0x2f3
04 ffffc100`d05f78d0 fffff806`1182d2b2     nt!KiDispatchException+0x1ae
05 ffffc100`d05f7fb0 fffff806`1182d280     nt!KxExceptionDispatchOnExceptionStack+0x12
06 fffffc85`57afb168 fffff806`11841d75     nt!KiExceptionDispatchOnExceptionStackContinue
07 fffffc85`57afb170 fffff806`1183b12d     nt!KiExceptionDispatch+0x135
08 fffffc85`57afb350 fffff806`11729425     nt!KiInvalidOpcodeFault+0x32d
fffffc85`57af9570  fffff80a`d9af0000Unable to load image rtwlane.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rtwlane.sys
 rtwlane
09 fffffc85`57afb4e0 fffff806`117c9d85     nt!KiGetNextTimerExpirationDueTime+0x1a5
0a fffffc85`57afb550 fffff806`116f4f12     nt!PpmIdleSelectStates+0x5d5
0b fffffc85`57afba50 fffff806`11831034     nt!PoIdle+0x452
0c fffffc85`57afbc40 00000000`00000000     nt!KiIdleLoop+0x54
Tak!!! As you can see, your realtek internet driver caused the problem. update this.
Apart from these, there are also calls related to disks. Also check your disks.
Code:
fffffc8557afb190 : fffff806131c2901 : storport!StorRemoveIoGatewayItem+0x101
ffffce888b4f9b58 : fffff80258372247 : stornvme!ProcessCommandInSpecificQueue+0x327
(...)
fffffc8557afb050 : fffff806140c6890 : CLASSPNP!TransferPktComplete
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Gigabyte B550M D3SH, R5 5600, 7900XT
Hi, I have updated my driver and still got some BSOD. Any tips in what should I do next? Also, what do you mean by verifying disks? Is there any tool? Thank you, I highly appreciate it!
 

My Computer

System One

  • OS
    Windows11
    Computer type
    Laptop
    Manufacturer/Model
    ASUS TUF GAMING A15
    CPU
    AMD Ryzen 7 4800H with Radeon Graphics 2.90 GhZ
    Motherboard
    ASUSTeK COMPUTER INC. FA506IU 1.0
    Memory
    16.0GB RAM
    Graphics Card(s)
    NVIDIA GeForce GTX 1660 Ti, AMD Radeon Graphics Processor
    Monitor(s) Displays
    built-in
    Screen Resolution
    1920x1080
    Hard Drives
    SSD KINGSTON OM8PcP3512F-AB
Back
Top Bottom