[SOLVED] Many BSOD'S... Have a minidump file and was wondering if someone knows what it is

[OpticD3ath]

Microsoft (R) Windows Debugger Version 10.0.19041.685 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122720-5390-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
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80332e00000 PsLoadedModuleList = 0xfffff80333a2a2b0
Debug session time: Sun Dec 27 14:03:05.397 2020 (UTC - 6:00)
System Uptime: 0 days 2:14:23.020
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
8: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80345262944, The address that the exception occurred at
Arg3: fffffb0d0ac4bbb8, Exception Record Address
Arg4: fffffb0d0ac4b3f0, Context Record Address

Debugging Details:
------------------

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

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.Sec
Value: 5

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-8E06VRU

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 36

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80345262944

BUGCHECK_P3: fffffb0d0ac4bbb8

BUGCHECK_P4: fffffb0d0ac4b3f0

EXCEPTION_RECORD: fffffb0d0ac4bbb8 -- (.exr 0xfffffb0d0ac4bbb8)
ExceptionAddress: fffff80345262944 (dxgmms2!VIDMM_PAGE_TABLE_BASE::IsResident)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffffb0d0ac4b3f0 -- (.cxr 0xfffffb0d0ac4b3f0)
rax=ffffac853a33e000 rbx=ffffe1033d0f4901 rcx=8000000000000000
rdx=ffffac8539eae260 rsi=ffffac8539eae260 rdi=8000000000000000
rip=fffff80345262944 rsp=fffffb0d0ac4bdf8 rbp=ffffe1033d247000
r8=0000000200c20000 r9=000000005d4bc001 r10=000000000000085b
r11=000000005d4bc000 r12=0000000200c20000 r13=ffffac8539eae201
r14=0000000000000800 r15=0000000200c20000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
dxgmms2!VIDMM_PAGE_TABLE_BASE::IsResident:
fffff80345262944 488b5108 mov rdx,qword ptr [rcx+8] ds:002b:8000000000000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff80333afa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80333a0f330: Unable to get Flags value from nt!KdVersionBlock
fffff80333a0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffffb0d0ac4bdf8 fffff803452d1feb : 0000000000000002 0000000200000000 0000000200000002 0000000200000000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::IsResident
fffffb0d0ac4be00 fffff803452f8985 : ffffe1033d0f4901 0000000000000000 0000000200c20000 0000000000000001 : dxgmms2!VIDMM_PAGE_DIRECTORY::EvictPageDirectory+0x2f
fffffb0d0ac4bf00 fffff803452c0093 : 000000005d4bc000 ffffac8539eae260 00000002000c0000 0000000000000001 : dxgmms2!VIDMM_PAGE_DIRECTORY::EvictPageDirectory+0x269c9
fffffb0d0ac4c000 fffff803452bf33c : ffffe1033d0f4968 ffffac8539eae260 000000005d4bc000 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xce3
fffffb0d0ac4c170 fffff803452be109 : ffffe10332e53000 ffffe1033d152280 0000000000000000 0000000000000000 : dxgmms2!CVirtualAddressAllocator::UncommitVirtualAddressRange+0xf4
fffffb0d0ac4c280 fffff803452b48a8 : 0000000000000002 fffff8034525241b ffffac85394b0ac8 fffff80300000003 : dxgmms2!VIDMM_GLOBAL::MakeOneVirtualAddressRangeNotResident+0x165
fffffb0d0ac4c710 fffff803452b2b6b : ffffac8539014b30 fffffb0d0ac4c800 ffffac8539014c50 ffffe1033ce7adb0 : dxgmms2!VIDMM_GLOBAL::MakeVirtualAddressRangeNotResident+0xc0
fffffb0d0ac4c770 fffff803452b5a27 : ffffac85394b0a90 fffffb0d0ac4c8c0 ffffe1033d247000 0000000000000000 : dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0x23b
fffffb0d0ac4c7c0 fffff803452da148 : ffffe1033d247000 ffffe1033d250c10 ffffe1033d247000 ffffe1033d247000 : dxgmms2!VIDMM_GLOBAL:rocessDeferredCommand+0x8f7
fffffb0d0ac4ca00 fffff803452e43d9 : ffffac8534c7c950 ffffe1033d152200 0000000000000000 0000000003037200 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
fffffb0d0ac4cbe0 fffff80333117e25 : ffffe1033d152280 fffff803452e43d0 ffffac8534c7c950 000f8067b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
fffffb0d0ac4cc10 fffff803331fcdd8 : ffff870139080180 ffffe1033d152280 fffff80333117dd0 00006b76ffffffe8 : nt!PspSystemThreadStartup+0x55
fffffb0d0ac4cc60 0000000000000000 : fffffb0d0ac4d000 fffffb0d0ac47000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_PAGE_TABLE_BASE::IsResident+0

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1131

STACK_COMMAND: .cxr 0xfffffb0d0ac4b3f0 ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_PAGE_TABLE_BASE::IsResident

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a89038c2-13a7-ca54-5acb-564f12261b9f}

Followup: MachineOwner
---------

 

[Colif]

dxgmms2!VIDMM_PAGE_TABLE_BASE::IsResident

direct X crashed. Its victim, it was caused by GPU drivers.
Run ddu, delete current drivers in safe mode and reinstall new drivers for the card - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. copy that file to documents
2. upload the copy from documents to a file sharing web site,
3. and share the link in your thread so we can help fix the problem

just in case you get more.