Windows 10: PC crashing when playing games, Mostly need for speed heat, Forza Horizon 4 and Dirt rally 2.0

PC Specs

• AMD Ryzen 7 3700X CPU
• MSI GeForce RTX 2060 Super 8GB
• MSI B450 Gaming Pro Carbon AC
• 16GB of RAM G-Skill Trident Z RGB
• 250GB SSD Samsung Evo
• Cooler Master Masterwatt 750 80+ Bronze PSU
• Cooler Master MB511 RGB Case

Need for speed heat crash dump analyze:



Loading Dump File [C:\Users\Jerry Jack\Documents\Need for Speed Heat\CrashDumps\CrashDump_2020.08.10_16.20.44.230.mdmp]Comment: 'Frostbite MiniDump. Address: 7ffe4daed339 In Windbg type: .ecxr[EOF]'User Mini Dump File: Only registers, stack and portions of memory are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Version 18363 MP 16 procs Free x64Product: WinNt, suite: SingleUserTSEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Nameebug session time: Mon Aug 10 16:20:44.000 2020 UTC + 5:30System Uptime: not availableProcess Uptime: 0 days 0:02:39.000....................................................................................................................................This dump file has an exception of interest stored in it.The stored exception information can be accessed via .ecxr.4e9c.31c0: Access violation - code c0000005 first/second chance not availableFor analysis of this file, run !analyze -vntdll!NtGetContextThread+0x14:00007ffe`ba0fde04 c3 ret0:017> !analyze -v******************************************************************************** ** Exception Analysis ** *********************************************************************************** WARNING: Unable to verify timestamp for igo64.dll*** WARNING: Unable to verify timestamp for legacy_forcefeedback_x64.dllKEY_VALUES_STRING: 1 Key : AV.Dereference Value: NullPtr Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 10531 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-SOI9BNE Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 120181 Key : Analysis.Memory.CommitPeak.Mb Value: 703 Key : Analysis.System Value: CreateObject Key : Timeline.Process.Start.DeltaSec Value: 159 Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1 Key : WER.Process.Version Value: 1.0.60.7040ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1COMMENT: Frostbite MiniDump. Address: 7ffe4daed339 In Windbg type: .ecxr[EOF]NTGLOBALFLAG: 0PROCESS_BAM_CURRENT_THROTTLED: 0PROCESS_BAM_PREVIOUS_THROTTLED: 0CONTEXT: .ecxrrax=0000000000000000 rbx=000000006c8eda00 rcx=00000000041072a0rdx=000000004a49f3e0 rsi=00000000beae3a78 rdi=000000000000001frip=00007ffe4daed339 rsp=000000004a49f3a0 rbp=000000004a49f409 r8=0000000000000014 r9=0000000000000013 r10=00007ffe4dd13200r11=000000006c8eda60 r12=000000014492b300 r13=00000000460fac3cr14=00000000041072a0 r15=0000000000000000iopl=0 nv up ei pl zr na po nccs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246sdk_legacy_steering_wheel_x64+0xed339:00007ffe`4daed339 488b08 mov rcx,qword ptr [rax] ds:00000000`00000000=????????????????Resetting default scopeEXCEPTION_RECORD: .exr -1ExceptionAddress: 00007ffe4daed339 sdk_legacy_steering_wheel_x64+0x00000000000ed339 ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000Attempt to read from address 0000000000000000PROCESS_NAME: NeedForSpeedHeat.exeREAD_ADDRESS: 0000000000000000 ERROR_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.EXCEPTION_CODE_STR: c0000005EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: 0000000000000000STACK_TEXT: 00000000`4a49f3a0 00000000`00000002 : 00000000`041072a0 00000000`00000000 00000000`04107290 00000000`6c8eda60 : sdk_legacy_steering_wheel_x64+0xed33900000000`4a49f3a8 00000000`041072a0 : 00000000`00000000 00000000`04107290 00000000`6c8eda60 00000000`00000014 : 0x200000000`4a49f3b0 00000000`00000000 : 00000000`04107290 00000000`6c8eda60 00000000`00000014 00000000`6c8eda60 : 0x41072a0SYMBOL_NAME: sdk_legacy_steering_wheel_x64+ed339MODULE_NAME: sdk_legacy_steering_wheel_x64IMAGE_NAME: sdk_legacy_steering_wheel_x64.dllSTACK_COMMAND: ~17s ; .ecxr ; kbFAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_sdk_legacy_steering_wheel_x64.dll!UnknownOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10IMAGE_VERSION: 2020.6.58918.0FAILURE_ID_HASH: {315b66a5-7cab-545a-28e0-15184ae3de6d}Followup: MachineOwner---------0:017> lmvm sdk_legacy_steering_wheel_x64Browse full module liststart end module name00007ffe`4da00000 00007ffe`4de80000 sdk_legacy_steering_wheel_x64 T no symbols Loaded symbol image file: sdk_legacy_steering_wheel_x64.dll Image path: C:\Program Files\LGHUB\sdk_legacy_steering_wheel_x64.dll Image name: sdk_legacy_steering_wheel_x64.dll Browse all global symbols functions data Timestamp: Wed Aug 5 10:17:50 2020 5F2A39F6 CheckSum: 0047B127 ImageSize: 00480000 File version: 2020.6.58918.0 Product version: 2020.6.58918.0 File flags: 0 Mask 3F File OS: 4 Unknown Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:


Memory Dump analyze:



Loading Dump File [E:\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff802`36800000 PsLoadedModuleList = 0xfffff802`3742a2f0Debug session time: Wed Aug 19 00:32:32.356 2020 UTC + 5:30System Uptime: 0 days 0:14:58.984Loading Kernel Symbols..................................................................Page 401dc4 not present in the dump file. Type ".hh dbgerr004" for details.............................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 00000000`00378018. Type ".hh dbgerr001" for detailsLoading unloaded module list..........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff802`36bddf40 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff802`3a879c90=00000000000001330: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor above.Arguments:Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace.Arg2: 0000000000001e00, The watchdog period.Arg3: fffff802374fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeoutArg4: 0000000000000000Debugging Details:------------------**************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files such as the public OS symbols do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: TickPeriods ****** ****************************************************************************KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2343 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-SOI9BNE Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 11604 Key : Analysis.Memory.CommitPeak.Mb Value: 81 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff802374fa320BUGCHECK_P4: 0DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDTRAP_FRAME: fffff8023a8726e0 -- .trap 0xfffff8023a8726e0NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffffd78c4edf9e02rdx=fffff8023a872a02 rsi=0000000000000000 rdi=0000000000000000rip=fffff80236b0e2bb rsp=fffff8023a872870 rbp=fffff8023a872a00 r8=fffff80247b30640 r9=fffff8023a872a50 r10=fffff80247b30640r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncnt!KzLowerIrql+0x1b:fffff802`36b0e2bb 4883c420 add rsp,20hResetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: NeedForSpeedHeat.exeDPC_STACK_BASE: FFFFF8023A872FB0STACK_TEXT: fffff802`3a879c88 fffff802`36c5963e : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`374fa320 : nt!KeBugCheckExfffff802`3a879c90 fffff802`36ace52d : 000002ff`31910e84 fffff802`320e4180 00000000`00000246 00000000`0000e0bf : nt!KeAccumulateTicks+0x18cbeefffff802`3a879cf0 fffff802`36ac7c21 : 00000000`0000e0be 00000000`000085f5 fffff802`320e4180 00000000`00000001 : nt!KiUpdateRunTime+0x5dfffff802`3a879d40 fffff802`36ac9abb : 00000000`00000000 fffff802`3a872700 fffff802`374318c0 00000000`00000000 : nt!KiUpdateTime+0x4a1fffff802`3a879e80 fffff802`36ac6cf2 : fffff802`3a8726e0 fffff802`3a872760 fffff802`3a872760 00000000`00000000 : nt!KeClockInterruptNotify+0x2bbfffff802`3a879f30 fffff802`36a08725 : 00000002`17f77c39 fffff802`374f38e0 fffff802`374f3990 ffffa1cf`b1e95924 : nt!HalpTimerClockInterrupt+0xe2fffff802`3a879f60 fffff802`36bdf9ea : fffff802`3a872760 fffff802`374f38e0 fffff802`3a8729e0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5fffff802`3a879fb0 fffff802`36bdff57 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffff802`3a8726e0 fffff802`36b0e2bb : 00000000`000001f4 00000000`00000000 ffffd78c`55131010 ffffd78c`551dd000 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffff802`3a872870 fffff802`472bd1ef : fffff802`3a872a38 fffff802`3a872a00 ffffd78c`55131010 fffff802`3a8729e0 : nt!KzLowerIrql+0x1bfffff802`3a8728a0 fffff802`472be995 : fffff802`3a872a30 00000000`00000000 ffff9b43`b3240404 ffffd78c`55131010 : nvlddmkm+0x11d1effffff802`3a8728d0 fffff802`472afc55 : ffffd78c`551dd000 ffffd78c`55131010 000002ff`2a438a48 000002ff`2a4390e4 : nvlddmkm+0x11e995fffff802`3a872900 fffff802`36a3a6be : fffff802`320e7240 ffffd78c`4d2da000 fffff802`3a872f10 fffff802`320e4180 : nvlddmkm+0x10fc55fffff802`3a872bb0 fffff802`36a399a4 : fffff802`320e4180 00000000`00000000 00000000`00000029 00000000`0000742b : nt!KiExecuteAllDpcs+0x30efffff802`3a872d20 fffff802`36be4f85 : 00000000`00000000 fffff802`320e4180 ffffa701`3edff500 00000000`00000009 : nt!KiRetireDpcList+0x1f4fffff802`3a872fb0 fffff802`36be4d70 : fffff802`36bda030 fffff802`36b160da 00000000`00000000 00000000`4a97fb20 : nt!KxRetireDpcList+0x5fffff888`96805ac0 fffff802`36be4625 : 00000000`00000009 fffff802`36bdfab1 00000000`00000005 00000000`00000000 : nt!KiDispatchInterruptContinuefffff888`96805af0 fffff802`36bdfab1 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterruptBypass+0x25fffff888`96805b00 00000001`41229a10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb100000000`4a97fa28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`41229a10SYMBOL_NAME: nvlddmkm+11d1efMODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 11d1efFAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_functionOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}Followup: MachineOwner---------0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor above.Arguments:Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace.Arg2: 0000000000001e00, The watchdog period.Arg3: fffff802374fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeoutArg4: 0000000000000000Debugging Details:------------------**************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files such as the public OS symbols do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: TickPeriods ****** ****************************************************************************KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2031 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-SOI9BNE Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 4375 Key : Analysis.Memory.CommitPeak.Mb Value: 84 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff802374fa320BUGCHECK_P4: 0DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDTRAP_FRAME: fffff8023a8726e0 -- .trap 0xfffff8023a8726e0NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffffd78c4edf9e02rdx=fffff8023a872a02 rsi=0000000000000000 rdi=0000000000000000rip=fffff80236b0e2bb rsp=fffff8023a872870 rbp=fffff8023a872a00 r8=fffff80247b30640 r9=fffff8023a872a50 r10=fffff80247b30640r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncnt!KzLowerIrql+0x1b:fffff802`36b0e2bb 4883c420 add rsp,20hResetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: NeedForSpeedHeat.exeDPC_STACK_BASE: FFFFF8023A872FB0STACK_TEXT: fffff802`3a879c88 fffff802`36c5963e : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`374fa320 : nt!KeBugCheckExfffff802`3a879c90 fffff802`36ace52d : 000002ff`31910e84 fffff802`320e4180 00000000`00000246 00000000`0000e0bf : nt!KeAccumulateTicks+0x18cbeefffff802`3a879cf0 fffff802`36ac7c21 : 00000000`0000e0be 00000000`000085f5 fffff802`320e4180 00000000`00000001 : nt!KiUpdateRunTime+0x5dfffff802`3a879d40 fffff802`36ac9abb : 00000000`00000000 fffff802`3a872700 fffff802`374318c0 00000000`00000000 : nt!KiUpdateTime+0x4a1fffff802`3a879e80 fffff802`36ac6cf2 : fffff802`3a8726e0 fffff802`3a872760 fffff802`3a872760 00000000`00000000 : nt!KeClockInterruptNotify+0x2bbfffff802`3a879f30 fffff802`36a08725 : 00000002`17f77c39 fffff802`374f38e0 fffff802`374f3990 ffffa1cf`b1e95924 : nt!HalpTimerClockInterrupt+0xe2fffff802`3a879f60 fffff802`36bdf9ea : fffff802`3a872760 fffff802`374f38e0 fffff802`3a8729e0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5fffff802`3a879fb0 fffff802`36bdff57 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffff802`3a8726e0 fffff802`36b0e2bb : 00000000`000001f4 00000000`00000000 ffffd78c`55131010 ffffd78c`551dd000 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffff802`3a872870 fffff802`472bd1ef : fffff802`3a872a38 fffff802`3a872a00 ffffd78c`55131010 fffff802`3a8729e0 : nt!KzLowerIrql+0x1bfffff802`3a8728a0 fffff802`472be995 : fffff802`3a872a30 00000000`00000000 ffff9b43`b3240404 ffffd78c`55131010 : nvlddmkm+0x11d1effffff802`3a8728d0 fffff802`472afc55 : ffffd78c`551dd000 ffffd78c`55131010 000002ff`2a438a48 000002ff`2a4390e4 : nvlddmkm+0x11e995fffff802`3a872900 fffff802`36a3a6be : fffff802`320e7240 ffffd78c`4d2da000 fffff802`3a872f10 fffff802`320e4180 : nvlddmkm+0x10fc55fffff802`3a872bb0 fffff802`36a399a4 : fffff802`320e4180 00000000`00000000 00000000`00000029 00000000`0000742b : nt!KiExecuteAllDpcs+0x30efffff802`3a872d20 fffff802`36be4f85 : 00000000`00000000 fffff802`320e4180 ffffa701`3edff500 00000000`00000009 : nt!KiRetireDpcList+0x1f4fffff802`3a872fb0 fffff802`36be4d70 : fffff802`36bda030 fffff802`36b160da 00000000`00000000 00000000`4a97fb20 : nt!KxRetireDpcList+0x5fffff888`96805ac0 fffff802`36be4625 : 00000000`00000009 fffff802`36bdfab1 00000000`00000005 00000000`00000000 : nt!KiDispatchInterruptContinuefffff888`96805af0 fffff802`36bdfab1 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterruptBypass+0x25fffff888`96805b00 00000001`41229a10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb100000000`4a97fa28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`41229a10SYMBOL_NAME: nvlddmkm+11d1efMODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 11d1efFAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_functionOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}Followup: MachineOwner


