Game freezes then PC restarts...

Hello,

I have a big problem very annoying with FH4 on PC.
Sometimes, the game freezes for 10 seconds and my PC restarts.
This happens about once every 2 hours of play and randomly.
I really have no problems with other games, only on FH4. T_T

My setup :

  • Motherboard : Asus Z97-A
  • CPU : Intel Core i7 4790K @ 4 GHz
  • GPU : Asus ROG STRIX GTX 1080 - Driver NVIDIA ver. 411.70
  • RAM : G.SKILL Trident X 16 Go (2 x 8 Go) - DDR3 1600 MHz Cas 7

Below the crash dump report :


  • Bugcheck Analysis *

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff808e18b86ba, ffffcb0819837748, ffffcb0819836f90}

*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+122 )

Followup: MachineOwner

nt!KeBugCheckEx:
fffff80024640380 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffcb0819836790=000000000000007e
6: 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: fffff808e18b86ba, The address that the exception occurred at
Arg3: ffffcb0819837748, Exception Record Address
Arg4: ffffcb0819836f90, Context Record Address

Debugging Details:

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: ASUS

SYSTEM_PRODUCT_NAME: All Series

SYSTEM_SKU: All

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2801

BIOS_DATE: 11/11/2015

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: Z97-A

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff808e18b86ba

BUGCHECK_P3: ffffcb0819837748

BUGCHECK_P4: ffffcb0819836f90

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L’instruction 0x%p emploie l’adresse m moire 0x%p. L’ tat de la m moire ne peut pas tre %s.

FAULTING_IP:
dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+122
fffff808`e18b86ba 458b4a4c mov r9d,dword ptr [r10+4Ch]

EXCEPTION_RECORD: ffffcb0819837748 – (.exr 0xffffcb0819837748)
ExceptionAddress: fffff808e18b86ba (dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0x0000000000000122)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000004c
Attempt to read from address 000000000000004c

CONTEXT: ffffcb0819836f90 – (.cxr 0xffffcb0819836f90)
rax=ffffa684fc1327a0 rbx=ffffa684f3fece60 rcx=0000000000000001
rdx=ffffa684f3fe3000 rsi=0000000000000001 rdi=0000000000000000
rip=fffff808e18b86ba rsp=ffffcb0819837980 rbp=ffffcb08198379d0
r8=0000000000000001 r9=7fffa684f3fed248 r10=0000000000000000
r11=0000000000000000 r12=ffffa684f8ee3010 r13=0000000000020000
r14=ffffde80a010a2a0 r15=ffffa684f8657f10
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0x122:
fffff808e18b86ba 458b4a4c mov r9d,dword ptr [r10+4Ch] ds:002b:000000000000004c=???
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: f9e

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 22’00000000 (cache) 22’00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

CUSTOMER_CRASH_COUNT: 18

PROCESS_NAME: System

CURRENT_IRQL: 0

FOLLOWUP_IP:
dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+122
fffff808`e18b86ba 458b4a4c mov r9d,dword ptr [r10+4Ch]

BUGCHECK_STR: AV

READ_ADDRESS: fffff800248e4388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
000000000000004c

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

ERROR_CODE: (NTSTATUS) 0xc0000005 - L’instruction 0x%p emploie l’adresse m moire 0x%p. L’ tat de la m moire ne peut pas tre %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000000000004c

ANALYSIS_SESSION_TIME: 10-07-2018 20:09:04.0211

ANALYSIS_VERSION: 10.0.18239.1000 amd64fre

LAST_CONTROL_TRANSFER: from fffff808e18ad2b4 to fffff808e18b86ba

STACK_TEXT:
ffffcb0819837980 fffff808e18ad2b4 : ffffa684f3e5cc00 ffffde80a010a2a0 fffff808e184b13c ffffa684f8657f00 : dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0x122
ffffcb0819837a10 fffff808e188f0b9 : ffffde80a010a2a0 fffff8002460d301 ffffde80a010a300 0000000000000000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1e144
ffffcb0819837be0 fffff8002450a4f7 : ffffa684f3e58700 fffff808e188f0b0 fffff800236a9180 00000425b59bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffcb0819837c10 fffff800246477f6 : fffff800236a9180 ffffa684f3e58700 fffff8002450a4b0 8883b70f0c468966 : nt!PspSystemThreadStartup+0x47
ffffcb0819837c60 0000000000000000 : ffffcb0819838000 ffffcb0819832000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

THREAD_SHA1_HASH_MOD_FUNC: 2ec4922f035ee131ee16b646cfdc0d90107d5a39

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3c2419db05b75ae674634ecab1caa6aa95215b30

THREAD_SHA1_HASH_MOD: c1cdca10cb2fbb68e6161de90d8b8a3362afe4e2

FAULT_INSTR_CODE: 4c4a8b45

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+122

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17134.81

STACK_COMMAND: .cxr 0xffffcb0819836f90 ; kb

BUCKET_ID_FUNC_OFFSET: 122

FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure

BUCKET_ID: AV_dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure

PRIMARY_PROBLEM_CLASS: AV_dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure

TARGET_TIME: 2018-10-07T13:00:21.000Z

OSBUILD: 17134

OSSERVICEPACK: 285

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-08-31 05:15:01

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 2e4c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_dxgmms2!vidmm_worker_thread::handlerecoverablepageinfailure

FAILURE_ID_HASH: {a4678fc3-4329-210d-c0db-63757bdd12c6}

Followup: MachineOwner

I do not know what to do, so please, could you help me by telling me where the issue comes from and if I can solve it ?

Thank you very much for your help !