Crash / écran noir sur nouvelle configuration Solved

Question

Hello, My girlfriend recently changed her GPU due to overheating and instability issues with her previous one. She had a GTX 1080 that was getting old and switched to a RTX 5070. She was planning to change the motherboard and CPU at the end of the year. Since the new card has been installed, she regularly experiences (3-4 times a day) system crashes (complete freeze of the screen and audio, and nothing works until a forced reboot). We suspected a compatibility issue between the GPU and the older components, but before taking the easy way out, we preferred to diagnose the origin of the problem to be sure it was a hardware issue. The current setup is as follows:  OS: Windows 10 GPU: MSI RTX 5070 Ventus CPU: i7-6700K MB: MSI z170A Gaming Pro Carbon PSU: G750M Cooler Master (750 W)  We have tried several solutions that have not worked so far:  Windows update Complete reinstallation of drivers (via DDU in safe mode) Installation of an older driver known to be more stable (572.83) Activation of safe boot following an error indicated in the event viewer BIOS update Change of PCI E slot Change of PCI E generation (gen switch) in the BIOS (feature not available on this motherboard) Change of GPU wiring (previously "daisy chained") Repair of corrupted files via sfc /scannow  After the BIOS update, the freezes sometimes turned into black screens, and the event viewer indicated the following message: The computer has restarted after a bug check. The bug check was: 0x00000116 (0xffff800c48cf2410, 0xfffff801a3d54930, 0xffffffffc000009a, 0x0000000000000004). A dump was recorded in: C:\WINDOWS\Minidump\092525-6812-01.dmp. Report ID: 7c0ddb6c-8c41-4582-b051-99353b5dda58. Two dump files were generated indicating a link with nvlddmkm.sys, the details will be posted at the end of the message. I noticed that two nvlddmkm.sys files were present in her System32 folder; I don't know if this has anything to do with our problem, I haven't really found any information about it. Among the remaining solutions, we plan to attempt:  Change the security settings of nvlddmkm.sys to Full Control for the Users group (solution often mentioned) Resetting overclocking settings via MSI Afterburner Complete reinstallation of Windows  For now, we have ruled out the possibility of a power supply problem, although it is relatively old, the power supply has been working perfectly until now. Finally, here are the WinDbg analysis reports: ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffbf067628c010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff80287e34930, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data. Debugging Details: ------------------ Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1     Key  : Analysis.CPU.mSec     Value: 1609     Key  : Analysis.Elapsed.mSec     Value: 7613     Key  : Analysis.IO.Other.Mb     Value: 0     Key  : Analysis.IO.Read.Mb     Value: 1     Key  : Analysis.IO.Write.Mb     Value: 0     Key  : Analysis.Init.CPU.mSec     Value: 781     Key  : Analysis.Init.Elapsed.mSec     Value: 76356     Key  : Analysis.Memory.CommitPeak.Mb     Value: 108     Key  : Analysis.Version.DbgEng     Value: 10.0.27920.1001     Key  : Analysis.Version.Description     Value: 10.2506.23.01 amd64fre     Key  : Analysis.Version.Ext     Value: 1.2506.23.1     Key  : Bugcheck.Code.LegacyAPI     Value: 0x116     Key  : Bugcheck.Code.TargetModel     Value: 0x116     Key  : Dump.Attributes.AsUlong     Value: 0x8     Key  : Dump.Attributes.KernelGeneratedTriageDump     Value: 1     Key  : Failure.Bucket     Value: 0x116_IMAGE_nvlddmkm.sys     Key  : Failure.Exception.IP.Address     Value: 0xfffff80287e34930     Key  : Failure.Exception.IP.Module     Value: nvlddmkm     Key  : Failure.Exception.IP.Offset     Value: 0x1874930     Key  : Failure.Hash     Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}     Key  : WER.System.BIOSRevision     Value: 5.12.0.0  BUGCHECK_CODE:  116 BUGCHECK_P1: ffffbf067628c010 BUGCHECK_P2: fffff80287e34930 BUGCHECK_P3: ffffffffc000009a BUGCHECK_P4: 4 FILE_IN_CAB:  092625-5578-01.dmp DUMP_FILE_ATTRIBUTES: 0x8   Kernel Generated Triage Dump FAULTING_THREAD:  ffffbf067ad2c040 VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffbf067628c010 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: 0000000000000004 BLACKBOXBSD: 1 (!blackboxbsd)  BLACKBOXNTFS: 1 (!blackboxntfs)  BLACKBOXPNP: 1 (!blackboxpnp)  BLACKBOXWINLOGON: 1 (!blackboxwinlogon)  CUSTOMER_CRASH_COUNT:  1 PROCESS_NAME:  System STACK_TEXT:   ffffad0d`aa58f918 fffff802`6d2d6efe     : 00000000`00000116 ffffbf06`7628c010 fffff802`87e34930 ffffffff`c000009a : nt!KeBugCheckEx ffffad0d`aa58f920 fffff802`6d287474     : fffff802`87e34930 ffffbf06`78cca660 00000000`00002000 ffffbf06`78cca720 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffffad0d`aa58f960 fffff802`6d27ffac     : ffffbf06`78ce0000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174 ffffad0d`aa58f990 fffff802`6d2d6625     : 00000000`00000100 ffffbf06`78ce0a70 00000000`763f81f0 fffff802`585083fc : dxgkrnl!DXGADAPTER::Reset+0x4dc ffffad0d`aa58fa10 fffff802`6d2d6797     : fffff802`58f25440 ffffbf06`7c6ca290 00000000`00000000 00000000`00000400 : dxgkrnl!TdrResetFromTimeout+0x15 ffffad0d`aa58fa40 fffff802`584418f5     : ffffbf06`7ad2c040 fffff802`6d2d6770 ffffbf06`70eb49a0 ffffbf06`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27 ffffad0d`aa58fa70 fffff802`5855d6e5     : ffffbf06`7ad2c040 00000000`00000080 ffffbf06`70eba080 00000000`00000000 : nt!ExpWorkerThread+0x105 ffffad0d`aa58fb10 fffff802`58606578     : ffffd280`92be5180 ffffbf06`7ad2c040 fffff802`5855d690 00000000`00000246 : nt!PspSystemThreadStartup+0x55 ffffad0d`aa58fb60 00000000`00000000     : ffffad0d`aa590000 ffffad0d`aa589000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28  SYMBOL_NAME:  nvlddmkm+1874930 MODULE_NAME: nvlddmkm IMAGE_NAME:  nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffbf0670eba080; .thread 0xffffbf067ad2c040 ; kb FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys OSPLATFORM_TYPE:  x64 OSNAME:  Windows 10 FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd} Followup:     MachineOwner ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffff800c48cf2410, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff801a3d54930, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data. Debugging Details: ------------------ Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1     Key  : Analysis.CPU.mSec     Value: 1828     Key  : Analysis.Elapsed.mSec     Value: 26118     Key  : Analysis.IO.Other.Mb     Value: 1     Key  : Analysis.IO.Read.Mb     Value: 1     Key  : Analysis.IO.Write.Mb     Value: 39     Key  : Analysis.Init.CPU.mSec     Value: 2156     Key  : Analysis.Init.Elapsed.mSec     Value: 455173     Key  : Analysis.Memory.CommitPeak.Mb     Value: 101     Key  : Analysis.Version.DbgEng     Value: 10.0.27920.1001     Key  : Analysis.Version.Description     Value: 10.2506.23.01 amd64fre     Key  : Analysis.Version.Ext     Value: 1.2506.23.1     Key  : Bugcheck.Code.LegacyAPI     Value: 0x116     Key  : Bugcheck.Code.TargetModel     Value: 0x116     Key  : Dump.Attributes.AsUlong     Value: 0x8     Key  : Dump.Attributes.KernelGeneratedTriageDump     Value: 1     Key  : Failure.Bucket     Value: 0x116_IMAGE_nvlddmkm.sys     Key  : Failure.Exception.IP.Address     Value: 0xfffff801a3d54930     Key  : Failure.Exception.IP.Module     Value: nvlddmkm     Key  : Failure.Exception.IP.Offset     Value: 0x1874930     Key  : Failure.Hash     Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}     Key  : WER.System.BIOSRevision     Value: 5.12.0.0  BUGCHECK_CODE:  116 BUGCHECK_P1: ffff800c48cf2410 BUGCHECK_P2: fffff801a3d54930 BUGCHECK_P3: ffffffffc000009a BUGCHECK_P4: 4 FILE_IN_CAB:  092525-6812-01.dmp DUMP_FILE_ATTRIBUTES: 0x8   Kernel Generated Triage Dump FAULTING_THREAD:  ffff800c43991040 VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff800c48cf2410 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: 0000000000000004 BLACKBOXBSD: 1 (!blackboxbsd)  BLACKBOXNTFS: 1 (!blackboxntfs)  BLACKBOXPNP: 1 (!blackboxpnp)  BLACKBOXWINLOGON: 1 (!blackboxwinlogon)  CUSTOMER_CRASH_COUNT:  1 PROCESS_NAME:  System STACK_TEXT:   ffffd68d`4c677918 fffff801`88116efe     : 00000000`00000116 ffff800c`48cf2410 fffff801`a3d54930 ffffffff`c000009a : nt!KeBugCheckEx ffffd68d`4c677920 fffff801`880c7474     : fffff801`a3d54930 ffff800c`3b1ea720 00000000`00002000 ffff800c`3b1ea7e0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffffd68d`4c677960 fffff801`880bffac     : ffff800c`3b1c9000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174 ffffd68d`4c677990 fffff801`88116625     : 00000000`00000100 ffff800c`3b1c9a70 00000000`3bcc86d0 fffff801`717083fc : dxgkrnl!DXGADAPTER::Reset+0x4dc ffffd68d`4c677a10 fffff801`88116797     : fffff801`72125440 ffff800c`3e8602d0 00000000`00000000 00000000`00000200 : dxgkrnl!TdrResetFromTimeout+0x15 ffffd68d`4c677a40 fffff801`716418f5     : ffff800c`43991040 fffff801`88116770 ffff800c`32b02a60 ffff800c`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27 ffffd68d`4c677a70 fffff801`7175d6e5     : ffff800c`43991040 00000000`00000080 ffff800c`32aaf040 00000000`00000000 : nt!ExpWorkerThread+0x105 ffffd68d`4c677b10 fffff801`71806578     : ffff9701`16da3180 ffff800c`43991040 fffff801`7175d690 00000000`00000001 : nt!PspSystemThreadStartup+0x55 ffffd68d`4c677b60 00000000`00000000     : ffffd68d`4c678000 ffff68d`4c671000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28  SYMBOL_NAME:  nvlddmkm+1874930 MODULE_NAME: nvlddmkm IMAGE_NAME:  nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffff800c32aaf040; .thread 0xffff800c43991040 ; kb FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys OSPLATFORM_TYPE:  x64 OSNAME:  Windows 10 FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd} Followup:     MachineOwner

flo88 · Answer

Hello The RTX 5070 doesn't specifically require a more powerful power supply than the GTX 1080, however, it consumes much more power on the PCI Express port because current motherboards deliver more due to modifications in the PCI Express 16 standard dedicated to graphics cards. Given the age of your motherboard, it's quite likely that the 5070 will overload the voltage on the bus. For me, there is no solution. The problem is known.

Crash / écran noir sur nouvelle configuration

1 réponse

Old lullaby

Texture issues in enshrouded

Unable to connect to freebox os

Edit ad on leboncoin for free

Freebox wifi password

Computer tower that won't turn on

Blocked: are my messages still being delivered?

Video intercom inspector

Your computer can't use another display.

Fransat decoder stuck