Hello,
I have the same issue with FH4 on PC.
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 a short summary of the crash dump report :
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
I hope maybe a patch to resolve this very annoying issue…