PC qui redémarre tout le temps

[modetoel1]

Bonjour,

 

J'ai un PC portable ASUS, qui depuis hier redémarre sans arrêt...

 

J'arrive juste au niveau du mot de passe, et dès que je le renseigne, il redémarre...

 

Merci pour votre aide.

 

Delphine

[Tonton]

Bonsoir modetoel1,

Fais ceci, stp :

• éteinds le PC
• déconnecte tous les périphériques externes : stockage USB, écrans externes, imprimantes, etc.
• débranche l'adaptateur secteur du PC
• retire la batterie du compartiment du PC
• appuie sur le bouton d'alimentation (On/Off) pendant 1 minute, afin de décharger complètement les condensateurs qui protègent la mémoire
• insére à nouveau la batterie et rebranche l'adaptateur secteur au PC, sans connecter les périphériques
• appuie sur le bouton d'alimentation (On/Off) pour mettre le PC sous tension
• si un menu de démarrage s'ouvre, utilise les touches de direction pour sélectionner Démarrer Windows normalement, puis valide par la touche Entrée
• reconnecte tous les périphériques externes
• si nécessaire, effectue une mise à jour des drivers pour les périphériques
• vérifie s'il y a une amélioration

@+,
Tonton

[modetoel1]

Bonsoir,

 

Non ça n'a rien changé

Après avoir tapé mon mot de passe, j ai un écran bleu et j ai pu lire : Bad pool header. Ensuite le pc redémarre....

[Tonton]

Re, modetoel1,

Fais ceci, stp :

• Clique Droit sur Ordinateur > Propriétés > Paramètres système avancés > Démarrage et Récupération > Paramètres
• Vérifie que « Image mémoire du noyau » soit sélectionnée, sinon il n'y aura pas de minidump
• « Redémarrer automatiquement » doit être décoché, ce qui te permettra de lire les informations relatives au BSOD
• Utilise l'outil WhoCrashed de Resplendence => lien + tuto WhoCrashed

Poste le rapport WhoCrashed dans ta prochaine réponse

 

@+,
Tonton

[modetoel1]

Désolée pour la question, mais comment je fais pour accéder à l icône ordinateur, je dois passer par un mode sans échec ??

[Tonton]

Cette icône se situe sur le Bureau => tente d'y accéder avant que le PC ne redémarre.

Si pas OK, essaie en mode sans échec.

[modetoel1]

Bonjour,

 

Ce matin au 1er démarrage, après avoir saisi mon mot de passe, j'ai eu un écran rempli de lignes. La 2ème fois, j'ai pu accéder au bureau, voici le résultat :

 

Computer name: PC-DE-LESTRITON
Windows version: Windows Vista Service Pack 2, 6.0, build: 6002
Windows dir: C:\Windows
Hardware: F50SL , ASUSTeK Computer Inc. , PEGATRON CORPORATION , F50SL
CPU: GenuineIntel Pentium® Dual-Core CPU T4200 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3219476480 bytes total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 11/10/2015 17:29:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101215-01.dmp
This was probably caused by the following module: asdsm.sys (AsDsm+0x5A1C)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFB14E9A50, 0xFFFFFFFFB14E9E58, 0xA810435)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\asdsm.sys
product: Windows ® Codename Longhorn DDK driver
company: Windows ® Codename Longhorn DDK provider
description: Data Security Manager 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.
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: asdsm.sys (Data Security Manager Driver, Windows ® Codename Longhorn DDK provider).
Google query: Windows ® Codename Longhorn DDK provider BAD_POOL_HEADER



On Sun 11/10/2015 17:29:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: asdsm.sys (AsDsm+0x5A1C)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFB14E9A50, 0xFFFFFFFFB14E9E58, 0xA810435)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\asdsm.sys
product: Windows ® Codename Longhorn DDK driver
company: Windows ® Codename Longhorn DDK provider
description: Data Security Manager 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.
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: asdsm.sys (Data Security Manager Driver, Windows ® Codename Longhorn DDK provider).
Google query: Windows ® Codename Longhorn DDK provider BAD_POOL_HEADER



