Plantages fréquents - ecran bleu
Résolu/Fermé
artis31
Messages postés
42
Date d'inscription
vendredi 9 mai 2008
Statut
Membre
Dernière intervention
8 décembre 2012
-
1 déc. 2012 à 12:33
artis31 Messages postés 42 Date d'inscription vendredi 9 mai 2008 Statut Membre Dernière intervention 8 décembre 2012 - 8 déc. 2012 à 12:41
artis31 Messages postés 42 Date d'inscription vendredi 9 mai 2008 Statut Membre Dernière intervention 8 décembre 2012 - 8 déc. 2012 à 12:41
A voir également:
- Plantages fréquents - ecran bleu
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran samsung - Guide
- Ecran noir pc - Guide
- Ecran d'accueil iphone - Guide
4 réponses
artis31
Messages postés
42
Date d'inscription
vendredi 9 mai 2008
Statut
Membre
Dernière intervention
8 décembre 2012
1
1 déc. 2012 à 15:47
1 déc. 2012 à 15:47
Re-bonjour,
Suite à la lecture d'autres messages identiques j'ai téléchargé Whocrashed et je vous copie ici l'analyse faite :
System Information (local)
--------------------------------------------------------------------------------
computer name: PC_BUREAU
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3219611648 total
VM: 2147352576, free: 1849831424
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 01/12/2012 09:21:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120112-17425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA0100000104, 0x1, 0xFFFFF800035CA6D9, 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 that cannot be identified at this time.
On Fri 30/11/2012 17:03:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113012-37518-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF80000B9C120, 0x0, 0x0, 0xFFFFF800032E061B)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
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 30/11/2012 17:01:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113012-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF5, 0x0, 0xFFFFF800035959AE, 0x0)
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 that cannot be identified at this time.
On Thu 29/11/2012 17:26:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112912-20092-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF88009BEB240, 0x0, 0x0, 0xFFFFF8000329A61B)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 29/11/2012 17:09:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112912-21824-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF80004864120, 0x0, 0x0, 0xFFFFF800032E361B)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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 actually 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.
Suite à la lecture d'autres messages identiques j'ai téléchargé Whocrashed et je vous copie ici l'analyse faite :
System Information (local)
--------------------------------------------------------------------------------
computer name: PC_BUREAU
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3219611648 total
VM: 2147352576, free: 1849831424
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 01/12/2012 09:21:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120112-17425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA0100000104, 0x1, 0xFFFFF800035CA6D9, 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 that cannot be identified at this time.
On Fri 30/11/2012 17:03:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113012-37518-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF80000B9C120, 0x0, 0x0, 0xFFFFF800032E061B)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
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 30/11/2012 17:01:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113012-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF5, 0x0, 0xFFFFF800035959AE, 0x0)
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 that cannot be identified at this time.
On Thu 29/11/2012 17:26:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112912-20092-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF88009BEB240, 0x0, 0x0, 0xFFFFF8000329A61B)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 29/11/2012 17:09:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112912-21824-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF80004864120, 0x0, 0x0, 0xFFFFF800032E361B)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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 actually 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.
fait une mise à jour du bios , si cela ne se réponds pas change la ram , ou l'inverse change de ram si cela ne réponds pas fait une mise à jour du bios.
moi je , je suis donc , bien volontiers , merci , et autre signe ostentatoire son obligatoire , je change la ram direct , normal .
Je porte ma croix
moi je , je suis donc , bien volontiers , merci , et autre signe ostentatoire son obligatoire , je change la ram direct , normal .
Je porte ma croix
artis31
Messages postés
42
Date d'inscription
vendredi 9 mai 2008
Statut
Membre
Dernière intervention
8 décembre 2012
1
3 déc. 2012 à 18:21
3 déc. 2012 à 18:21
Bonsoir,
Merci pour ta réponse, même si je n'ai pas bien compris la seconde et troisième phrase ;o)
Bios mis à jour, réinstallation complète de Vista puis mise à jour de Vista vers Windows 7 (parce que HP ne fait pas les mises à jour compatibles Windows 7......... ), ce soir plein d'espoir, sortie de veille prolongée, 10mn après plantage...
Je vais tester en enlevant l'une puis l'autre barrette de RAM en espérant ne pas avoir à changer les deux...
Voici le log du dernier plantage :
System Information (local)
--------------------------------------------------------------------------------
computer name: PC_THIERRY
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3219628032 total
VM: 2147352576, free: 1976328192
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 03/12/2012 17:06:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-37299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x13339, 0xB08B00026662)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.
Bon, je vais
Merci pour ta réponse, même si je n'ai pas bien compris la seconde et troisième phrase ;o)
Bios mis à jour, réinstallation complète de Vista puis mise à jour de Vista vers Windows 7 (parce que HP ne fait pas les mises à jour compatibles Windows 7......... ), ce soir plein d'espoir, sortie de veille prolongée, 10mn après plantage...
Je vais tester en enlevant l'une puis l'autre barrette de RAM en espérant ne pas avoir à changer les deux...
Voici le log du dernier plantage :
System Information (local)
--------------------------------------------------------------------------------
computer name: PC_THIERRY
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3219628032 total
VM: 2147352576, free: 1976328192
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 03/12/2012 17:06:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-37299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x13339, 0xB08B00026662)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.
Bon, je vais
artis31
Messages postés
42
Date d'inscription
vendredi 9 mai 2008
Statut
Membre
Dernière intervention
8 décembre 2012
1
8 déc. 2012 à 12:41
8 déc. 2012 à 12:41
Bon effectivement après suppression de 2 barettes de mémoire, plus de plantage. Ca devait venir de là.
Merci !!
Merci !!
