disfonctionnement pc HP

[débutants]

bonjour

je sollicite votre aide en raison du disfonctionnement de mon pc : il s'arrête seul et passe en écran bleu très souvent ou se bloque à tel point qu'on doit l'éteindre à la sauvage
j'ai fait des mises à jour windows , plusieurs restaurations ,vérification d'erreurs au démarage ,débranché les périphériques , mais rien n'y fait.

j'ai avast en antivirus avec lequel j'ai lancé un scan minutieux je ne trouve rien ..

est-ce la fin du disc dur ?

merci pour votre aide
bonne journée

[alain 64]

bonsoir
installes Whocrashed 3.06 pour analyser tes écrans bleus .
Whocrashed 3.06
Tu l'installes en faisant un clic droit et "en tant qu'administrateur" puis tu clic sur "Analize" puis tu copie/colle le résultat dans ta prochaine réponse.
A plus

[débutants]

bonjour
merci beaucoup pour le temps que vous prenez à nous aider

voici le rapport


Welcome to WhoCrashed (HOME EDITION) v 3.06
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue 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 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. If 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 also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: PC-DE-MRBOURDET
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 Processor 4000+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 937177088 total
VM: 2147352576, free: 1928523776



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 21/09/2012 04:39:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092112-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x91159)
Bugcheck code: 0xD1 (0xD1BBA00, 0x2, 0x1, 0xFFFFFFFF8689D159)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 21/09/2012 04:39:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x91159)
Bugcheck code: 0xD1 (0xD1BBA00, 0x2, 0x1, 0xFFFFFFFF8689D159)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 21/09/2012 03:21:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092112-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x11998)
Bugcheck code: 0xD1 (0x56C033FC, 0x2, 0x1, 0xFFFFFFFF86819998)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 18/09/2012 05:09:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091812-01.dmp
This was probably caused by the following module: pacer.sys (pacer+0x59A8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8D2949A8, 0xFFFFFFFF8B26CAC4, 0xFFFFFFFF8B26C7C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\pacer.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Planificateur de paquets QoS
Bug check description: This indicates that a system thread 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 17/09/2012 18:29:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091712-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x818DE)
Bugcheck code: 0xD1 (0xFFFFFFFFFAD2C493, 0x2, 0x1, 0xFFFFFFFF8688C8DE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 11/09/2012 06:28:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091112-02.dmp
This was probably caused by the following module: ndis.sys (ndis+0xD8C46)
Bugcheck code: 0x50 (0xFFFFFFFFEC8B55FF, 0x8, 0xFFFFFFFFEC8B55FF, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 11/09/2012 06:17:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091112-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x186DC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF868276DC, 0xFFFFFFFF803ECBE5, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 08/09/2012 15:41:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090812-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0x94CA0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF954A4CA0, 0xFFFFFFFF818A6AE0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 08/09/2012 12:39:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090812-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x94CA0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF96D04CA0, 0xFFFFFFFFAF4FBAE0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 08/09/2012 06:15:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090812-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x11299)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E87299, 0xFFFFFFFF803F44E8, 0xFFFFFFFF803F41E4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
Bug check description: This indicates that a system thread 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 06/09/2012 05:29:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090612-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x106E9)
Bugcheck code: 0x50 (0xFFFFFFFF8EC886A2, 0x0, 0xFFFFFFFF8681F6E9, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 05/09/2012 06:14:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090512-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xD8DF1)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F57DF1, 0xFFFFFFFF803D4990, 0xFFFFFFFF803D468C)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
Bug check description: This indicates that a system thread 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 03/09/2012 16:12:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090312-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x77 (0xFFFFFFFFC000000E, 0xFFFFFFFFC000000E, 0x0, 0x51BE0000)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 02/09/2012 05:22:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090212-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x10E1C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF86816E1C, 0xFFFFFFFF803D4954, 0xFFFFFFFF803D4650)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a system thread 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 01/09/2012 06:11:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090112-03.dmp
This was probably caused by the following module: ndis.sys (ndis+0xB49C)
Bugcheck code: 0xD1 (0xFFFFFFFF8CC0BB90, 0x2, 0x0, 0xFFFFFFFF82E8349C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

52 crash dumps have been found and analyzed. Only 15 are included in this report. 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.



merci encore pour votre aide
bonne journée

[alain 64]

Bonsoir
effectivement tu as de gros soucis de pilotes au vu des résultats de Whocrashed
Dans un premier temps essai de faire une analyse et réparation des fichiers système avec une invite de commande.
Donc:
démarrer==> tous les programmes==> accessoires==>clic droit sur "invite de commande" et "en tant qu'administrateur"
Tu fais un copier/ coller de cette ligne de commande:
CHKDSK C: /f /r
(a condition que C soit la partition ou est installé ton système, sinon tu adaptes)
Tu fais "entrée"
Il te sera demandé de redémarrer
Tu mets O puis entrée
Tu redémarres ton pc et tu laisses faire le scan (plus ou moins long suivant configuration)
Ton pc va redémarrer tout seul
testes le et vois s'il y a toujours des écrans bleus
A plus

[débutants]

bonjour

merci pour votre aide

j'ai mis du temps à repondre car je voulais voir si la manip indiquée a été efficace

au debut ça été mais ça recommence , je ne sais plus trop quoi faire, je pense à demarrer le pc sous reglage usine d'irigine, est-ce possible et comment faire ?
ou bien dois-je chercher des virus ? je n'ai pas trop confiance en avast
merci pour votre aide

bonne journée

[nardino]

Bonjour,
Voir aussi à faire un test de la mémoire.
http://netah25.developpez.com/Tutoriels/TutoMemtest86/
@+

[SYNTAX-ERROR]

Bonjour.


Sans vouloir taper l'incruste,mais pratiquement tout les rapports on a voir avec un problème de carte réseau.
Réinstalle le pilote.
Dis nous aussi quel est le modèle exact de ton PC HP et si Vista 32 ou 64.

Sinon, les PC HP se remettent en config usine soit avec les dvd de récup qu'on doit graver mais que pratiquement personne ne fais jamais.
Ou bien en pressant la touche F11 au démarrage du PC pour entrer dans le gestionnaire de récup dans lequel se trouve parmi diverses options la reconfiguration usine.


@+

[débutants]

bonjour,

merci pour votre aide

mon pc est un HP vista familial premium 32 bits
en fait mon pc ne veut plus démarrer il me met ( je n'ai encore fait aucune manipulation ) la tour démarre mais pas windows , l'écran m'indique = disk boot failure insert system disk and press enter
je n'ai pas le dvd de recup

je vais essayer la touche 11 mais avant j'attends vos conseils

merci d'avance pour votre aide

[SYNTAX-ERROR]

Bonjour.

Il faut presser la touche F8 puis cliquer sur réparer l'ordinateur===>réparer le démarrage pour réparer le secteur de boot de Vista.
Peut être que cette méthode de réparation ne fonctionnera pas, dans ce cas toujours en passant par la touche F8 il faudra ouvrir une invite de commande
pour y taper quelques script.
Maintenant ce message peut aussi vouloir dire que le disque dur est défectueux.
Voir aussi dans le bios si le DD est toujours présent et bien inscrit dans l'ordre de boot.

@+

[débutants]

bonjour

merci pour votre aide

en fait j'ai tout essayé mais il ne veut rien comprendre, il ne veut plus démarrer donc je pense qu'on peut fermer ce post , comme vous dites je crois que c'est le disc dur qui a lâché , il faisait toujours un bruit bizzard au démarrage .

voilà merci encore , vous pouvez noter ce post résolu

bonne journée

[débutants]

bonsoir

en fait j'ai réussi à afficher le bios ( c'est la touche f8 ?)

mais je ne sais pas du tout quelles manip à faire pour

ouvrir une invite de commande
pour y taper quelques script.

et

Voir aussi dans le bios si le DD est toujours présent et bien inscrit dans l'ordre de boot.

donc finalement j'aimerais savoir si il n'y a pas moyen de récupérer le pc ou être sûre que le DD n'est pas mort

merci pour votre aide

[vctr]

hp pavilion dv5 / windows vista premium

Contenu du message modéré

[chantal11]

Bonjour,

@ vctr : si tu veux une aide d'un des membres de ce forum .... déjà, commencer par une formule de politesse !

Il te faut ouvrir ton propre sujet en expliquant la nature de ton problème, dans un langage correct, sans insultes envers qui que ce soit.

Merci de ta compréhension,

@+