Question Bsod while playing

Jun 2, 2022
1
0
10
0
Hi all
after experiencing during last 10 days some random crashes to desktop while playing lost ark, today i had a BSOD(also while playing LOST ARK).

SPECS CPU: I7 12700K GPU: RTX 3060 16 GB RAM8(KINGSTON FURY BEAST 3200 MHZ 2X8GB) MOBO:TUF GAMING B660M-PLUS-D4 CPU COOLER: HYPER 212 BLACK EDITION
PSU: COOLER MASTER ELITE 600 OS:WIN 10 PRO 64BIT SSD: SAMSUNG 980 PRO 500GB
My temps are fine (monited with hwmonitor64 while playing) but my case became hot because of bad airflow inside it(sharkoon tg4).
I bought this PC 20 days ago. So all components are new.

This is the dumpfile:


ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff805a8d3be60, Virtual address for the attempted execute.
Arg2: 800000037cac1929, PTE contents.
Arg3: ffff898778357100, (reserved)
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2953

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 37822

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

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

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

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: 060222-5046-01.dmp

BUGCHECK_CODE: fc

BUGCHECK_P1: fffff805a8d3be60

BUGCHECK_P2: 800000037cac1929

BUGCHECK_P3: ffff898778357100

BUGCHECK_P4: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff898778357100 -- (.trap 0xffff898778357100)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9c09c99fd000 rbx=0000000000000000 rcx=ffff9c09bf66ca80
rdx=ffff9c09b6ee76d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805a8d3be60 rsp=ffff898778357298 rbp=0000000000000000
r8=ffff8987783575f0 r9=0000000238d10000 r10=0000000000000020
r11=00000000000001c6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
fffff805a8d3be60 0000 add byte ptr [rax],al ds:ffff9c09c99fd000=00
Resetting default scope

STACK_TEXT:
ffff898778356e18 fffff80578e80c9c : 00000000000000fc fffff805a8d3be60 800000037cac1929 ffff898778357100 : nt!KeBugCheckEx
ffff898778356e20 fffff80578cc5076 : fffff805a8d3be60 ffff898778357020 ffff898700000000 ffff800000000000 : nt!MiCheckSystemNxFault+0x135b64
ffff898778356e60 fffff80578ca6960 : 0000000000000111 0000000000000011 ffff898778357180 0000000000000000 : nt!MiSystemFault+0x6c6
ffff898778356f60 fffff80578e05e5e : 0000000000000000 ffff898778357180 00000000000000c6 0000000000000000 : nt!MmAccessFault+0x400
ffff898778357100 fffff805a8d3be60 : fffff80598d3b562 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e
ffff898778357298 fffff80598d3b562 : 0000000000000000 0000000000000000 0000000000000000 ffff8987783575a0 : 0xfffff805a8d3be60
ffff8987
783572a0 fffff80598d63dce : 0000000000000000 ffff9c09b6ee76d0 0000000000000001 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x422
ffff8987
78357410 fffff80598d3b0cc : ffff8b02a1992628 ffff9c09b6ee76d0 ffff898778357600 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x28c8e
ffff8987
78357580 fffff80598d31d89 : 0000000000000002 ffff8987783576e0 ffff3103c0b0c1ad ffff9c09b5f57520 : dxgmms2!CVirtualAddressAllocator::UncommitVirtualAddressRange+0xf4
ffff8987
78357690 fffff80598d364a2 : fffff80598d02c90 0000000000000071 ffff898778357820 ffff8b02a1a47000 : dxgmms2!VIDMM_GLOBAL::CommitVirtualAddressRangeSystemCommand+0xb1
ffff8987
78357720 fffff80598d4c65e : 0000000000000001 0000000000989680 ffff9c09b08935a0 0000000000000001 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xea2
ffff8987
78357940 fffff80598d56809 : ffff9c09b08934d0 ffff8b02a18f2101 0000000000000000 0000000002d8b100 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xe5e
ffff8987
78357b20 fffff80578ceea75 : ffff8b02a18f2140 fffff80598d56800 ffff9c09b08934d0 002fe47fbd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff8987
78357b50 fffff80578dff3b8 : ffffc780d22e6180 ffff8b02a18f2140 fffff80578ceea20 007d003000660036 : nt!PspSystemThreadStartup+0x55
ffff8987
78357ba0 0000000000000000 : ffff898778358000 ffff898778351000 0000000000000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+422

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1645

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 422

FAILURE_BUCKET_ID: 0xFC_dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3e08d1fa-9669-b99d-bc4d-ece9953749d1}

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

Do you have any idea what happened?
 
Last edited:

Lutfij

Titan
Moderator
Welcome to the forums, newcomer!

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list them like so:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:

Include the age of your PSU as well, if it's been in service for a while. How are you cooling that processor?
 
