Minecraft ce coupe et pc plante
Résolu/Fermé
A voir également:
- Minecraft ce coupe et pc plante
- Benchmark pc - Guide
- Ecran noir pc - Guide
- Reinitialiser pc - Guide
- Minecraft download pc - Télécharger - Stratégie
- Pc lent - Guide
14 réponses
Destrio5
Messages postés
85926
Date d'inscription
dimanche 11 juillet 2010
Statut
Modérateur
Dernière intervention
17 février 2023
10 297
7 juil. 2012 à 23:17
7 juil. 2012 à 23:17
Bonjour,
Utilise WhoCrashed et poste le diagnostic ici.
https://forum.malekal.com/viewtopic.php?t=16793&start=
Utilise WhoCrashed et poste le diagnostic ici.
https://forum.malekal.com/viewtopic.php?t=16793&start=
Destrio5
Messages postés
85926
Date d'inscription
dimanche 11 juillet 2010
Statut
Modérateur
Dernière intervention
17 février 2023
10 297
8 juil. 2012 à 15:00
8 juil. 2012 à 15:00
up
Personne ne sais???
Car c'est un peu lourd la, d'ailleurs plusieurs autres jeux plantent, comme league of legend et S4 league
Personne ne sais???
Car c'est un peu lourd la, d'ailleurs plusieurs autres jeux plantent, comme league of legend et S4 league
Merci, voila la liste :s
On Sat 07/07/2012 18:21:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCCC45)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600012CC45, 0xFFFFF88008959F00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 06/07/2012 15:11:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070612-18376-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0xFFFFF100112F1758, 0x1, 0xFFFFF80002CB917E, 0x7)
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 which cannot be identified at this time.
On Thu 05/07/2012 18:36:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070512-51246-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xC5 (0xFFFFFA8002BBC018, 0x2, 0x1, 0xFFFFF80002DF190D)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 05/07/2012 08:13:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070512-61230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xBE (0xFFFFF680003FFF00, 0x50D000003E86B025, 0xFFFFF88003324760, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
On Wed 04/07/2012 15:39:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-28844-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CDA638, 0xFFFFF8800753ACD0, 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 which cannot be identified at this time.
On Wed 04/07/2012 08:39:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-26036-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80002DB70BF)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 04/07/2012 08:34:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-33446-01.dmp
This was probably caused by the following module: afd.sys (afd+0x2580)
Bugcheck code: 0xD1 (0x5708245F, 0x2, 0x1, 0xFFFFF88003EEB580)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 which cannot be identified at this time.
On Sun 01/07/2012 14:02:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-29998-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00F979680, 0xFFFFF8A00F979720, 0x50A0203)
Error: BAD_POOL_HEADER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 28/06/2012 10:59:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062812-27534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x4A (0x7756F72A, 0x2, 0x0, 0xFFFFF88006B1AC60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 24/06/2012 11:31:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-18454-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x220D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800480220D, 0xFFFFF8800792D130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 24/06/2012 11:01:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-29343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0x240000, 0x0, 0xFFFFF88000CFBE63, 0x8)
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 which cannot be identified at this time.
On Sun 24/06/2012 10:59:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-30841-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xBE (0xFFFFFA800B040028, 0x29000000A6912121, 0xFFFFF88007C36060, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\070712-23930-01.dmp
Apparament : C:\Windows\Minidump\062412-29343-01.dmp
Ce serais souvent ce fichier qui bug, après comment régler le soucis :s
On Sat 07/07/2012 18:21:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCCC45)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600012CC45, 0xFFFFF88008959F00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 06/07/2012 15:11:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070612-18376-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0xFFFFF100112F1758, 0x1, 0xFFFFF80002CB917E, 0x7)
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 which cannot be identified at this time.
On Thu 05/07/2012 18:36:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070512-51246-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xC5 (0xFFFFFA8002BBC018, 0x2, 0x1, 0xFFFFF80002DF190D)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 05/07/2012 08:13:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070512-61230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xBE (0xFFFFF680003FFF00, 0x50D000003E86B025, 0xFFFFF88003324760, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
On Wed 04/07/2012 15:39:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-28844-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CDA638, 0xFFFFF8800753ACD0, 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 which cannot be identified at this time.
On Wed 04/07/2012 08:39:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-26036-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80002DB70BF)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 04/07/2012 08:34:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-33446-01.dmp
This was probably caused by the following module: afd.sys (afd+0x2580)
Bugcheck code: 0xD1 (0x5708245F, 0x2, 0x1, 0xFFFFF88003EEB580)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 which cannot be identified at this time.
On Sun 01/07/2012 14:02:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-29998-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00F979680, 0xFFFFF8A00F979720, 0x50A0203)
Error: BAD_POOL_HEADER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 28/06/2012 10:59:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062812-27534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x4A (0x7756F72A, 0x2, 0x0, 0xFFFFF88006B1AC60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 24/06/2012 11:31:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-18454-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x220D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800480220D, 0xFFFFF8800792D130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 24/06/2012 11:01:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-29343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0x240000, 0x0, 0xFFFFF88000CFBE63, 0x8)
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 which cannot be identified at this time.
On Sun 24/06/2012 10:59:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-30841-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xBE (0xFFFFFA800B040028, 0x29000000A6912121, 0xFFFFF88007C36060, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 which cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\070712-23930-01.dmp
Apparament : C:\Windows\Minidump\062412-29343-01.dmp
Ce serais souvent ce fichier qui bug, après comment régler le soucis :s
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Destrio5
Messages postés
85926
Date d'inscription
dimanche 11 juillet 2010
Statut
Modérateur
Dernière intervention
17 février 2023
10 297
8 juil. 2012 à 13:16
8 juil. 2012 à 13:16
Est-ce que Windows est à jour (Windows Update) ?
Est-ce que tu as mis le pilote de ta carte graphique à jour ?
As-tu essayé de jouer en désactivant temporairement l'antivirus ?
Est-ce que tu as mis le pilote de ta carte graphique à jour ?
As-tu essayé de jouer en désactivant temporairement l'antivirus ?
La carte graphique oui elle est à jour, je l'ai fait après les premiers plantage.
Et j'ai 2 mises à jours importantes mais elles ne ce font pas, ça bug :s
Et j'ai 2 mises à jours importantes mais elles ne ce font pas, ça bug :s
Destrio5
Messages postés
85926
Date d'inscription
dimanche 11 juillet 2010
Statut
Modérateur
Dernière intervention
17 février 2023
10 297
8 juil. 2012 à 14:27
8 juil. 2012 à 14:27
Tu peux me donner leurs noms ?
Destrio5
Messages postés
85926
Date d'inscription
dimanche 11 juillet 2010
Statut
Modérateur
Dernière intervention
17 février 2023
10 297
8 juil. 2012 à 15:11
8 juil. 2012 à 15:11
windows6.1-KB976932-X64.exe
J'ai tout installer et mis à jour
Apparemment cela ne plante plus, pour le moment en tout cas.
Merci pour ton aide
Apparemment cela ne plante plus, pour le moment en tout cas.
Merci pour ton aide
Destrio5
Messages postés
85926
Date d'inscription
dimanche 11 juillet 2010
Statut
Modérateur
Dernière intervention
17 février 2023
10 297
8 juil. 2012 à 21:18
8 juil. 2012 à 21:18
Bonne soirée ;)