Crash intempestif
halphasten
Messages postés
4
Statut
Membre
-
halphasten Messages postés 4 Statut Membre -
halphasten Messages postés 4 Statut Membre -
bonjour,
j'ai récemment acheter et monter mon premier ordinateur pièce par pièce, mais qui est malheureusement sujet a de nombreux crash.
j'ais essayer de mettre a jour Windows et les pilotes sans succès, avent de devoirs formater mon disque dur et réinstaller Windows a cause d'un problème avec la fonction "verifier" de l'ordinateur.
les crash persiste toujours, même après remise a niveaux de Windows et des pilote, je vous indique ici quelle-que rapport de crashe obtenue via WhoCrashed :
On Fri 01/09/2017 09:10:59 your computer crashed
crash dump file: C:\Windows\Minidump\090117-4000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0xEF (0xFFFFB68977654180, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 01/09/2017 09:10:59 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!memset+0x8DA)
Bugcheck code: 0xEF (0xFFFFB68977654180, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED
On Fri 01/09/2017 09:10:18 your computer crashed
crash dump file: C:\Windows\Minidump\090117-4234-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Thu 31/08/2017 10:34:14 your computer crashed
crash dump file: C:\Windows\Minidump\083117-4093-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF8018DCEF653)
Bugcheck code: 0xD1 (0xFFFFD0840C730348, 0x2, 0x0, 0xFFFFF8018DCEF653)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
On Thu 31/08/2017 10:20:39 your computer crashed
crash dump file: C:\Windows\Minidump\083117-4281-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x3F3A3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80BB96EF3A3, 0xFFFFBA017ECE6418, 0xFFFFBA017ECE5C60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 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.
se pourrais t'il que l'un des composant de l'ordinateur soit en mauvais état ou malle monter ? je tien a préciser que sur les deux barrette de RAM, l'une est défectueuse et cause de nombreux crash, je l'ai retirer, mais la second barrette n'est pas détecter comme défectueuse par MemTest86
quelle composant est défectueux ?
ou quelle mise a jour dois-je installer ?
quelque indication :
windows 10
intel cor I5 7600
geforce GTX 1060
MSI Krait Gaming B250
1x8 G de RAM (plus 8G défectueux)
merci d’avance pour vos réponde
j'ai récemment acheter et monter mon premier ordinateur pièce par pièce, mais qui est malheureusement sujet a de nombreux crash.
j'ais essayer de mettre a jour Windows et les pilotes sans succès, avent de devoirs formater mon disque dur et réinstaller Windows a cause d'un problème avec la fonction "verifier" de l'ordinateur.
les crash persiste toujours, même après remise a niveaux de Windows et des pilote, je vous indique ici quelle-que rapport de crashe obtenue via WhoCrashed :
On Fri 01/09/2017 09:10:59 your computer crashed
crash dump file: C:\Windows\Minidump\090117-4000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0xEF (0xFFFFB68977654180, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 01/09/2017 09:10:59 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!memset+0x8DA)
Bugcheck code: 0xEF (0xFFFFB68977654180, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED
On Fri 01/09/2017 09:10:18 your computer crashed
crash dump file: C:\Windows\Minidump\090117-4234-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Thu 31/08/2017 10:34:14 your computer crashed
crash dump file: C:\Windows\Minidump\083117-4093-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF8018DCEF653)
Bugcheck code: 0xD1 (0xFFFFD0840C730348, 0x2, 0x0, 0xFFFFF8018DCEF653)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
On Thu 31/08/2017 10:20:39 your computer crashed
crash dump file: C:\Windows\Minidump\083117-4281-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x3F3A3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80BB96EF3A3, 0xFFFFBA017ECE6418, 0xFFFFBA017ECE5C60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 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.
se pourrais t'il que l'un des composant de l'ordinateur soit en mauvais état ou malle monter ? je tien a préciser que sur les deux barrette de RAM, l'une est défectueuse et cause de nombreux crash, je l'ai retirer, mais la second barrette n'est pas détecter comme défectueuse par MemTest86
quelle composant est défectueux ?
ou quelle mise a jour dois-je installer ?
quelque indication :
windows 10
intel cor I5 7600
geforce GTX 1060
MSI Krait Gaming B250
1x8 G de RAM (plus 8G défectueux)
merci d’avance pour vos réponde
3 réponses
bjr
faut voir avec un autre système si ça fais
la même chose
ça semble quand même être du a des pilotes
faut voir avec un autre système si ça fais
la même chose
ça semble quand même être du a des pilotes
après test, aucun crash ne se produit sous Ubuntu, et après avoir remplacer certain fichier détecter comme responsable de crash par WhoCrashed, il ne reste plus que le fichier win32kfull.sys
cependant, lorsque j'ai tenter de remplacer ce fichier, l'ordinateur ne pouvais même plus démarrer, j'ai du passer par Ubuntu pour remettre le fichier d'origine, que j'avais heureusement conserver
des idée pour éviter ce genre de crash ?
voici un rapport type de crash :
On Wed 06/09/2017 15:32:21 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!Win32AllocPoolImpl+0x2E)
Bugcheck code: 0x19 (0xE, 0xFFFF8158C1D57750, 0xA48D38D3CD3B864E, 0xA48D38D3CF3B864E)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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.
merci d’avance pour vos conseille
cependant, lorsque j'ai tenter de remplacer ce fichier, l'ordinateur ne pouvais même plus démarrer, j'ai du passer par Ubuntu pour remettre le fichier d'origine, que j'avais heureusement conserver
des idée pour éviter ce genre de crash ?
voici un rapport type de crash :
On Wed 06/09/2017 15:32:21 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!Win32AllocPoolImpl+0x2E)
Bugcheck code: 0x19 (0xE, 0xFFFF8158C1D57750, 0xA48D38D3CD3B864E, 0xA48D38D3CF3B864E)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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.
merci d’avance pour vos conseille
