Question PC crash and critical error message ?

[Jblaze24]

PC has been crashing for few months now but only when gaming. It passes CPU stress test and memtest86 but crashes in games and on GPU stress test everytime. I tried new PSU but still crashing. uninstalled and re-installed Nvidia and windows drivers and all drivers in task manager and still crashing. I cleaned and repasted GPU and it worked perfect for 5 days and started crashing again today when gaming and hasn't stopped. I don't think it is drivers because it worked for 5 day's in a row after cleaning it. if the driver is broke it wouldn't run at all correct?

Specs: i7 9700k
RTX2080 super
Z390 phantom gaming 4s-ib
Seasonic focus gold 750watt PSU
2x8GB ram
480Gb SSD
1TB harddrive

I want to buy new GPU but figured I would post the dump files here to see if anyone can notice anything obvious cause I don't know what it means. Thanks in advance


Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff83015af95000, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff8053d60a706, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_246e95e4066041ad\nvlddmkm.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Write

Key : Analysis.CPU.mSec
Value: 2296

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 43134

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

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

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

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: 50

BUGCHECK_P1: ffff83015af95000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8053d60a706

BUGCHECK_P4: 0

READ_ADDRESS: ffff83015af95000

MM_INTERNAL_CODE: 0

IMAGE_NAME: nvlddmkm.sys

MODULE_NAME: nvlddmkm

