Mon pc plante
pebounet
-
pebounet Messages postés 21 Statut Membre -
pebounet Messages postés 21 Statut Membre -
Bonjour, depuis un peut plus d'une semaine j'ai un gros probléme , mon pc "plante" ca
me mais un message bleu , puis le pc redemarre
"et quelque fois le pc fait de gros BIP BIP"
quand j'arrive sur mon bureau j'ai se message>
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7600.2.0.0.256.1
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002A16005
BCP3: 0000000000000001
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\022511-15428-01.dmp
C:\Users\pebqq\AppData\Local\Temp\WER-30061-0.sysdata.xml
Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c
Si la déclaration de confidentialité en ligne n'est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt
j'ai regarder sur internet qui ma permis de trouver un logiciel pour me dire pourquoi le pc
planter qui est "whocrashed"
j'ai fait une analyze qui donne sa ( sur 2 jour car j'ai reformater ) >
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 25/02/2011 13:29:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-15428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A16005, 0x1, 0x0)
Error: KMODE_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 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 which cannot be identified at this time.
On Fri 25/02/2011 13:29:28 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A16005, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 which cannot be identified at this time.
On Fri 25/02/2011 12:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-20295-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x4E (0x7, 0x7B1EA, 0x7B1F2, 0x0)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 24/02/2011 23:15:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-17316-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BBDEE1, 0xFFFFF88003A8BAC0, 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 Thu 24/02/2011 01:00:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022411-25708-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFD69E00000C0, 0x2, 0x1, 0xFFFFF800028E4801)
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 which cannot be identified at this time.
On Thu 24/02/2011 00:22:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022411-16707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0x80, 0x0, 0x0)
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 which cannot be identified at this time.
On Wed 23/02/2011 23:48:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022411-25942-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF900C81CA2A0, 0x0, 0xFFFFF960001A3C45, 0x2)
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.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\022511-21543-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 8 crash dumps have been found. Only 7 could be analyzed.
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.
me mais un message bleu , puis le pc redemarre
"et quelque fois le pc fait de gros BIP BIP"
quand j'arrive sur mon bureau j'ai se message>
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7600.2.0.0.256.1
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002A16005
BCP3: 0000000000000001
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\022511-15428-01.dmp
C:\Users\pebqq\AppData\Local\Temp\WER-30061-0.sysdata.xml
Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c
Si la déclaration de confidentialité en ligne n'est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt
j'ai regarder sur internet qui ma permis de trouver un logiciel pour me dire pourquoi le pc
planter qui est "whocrashed"
j'ai fait une analyze qui donne sa ( sur 2 jour car j'ai reformater ) >
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 25/02/2011 13:29:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-15428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A16005, 0x1, 0x0)
Error: KMODE_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 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 which cannot be identified at this time.
On Fri 25/02/2011 13:29:28 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A16005, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 which cannot be identified at this time.
On Fri 25/02/2011 12:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-20295-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x4E (0x7, 0x7B1EA, 0x7B1F2, 0x0)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 24/02/2011 23:15:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-17316-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BBDEE1, 0xFFFFF88003A8BAC0, 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 Thu 24/02/2011 01:00:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022411-25708-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFD69E00000C0, 0x2, 0x1, 0xFFFFF800028E4801)
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 which cannot be identified at this time.
On Thu 24/02/2011 00:22:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022411-16707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0x80, 0x0, 0x0)
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 which cannot be identified at this time.
On Wed 23/02/2011 23:48:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022411-25942-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF900C81CA2A0, 0x0, 0xFFFFF960001A3C45, 0x2)
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.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\022511-21543-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 8 crash dumps have been found. Only 7 could be analyzed.
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.
A voir également:
- Mon pc plante
- Mon pc est lent - Guide
- Reinitialiser pc - Guide
- Downloader for pc - Télécharger - Téléchargement & Transfert
- Plus de son sur mon pc - Guide
- Double ecran pc - Guide
13 réponses
Une des pieces de ton PC vient peut etre de mourir. Est ce que tu as memetest ? pour verifier tes RAM?
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
il arrive que meme des RAM neuve soient defectueuses. ca m'est arrivé avec des corsairs!
si tu ne fais pas le test, je ne pourrai pas t'aider plus...
Peut etre que quelqu'un d'autre le pourra.
si tu ne fais pas le test, je ne pourrai pas t'aider plus...
Peut etre que quelqu'un d'autre le pourra.
http://www.depannetonpc.net/fiches-pratiques/lire_35_1_tutorial-memtest.html
je t'ai mis un tuto avec pour l'utilisation.
je t'ai mis un tuto avec pour l'utilisation.
telecharge le logiciel ici :
https://www.01net.com/telecharger/windows/Utilitaire/optimiseurs_et_tests/fiches/29059.html
https://www.01net.com/telecharger/windows/Utilitaire/optimiseurs_et_tests/fiches/29059.html
Puis perso je ne pense vraiment pas , que se sois du au ram , les ecran bleu on commencer apres avoir reformater , et aussi , serai ce du , a windows update ? j'ai 3 mise a jour " importante qui ne marche pas "
héhé... tu ne croyais pas que ca allais se passer comme ça!
De toute façon, lors du lancement du logiciel, tu verras rapidement s'il voit des érreurs ou pas. le faire tourner 4 a 6h, c'est pour etre sur qu'il y a zéro défaut!
De toute façon, lors du lancement du logiciel, tu verras rapidement s'il voit des érreurs ou pas. le faire tourner 4 a 6h, c'est pour etre sur qu'il y a zéro défaut!
Bon ben si tu ne crois pas... c'ets que tu dois avoir raison...
Enfin...
Si tu pense que c'est le formatage, recommence le, si il y a toujours des erreurs apres, tu reviendras pour qu'on cherche quelle piece est defectueuse...
Bonne chance, en te souhaitant quand meme que se soit juste un plantage windows!
Enfin...
Si tu pense que c'est le formatage, recommence le, si il y a toujours des erreurs apres, tu reviendras pour qu'on cherche quelle piece est defectueuse...
Bonne chance, en te souhaitant quand meme que se soit juste un plantage windows!