Hi all
after experiencing during last 10 days some random crashes to desktop while playing lost ark, today i had a BSOD(also while playing LOST ARK).

SPECS CPU: I7 12700K GPU: RTX 3060 16 GB RAM8(KINGSTON FURY BEAST 3200 MHZ 2X8GB) MOBO:TUF GAMING B660M-PLUS-D4 CPU COOLER: HYPER 212 BLACK EDITION
PSU: COOLER MASTER ELITE 600 OS:WIN 10 PRO 64BIT SSD: SAMSUNG 980 PRO 500GB
My temps are fine (monited with hwmonitor64 while playing) but my case became hot because of bad airflow inside it(sharkoon tg4).
I bought this PC 20 days ago. So all components are new.

This is the dumpfile:


ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff805a8d3be60, Virtual address for the attempted execute.
Arg2: 800000037cac1929, PTE contents.
Arg3: ffff898778357100, (reserved)
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2953

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 37822

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

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

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

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: 060222-5046-01.dmp

BUGCHECK_CODE: fc

BUGCHECK_P1: fffff805a8d3be60

BUGCHECK_P2: 800000037cac1929

BUGCHECK_P3: ffff898778357100

BUGCHECK_P4: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff898778357100 -- (.trap 0xffff898778357100)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9c09c99fd000 rbx=0000000000000000 rcx=ffff9c09bf66ca80
rdx=ffff9c09b6ee76d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805a8d3be60 rsp=ffff898778357298 rbp=0000000000000000
r8=ffff8987783575f0 r9=0000000238d10000 r10=0000000000000020
r11=00000000000001c6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
fffff805a8d3be60 0000 add byte ptr [rax],al ds:ffff9c09c99fd000=00
Resetting default scope

STACK_TEXT:
ffff898778356e18 fffff80578e80c9c : 00000000000000fc fffff805a8d3be60 800000037cac1929 ffff898778357100 : nt!KeBugCheckEx
ffff898778356e20 fffff80578cc5076 : fffff805a8d3be60 ffff898778357020 ffff898700000000 ffff800000000000 : nt!MiCheckSystemNxFault+0x135b64
ffff898778356e60 fffff80578ca6960 : 0000000000000111 0000000000000011 ffff898778357180 0000000000000000 : nt!MiSystemFault+0x6c6
ffff898778356f60 fffff80578e05e5e : 0000000000000000 ffff898778357180 00000000000000c6 0000000000000000 : nt!MmAccessFault+0x400
ffff898778357100 fffff805a8d3be60 : fffff80598d3b562 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e
ffff898778357298 fffff80598d3b562 : 0000000000000000 0000000000000000 0000000000000000 ffff8987783575a0 : 0xfffff805a8d3be60
ffff8987
783572a0 fffff80598d63dce : 0000000000000000 ffff9c09b6ee76d0 0000000000000001 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x422
ffff8987
78357410 fffff80598d3b0cc : ffff8b02a1992628 ffff9c09b6ee76d0 ffff898778357600 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x28c8e
ffff8987
78357580 fffff80598d31d89 : 0000000000000002 ffff8987783576e0 ffff3103c0b0c1ad ffff9c09b5f57520 : dxgmms2!CVirtualAddressAllocator::UncommitVirtualAddressRange+0xf4
ffff8987
78357690 fffff80598d364a2 : fffff80598d02c90 0000000000000071 ffff898778357820 ffff8b02a1a47000 : dxgmms2!VIDMM_GLOBAL::CommitVirtualAddressRangeSystemCommand+0xb1
ffff8987
78357720 fffff80598d4c65e : 0000000000000001 0000000000989680 ffff9c09b08935a0 0000000000000001 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xea2
ffff8987
78357940 fffff80598d56809 : ffff9c09b08934d0 ffff8b02a18f2101 0000000000000000 0000000002d8b100 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xe5e
ffff8987
78357b20 fffff80578ceea75 : ffff8b02a18f2140 fffff80598d56800 ffff9c09b08934d0 002fe47fbd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff8987
78357b50 fffff80578dff3b8 : ffffc780d22e6180 ffff8b02a18f2140 fffff80578ceea20 007d003000660036 : nt!PspSystemThreadStartup+0x55
ffff8987
78357ba0 0000000000000000 : ffff898778358000 ffff898778351000 0000000000000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+422

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1645

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 422

FAILURE_BUCKET_ID: 0xFC_dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3e08d1fa-9669-b99d-bc4d-ece9953749d1}

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

Do you have any idea what happened?
error came out of the graphics subsystem. first fix attempt would be to remove any overclock driver, and update the graphics drivers and retest.
sometimes you see this type of problem with some audio drivers responding to the gpu graphics audio driver. So you should also update the motherboard audio driver even if you are not using it.
 

ASK THE COMMUNITY

TRENDING THREADS