FAULTING_MODULE: fffff8053ce10000 nvlddmkm

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: ffffd304ddf22f60 -- (.trap 0xffffd304ddf22f60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff83015af94000 rbx=0000000000000000 rcx=0000000000000400
rdx=00000000000bf016 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8053d60a706 rsp=ffffd304ddf230f0 rbp=0000000000000000
r8=0000000000002614 r9=00000000000be066 r10=0000000000000000
r11=ffffd304ddf23130 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x7fa706:
fffff8053d60a706 893488 mov dword ptr [rax+rcx*4],esi ds:ffff83015af95000=????????
Resetting default scope

STACK_TEXT:
ffffd304ddf22cb8 fffff80521a5ec7d : 0000000000000050 ffff83015af95000 0000000000000002 ffffd304ddf22f60 : nt!KeBugCheckEx
ffffd304ddf22cc0 fffff805218cf670 : 0000000000000005 0000000000000002 ffffd304ddf22fe0 0000000000000000 : nt!MiSystemFault+0x1715bd
ffffd304ddf22dc0 fffff80521a0675e : fffff805378c260e 0000000000000001 0000000000000000 0000000000000000 : nt!MmAccessFault+0x400
ffffd304ddf22f60 fffff8053d60a706 : ffffb206b23af0b0 0000000000000028 fffff8053d63bf69 fffff8053d600100 : nt!KiPageFault+0x35e
ffffd304ddf230f0 fffff8053da58a22 : 0000000000000001 ffffb206b23af0b0 000000000000000f 0000000000000000 : nvlddmkm+0x7fa706
ffffd304ddf23140 fffff8053ce23603 : ffffb206b23a6000 000000000000000f 0000000000000000 0000000000050201 : nvlddmkm+0xc48a22
ffffd304ddf231e0 fffff8053d9a52a0 : 0000000000000000 ffffd304ddf23289 ffffb206b1cec000 ffffd304ddf1d000 : nvlddmkm+0x13603
ffffd304ddf23220 fffff8053d9adcfe : 0000000000000000 0000000000000005 0000000000000001 ffffb206b1cec000 : nvlddmkm+0xb952a0
ffffd304ddf232f0 fffff8053dc82788 : 0000000000000001 0000000000000005 ffffb206b1cca000 0000000000000001 : nvlddmkm+0xb9dcfe
ffffd304ddf23370 fffff8053dc81fa7 : 0000000000000000 0000000000000000 0000000000000000 a58d80b900000002 : nvlddmkm+0xe72788
ffffd304ddf23440 fffff8053dcad2e6 : ffffb206b1cca000 ffffd304ddf235b0 0000000000000001 0000000000000007 : nvlddmkm+0xe71fa7
ffffd304ddf234a0 fffff8053dcc0431 : fffff8053dcad18f 0000000000000001 0000000000000002 00000000ffffffff : nvlddmkm+0xe9d2e6
ffffd304ddf235e0 fffff805378c260e : 3053514d4c364c00 4c010a3038323838 ffff33dcf9c758c1 ffffb206b1cca000 : nvlddmkm+0xeb0431
ffffd304ddf23620 fffff805378c1b5f : 0000000000000005 ffffd304ddf236e1 0000000000000000 ffffb206b1430180 : dxgkrnl!DpiDxgkDdiSetPowerState+0x5a
ffffd304ddf23680 fffff805378c2a8e : 0000000000000000 ffffb206b032c010 0000000000000001 0000000000000001 : dxgkrnl!DpiFdoSetAdapterPowerState+0x15f
ffffd304ddf23740 fffff805378c1ee1 : ffffd304ddf23800 0000000000000004 ffffb206ab09f9d0 ffffb206b032c170 : dxgkrnl!DpiFdoHandleDevicePower+0x2ee
ffffd304ddf237e0 fffff805378c3431 : ffffb206b032c010 ffffb206b1430180 ffffb206b1430030 ffffb206b1430030 : dxgkrnl!DpiFdoDispatchPower+0x21
ffffd304ddf23810 fffff8053dcbd230 : 0000000000000000 ffffd304ddf239d9 0000000000000000 ffffb206b1cca000 : dxgkrnl!DpiDispatchPower+0xe1
ffffd304ddf23930 fffff8053dcbc62e : ffffb206b1430030 ffffb206b1cca000 ffffb206b09b8640 ffffb20600000000 : nvlddmkm+0xead230
ffffd304ddf23a40 fffff8052199d889 : ffffb206b09b8640 ffffd304ddf23af0 ffffb206b032c010 ffffb206ab986000 : nvlddmkm+0xeac62e
ffffd304ddf23a70 fffff8052194edc5 : fffffffffa0a1f00 fffff8052199d6b0 ffffb206b3ef8330 00000000000000ee : nt!PopIrpWorker+0x1d9
ffffd304ddf23b10 fffff805219ffbe8 : fffff8051dea0180 ffffb206b09b8640 fffff8052194ed70 0000000000000246 : nt!PspSystemThreadStartup+0x55
ffffd304ddf23b60 0000000000000000 : ffffd304ddf24000 ffffd304ddf1d000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+7fa706

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 7fa706

FAILURE_BUCKET_ID: AV_W_(null)_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {838100fa-f28b-2ef7-d702-e31713cb338c}

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

7: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff8053ce10000 fffff8053f8b8000 nvlddmkm (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_246e95e4066041ad\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Thu Jun 23 18:18:39 2022 (62B4F4CF)
CheckSum: 029BBFF9
ImageSize: 02AA8000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

 

[Colif]

nvlddmkm.sys

that ones blaming Nvidia drivers.

I would run DDU in safe mode, uninstall Nvidia drivers, then once back in normal mode, either:

1. download drivers from Nvidia; or
2. Run windows update and let it find older Nvidia drivers that may be more stable than current ones.

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

in case it continues
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. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

if the driver is broke it wouldn't run at all correct?

not necessarily. It can work for most of the time and just not in some cases. I seen Nvidia drivers mess up enough.

If you think its the GPU you better testing it in another PC and if it still does it there, its the card. Too many unknowns in the system it plays up in.
I have a 2070S, its hard to find something better than it still. I imagine a 2080S is only bettered by a 3090 now.

 

[Jblaze24]

ya I will try to re-install the drivers with DDU again and see if anything changes. Would be simple to try in someone else's rig but I don't know anyone. How long should graphics card last? probably had it 2- 2 1/2 years.

The crashes started slow about 2-3 months ago and just got worse over time till now it is impossible to play. That's why I'm leaning towards GPU and the fact that it only crashes in games and GPU stress test

If drivers doesn't work I will try to re-paste again and just buy new GPU if it crashes again.

1 more question. What about replacing thermal pads too? I did notice one of the edges was falling off on one of them. Is that something I can just order from Amazon or somewhere?

 

[Colif]

How long should graphics card last? probably had it 2- 2 1/2 years.

I would expect longer than that. Looking around average seems to be it can last 5-6 years and longer in cool temps. My last GTX 980 lasted 5 years before it started to run hot. I coincidentally was replacing GPU same week anyway.

MY 2070S is only 2 years old, I would expect it to last at least that if not longer.

What BSOD codes are you getting? I can't tell from that report.. All it tells me is you aren't getting WHEA errors

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. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

1 more question. What about replacing thermal pads too? I did notice one of the edges was falling off on one of them. Is that something I can just order from Amazon or somewhere?

i would take photos of what it looks like and make a post asking about it in the Graphics card area as I am not sure.

 

[Jblaze24]

Ok I got the mini dump files if someone can check it out. will post below.

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000033, The subtype of the BugCheck:
Arg2: ffffda8334f24010
Arg3: 0000000000000000
Arg4: 0000000000000000

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3702

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 32711

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

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

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

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


ORIGINAL_CAB_PATH: C:\Users\Bamac\OneDrive\Desktop\Minidump.zip

FILE_IN_CAB: Minidump/062722-7078-01.dmp

FILE_IN_CAB: Minidump/071422-5843-01.dmp

BUGCHECK_CODE: 10e

BUGCHECK_P1: 33

BUGCHECK_P2: ffffda8334f24010

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffea8fa0996f98 fffff80135f33ad0 : 000000000000010e 0000000000000033 ffffda8334f24010 0000000000000000 : nt!KeBugCheckEx
ffffea8fa0996fa0 fffff801353ed30d : 0000000000000000 ffffda8334f24110 ffffb48fe4969000 0000000000000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffea8fa0996fe0 fffff8013536151a : ffffda8334f24010 0000000000000000 ffffda83345fd310 0000000000000001 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x33179
ffffea8fa0997020 fffff801353ba14d : ffffda8334f24010 0000000000000000 ffffda83345fd310 ffffb48fe47e9010 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::scalar deleting destructor'+0xe ffffea8fa0997050 fffff801353ba81d : 0000000000000000 ffffda83345fd310 ffffda8334f24010 ffffb48fe5454080 : dxgmms2!VIDMM_PROCESS::DestroyAdapterInfo+0xe5 ffffea8fa0997080 fffff801353614fe : ffffda83348b1750 ffffea8fa0997239 ffffb48fe47e9010 0100000000100000 : dxgmms2!VIDMM_PROCESS::CloseAdapter+0xb9 ffffea8fa0997140 fffff80135ce540a : 0000000000000000 0000000000000000 0000000040009a40 0000000000000000 : dxgmms2!VidMmCloseAdapter+0x1e ffffea8fa0997170 fffff80135c9295f : ffffb48fe0d60000 0000000000000000 ffffb48fe4ada690 fffff8011e050f23 : dxgkrnl!DXGPROCESS_ADAPTER_INFO::CloseVidMmAdapter+0x2e ffffea8fa09971a0 fffff80135c63c0d : ffffda83348b1750 ffffda8300000002 ffffda83348b1750 ffffb48fe47e9010 : dxgkrnl!DXGPROCESS::DestroyAdapterInfo+0x143 ffffea8fa09972a0 fffff80135c62061 : ffffb48fe4820000 fffff80100000001 ffffb48fe4820000 ffffea8fa0997480 : dxgkrnl!DXGPROCESS::CloseAdapter+0xf9 ffffea8fa0997330 fffff80135c93475 : ffffb48feb1ac380 ffffea8fa0997480 00000000000002c9 ffffda8334622460 : dxgkrnl!DXGADAPTER::DestroyHandle+0x11d ffffea8fa0997380 fffff80135c943f9 : ffffda8334622460 ffffb48fe482b3a0 ffffda8334622460 ffffea8fa09977f9 : dxgkrnl!DXGPROCESS::Destroy+0x341 ffffea8fa09975f0 fffff80135b86841 : 0000000000000000 ffffb48feb403190 0000000000000000 fffff80120c7c078 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105 ffffea8fa0997740 fffff8011e47373f : 0000000000000000 ffffb48fe0374c10 ffffb48fe549e340 ffffb48fe5388100 : dxgkrnl!DxgkProcessNotify+0x1a1 ffffea8fa0997790 fffff8011e44d6d4 : ffffb48fe549e300 ffffb48fe549e340 0000000000000000 0000000000000000 : nt!PspCallProcessNotifyRoutines+0x213 ffffea8fa0997860 fffff8011e3e359a : ffffb48fe54544b8 0000000000000000 0000000000000000 0000000000000000 : nt!PspExitProcess+0x70 ffffea8fa0997890 fffff8011e4f62fe : ffffb48fd00002fe 0000000000000001 0000000000000000 000000bd29111000 : nt!PspExitThread+0x5b2 ffffea8fa0997990 fffff8011e2097b5 : ffffb48fe549e340 ffffb48fe5454080 ffffea8fa0997a80 ffffb48fe549e340 : nt!NtTerminateProcess+0xde ffffea8fa0997a00 00007ffcbad0d2c4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 000000bd2927fc98 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffcbad0d2c4


SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+33179

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1767

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 33179

FAILURE_BUCKET_ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {590e82e4-fa32-3e14-0943-e6b01c6637c4}

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

 

[Colif]

did you ask about that thermal pad?