question

DericC-4194 avatar image
0 Votes"
DericC-4194 asked SQx answered

BSOD once a day

I get BSOD IRQL_NOT_LESS_OR_EQUAL constantly and other BSOD having to do with "Kernel" I did have ram issues a month or so ago but that fixed simply by reseating my ram. This may help. If any additional info is needed please let me know.

https://www.dropbox.com/s/yj45dl2x1fw3p32/032321-11375-01.dmp?dl=0

Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\032321-11375-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available 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 = 0xfffff803`7f400000 PsLoadedModuleList = 0xfffff803`8002a490 Debug session time: Tue Mar 23 03:36:11.612 2021 (UTC - 7:00) System Uptime: 0 days 8:56:23.224 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........... Loading User Symbols Loading unloaded module list ........................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`7f7f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff803`8406c990=000000000000000a 0: 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: 0000001158adeb4b, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000001158adeb4b, address which referenced memory Debugging Details: ------------------ *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4828 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 12705 Key : Analysis.Init.CPU.mSec Value: 327 Key : Analysis.Init.Elapsed.mSec Value: 3419 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 BUGCHECK_CODE: d1 BUGCHECK_P1: 1158adeb4b BUGCHECK_P2: 2 BUGCHECK_P3: 8 BUGCHECK_P4: 1158adeb4b READ_ADDRESS: fffff803800fb390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse 0000001158adeb4b PROCESS_NAME: System BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 TRAP_FRAME: fffff8038406cad0 -- (.trap 0xfffff8038406cad0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff8038406ccc0 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=0000001158adeb4b rsp=fffff8038406cc60 rbp=0000006a81fffa18 r8=0000000000000000 r9=fffff8037bd6f180 r10=fffff80380124a00 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc 00000011`58adeb4b ?? ??? Resetting default scope FAILED_INSTRUCTION_ADDRESS: +0 00000011`58adeb4b ?? ??? STACK_TEXT: fffff803`8406c988 fffff803`7f807b69 : 00000000`0000000a 00000011`58adeb4b 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff803`8406c990 fffff803`7f803e69 : 00000000`00000000 00000000`00000000 fffff803`8406cb18 fffff803`7f670188 : nt!KiBugCheckDispatch+0x69 fffff803`8406cad0 00000011`58adeb4b : 00000000`00000000 00007ffa`9ca2cc94 00000000`00000033 00000000`00000246 : nt!KiPageFault+0x469 fffff803`8406cc60 00000000`00000000 : 00007ffa`9ca2cc94 00000000`00000033 00000000`00000246 0000006a`81fff9e8 : 0x00000011`58adeb4b SYMBOL_NAME: nt!KiPageFault+469 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.867 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 469 FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403} Followup: MachineOwner ---------

qna-feedback
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SQx avatar image
0 Votes"
SQx answered

Hello,

Could you please upload all minidump files that are present in the C:\Windows\Minidump ?

P.S. It is difficult to say anything yet. I need more data to analyze the above problem.

Thanks.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.