Ecran de la mort stop 0x0000000A
alexdu62510
Messages postés
117
Date d'inscription
Statut
Membre
Dernière intervention
-
alexdu62510 Messages postés 117 Date d'inscription Statut Membre Dernière intervention -
alexdu62510 Messages postés 117 Date d'inscription Statut Membre Dernière intervention -
Bonjours a tous j'ai windows 7 ultimate 64bit et j'ai eu il y a peu de temps pendant que je jouer a minecraft un ecran bleu appeler ecran de la mort, alors suite a ça j'ai faitt une mise a nieau de windows et quand je l'ai reinstaller il y aquelque jour l'ecran est revenu mais pas avec la meme erreur cette fois c'est stop 0x0000000A, il parret que c'est un logiciel incompatible mais comment savoir lequel merci.
A voir également:
- Ecran de la mort stop 0x0000000A
- Stop 36200 - Guide
- Double ecran - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Windows stop code - Guide
- Retourner ecran pc - Guide
1 réponse
voila le rapport de whocrashed:
System Information (local)
--------------------------------------------------------------------------------
computer name: ALEXIS-JO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Extensa 5235 , Acer , BA50-MV
CPU: GenuineIntel Intel(R) Celeron(R) CPU 900 @ 2.20GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 3146711040 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 28/07/2014 19:28:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072814-37346-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xA (0xFFFFFA8014446010, 0x2, 0x1, 0xFFFFF80002F442A6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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/07/2014 19:28:38 GMT 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: 0xA (0xFFFFFA8014446010, 0x2, 0x1, 0xFFFFF80002F442A6)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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
--------------------------------------------------------------------------------
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.
System Information (local)
--------------------------------------------------------------------------------
computer name: ALEXIS-JO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Extensa 5235 , Acer , BA50-MV
CPU: GenuineIntel Intel(R) Celeron(R) CPU 900 @ 2.20GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 3146711040 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 28/07/2014 19:28:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072814-37346-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xA (0xFFFFFA8014446010, 0x2, 0x1, 0xFFFFF80002F442A6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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/07/2014 19:28:38 GMT 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: 0xA (0xFFFFFA8014446010, 0x2, 0x1, 0xFFFFF80002F442A6)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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
--------------------------------------------------------------------------------
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.