Bluescreen
regine83000
Messages postés
60
Statut
Membre
-
Malekal_morte- Messages postés 184348 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Malekal_morte- Messages postés 184348 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Bonjour,
j''ai une erreur qui s'affiche et éteint l'ordinateur, je suis sous windows 7. Comment faire pour la corriger?
Merci de votre réponse
voici l'erreur :
Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.256.48
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: 19
BCP1: 0000000000000020
BCP2: FFFFFA800B213C50
BCP3: FFFFFA800B214AE0
BCP4: 0000000005E91410
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\083016-13041-01.dmp
C:\Users\montana\AppData\Local\Temp\WER-54101-0.sysdata.xml
j''ai une erreur qui s'affiche et éteint l'ordinateur, je suis sous windows 7. Comment faire pour la corriger?
Merci de votre réponse
voici l'erreur :
Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.256.48
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: 19
BCP1: 0000000000000020
BCP2: FFFFFA800B213C50
BCP3: FFFFFA800B214AE0
BCP4: 0000000005E91410
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\083016-13041-01.dmp
C:\Users\montana\AppData\Local\Temp\WER-54101-0.sysdata.xml
4 réponses
Salut,
Il faut fournir un rapport whocrashed.
Clic sur le mot whocrashed et suis les instructions et donne le contenu ici en réponse.
Il faut fournir un rapport whocrashed.
Clic sur le mot whocrashed et suis les instructions et donne le contenu ici en réponse.
merci mais comme je pige pas l'anglais alors je met tout!
Welcome to WhoCrashed (HOME EDITION) v 5.52
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: MONTANA-THINK
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: 29295R4, LENOVO, MAHOBAY
CPU: GenuineIntel Intel(R) Pentium(R) CPU G2130 @ 3.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4080898048 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 30/08/2016 08:02:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083016-13041-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800B213C50, 0xFFFFFA800B214AE0, 0x5E91410)
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. This problem might also be caused because of overheating (thermal issue).
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 30/08/2016 08:02:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wna1000m.sys (WNA1000M+0x1C716)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800B213C50, 0xFFFFFA800B214AE0, 0x5E91410)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\wna1000m.sys
product: Realtek RTL8192C Wireless USB 2.0 Adapter
company: Realtek Semiconductor Corporation
description: Realtek RTL8192C USB NDIS Driver
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. This problem might also be caused because of overheating (thermal issue).
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: wna1000m.sys (Realtek RTL8192C USB NDIS Driver, Realtek Semiconductor Corporation ).
Google query: Realtek Semiconductor Corporation BAD_POOL_HEADER
On Tue 30/08/2016 07:32:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083016-22230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40D0001, 0xFFFFFA800B32BDB0)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
wna1000m.sys (Realtek RTL8192C USB NDIS Driver, Realtek Semiconductor Corporation )
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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.
Welcome to WhoCrashed (HOME EDITION) v 5.52
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: MONTANA-THINK
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: 29295R4, LENOVO, MAHOBAY
CPU: GenuineIntel Intel(R) Pentium(R) CPU G2130 @ 3.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4080898048 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 30/08/2016 08:02:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083016-13041-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800B213C50, 0xFFFFFA800B214AE0, 0x5E91410)
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. This problem might also be caused because of overheating (thermal issue).
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 30/08/2016 08:02:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wna1000m.sys (WNA1000M+0x1C716)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800B213C50, 0xFFFFFA800B214AE0, 0x5E91410)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\wna1000m.sys
product: Realtek RTL8192C Wireless USB 2.0 Adapter
company: Realtek Semiconductor Corporation
description: Realtek RTL8192C USB NDIS Driver
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. This problem might also be caused because of overheating (thermal issue).
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: wna1000m.sys (Realtek RTL8192C USB NDIS Driver, Realtek Semiconductor Corporation ).
Google query: Realtek Semiconductor Corporation BAD_POOL_HEADER
On Tue 30/08/2016 07:32:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083016-22230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40D0001, 0xFFFFFA800B32BDB0)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
wna1000m.sys (Realtek RTL8192C USB NDIS Driver, Realtek Semiconductor Corporation )
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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.
Tu as deux plantages avec potentiellement deux sources différentes.
Le second, c'est un plantage du pilote RealTek qui semble être lié à un dongle USB Wifi ?
C'était peut-être juste un plantage anodin.
~~
Le premier, c'est plus un problème matériel, soit température trop haute, soit une barrette de mémoire défectueux.
Je t'invite à suivre ce topic et vérifier : Diagnostiquer problème matériel
- les température de l'ordinateur
- les barettes de mémoire avec memtest
Veuillez appuyer sur une touche pour continuer la désinfection...
Le second, c'est un plantage du pilote RealTek qui semble être lié à un dongle USB Wifi ?
C'était peut-être juste un plantage anodin.
~~
Le premier, c'est plus un problème matériel, soit température trop haute, soit une barrette de mémoire défectueux.
Je t'invite à suivre ce topic et vérifier : Diagnostiquer problème matériel
- les température de l'ordinateur
- les barettes de mémoire avec memtest
Veuillez appuyer sur une touche pour continuer la désinfection...
