Blue screen errors and crashing

Question

The extract is from minidump generated after blue screen crash. Can you please help in fixing?

Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [F:\Venkat\031922-7671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

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 = 0xfffff80519400000 PsLoadedModuleList = 0xfffff8051a02a2d0
Debug session time: Sat Mar 19 04:11:56.972 2022 (UTC + 5:30)
System Uptime: 3 days 8:11:09.268
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805197f7620 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff80520875160=000000000000001e
0: kd> !analyze -v

---

• *
• Bugcheck Analysis *
• *

  ---

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80536c67fad, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffe28f02e006c8, Parameter 1 of the exception

Debugging Details:

---

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3093

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 23711

Key  : Analysis.Init.CPU.mSec
Value: 406

Key  : Analysis.Init.Elapsed.mSec
Value: 62992

Key  : Analysis.Memory.CommitPeak.Mb
Value: 96

Key  : Memory.System.Errors.BadPageCount
Value: 466

Key  : Memory.System.Errors.ScrubErrors
Value: 466

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: 031922-7671-01.dmp

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80536c67fad

BUGCHECK_P3: 0

BUGCHECK_P4: ffffe28f02e006c8

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

BAD_PAGES_DETECTED: 1d2

TRAP_FRAME: fffff8052085eef0 -- (.trap 0xfffff8052085eef0)
Unable to read trap frame at fffff805`2085eef0

STACK_TEXT:
fffff80520875158 fffff805198f5cae : 000000000000001e ffffffffc0000005 fffff80536c67fad 0000000000000000 : nt!KeBugCheckEx
fffff80520875160 fffff805198004df : fffff805198f5c8c 0000000000000000 0000000000000000 0000000000000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff805208751a0 fffff805196e6f97 : fffff80520875710 0000000000000000 fffff8052085fb60 fffff805197fb18e : nt!RtlpExecuteHandlerForException+0xf
fffff805208751d0 fffff805196e5b96 : fffff8052085ee48 fffff80520875e20 fffff8052085ee48 ffffe28f22d91020 : nt!RtlDispatchException+0x297
fffff805208758f0 fffff805197f84b2 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDispatchException+0x186
fffff80520875fb0 fffff805197f8480 : fffff805198096a5 ffffe28f02e006c8 fffff8052085ee10 ffffe28f26e22010 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff8052085ed08 fffff805198096a5 : ffffe28f02e006c8 fffff8052085ee10 ffffe28f26e22010 ffffe28f26e22010 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff8052085ed10 fffff80519805843 : 0000000000000000 ffffe28f22dead01 0000000000000000 0000000000000002 : nt!KiExceptionDispatch+0x125
fffff8052085eef0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x443

SYMBOL_NAME: PAGE_NOT_ZERO

MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: PAGE_NOT_ZERO_AV

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {91fefd05-7a2b-5d37-e27f-7af624353ffc}

Followup: MachineOwner

---

*** Memory manager detected 466 instance(s) of page corruption, target is likely to have memory corruption.

Answer 1

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.