Crash du pc en jeu - Win 10 - Windows & Software
Marsh Posté le 28-11-2016 à 20:34:55
Je viens de faire une analyse avec WhoCrashed. Voici son rapport :
System Information (local)
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: MS-7976, MSI, Z170A GAMING M7 (MS-7976)
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17137807360 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 26/11/2016 17:27:24 your computer crashed
crash dump file: C:\Windows\Minidump\112616-75203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970)
Bugcheck code: 0xF7 (0xFFFFFFFFFFF0BDC0, 0xC56373878D5F, 0xFFFF3A9C8C7872A0, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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 26/11/2016 17:27:24 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalRequestSoftwareInterrupt+0x165)
Bugcheck code: 0xF7 (0xFFFFFFFFFFF0BDC0, 0xC56373878D5F, 0xFFFF3A9C8C7872A0, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
Marsh Posté le 28-11-2016 à 20:35:23
Bon après tentative de fixer le problème du ntoskrnl.exe, le pc ne plante plus mais le jeu fige et j'ai plus accès à rien à part le menu via la touche windows. Des idées?
edit : j'ai parlé trop vite.
WhoCrashed :
On Mon 28/11/2016 16:26:55 your computer crashed
crash dump file: C:\Windows\Minidump\112816-5562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF802A9498213, 0xFFFFD00023E9FB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Mon 28/11/2016 16:26:55 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF802A9498213, 0xFFFFD00023E9FB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Mon 28/11/2016 16:25:44 your computer crashed
crash dump file: C:\Windows\Minidump\112816-5796-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xC3D33)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF801CAF33D33, 0xFFFFE0000C9B8340, 0xFFFFC0008223D4B0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a kernel-mode program 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Ça me fatigue!
Marsh Posté le 28-11-2016 à 20:34:29
Bonjour,
Je viens à vous dans l'espoir de trouver une solution. (enfin, mon épouse, ci joint le copier/collé d'un topic crée sur un autre forum, sans réponses. Si vous pouviez nous aider, cela m'arrangerai, ca me gonfle un peu de lui avoir offert une config de gamer, et de ne pas être foutu de le faire tourner (et ca la gonfle encore plus! merci ).
Lorsque j'entre en jeu (GW2 pour être précise), le pc crash systématiquement. Le code erreur correspond à un problème de driver. Mais tous les drivers ont été mis à jour. On a vérifier la ram; le cpu, tout est ok. Je ne sais plus quoi faire.
Voici ma config :
carte mère MSI Z170A GAMING M7
processeur Intel Core i7-6700K (4.0 GHz)
carte graphique MSI GeForce GTX 980 Ti GAMING 6G, 6 Go
DDR4 G.Skill Ripjaws V 2 x 8 Go, 2666 MHz, CAS 15
SSD 240 Go SATA III
hd 3 x 1 To
Système d'exploitation : Windows 10
Le pc fonctionnait parfaitement jusqu'au formatage qui a précédé son acquisition (je l'ai vu tourner sur Dying Light). La config a moins d'un an
Message édité par tooffy le 28-11-2016 à 20:37:04
---------------
Dans l'espace, personne ne vous entend faire une raclette ...