bsod Uncorrectable Error

[nosam1g]

Hey guys good day , ive been running into a problem ,
bsod error - whea uncorrectable error, i got this like 20 times
kernel_security_check_failure , and got this 1 time



here are my specs
i9-10900k - Water Cooled
asus apex z490
3600 32gig g.skill
2080ti Hybrid
1200w PSU
1tb m.2
500gig m.2
3tb hdd
1tb ssd

So a little back story when i first got the pc i had 4500mhz ram 16gig team group ram , and i installed everything it ran good at 4500mhz xmp oc for about 4 months. Then out of the blue i started getting bsod. This was the only thing i overclocked. So i got a intially bsod and i thought it was my profile corrupt, so i created another profile. Bsod happened again. So i set my ram to default at 2400mhz stock. There was no cpu oc besides maybe the auto asus bios. One really odd thing to note is i only get BSOD when im literally doing nothing. Like surfing youtube, browsing internet or just chillen on my pc. Whenever im in games and high cpu intensive stuff no bsod , i only bsod when im doing nothing intense.
So i keep getting bsod and its bugging at this point , so i do a clean re install through windows 10 repair. Still after reinstall im still getting BSOD
i look up the error uncorrectable error , and it states mainly due to hardware failure. So im thinking its my ram since i overclocked it at 4500mhz for like 5 months. I reset all my bios settings to default .. cpu is def , and ram. Bam once again BSod with everyhthing on stock settings. Now im just getting annoyed. Im thinking my ram is done. So i ordered new ram which is my current setup 3600mhz 32 gig g.skillz on xmp1. Nope still bsod, but this time i oc my cpu 5.1 , 1.365v. SO now im at the point where i let my bios OC my cpu on Auto , but have my ram on 3600mhz xmp1. At this point im thinking its my CPU ? it literally only happens when im browsing through chrome. Please if anyone has any idea what this issue is , let me know !

[nosam1g]

It lists the errors at the bottom. Main one I searched was
IMAGE_NAME: nvlddmkm.sys
Which is Nivida Driver Error from Software Driver.

Still troubleshooting , but looks like my BSOD is related to my Nivida Drivers



*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff80382fe0e36, The address that the exception occurred at
Arg3: ffff8a81d3bd5ec8, Exception Record Address
Arg4: ffff8a81d3bd5700, Context Record Address

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

Page 84a397 not present in the dump file. Type ".hh dbgerr004" for details
Page 84a397 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.Sec
Value: 1

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 7

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80382fe0e36

BUGCHECK_P3: ffff8a81d3bd5ec8

BUGCHECK_P4: ffff8a81d3bd5700

EXCEPTION_RECORD: ffff8a81d3bd5ec8 -- (.exr 0xffff8a81d3bd5ec8)
ExceptionAddress: fffff80382fe0e36 (nvlddmkm+0x00000000007c0e36)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048

CONTEXT: ffff8a81d3bd5700 -- (.cxr 0xffff8a81d3bd5700)
rax=0000000000000000 rbx=0000000000000000 rcx=ffff9a84ccb131d8
rdx=0000000000000000 rsi=ffffd18f76a76a7d rdi=ffff9a84cca7d000
rip=fffff80382fe0e36 rsp=ffff8a81d3bd6100 rbp=ffff9a84cca9ef20
r8=0000000000000009 r9=0000000000000000 r10=0000000000000000
r11=ffffd18f76a76ae9 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=ffff9a84cca7d180
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nvlddmkm+0x7c0e36:
fffff803`82fe0e36 ff5048 call qword ptr [rax+48h] ds:002b:00000000`00000048=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

READ_ADDRESS: 0000000000000048

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

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff8a81`d3bd6100 fffff803`82fcd033 : 00000000`00000001 ffff8a81`00000000 00000000`00000000 ffff9a84`ccb131d8 : nvlddmkm+0x7c0e36
ffff8a81`d3bd6160 fffff803`82fcd9e3 : ffff9a84`cca7d180 00000000`00001c77 00000000`00081d9a ffffd18f`76a135e9 : nvlddmkm+0x7ad033
ffff8a81`d3bd7440 fffff803`8300c209 : ffff8a81`d3bd7738 00000000`00000000 ffffd18f`76895387 ffffd18f`768f798e : nvlddmkm+0x7ad9e3
ffff8a81`d3bd7500 fffff803`8300c0e8 : ffff8a81`d3bd7738 ffffd18f`768f7986 ffff8a81`d3bd76b0 ffff9a84`ccdf1000 : nvlddmkm+0x7ec209
ffff8a81`d3bd7550 fffff803`834602ea : ffff9a84`c6c87000 ffff8a81`d3bd76b0 ffff9a84`ccdf1000 ffff8a81`d3bd7738 : nvlddmkm+0x7ec0e8
ffff8a81`d3bd7580 fffff803`7ec1b917 : fffff803`83460257 ffff9a84`ca761eb0 ffff8a81`d3bd77e0 fffff803`7edc0fbf : nvlddmkm+0xc402ea
ffff8a81`d3bd7630 fffff803`7ec5f98f : ffffd18f`8860b540 ffffd18f`8860b540 ffffd18f`8860b540 ffff9a84`ccdf1000 : dxgkrnl!DXGADAPTER::_DdiCollectDbgInfoNoLocks+0xd7
ffff8a81`d3bd76e0 fffff803`7ec609f4 : ffff9a84`00000000 ffff9a84`d1355460 00000000`00000000 00000000`00000000 : dxgkrnl!TdrCollectDbgInfoStage1+0x38f
ffff8a81`d3bd7820 fffff803`8617d6c3 : ffff9a84`d1355460 00000000`00989680 ffff8a81`d3bd7a80 00000000`000214a5 : dxgkrnl!TdrIsRecoveryRequired+0x154
ffff8a81`d3bd7850 fffff803`861e59c7 : ffff9a84`d0443060 00000000`00989680 ffff9a84`cce22000 ffff9a84`cce22000 : dxgmms2!VidSchiReportHwHang+0x62f
ffff8a81`d3bd7950 fffff803`8614b74f : ffff9a84`d0443060 00000000`00021431 00000000`00989680 00000000`00000000 : dxgmms2!VidSchiCheckHwProgress+0x282e7
ffff8a81`d3bd79c0 fffff803`861cb1a5 : ffff9a84`d1020000 ffff9a84`cce22000 ffff9a84`d1020010 ffff9a84`d06cf7b0 : dxgmms2!VidSchiScheduleCommandToRun+0x4f
ffff8a81`d3bd7a80 fffff803`861cb15a : ffff9a84`cce22400 fffff803`861cb090 ffff9a84`cce22000 fffff803`63c1a100 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffff8a81`d3bd7ad0 fffff803`68d17e25 : ffff9a84`c7e9f0c0 fffff803`00000001 ffff9a84`cce22000 000fa4ef`b59bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff8a81`d3bd7b10 fffff803`68dfcdd8 : fffff803`63c1a180 ffff9a84`c7e9f0c0 fffff803`68d17dd0 049d1230`00000001 : nt!PspSystemThreadStartup+0x55
ffff8a81`d3bd7b60 00000000`00000000 : ffff8a81`d3bd8000 ffff8a81`d3bd1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+7c0e36

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffff8a81d3bd5700 ; kb

BUCKET_ID_FUNC_OFFSET: 7c0e36

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner