Question Whenever I try to play games they either crash or my entire system blue screens.

Jan 15, 2021
5
2
15
0
Recently when I’ve been playing CSGO my screen will freeze but I’ll still be able to control myself and move/shoot as I can hear this through my headset even when the screen is frozen. I thought it was just CSGO but I tried to boot up valorant and it crashed saying there was an issue with the graphics driver and that it crashed.

I did a fresh install of my graphics driver, same issue occurred, I then decided to run cyberpunk at max settings to see if it would crash and that blue screened my PC.

I’m not sure what is going on, I am in the process of updating my bios to see if that might fix the issue.

Any help would be appreciated.

(Note: I’ve had this PC for over a year now and have had no issues up until this point)

PC Specs:
GPU - ASUS ROG Strix 2080 Ti
CPU - Ryzen 9 3900x
Memory - Trident Z Neo 2 x 16Gb 3600 MHz
Storage - Intel SSD 660P 1TB
Motherboard - ROG Crosshair Hero VIII (Wifi)
 
Recently when I’ve been playing CSGO my screen will freeze but I’ll still be able to control myself and move/shoot as I can hear this through my headset even when the screen is frozen. I thought it was just CSGO but I tried to boot up valorant and it crashed saying there was an issue with the graphics driver and that it crashed.

I did a fresh install of my graphics driver, same issue occurred, I then decided to run cyberpunk at max settings to see if it would crash and that blue screened my PC.

I’m not sure what is going on, I am in the process of updating my bios to see if that might fix the issue.

Any help would be appreciated.

(Note: I’ve had this PC for over a year now and have had no issues up until this point)

PC Specs:
GPU - ASUS ROG Strix 2080 Ti
CPU - Ryzen 9 3900x
Memory - Trident Z Neo 2 x 16Gb 3600 MHz
Storage - Intel SSD 660P 1TB
Motherboard - ROG Crosshair Hero VIII (Wifi)
a little over kill for some cs go but hey, have you tried bios update?
and verifying steam files
 
Jan 15, 2021
5
2
15
0
This is the blue screen dump message.


***
  • *
  • 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: fffff80774810e36, The address that the exception occurred at
Arg3: ffff9908434e4ef8, Exception Record Address
Arg4: ffff9908434e4730, Context Record Address

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


KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: String

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 2765

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 6277

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80774810e36

BUGCHECK_P3: ffff9908434e4ef8

BUGCHECK_P4: ffff9908434e4730

EXCEPTION_RECORD: ffff9908434e4ef8 -- (.exr 0xffff9908434e4ef8)
ExceptionAddress: fffff80774810e36 (nvlddmkm+0x00000000007c0e36)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00002b202b202b68
Attempt to read from address 00002b202b202b68

CONTEXT: ffff9908434e4730 -- (.cxr 0xffff9908434e4730)
rax=00002b202b202b20 rbx=0000000000000000 rcx=ffffbe098013a1d8
rdx=0000000000000000 rsi=ffff8685729ea341 rdi=ffffbe09800a4000
rip=fffff80774810e36 rsp=ffff9908434e5130 rbp=ffffbe09800c5f20
r8=000000000000000d r9=0000000000000000 r10=0000000000000000
r11=ffff8685729ea3ad r12=0000000000000000 r13=0000000000000000
r14=0000000000000002 r15=ffffbe09800a4180
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:
fffff80774810e36 ff5048 call qword ptr [rax+48h] ds:002b:00002b202b202b68=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

