- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I keep getting this when my I plug in or out my charger and the laptop freezes for 10 minutes straight. Then suddenly BLUE SCREEN OF DEATH. I researched it and found out that it can be due to incompatible hardware, driver, third-party software. My hardware is good as told by the official Asus service center. My drivers are updated via Microsoft windows update and Intel driver support software. Already re-installed Windows 2 times (clean install). Ran memory diagnostics by windows and it diagnose no errors. Updated the bios but still getting the bsod mostly irql not less or equal and sometimes attempt to write on read-only memory.
I have check the dump files too. I will post the results below
************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff806`1f200000 PsLoadedModuleList = 0xfffff806`1fe2a1b0 Debug session time: Mon Jan 31 11:56:28.204 2022 (UTC + 5:30) System Uptime: 0 days 0:37:51.838 Loading Kernel Symbols ............................................................... ..................Page 15a326 not present in the dump file. Type ".hh dbgerr004" for details .............................................. ................................................................ ............................... Loading User Symbols Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff806`1f5f73b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa03`93e86ba0=000000000000000a 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00000000000000d0, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8062397f115, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3124 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 13268 Key : Analysis.Init.CPU.mSec Value: 281 Key : Analysis.Init.Elapsed.mSec Value: 3751 Key : Analysis.Memory.CommitPeak.Mb Value: 81 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.1 FILE_IN_CAB: MEMORY.DMP BUGCHECK_CODE: d1 BUGCHECK_P1: d0 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8062397f115 READ_ADDRESS: 00000000000000d0 PROCESS_NAME: System DPC_STACK_BASE: FFFFFA0393E87FB0 TRAP_FRAME: fffffa0393e86ce0 -- (.trap 0xfffffa0393e86ce0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000001e8 rbx=0000000000000000 rcx=ffffac0be6e28c48 rdx=fffffa039478f8c4 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8062397f115 rsp=fffffa0393e86e70 rbp=ffffac0be6e28b78 r8=ffffac0be8d10008 r9=fffffa0393e86f20 r10=fffffa039478f5c0 r11=fffffa0393e86e20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy iaStorAC+0xdf115: fffff806`2397f115 488b86d0000000 mov rax,qword ptr [rsi+0D0h] ds:00000000`000000d0=???????????????? Resetting default scope STACK_TEXT: fffffa03`93e86b98 fffff806`1f609369 : 00000000`0000000a 00000000`000000d0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffffa03`93e86ba0 fffff806`1f605669 : 00000000`0000002a 00000000`00000000 00000000`00000034 00000000`0000000c : nt!KiBugCheckDispatch+0x69 fffffa03`93e86ce0 fffff806`2397f115 : fffffa03`93e86ec0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469 fffffa03`93e86e70 fffff806`2399aaf7 : fffffa03`93e86f38 ffffac0b`e8d10008 fffffa03`9478f5c0 fffffa03`93e86f20 : iaStorAC+0xdf115 fffffa03`93e86ee0 fffff806`2397a595 : fffffa03`93e86f20 ffffac0b`e8d31078 fffffa03`9478f5c0 ffffac0b`e4db90d0 : iaStorAC+0xfaaf7 fffffa03`93e86f10 fffff806`2397193a : 00000005`5bfa546e ffffac0b`e6ed9fb0 fffffa03`93e87038 fffff806`1f5618bd : iaStorAC+0xda595 fffffa03`93e86f50 fffff806`23970647 : 00000000`0000001c fffffa03`93e87130 fffffa03`93e87050 ffffac0b`e8d31078 : iaStorAC+0xd193a fffffa03`93e86fe0 fffff806`2396e0dd : ffffac0b`e49c8100 fffff806`1f49ae00 ffffac0b`e8d31078 fffff806`239d3020 : iaStorAC+0xd0647 fffffa03`93e87030 fffff806`2396cb41 : fffffa03`93e87750 00000000`00000000 fffff806`239d6280 ffffac0b`00000002 : iaStorAC+0xce0dd fffffa03`93e872c0 fffff806`23966d8b : 00000000`00000002 ffffac0b`e6e8c1f8 fffffa03`93e87750 00000000`00000003 : iaStorAC+0xccb41 fffffa03`93e87570 fffff806`238bc905 : fffffa03`93e87750 ffffac0b`e6e8c1f8 00000000`00000003 fffffa03`93e87750 : iaStorAC+0xc6d8b fffffa03`93e87620 fffff806`238b510d : 00000000`00000002 ffffac0b`e6e24010 fffffa03`93e87750 00000000`00000000 : iaStorAC+0x1c905 fffffa03`93e87660 fffff806`244a82dc : ffffac0b`e6e8c1a0 00000000`1f200000 ffffe401`ffffffff fffff806`00000000 : iaStorAC+0x1510d fffffa03`93e87700 fffff806`244a1df6 : 00000000`c00000bb ffffac0b`ead158a0 00000000`00000000 00000000`00000000 : storport!RaCallMiniportUnitControl+0x28 fffffa03`93e87730 fffff806`244a18b0 : ffffac0b`e6e8c1a0 00000000`00000001 00000000`00000001 ffffac0b`ead158a0 : storport!RaidUnitSendPowerToMiniport+0x62 fffffa03`93e87770 fffff806`244a1291 : ffffac0b`e6e0d1a0 00000000`00000000 ffffac0b`e6e8c1a0 00000000`4d706341 : storport!RaidUnitProcessSetDevicePowerIrp+0xb4 fffffa03`93e87830 fffff806`244a0e94 : ffffac0b`ead158a0 ffffac0b`e6e8c1a0 ffffac0b`e6e8c1a0 fffff806`2449c3cf : storport!RaidUnitSetDevicePowerIrp+0x175 fffffa03`93e87890 fffff806`244a0db2 : 00000000`00000002 ffffac0b`e6e8c1a0 ffffac0b`ead158a0 fffff806`244f9000 : storport!RaidUnitSetPowerIrp+0x68 fffffa03`93e878e0 fffff806`244a0c68 : ffffac0b`ead158a0 ffffac0b`ead15a48 ffffac0b`e6e8c050 ffffac0b`ead158a0 : storport!RaUnitPowerIrp+0x6a fffffa03`93e87930 fffff806`1f595f6f : ffffac0b`ead158a0 00000000`00000000 ffffac0b`ead158a0 fffff806`2333e2d1 : storport!RaDriverPowerIrp+0x98 fffffa03`93e87970 fffff806`1f48f83d : ffffac0c`038403b8 fffffa03`00000000 00000000`03540020 fffffa03`93e87a68 : nt!IopPoHandleIrp+0x3b fffffa03`93e879a0 fffff806`1f598239 : 00000000`00000008 fffff806`233901ba 00000000`00000001 fffff806`233901ba : nt!IofCallDriver+0x6d fffffa03`93e879e0 fffff806`2332cae2 : ffffac0b`ead158a0 fffff806`233901bc fffff806`23320000 fffff806`233a2130 : nt!IoCallDriver+0x9 fffffa03`93e87a10 fffff806`2332cbc1 : ffffac0b`e67fe000 ffffac0b`e6cb8010 ffffac0b`ead15a48 00000000`00000000 : ACPI!ACPIDispatchForwardPowerIrp+0x52 fffffa03`93e87a40 fffff806`2333e9b7 : ffffac0b`e6d5ec70 fffff806`2332cb00 ffffac0b`e6d5ecc0 ffffac0b`e6d5ec70 : ACPI!ACPIDeviceIrpForwardRequest+0xc1 fffffa03`93e87aa0 fffff806`23340399 : fffff806`233a2180 fffff806`2339f000 ffffac0b`e6d5ec70 00000000`00000002 : ACPI!ACPIDeviceCompleteRequest+0x11f fffffa03`93e87b00 fffff806`1f49a3fe : ffffe401`c584d240 fffffa03`93e87cb0 fffffa03`93e87e70 ffffac0c`00000002 : ACPI!ACPIDevicePowerDpc+0x5b9 fffffa03`93e87bb0 fffff806`1f4996e4 : 00000000`00000000 00000000`00000000 00000000`0000002a 00000000`0001439b : nt!KiExecuteAllDpcs+0x30e fffffa03`93e87d20 fffff806`1f5fe3f5 : 00000000`00000000 ffffe401`c584a180 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0x1f4 fffffa03`93e87fb0 fffff806`1f5fe1e0 : ffffac0c`12835320 fffff806`233238fa ffffac0b`e8b6fdd8 ffffac0c`12835320 : nt!KxRetireDpcList+0x5 fffffa03`9410d710 fffff806`1f5fd8ae : ffffac0b`e8b6f108 00000000`ffffffff ffff6c64`597a3008 fffff806`23326d56 : nt!KiDispatchInterruptContinue fffffa03`9410d740 fffff806`2333fd85 : fffff806`23325243 ffffac0c`12b5c760 ffffac0c`12b5c760 ffffac0c`12b5c760 : nt!KiDpcInterrupt+0x2ee fffffa03`9410d8d8 fffff806`23325243 : ffffac0c`12b5c760 ffffac0c`12b5c760 ffffac0c`12b5c760 00000000`00000400 : ACPI!ACPIDeviceCompleteGenericPhase+0xf5 fffffa03`9410d8e0 fffff806`23324685 : ffffac0b`e49c6000 ffffac0c`12b5c760 00000000`00000000 00000000`0000009a : ACPI!RunContext+0x833 fffffa03`9410da10 fffff806`2334a325 : ffffac0c`12b5c760 00000000`00000080 ffffac0c`12b5c760 00000000`00000492 : ACPI!InsertReadyQueue+0x2a5 fffffa03`9410da70 fffff806`23348c97 : ffffac0c`12b5c760 00000000`00000000 00000000`00000000 fffffa03`94104c00 : ACPI!RestartCtxtPassive+0x35 fffffa03`9410daa0 fffff806`1f555a05 : ffffac0b`e46bf040 fffff806`23348b90 00000000`00000000 ffffac0b`e46a1100 : ACPI!ACPIWorkerThread+0x107 fffffa03`9410db10 fffff806`1f5fea08 : ffffe401`c584a180 ffffac0b`e46bf040 fffff806`1f5559b0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 fffffa03`9410db60 00000000`00000000 : fffffa03`9410e000 fffffa03`94107000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: iaStorAC+df115 MODULE_NAME: iaStorAC IMAGE_NAME: iaStorAC.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: df115 FAILURE_BUCKET_ID: AV_iaStorAC!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {2c48c538-0bdc-1937-76bb-851b68345fca} Followup: MachineOwner
SOMEONE PLEASE HELP ME FIX THIS ISSUE. WHAT WILL BE THE CAUSE?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @NitishKaashyap
Thank you for posting on the Intel® communities.
We found you have another thread describing the same issue as this one. To avoid duplication of efforts and duplicate threads, we will close this thread and we recommend continuing working on your other thread. Thank you for your understanding.
Best regards,
Andrew G.
Intel Customer Support Technician
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @NitishKaashyap
Thank you for posting on the Intel® communities.
We found you have another thread describing the same issue as this one. To avoid duplication of efforts and duplicate threads, we will close this thread and we recommend continuing working on your other thread. Thank you for your understanding.
Best regards,
Andrew G.
Intel Customer Support Technician
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page