precise GPU connector, graphics card requires significant effort and must be fully seated to display properly
precise GPU connector, graphics card requires significant effort and must be fully seated to display properly
ispatchWithLock Key : Failure.Exception.IP.Address Value: 0xfffff80713e6a7b0 Key : Failure.Exception.IP.Module Value: Wdf01000 Key : Failure.Exception.IP.Offset Value: 0xa7b0 Key : Failure.Hash Value: {4a77324b-c183-62b8-a544-6b04608ba368} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: c9 BUGCHECK_P1: 24c BUGCHECK_P2: fffff80713e6a7b0 BUGCHECK_P3: ffff9a81858785a0 BUGCHECK_P4: 103 FILE_IN_CAB: 080525-11265-01.dmp FAULTING_THREAD: ffff9a8154443080 DRIVER_VERIFIER_IO_VIOLATION_TYPE: 24c IRP_ADDRESS: ffff9a81858785a0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffad02`2b9984a8 fffff807`131d7e44 : 00000000`000000c9 00000000`0000024c fffff807`13e6a7b0 ffff9a81`858785a0 : nt!KeBugCheckEx ffffad02`2b9984b0 fffff807`131df383 : 00000000`00000000 00000000`00000103 00000000`0000024c fffff807`135499b0 : nt!VerifierBugCheckIfAppropriate+0xe0 ffffad02`2b9984f0 fffff807`12da8f12 : 00000000`0000024c 00000000`00000103 ffff9a81`858785a0 00000000`00000000 : nt!ViErrorFinishReport+0x117 ffffad02`2b998550 fffff807`131d72d8 : ffff9a81`5ef48bb0 ffff9a81`83ea27b0 00000000`00400000 ffff9a81`7d61bb50 : nt!ViErrorReport6+0x6e ffffad02`2b998620 fffff807`131d806c : ffff9a81`83ea27b0 ffff9a81`83ea2868 00000000`00000000 00000000`00000000 : nt!IovpCallDriver2+0x184 ffffad02`2b998670 fffff807`131cbf3b : ffff9a81`858785a0 00000000`00000000 ffff9a81`701bddd0 fffff807`131d86d9 : nt!VfAfterCallDriver+0x1d8 ffffad02`2b9986a0 fffff807`12c61e79 : ffff9a81`858785a0 ffffad02`2b998800 ffff9a81`6ee0ede0 ffff9a81`83ea27b0 : nt!IovCallDriver+0x277 ffffad02`2b9986e0 fffff807`12f6f546 : ffff9a81`6ee0ede0 ffff9a81`83fdc030 00000000`00000010 00000000`00050286 : nt!IofCallDriver+0x188cc9 ffffad02`2b998720 fffff807`12b68486 : ffff9a81`6ee0ede0 00000000`00000000 ffff9a81`83fdc030 fffff807`12b50126 : nt!PnpAsynchronousCall+0xea ffffad02`2b998760 fffff807`12f4a159 : 00000000`00000001 00000000`00000000 ffff9a81`6ee0ede0 ffff9a81`00000000 : nt!PnpSendIrp+0x9e ffffad02`2b9987d0 fffff807`12f4a0c0 : ffff9a81`83fdc030 ffff9a81`6facea88 ffff9a81`6facea60 00000000`00000018 : nt!PnpQueryDeviceRelations+0x51 ffffad02`2b998860 fffff807`12f4466b : ffff9a81`6facea60 ffffad02`2b998911 00000000`00000002 00000000`00000000 : nt!PipEnumerateDevice+0xc8 ffffad02`2b998890 fffff807`12f50034 : ffff9a81`7d61bb00 ffffad02`2b998a01 ffffad02`2b9989b0 fffff807`00000002 : nt!PipProcessDevNodeTree+0x297 ffffad02`2b998960 fffff807`12b76b46 : 00000001`00000003 ffff9a81`5cbbd4c0 ffff9a81`7d61bb50 ffff9a81`7d61bb50 : nt!PiProcessReenumeration+0x88 ffffad02`2b9989b0 fffff807`12a488f5 : ffff9a81`54443080 ffff9a81`518eb300 fffff807`1344a500 00000000`00000000 : nt!PnpDeviceActionWorker+0x206 ffffad02`2b998a70 fffff807`12b64635 : ffff9a81`54443080 00000000`00000080 ffff9a81`518cc040 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105 ffffad02`2b998b10 fffff807`12c0d3c8 : ffffc482`001c2180 ffff9a81`54443080 fffff807`12b645e0 1f1f1f1f`1f1f1f1f : nt!PspSystemThreadStartup+0x55 ffffad02`2b998b60 00000000`00000000 : ffffad02`2b999000 ffffad02`2b992000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 FAULTING_SOURCE_LINE: minkernel\wdf\framework\shared\core\fxdevice.cpp FAULTING_SOURCE_FILE: minkernel\wdf\framework\shared\core\fxdevice.cpp FAULTING_SOURCE_LINE_NUMBER: 1385 FAULTING_SOURCE_CODE: No source found for 'minkernel\wdf\framework\shared\core\fxdevice.cpp' SYMBOL_NAME: Wdf01000!FxDevice:ispatchWithLock+0 MODULE_NAME: Wdf01000 IMAGE_NAME: Wdf01000.sys IMAGE_VERSION: 1.31.19041.5965 STACK_COMMAND: .process /r /p 0xffff9a81518cc040; .thread 0xffff9a8154443080 ; kb BUCKET_ID_FUNC_OFFSET: 0 FAILURE_BUCKET_ID: 0xc9_24c_VRF_Wdf01000!FxDevice:ispatchWithLock OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {4a77324b-c183-62b8-a544-6b04608ba368} Followup: MachineOwner --------- with my own 1050 ti Spoiler DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a call to IoMarkIrpPending. Arg2: fffff80271a6a7b0, The address in the driver's code where the error was detected. Arg3: ffff9b0469d98430, IRP address. Arg4: 0000000000000103, Status code. Debugging Details: ------------------ *** WARNING: Check Image - Checksum mismatch - Dump: 0x2b7de2, File: 0x2b8c86 - C:\ProgramData\Dbg\sym\Ntfs.sys\A9E0F8AC2D7000\Ntfs.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1859 Key : Analysis.Elapsed.mSec Value: 36634 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 32 Key : Analysis.Init.CPU.mSec Value: 593 Key : Analysis.Init.Elapsed.mSec Value: 104304 Key : Analysis.Memory.CommitPeak.Mb Value: 108 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0xc9 Key : Bugcheck.Code.TargetModel Value: 0xc9 Key : Failure.Bucket Value: 0xc9_24c_VRF_Wdf01000!FxDevice:ispatchWithLock Key : Failure.Exception.IP.Address Value: 0xfffff80271a6a7b0 Key : Failure.Exception.IP.Module Value: Wdf01000 Key : Failure.Exception.IP.Offset Value: 0xa7b0 Key : Failure.Hash Value: {4a77324b-c183-62b8-a544-6b04608ba368} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: c9 BUGCHECK_P1: 24c BUGCHECK_P2: fffff80271a6a7b0 BUGCHECK_P3: ffff9b0469d98430 BUGCHECK_P4: 103 FILE_IN_CAB: 080425-10343-01.dmp FAULTING_THREAD: ffff9b043d6ac080 DRIVER_VERIFIER_IO_VIOLATION_TYPE: 24c IRP_ADDRESS: ffff9b0469d98430 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff488`0b9df4a8 fffff802`70dd8e44 : 00000000`000000c9 00000000`0000024c fffff802`71a6a7b0 ffff9b04`69d98430 : nt!KeBugCheckEx fffff488`0b9df4b0 fffff802`70de0383 : 00000000`00000000 00000000`00000103 00000000`0000024c fffff802`7114a9b0 : nt!VerifierBugCheckIfAppropriate+0xe0 fffff488`0b9df4f0 fffff802`709a9f12 : 00000000`0000024c 00000000`00000103 ffff9b04`69d98430 00000000`00000000 : nt!ViErrorFinishReport+0x117 fffff488`0b9df550 fffff802`70dd82d8 : ffff9b04`3ebe57b0 ffff9b04`5eec1880 00000000`00400000 ffff9b04`678b5770 : nt!ViErrorReport6+0x6e fffff488`0b9df620 fffff802`70dd906c : ffff9b04`5eec1880 ffff9b04`5eec1938 00000000`00000000 00000000`00000000 : nt!IovpCallDriver2+0x184 fffff488`0b9df670 fffff802`70dccf3b : ffff9b04`69d98430 00000000`00000000 ffff9b04`5383bdc0 fffff802`70dd96d9 : nt!VfAfterCallDriver+0x1d8 fffff488`0b9df6a0 fffff802`70862e79 : ffff9b04`69d98430 fffff488`0b9df800 ffff9b04`552b8de0 ffff9b04`5eec1880 : nt!IovCallDriver+0x277 fffff488`0b9df6e0 fffff802`70b70546 : ffff9b04`552b8de0 ffff9b04`692e3a70 00000000`00000010 00000000`00050286 : nt!IofCallDriver+0x188cc9 fffff488`0b9df720 fffff802`70769486 : ffff9b04`552b8de0 00000000`00000000 ffff9b04`692e3a70 00000000`00000000 : nt!PnpAsynchronousCall+0xea fffff488`0b9df760 fffff802`70b4b159 : 00000000`00000001 00000000`00000000 ffff9b04`552b8de0 ffff9b04`00000000 : nt!PnpSendIrp+0x9e fffff488`0b9df7d0 fffff802`70b4b0c0 : ffff9b04`692e3a70 ffff9b04`5418aa88 ffff9b04`5418aa60 00000000`00000018 : nt!PnpQueryDeviceRelations+0x51 fffff488`0b9df860 fffff802`70b4566b : ffff9b04`5418aa60 fffff488`0b9df911 00000000`00000002 00000000`00000000 : nt!PipEnumerateDevice+0xc8 fffff488`0b9df890 fffff802`70b51034 : ffff9b04`678b5700 fffff802`706d3101 fffff488`0b9df9b0 fffff802`00000002 : nt!PipProcessDevNodeTree+0x297 fffff488`0b9df960 fffff802`70777b46 : 00000001`00000003 ffff9b04`55057c60 ffff9b04`678b5770 ffff9b04`678b5770 : nt!PiProcessReenumeration+0x88 fffff488`0b9df9b0 fffff802`706498f5 : ffff9b04`3d6ac080 ffff9b04`320c7cc0 fffff802`7104b500 ffff9b04`00000000 : nt!PnpDeviceActionWorker+0x206 fffff488`0b9dfa70 fffff802`70765635 : ffff9b04`3d6ac080 00000000`00000080 ffff9b04`320d2040 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105 fffff488`0b9dfb10 fffff802`7080e3c8 : ffffc700`7f140180 ffff9b04`3d6ac080 fffff802`707655e0 afafafaf`afafafaf : nt!PspSystemThreadStartup+0x55 fffff488`0b9dfb60 00000000`00000000 : fffff488`0b9e0000 fffff488`0b9d9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 FAULTING_SOURCE_LINE: minkernel\wdf\framework\shared\core\fxdevice.cpp FAULTING_SOURCE_FILE: minkernel\wdf\framework\shared\core\fxdevice.cpp FAULTING_SOURCE_LINE_NUMBER: 1385 SYMBOL_NAME: Wdf01000!FxDevice:ispatchWithLock+0 MODULE_NAME: Wdf01000 IMAGE_NAME: Wdf01000.sys IMAGE_VERSION: 1.31.19041.5965 STACK_COMMAND: .process /r /p 0xffff9b04320d2040; .thread 0xffff9b043d6ac080 ; kb BUCKET_ID_FUNC_OFFSET: 0 FAILURE_BUCKET_ID: 0xc9_24c_VRF_Wdf01000!FxDevice:ispatchWithLock OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {4a77324b-c183-62b8-a544-6b04608ba368} Followup: MachineOwner --------- GTA 5, SOTTR and kodi crash with memory violation (error 0xc0000005) Spoiler Faulting application name: GTA5.exe, version: 1.0.3570.0, time stamp: 0x684af14b Faulting module name: dxgi.asi, version: 6.3.3.0, time stamp: 0x67c6523a Exception code: 0xc0000005 Fault offset: 0x00000000000233d4 Faulting process id: 0xa6c Faulting application start time: 0x01dc0557257aa2b5 Faulting application path: E:\Games\Grand.Theft.Auto.V.Legacy\GTA5.exe Faulting module path: E:\Games\Grand.Theft.Auto.V.Legacy\dxgi.asi Report Id: 78082770-fe05-49dd-81fc-e359bd00a9fe Faulting package full name: Faulting package-relative application ID: Faulting application name: kodi.exe, version: 21.2.0.0, time stamp: 0x678c02ae Faulting module name: kodi.exe, version: 21.2.0.0, time stamp: 0x678c02ae Exception code: 0xc0000005 Fault offset: 0x0000000000723007 Faulting process id: 0x26d8 Faulting application start time: 0x01dc054a2bc57ef5 Faulting application path: C:\Program Files\Kodi\kodi.exe Faulting module path: C:\Program Files\Kodi\kodi.exe Report Id: 3d5efdf9-4907-4711-820a-8a6a362d2b77 Faulting package full name: Faulting package-relative application ID:
Carzy_Daisy246
09-25-2025, 02:56 AM #1so recently been facing issues with crashing in games and certain apps with specific activity. For eg. GTA V crashes when changing certain graphics settings, kodi crashes when watching a channel clearing epg data at the same time, the crash before was different and now also different with my brother's 3060 ti, i think both my gpu and mobo is failing (1050 ti and h470) Driver Verifier Crash Dump with 3060 ti (works properly on original pc) Spoiler DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a call to IoMarkIrpPending. Arg2: fffff80713e6a7b0, The address in the driver's code where the error was detected. Arg3: ffff9a81858785a0, IRP address. Arg4: 0000000000000103, Status code. Debugging Details: ------------------ *** WARNING: Check Image - Checksum mismatch - Dump: 0x3a5e6c, File: 0x3a7c52 - C:\ProgramData\Dbg\sym\dxgkrnl.sys\11AB52763AA000\dxgkrnl.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1828 Key : Analysis.Elapsed.mSec Value: 25222 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 7 Key : Analysis.Init.CPU.mSec Value: 343 Key : Analysis.Init.Elapsed.mSec Value: 58117 Key : Analysis.Memory.CommitPeak.Mb Value: 114 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0xc9 Key : Bugcheck.Code.TargetModel Value: 0xc9 Key : Failure.Bucket Value: 0xc9_24c_VRF_Wdf01000!FxDevice:ispatchWithLock Key : Failure.Exception.IP.Address Value: 0xfffff80713e6a7b0 Key : Failure.Exception.IP.Module Value: Wdf01000 Key : Failure.Exception.IP.Offset Value: 0xa7b0 Key : Failure.Hash Value: {4a77324b-c183-62b8-a544-6b04608ba368} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: c9 BUGCHECK_P1: 24c BUGCHECK_P2: fffff80713e6a7b0 BUGCHECK_P3: ffff9a81858785a0 BUGCHECK_P4: 103 FILE_IN_CAB: 080525-11265-01.dmp FAULTING_THREAD: ffff9a8154443080 DRIVER_VERIFIER_IO_VIOLATION_TYPE: 24c IRP_ADDRESS: ffff9a81858785a0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffad02`2b9984a8 fffff807`131d7e44 : 00000000`000000c9 00000000`0000024c fffff807`13e6a7b0 ffff9a81`858785a0 : nt!KeBugCheckEx ffffad02`2b9984b0 fffff807`131df383 : 00000000`00000000 00000000`00000103 00000000`0000024c fffff807`135499b0 : nt!VerifierBugCheckIfAppropriate+0xe0 ffffad02`2b9984f0 fffff807`12da8f12 : 00000000`0000024c 00000000`00000103 ffff9a81`858785a0 00000000`00000000 : nt!ViErrorFinishReport+0x117 ffffad02`2b998550 fffff807`131d72d8 : ffff9a81`5ef48bb0 ffff9a81`83ea27b0 00000000`00400000 ffff9a81`7d61bb50 : nt!ViErrorReport6+0x6e ffffad02`2b998620 fffff807`131d806c : ffff9a81`83ea27b0 ffff9a81`83ea2868 00000000`00000000 00000000`00000000 : nt!IovpCallDriver2+0x184 ffffad02`2b998670 fffff807`131cbf3b : ffff9a81`858785a0 00000000`00000000 ffff9a81`701bddd0 fffff807`131d86d9 : nt!VfAfterCallDriver+0x1d8 ffffad02`2b9986a0 fffff807`12c61e79 : ffff9a81`858785a0 ffffad02`2b998800 ffff9a81`6ee0ede0 ffff9a81`83ea27b0 : nt!IovCallDriver+0x277 ffffad02`2b9986e0 fffff807`12f6f546 : ffff9a81`6ee0ede0 ffff9a81`83fdc030 00000000`00000010 00000000`00050286 : nt!IofCallDriver+0x188cc9 ffffad02`2b998720 fffff807`12b68486 : ffff9a81`6ee0ede0 00000000`00000000 ffff9a81`83fdc030 fffff807`12b50126 : nt!PnpAsynchronousCall+0xea ffffad02`2b998760 fffff807`12f4a159 : 00000000`00000001 00000000`00000000 ffff9a81`6ee0ede0 ffff9a81`00000000 : nt!PnpSendIrp+0x9e ffffad02`2b9987d0 fffff807`12f4a0c0 : ffff9a81`83fdc030 ffff9a81`6facea88 ffff9a81`6facea60 00000000`00000018 : nt!PnpQueryDeviceRelations+0x51 ffffad02`2b998860 fffff807`12f4466b : ffff9a81`6facea60 ffffad02`2b998911 00000000`00000002 00000000`00000000 : nt!PipEnumerateDevice+0xc8 ffffad02`2b998890 fffff807`12f50034 : ffff9a81`7d61bb00 ffffad02`2b998a01 ffffad02`2b9989b0 fffff807`00000002 : nt!PipProcessDevNodeTree+0x297 ffffad02`2b998960 fffff807`12b76b46 : 00000001`00000003 ffff9a81`5cbbd4c0 ffff9a81`7d61bb50 ffff9a81`7d61bb50 : nt!PiProcessReenumeration+0x88 ffffad02`2b9989b0 fffff807`12a488f5 : ffff9a81`54443080 ffff9a81`518eb300 fffff807`1344a500 00000000`00000000 : nt!PnpDeviceActionWorker+0x206 ffffad02`2b998a70 fffff807`12b64635 : ffff9a81`54443080 00000000`00000080 ffff9a81`518cc040 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105 ffffad02`2b998b10 fffff807`12c0d3c8 : ffffc482`001c2180 ffff9a81`54443080 fffff807`12b645e0 1f1f1f1f`1f1f1f1f : nt!PspSystemThreadStartup+0x55 ffffad02`2b998b60 00000000`00000000 : ffffad02`2b999000 ffffad02`2b992000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 FAULTING_SOURCE_LINE: minkernel\wdf\framework\shared\core\fxdevice.cpp FAULTING_SOURCE_FILE: minkernel\wdf\framework\shared\core\fxdevice.cpp FAULTING_SOURCE_LINE_NUMBER: 1385 FAULTING_SOURCE_CODE: No source found for 'minkernel\wdf\framework\shared\core\fxdevice.cpp' SYMBOL_NAME: Wdf01000!FxDevice:ispatchWithLock+0 MODULE_NAME: Wdf01000 IMAGE_NAME: Wdf01000.sys IMAGE_VERSION: 1.31.19041.5965 STACK_COMMAND: .process /r /p 0xffff9a81518cc040; .thread 0xffff9a8154443080 ; kb BUCKET_ID_FUNC_OFFSET: 0 FAILURE_BUCKET_ID: 0xc9_24c_VRF_Wdf01000!FxDevice:ispatchWithLock OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {4a77324b-c183-62b8-a544-6b04608ba368} Followup: MachineOwner --------- with my own 1050 ti Spoiler DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a call to IoMarkIrpPending. Arg2: fffff80271a6a7b0, The address in the driver's code where the error was detected. Arg3: ffff9b0469d98430, IRP address. Arg4: 0000000000000103, Status code. Debugging Details: ------------------ *** WARNING: Check Image - Checksum mismatch - Dump: 0x2b7de2, File: 0x2b8c86 - C:\ProgramData\Dbg\sym\Ntfs.sys\A9E0F8AC2D7000\Ntfs.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1859 Key : Analysis.Elapsed.mSec Value: 36634 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 32 Key : Analysis.Init.CPU.mSec Value: 593 Key : Analysis.Init.Elapsed.mSec Value: 104304 Key : Analysis.Memory.CommitPeak.Mb Value: 108 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0xc9 Key : Bugcheck.Code.TargetModel Value: 0xc9 Key : Failure.Bucket Value: 0xc9_24c_VRF_Wdf01000!FxDevice:ispatchWithLock Key : Failure.Exception.IP.Address Value: 0xfffff80271a6a7b0 Key : Failure.Exception.IP.Module Value: Wdf01000 Key : Failure.Exception.IP.Offset Value: 0xa7b0 Key : Failure.Hash Value: {4a77324b-c183-62b8-a544-6b04608ba368} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: c9 BUGCHECK_P1: 24c BUGCHECK_P2: fffff80271a6a7b0 BUGCHECK_P3: ffff9b0469d98430 BUGCHECK_P4: 103 FILE_IN_CAB: 080425-10343-01.dmp FAULTING_THREAD: ffff9b043d6ac080 DRIVER_VERIFIER_IO_VIOLATION_TYPE: 24c IRP_ADDRESS: ffff9b0469d98430 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff488`0b9df4a8 fffff802`70dd8e44 : 00000000`000000c9 00000000`0000024c fffff802`71a6a7b0 ffff9b04`69d98430 : nt!KeBugCheckEx fffff488`0b9df4b0 fffff802`70de0383 : 00000000`00000000 00000000`00000103 00000000`0000024c fffff802`7114a9b0 : nt!VerifierBugCheckIfAppropriate+0xe0 fffff488`0b9df4f0 fffff802`709a9f12 : 00000000`0000024c 00000000`00000103 ffff9b04`69d98430 00000000`00000000 : nt!ViErrorFinishReport+0x117 fffff488`0b9df550 fffff802`70dd82d8 : ffff9b04`3ebe57b0 ffff9b04`5eec1880 00000000`00400000 ffff9b04`678b5770 : nt!ViErrorReport6+0x6e fffff488`0b9df620 fffff802`70dd906c : ffff9b04`5eec1880 ffff9b04`5eec1938 00000000`00000000 00000000`00000000 : nt!IovpCallDriver2+0x184 fffff488`0b9df670 fffff802`70dccf3b : ffff9b04`69d98430 00000000`00000000 ffff9b04`5383bdc0 fffff802`70dd96d9 : nt!VfAfterCallDriver+0x1d8 fffff488`0b9df6a0 fffff802`70862e79 : ffff9b04`69d98430 fffff488`0b9df800 ffff9b04`552b8de0 ffff9b04`5eec1880 : nt!IovCallDriver+0x277 fffff488`0b9df6e0 fffff802`70b70546 : ffff9b04`552b8de0 ffff9b04`692e3a70 00000000`00000010 00000000`00050286 : nt!IofCallDriver+0x188cc9 fffff488`0b9df720 fffff802`70769486 : ffff9b04`552b8de0 00000000`00000000 ffff9b04`692e3a70 00000000`00000000 : nt!PnpAsynchronousCall+0xea fffff488`0b9df760 fffff802`70b4b159 : 00000000`00000001 00000000`00000000 ffff9b04`552b8de0 ffff9b04`00000000 : nt!PnpSendIrp+0x9e fffff488`0b9df7d0 fffff802`70b4b0c0 : ffff9b04`692e3a70 ffff9b04`5418aa88 ffff9b04`5418aa60 00000000`00000018 : nt!PnpQueryDeviceRelations+0x51 fffff488`0b9df860 fffff802`70b4566b : ffff9b04`5418aa60 fffff488`0b9df911 00000000`00000002 00000000`00000000 : nt!PipEnumerateDevice+0xc8 fffff488`0b9df890 fffff802`70b51034 : ffff9b04`678b5700 fffff802`706d3101 fffff488`0b9df9b0 fffff802`00000002 : nt!PipProcessDevNodeTree+0x297 fffff488`0b9df960 fffff802`70777b46 : 00000001`00000003 ffff9b04`55057c60 ffff9b04`678b5770 ffff9b04`678b5770 : nt!PiProcessReenumeration+0x88 fffff488`0b9df9b0 fffff802`706498f5 : ffff9b04`3d6ac080 ffff9b04`320c7cc0 fffff802`7104b500 ffff9b04`00000000 : nt!PnpDeviceActionWorker+0x206 fffff488`0b9dfa70 fffff802`70765635 : ffff9b04`3d6ac080 00000000`00000080 ffff9b04`320d2040 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105 fffff488`0b9dfb10 fffff802`7080e3c8 : ffffc700`7f140180 ffff9b04`3d6ac080 fffff802`707655e0 afafafaf`afafafaf : nt!PspSystemThreadStartup+0x55 fffff488`0b9dfb60 00000000`00000000 : fffff488`0b9e0000 fffff488`0b9d9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 FAULTING_SOURCE_LINE: minkernel\wdf\framework\shared\core\fxdevice.cpp FAULTING_SOURCE_FILE: minkernel\wdf\framework\shared\core\fxdevice.cpp FAULTING_SOURCE_LINE_NUMBER: 1385 SYMBOL_NAME: Wdf01000!FxDevice:ispatchWithLock+0 MODULE_NAME: Wdf01000 IMAGE_NAME: Wdf01000.sys IMAGE_VERSION: 1.31.19041.5965 STACK_COMMAND: .process /r /p 0xffff9b04320d2040; .thread 0xffff9b043d6ac080 ; kb BUCKET_ID_FUNC_OFFSET: 0 FAILURE_BUCKET_ID: 0xc9_24c_VRF_Wdf01000!FxDevice:ispatchWithLock OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {4a77324b-c183-62b8-a544-6b04608ba368} Followup: MachineOwner --------- GTA 5, SOTTR and kodi crash with memory violation (error 0xc0000005) Spoiler Faulting application name: GTA5.exe, version: 1.0.3570.0, time stamp: 0x684af14b Faulting module name: dxgi.asi, version: 6.3.3.0, time stamp: 0x67c6523a Exception code: 0xc0000005 Fault offset: 0x00000000000233d4 Faulting process id: 0xa6c Faulting application start time: 0x01dc0557257aa2b5 Faulting application path: E:\Games\Grand.Theft.Auto.V.Legacy\GTA5.exe Faulting module path: E:\Games\Grand.Theft.Auto.V.Legacy\dxgi.asi Report Id: 78082770-fe05-49dd-81fc-e359bd00a9fe Faulting package full name: Faulting package-relative application ID: Faulting application name: kodi.exe, version: 21.2.0.0, time stamp: 0x678c02ae Faulting module name: kodi.exe, version: 21.2.0.0, time stamp: 0x678c02ae Exception code: 0xc0000005 Fault offset: 0x0000000000723007 Faulting process id: 0x26d8 Faulting application start time: 0x01dc054a2bc57ef5 Faulting application path: C:\Program Files\Kodi\kodi.exe Faulting module path: C:\Program Files\Kodi\kodi.exe Report Id: 3d5efdf9-4907-4711-820a-8a6a362d2b77 Faulting package full name: Faulting package-relative application ID:
megamcgirl
09-25-2025, 02:56 AM #2Checked if removing and readding graphics drivers worked. Regarding the post, does the GPU slot feel loose or not fully seated in the case?
ayapasdepb
09-25-2025, 02:56 AM #3I've experienced that situation quite often too. It seems my GPU slot or traces might be faulty, but I thought I checked and it appears okay from the front—just a slight hairline crack maybe. The PC didn’t show anything at that time, probably because he forgot to install the 8pin EPS CPU. My brother installed the GPU into the slot, which caused a noticeable snap sound from the motherboard ever since. I’ve had several stability problems lately, so I suspect the slot has lost its shape from the stress. It might be time to have my motherboard repaired.
It seems there was some physical damage. It’s a good idea to re-seat the GPU and verify all motherboard cables are properly connected. If that doesn’t resolve the issue, replacing the motherboard might be necessary. I suggest inspecting it first by removing it. Good luck, and let me know the outcome!
CrazyBessyCat
09-25-2025, 02:56 AM #7If damage occurs due to user action, repairs or replacements won't be offered. If the GPU was forced into place and broke physically, they may notice it. This also depends on whether the RMA process identifies such issues. You might send it in and wait a few weeks to a month for a replacement, or accept the notice that RMA isn't possible because of user damage. Usually, replacing it is simpler. You could obtain a new board and then RMA the faulty one—either replace it or return the temporary unit. Also, note that for an H470 motherboard from the 10th/11th generation (unless purchased new less than a year ago), manufacturer warranty likely expired, making RMA unavailable.
ErenKartal
09-25-2025, 02:56 AM #8asrock offers a 3-year warranty, leaving me with just 1 year remaining. They also mention they will repair any user-induced damage, even if it's found later.