Bonjour,
je viens vers vous car je suis face a une impasse :
Depuis la sortie de new world mon pc a des soucis d'arrêt d'urgence mais ce n'est pas le jeux qui pose problème.
En effet j'ai constaté que mon proc et ma carte graphique chauffaient trop (+ de 85 / 90°).
De ce fait, j'ai changé le ventilateur de mon proc ainsi que la pate thermique.
Pour la carte graphique, je l'ai dépoussiéré et changer la pate thermique aussi.
Depuis, j'ai des BSOD en boucle.
voici le retour de whocrashed:
System Information (local)
--------------------------------------------------------------------------------
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\Windows
Hardware: MS-7B45, Micro-Star International Co., Ltd., Z370 GAMING PRO CARBON (MS-7B45)
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 8664, level: 6
12 logical processors, active mask: 4095
RAM: 17119117312 bytes (15,9G
rajout de ma part:
Carte graphique : MSI Nvidia GeForce GTX 1080 Ti
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sat 16/10/2021 11:07:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101621-14984-01.dmp
This was probably caused by the following module: e1d68x64.sys (0xFFFFF806565E3420)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF806565E3420, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\System32\DriverStore\FileRepository\e1d 68x64.inf_amd64_ae1f744955c174dc\e1d68x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e1d68x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: e1d68x64.sys Intel Corporation KMODE_EXCEPTION_NOT_HANDLED
On Sat 16/10/2021 11:07:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: e1d68x64.sys (0xFFFFF806565E3420)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF806565E3420, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\System32\DriverStore\FileRepository\e1d 68x64.inf_amd64_ae1f744955c174dc\e1d68x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e1d68x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: e1d68x64.sys Intel Corporation KMODE_EXCEPTION_NOT_HANDLED
On Sat 16/10/2021 11:05:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101621-15171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x50 (0xFFFF8A0845040180, 0x0, 0xFFFFF8074112E088, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 16/10/2021 11:03:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101621-14828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8043D3686D3, 0xFFFF920DE6769B88, 0xFFFF810002486920)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 16/10/2021 10:09:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101621-15562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x139 (0x3, 0xFFFFF807244B1540, 0xFFFFF807244B1498, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 16/10/2021 09:59:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101621-15359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF8005A9038C3, 0xFFFF8D874A716458, 0xFFFF8D874A715C90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
e1d68x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Depuis:
J'ai fais un memtest qui n'a donné aucune erreur.
J'ai totalement réinstaller Windows en formatant tous mes disques dur.
J'ai fais une vérification des disques dur via l'outil Windows.
j'ai mis une version plus vieille de pilote graphique qui fonctionnait correctement.
J'ai mis a jour tous les driver (sauf la carte graphique du coup).
j'ai vérifier tous mes composants physiquement.
Le Bios est a jour.
J'aimerai avoir votre avis avant de balancer le pc par la fenêtre :D
Merci d'avance