MinDump Analyze

Loading Dump File [C:\Users\Jerry Jack\Desktop\081820-7578-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff803`026b4000 PsLoadedModuleList = 0xfffff803`02afc0f0Debug session time: Tue Aug 18 16:11:00.076 2020 UTC + 5:30System Uptime: 0 days 0:01:59.802Loading Kernel Symbols..........................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff803`028763c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb905`ff67c180=000000000000007e15: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003. This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG. This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG. This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff80303019cc5, The address that the exception occurred atArg3: ffffb905ff67d198, Exception Record AddressArg4: ffffb905ff67c9e0, Context Record AddressDebugging Details:------------------*** WARNING: Unable to verify timestamp for win32k.sysKEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 5093 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-SOI9BNE Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 16349 Key : Analysis.Memory.CommitPeak.Mb Value: 79 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 7eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff80303019cc5BUGCHECK_P3: ffffb905ff67d198BUGCHECK_P4: ffffb905ff67c9e0EXCEPTION_RECORD: ffffb905ff67d198 -- .exr 0xffffb905ff67d198ExceptionAddress: fffff80303019cc5 nt!IovpValidateDeviceObject+0x0000000000000005 ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000046dc232Attempt to read from address 00000000046dc232CONTEXT: ffffb905ff67c9e0 -- .cxr 0xffffb905ff67c9e0rax=ffffe10f500ace10 rbx=ffffe10f500ace10 rcx=00000000046dc232rdx=0000000000000000 rsi=00000000046dc232 rdi=ffffe10f3a09dc90rip=fffff80303019cc5 rsp=ffffb905ff67d3d8 rbp=fffff803028337aa r8=0000000000000000 r9=0000000000000000 r10=fffff8030307f840r11=ffff827a03400000 r12=ffffe10f5a1c3000 r13=fffff80fd5114000r14=0000000000000000 r15=0000000000400000iopl=0 nv up ei pl nz na pe nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202nt!IovpValidateDeviceObject+0x5:fffff803`03019cc5 66833903 cmp word ptr [rcx],3 ds:002b:00000000`046dc232=????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemREAD_ADDRESS: fffff80302c273b8: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff80302ade3b8: Unable to get Flags value from nt!KdVersionBlockfffff80302ade3b8: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 00000000046dc232 ERROR_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.EXCEPTION_CODE_STR: c0000005EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: 00000000046dc232EXCEPTION_STR: 0xc0000005LOCK_ADDRESS: fffff80302b168e0 -- !locks fffff80302b168e0Cannot get _ERESOURCE typeResource @ nt!PiEngineLock 0xfffff80302b168e0 Available1 total locksPNP_TRIAGE_DATA: Lock address : 0xfffff80302b168e0 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0STACK_TEXT: ffffb905`ff67d3d8 fffff803`03018f9e : ffffe10f`500ace10 ffffb905`ff67d3f8 ffffe10f`500acf70 ffffe10f`5639c150 : nt!IovpValidateDeviceObject+0x5ffffb905`ff67d3e0 fffff803`03026af8 : ffffe10f`500ace10 00000000`00000000 ffffe10f`5af93c90 ffffe10f`3a09dc90 : nt!IovCallDriver+0x16affffb905`ff67d420 fffff803`028337aa : 00000000`00000000 fffff803`03024a5c ffffe10f`00000000 ffffe10f`00000000 : nt!VerifierIofCallDriver+0x18ffffb905`ff67d450 fffff803`030190a9 : ffffe10f`500ace10 ffffe10f`5af93c90 00000000`c00000bb 00000000`00000000 : nt!IopfCallDriver+0x56ffffb905`ff67d490 fffff803`03026af8 : ffffe10f`500ace10 00000000`00000017 ffffe10f`433a7060 ffffe10f`42fa1880 : nt!IovCallDriver+0x275ffffb905`ff67d4d0 fffff80f`d50f3939 : fffff803`03a66010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierIofCallDriver+0x18ffffb905`ff67d500 fffff80f`d5103d81 : 00000000`00000000 ffffe10f`433a71d0 ffffe10f`500ace10 00000000`00000000 : HIDCLASS!HidpCallDriver+0xb9ffffb905`ff67d570 fffff80f`d5120f1d : ffffe10f`433a71b0 00000000`00050286 ffffb905`ff67d5f8 00000000`00000018 : HIDCLASS!HidpIrpMajorDefault+0x129ffffb905`ff67d5d0 fffff80f`d50f269b : ffffe10f`00000002 ffffe10f`433a71b0 ffffe10f`5639c1c8 00000000`00000017 : HIDCLASS!HidpIrpMajorSystemControl+0x5e5ffffb905`ff67d600 fffff803`028337aa : 00000000`00000000 ffffe10f`500ace10 ffffe10f`433a7060 ffffe10f`00000001 : HIDCLASS!HidpMajorHandler+0x26bffffb905`ff67d690 fffff803`030190a9 : ffffe10f`500ace10 ffffe10f`433a7060 00000000`00000000 fffff803`03024f69 : nt!IopfCallDriver+0x56ffffb905`ff67d6d0 fffff803`028d2b75 : ffffe10f`500ace10 ffffe10f`433a7060 00000000`00000000 ffffe10f`329c33e0 : nt!IovCallDriver+0x275ffffb905`ff67d710 fffff803`03024ec5 : ffffe10f`5af93c90 00000000`00000000 ffffb905`00000002 00000000`000000c0 : nt!IofCallDriver+0x184cf5ffffb905`ff67d750 fffff803`0303687a : ffffe10f`5af93c90 ffffb905`ff67d939 00000000`00000001 ffffe10f`5af93c90 : nt!VfIrpSendSynchronousIrp+0x115ffffb905`ff67d7c0 fffff803`0302b234 : 00000000`00000000 ffffb905`ff67d939 00000000`00000001 ffffe10f`5af93c90 : nt!VfWmiTestStartedPdoStack+0x5affffb905`ff67d860 fffff803`0280f6eb : 00000000`00000000 ffffb905`ff67d939 00000000`00000001 ffffe10f`11753c40 : nt!VfMajorTestStartedPdoStack+0x58ffffb905`ff67d890 fffff803`02dbcf17 : 00000000`00000000 ffffb905`ff67d939 00000000`00000001 ffffb905`ff67d939 : nt!PpvUtilTestStartedPdoStack+0x17ffffb905`ff67d8c0 fffff803`02db6b7d : ffffe10f`5634dc40 ffffb905`00000001 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase3+0xbfffffb905`ff67d9a0 fffff803`02dd3fdc : ffffe10f`33c3c900 fffff803`02755b01 ffffb905`ff67dab0 fffff803`00000002 : nt!PipProcessDevNodeTree+0x375ffffb905`ff67da60 fffff803`02810747 : 00000001`00000003 ffffe10f`11ae5bd0 ffffe10f`33c3c9d0 ffffe10f`33c3c9d0 : nt!PiProcessReenumeration+0x88ffffb905`ff67dab0 fffff803`02737965 : ffffe10f`5a01c040 ffffe10f`11686cd0 fffff803`02b151a0 ffffe10f`11686cd0 : nt!PnpDeviceActionWorker+0x207ffffb905`ff67db70 fffff803`027d2155 : ffffe10f`5a01c040 00000000`00000080 ffffe10f`11691300 00000067`b4bbbdff : nt!ExpWorkerThread+0x105ffffb905`ff67dc10 fffff803`0287d9c8 : ffff9281`1e879180 ffffe10f`5a01c040 fffff803`027d2100 55555555`55555555 : nt!PspSystemThreadStartup+0x55ffffb905`ff67dc60 00000000`00000000 : ffffb905`ff67e000 ffffb905`ff678000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: HIDCLASS!HidpCallDriver+b9MODULE_NAME: HIDCLASSIMAGE_NAME: HIDCLASS.SYSIMAGE_VERSION: 10.0.18362.175STACK_COMMAND: .cxr 0xffffb905ff67c9e0 ; kbBUCKET_ID_FUNC_OFFSET: b9FAILURE_BUCKET_ID: AV_VRF_HIDCLASS!HidpCallDriverOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {25e71b60-36c1-fafe-99dd-4c12cfb82b8a}Followup: MachineOwner---------15: kd> lmvm HIDCLASSBrowse full module liststart end module namefffff80f`d50f0000 fffff80f`d512b000 HIDCLASS pdb symbols C:\ProgramData\Dbg\sym\hidclass.pdb\531804ABD6B8D5A93CC8BAF11E47940E1\hidclass.pdb Loaded symbol image file: HIDCLASS.SYS Mapped memory image file: C:\ProgramData\Dbg\sym\HIDCLASS.SYS\D4D0DEE63b000\HIDCLASS.SYS Image path: \SystemRoot\System32\drivers\HIDCLASS.SYS Image name: HIDCLASS.SYS Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: D4D0DEE6 This is a reproducible build file hash, not a timestamp CheckSum: 000369B1 ImageSize: 0003B000 File version: 10.0.18362.175 Product version: 10.0.18362.175 File flags: 0 Mask 3F File OS: 40004 NT Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 Information from resource tables: CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: hidclass.sys OriginalFilename: hidclass.sys ProductVersion: 10.0.18362.175 FileVersion: 10.0.18362.175 WinBuild.160101.0800 FileDescription: Hid Class Library LegalCopyright: © Microsoft Corporation. All rights reserved.

:)

 

Looking for racing game recommendations.....


Here are few racing games you can play:
Forza Horizon
Dirt Rally
Project Cars 2
Gran Turismo Sport
Dirt 4
Real Racing 3
F1 201

 

Forza 4 Horizon Crashing at Exact Same Point | PC

I installed Forza Horizon 4 as part of the XBox game pass for PC. The game starts of with the standard play sequence of Autmun, then Winter and so on.

Every single time when I am in the Winter sequence (Race to the Frozen Lake) at about 70% completion, the game crashes.

I have deleted and reinstalled the game as well. Still the same problem.

Fed up - I downloaded a different version of Forza Horizon 4 as well (Forza Horizon 4 Ultimate Edition), still, the same result.

The PC is fairly good - intel i9 10900K, RTX 2080 Ti, 64 Gb RAM.

I am not sure if this is an external issue (driver/ hardware etc.) since the crash happens at the exact same point every time.

Any ideas?

 

Forza Horizon 3 Crash on Gameplay

Hi,

Thank you for writing to Microsoft Community Forums.

I understand that Forza Horizon 3 keeps crashing.

• Are you aware of any changes made to the computer recently?
  

I suggest you refer and follow the steps mentioned in the article and check if that resolves the issue. Refer to the article
My Game is Not Launching or is Crashing on PC.

Let us know how it goes.

Regards,

Zaki