READ_ADDRESS: 00002b202b202b68

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: 00002b202b202b68

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff9908434e5130 fffff807747fd033 : 0000000000000001 ffff990800000000 0000000000000000 ffffbe098013a1d8 : nvlddmkm+0x7c0e36
ffff9908434e5190 fffff807747fd9e3 : ffffbe09800a4180 00000000000036b8 00000000000ce4c9 ffff868572986ead : nvlddmkm+0x7ad033
ffff9908434e6470 fffff8077483c209 : ffff9908434e6768 0000000000000000 ffff86857285537a ffff8685728b8be1 : nvlddmkm+0x7ad9e3
ffff9908434e6530 fffff8077483c0e8 : ffff9908434e6768 ffff8685728b8bd9 ffff9908434e66e0 ffffbe0980482000 : nvlddmkm+0x7ec209
ffff9908434e6580 fffff80774c902ea : ffffbe097a6e2000 ffff9908434e66e0 ffffbe0980482000 ffff9908434e6768 : nvlddmkm+0x7ec0e8
ffff9908434e65b0 fffff8076e2ab916 : fffff80774c90257 ffffbe09802e4e70 ffff9908434e6810 fffff8076e450fbf : nvlddmkm+0xc402ea
ffff9908434e6660 fffff8076e2ef98f : ffff86858a32dc60 ffff86858a32dc60 ffff86858a32dc60 ffffbe0980482000 : dxgkrnl!DXGADAPTER::_DdiCollectDbgInfoNoLocks+0xd6
ffff9908434e6710 fffff80773a20ef2 : ffffbe0980571000 0000000000000800 ffffbe09862f0460 ffffbe0980571000 : dxgkrnl!TdrCollectDbgInfoStage1+0x38f
ffff9908434e6850 fffff80773ac1db5 : ffffbe0980571000 0000000000000000 ffffbe0980484000 ffffbe0980571001 : dxgmms2!VidSchiResetEngine+0x312
ffff9908434e6a00 fffff80773a9591b : ffffbe0980484000 0000000000000001 0000000000000000 0000000000000000 : dxgmms2!VidSchiResetEngines+0xb1
ffff9908434e6a50 fffff807739fb74f : 0000000000000000 0000000000002bc1 0000000000989680 0000000000000800 : dxgmms2!VidSchiCheckHwProgress+0x2823b
ffff9908434e6ac0 fffff80773a7b1a5 : ffffbe09821f1000 ffffbe0980484000 ffffbe09821f1010 ffffbe0982176050 : dxgmms2!VidSchiScheduleCommandToRun+0x4f
ffff9908434e6b80 fffff80773a7b15a : ffffbe0980484400 fffff80773a7b090 ffffbe0980484000 ffffdb01036b6100 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffff9908434e6bd0 fffff80767517e25 : ffffbe097de1a080 fffff80700000001 ffffbe0980484000 000f8067b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffff9908434e6c10 fffff807675fcdd8 : ffffdb01036b6180 ffffbe097de1a080 fffff80767517dd0 0000000400000000 : nt!PspSystemThreadStartup+0x55
ffff9908434e6c60 0000000000000000 : ffff9908434e7000 ffff9908434e1000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+7c0e36

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffff9908434e4730 ; 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
 
Jan 15, 2021
5
2
15
0
Okay with research it seems to be the graphics driver the error is pointing to.

Going to try and roll back to an earlier driver and see if that fixes the issue.
 
Last edited:
Jan 9, 2021
47
10
45
2
Okay with research it seems to be the graphics driver the error is pointing to.

Going to try and roll back to an earlier driver and see if that fixes the issue.
Hello IGUGSVA.

Did you ever check before you reverted to see if they were the up-to-date drivers? Tells us how the driver reversion process goes, and provide crash dumps if applicable.
 
Jan 15, 2021
5
2
15
0
Hello IGUGSVA.

Did you ever check before you reverted to see if they were the up-to-date drivers? Tells us how the driver reversion process goes, and provide crash dumps if applicable.
I actually think my GPU has just been thermal throttling. I didn’t even consider it because I’ve never had thermal issues before, I noticed that whenever my GPU gets to 80ish degrees Celsius the game either freezes or I blue screen. Making a custom GPU fan curve to keep the temps below 80 seemed to have fixed it for now
 
Reactions: Uncodable
Jan 9, 2021
47
10
45
2
I actually think my GPU has just been thermal throttling. I didn’t even consider it because I’ve never had thermal issues before, I noticed that whenever my GPU gets to 80ish degrees Celsius the game either freezes or I blue screen. Making a custom GPU fan curve to keep the temps below 80 seemed to have fixed it for now
Alright, sorry for the delayed response. Let me know how it goes!
 

ASK THE COMMUNITY