On Fri 09/10/2015 08:00:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100915-07.dmp
This was probably caused by the following module: avgmfx86.sys (avgmfx86+0x4047)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF83306E7B, 0xFFFFFFFFAF91A71C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avgmfx86.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Resident Shield Minifilter Driver
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.
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: avgmfx86.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Fri 09/10/2015 07:55:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100915-06.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xEDE7B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF832FFE7B, 0xFFFFFFFFA4619AC4, 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 Fri 09/10/2015 07:51:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100915-05.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x1BF681)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF833F7681, 0xFFFFFFFFAC7887A4, 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 Fri 09/10/2015 07:40:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100915-04.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x46305)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF83290305, 0xFFFFFFFFAB6A8930, 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 Fri 09/10/2015 07:37:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100915-03.dmp
This was probably caused by the following module: lullaby.sys (lullaby+0x10E1)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8332882A, 0xFFFFFFFFA2EB066C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\lullaby.sys
product: Windows ® Codename Longhorn DDK driver
company: Windows ® Codename Longhorn DDK provider
description: ASUS CopyProtect driver
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.
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: lullaby.sys (ASUS CopyProtect driver, Windows ® Codename Longhorn DDK provider).
Google query: Windows ® Codename Longhorn DDK provider KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Fri 09/10/2015 07:32:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100915-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDA5B)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x5C007C, 0xFFFFFFFFAB96F418)
Error: BAD_POOL_CALLER
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 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.



On Fri 09/10/2015 07:29:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100915-01.dmp
This was probably caused by the following module: asdsm.sys (AsDsm+0x5FE6)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFB7C31128, 0xFFFFFFFFB7C31530, 0xA810616)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\asdsm.sys
product: Windows ® Codename Longhorn DDK driver
company: Windows ® Codename Longhorn DDK provider
description: Data Security Manager 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.
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: asdsm.sys (Data Security Manager Driver, Windows ® Codename Longhorn DDK provider).
Google query: Windows ® Codename Longhorn DDK provider BAD_POOL_HEADER



On Sun 19/07/2015 16:17:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071915-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCD96F)
Bugcheck code: 0xC0000218 (0xFFFFFFFF94F4C810, 0x0, 0x0, 0x0)
Error: STATUS_CANNOT_LOAD_REGISTRY_FILE
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 registry file could not be loaded.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion

12 crash dumps have been found and analyzed. Only 10 are included in this report. 4 third party drivers have 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:

hidusb.sys (USB Miniport Driver for Input Devices, Microsoft Corporation)
asdsm.sys (Data Security Manager Driver, Windows ® Codename Longhorn DDK provider)
lullaby.sys (ASUS CopyProtect driver, Windows ® Codename Longhorn DDK provider)
avgmfx86.sys (AVG Resident Shield Minifilter Driver, AVG Technologies CZ, s.r.o.)

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.

[modetoel1]

Bonjour,

 

J ai de nouveau le même soucis, mais j ai pu faire une image écran du message d erreur, mais je ne sais pas comment la poster....

[Invité Notpa]

Bonjour modetoel1,

 

Pour mettre une image dans Zébulon, faire comme suit :

Pour une copie d'écran :
- appuyer sur la touche Alt+Imprécr
- ouvrir un éditeur d'images (Photofiltre par exemple)
- dans une nouvelle image, faire un coller (Ctrl+V) et valider la copie (clic droit) ou alors, dans la zone grise de Photofiltre une fois lancé, faire un clic droit et choisir : "Coller en tant qu’image"
- retailler l'image si nécessaire (supprimer les zones inutiles)
- sauvegarder l'image

Pour transférer l'image :
- accéder à un hébergeur d'images (Hostingpics,Zupimages, ImageShack, Imagik, etc.)
- transférer l'image sauvegardée sur le site choisi
- dans la fenêtre qui apparait, cliquer sur l'image
- une nouvelle fenêtre apparait avec l'image sur fond noir.
- copier l'URL de l'image stockée de la fenêtre ci-dessus
- dans la réponse de Zébulon, sélectionner l'icône 'Insérer une image'

- coller l'URL
- valider

Cordialement

 

Notpa

[pear]

Bonjour,

 

Bonjour
Les erreurs que vous indiquez peuvent être dues à une ram défectueuse.
vérifiez l'état de vos barrettes RAM avecMemtest:

Tuto ici

Téléchargement Memtest86+ 4.10:
Iso bootable 4.10
Il faut en graver l'image.
Key usb 4.10

Si vous avez plusieurs barrettes, il faut les tester ensemble et séparément.

Si une barrette est défectueuse, il faudra la changer.

Sinon,
C'est souvent la carte graphique