Crach intempestif de windows 7 (Image à l'appui)
tony123
Messages postés
29
Date d'inscription
Statut
Membre
Dernière intervention
-
jeanbern Messages postés 13848 Date d'inscription Statut Contributeur Dernière intervention -
jeanbern Messages postés 13848 Date d'inscription Statut Contributeur Dernière intervention -
Bonjour, il arrive souvent que mon Ordi portable affiche spontanément ce genre d'écriture en anglais sous fond bleu pendant que je suis dessus. C'est arriver plusieurs fois, et quand ça arrive, J'étains mon PC de force et je le ré allume par la suite. De quelle PB peut t'il s'agir?
PS: j'ai masquer certain chiffre sur l'image, comme je ne sais pas de quoi il peut s'agir
PS: j'ai masquer certain chiffre sur l'image, comme je ne sais pas de quoi il peut s'agir
A voir également:
- Crach intempestif de windows 7 (Image à l'appui)
- Photofiltre 7 - Télécharger - Retouche d'image
- Clé windows 7 - Guide
- Passer de windows 7 à windows 10 - Accueil - Mise à jour
- Windows defender windows 7 - Télécharger - Antivirus & Antimalwares
- Télécharger windows 7 32 bits usb - Télécharger - Systèmes d'exploitation
8 réponses
Tu va télécharger : WhoCrashed
Tu fais analyse puis OK
et descend la barre latérale droite
et tu me fait un copier / coller
Tu fais analyse puis OK
et descend la barre latérale droite
et tu me fait un copier / coller
System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: LIFEBOOK AH531, FUJITSU, FJNBB0F
CPU: GenuineIntel Intel(R) Pentium(R) CPU B960 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3668570112 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 18/02/2015 17:13:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021815-16926-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3DBF9)
Bugcheck code: 0x4A (0xFFFFFFFF95395C80, 0x2, 0x0, 0x0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.
On Wed 18/02/2015 17:13:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!ZwYieldExecution+0xEC5)
Bugcheck code: 0x4A (0xFFFFFFFF95395C80, 0x2, 0x0, 0x0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_GT_ZERO_AT_SYSTEM_SERVICE
On Fri 30/01/2015 10:28:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013015-28282-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x38E73)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000006, 0xFFFFFFFF8324CE73, 0xFFFFFFFF92BFCADC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 21/01/2015 18:10:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012115-58859-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x24C3B7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF834923B7, 0xFFFFFFFF92BF4B28, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 13/01/2015 06:09:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011315-54335-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x24C373)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8348E373, 0xFFFFFFFF921E4B28, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: LIFEBOOK AH531, FUJITSU, FJNBB0F
CPU: GenuineIntel Intel(R) Pentium(R) CPU B960 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3668570112 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 18/02/2015 17:13:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021815-16926-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3DBF9)
Bugcheck code: 0x4A (0xFFFFFFFF95395C80, 0x2, 0x0, 0x0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.
On Wed 18/02/2015 17:13:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!ZwYieldExecution+0xEC5)
Bugcheck code: 0x4A (0xFFFFFFFF95395C80, 0x2, 0x0, 0x0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_GT_ZERO_AT_SYSTEM_SERVICE
On Fri 30/01/2015 10:28:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013015-28282-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x38E73)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000006, 0xFFFFFFFF8324CE73, 0xFFFFFFFF92BFCADC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 21/01/2015 18:10:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012115-58859-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x24C3B7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF834923B7, 0xFFFFFFFF92BF4B28, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 13/01/2015 06:09:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011315-54335-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x24C373)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8348E373, 0xFFFFFFFF921E4B28, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Quand les causes des BSoD sont aussi multiples, il y a deux choses à vérifier :
La mémoire et l'intégrité du disque dur.
Avec Windows 7:
Dans le panneau de configuration, Outils d'administration, Diagnostic de mémoire Windows, choisis parmi les deux options proposées.
Cette opération se fera au redémarrage.
Un rapport sera affiché sur le bureau en cas de problème.
La mémoire et l'intégrité du disque dur.
Avec Windows 7:
Dans le panneau de configuration, Outils d'administration, Diagnostic de mémoire Windows, choisis parmi les deux options proposées.
Cette opération se fera au redémarrage.
Un rapport sera affiché sur le bureau en cas de problème.