Hp divilion dv7 crash, écrans bleus à répétition

Fermé
mugi347 Messages postés 3 Date d'inscription mercredi 9 juillet 2014 Statut Membre Dernière intervention 11 juillet 2014 - Modifié par mugi347 le 9/07/2014 à 17:14
mugi347 Messages postés 3 Date d'inscription mercredi 9 juillet 2014 Statut Membre Dernière intervention 11 juillet 2014 - 11 juil. 2014 à 17:06
Salut,

J'ai un problème avec mon ordinateur que je n'arrive pas à résoudre tout seul (bon faut dire que mes connaissances informatiques sont très limitées :s). Mon ordinateur a crash (écran bleu) plusieurs fois. Donc une aide serait la bienvenue.

Je vais essayer de vous exposer mon problème le plus précisément possible pour augmenter l'efficacité de l'aide :).

Je vais commencer avec la config de l'ordinateur ;
Modèle : HP Pavilion dv7-4171sf
Système exploitation : Windows 7 Edition Familiale Premium 64 bits (6.1 version 7601)
Processeur : Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz, 4 coeurs, 8 processeurs logiques
Version du BIOS/Date : Hewlett-Packard F.29, 07/11/2011
Version DirectX 11
Carte graphique : ATI Mobility Radeon HD 5650

Maintenant le problème :
Sur une période de 1 mois environ, mon ordinateur a crash un nombre incalculable de fois.
Ça arrive en général quand je surf sur internet ou que je joue à un jeu vidéo (mais ce n'est pas systématique). En général pas de crash pendant plusieurs jours puis plusieurs crash d'affilés en quelques heures...

Je poste le rapport des crashs dans un autre message pour pas poster un trop gros pavé (on peut remarquer que les causes ne sont pas toujours les mêmes). L'analyse a été faite avec Whocrashed.

J'ai acheté l'ordinateur il y a 2 ans et demi et j'ai toujours eu des problèmes de chauffe. Depuis le début il atteint des températures assez extrêmes (plus de 80° en jeu...), mais je n'ai jamais eu de soucis jusqu'à il y a un mois.
Je ne sais pas si le souci vient de là car mon ordi peut crash alors que l'ordinateur est froid (surf sur internet...).

Il y a également un autre problème qui a commencé il y a 2 mois (donc un mois avant le début des crashs). J'ai eu un message du système qui me disait qu'il y a un problème avec le disque dur et maintenant à chaque démarrage, on me propose de faire une analyse du disque dur. Je ne me rappelle plus trop du résultat du test... mais on me disait qu'il y avait un problème 301 (un truc de genre)

J'ai essayé de faire une restauration système à une date antérieur, mais impossible, voilà ce qu'on me dit :
La restauration du système ne semble pas fonctionner correctement sur ce système.
Un composant du service VSS a rencontré une erreur inattendue. Consultez le journal d'événements d'applications pour plus d'informations. (0x80042302)



Voilà je pense avoir été assez clair, de l'aide serait vraiment cool parce que je commence à désespérer.

A l'attente d'une réponse :).
A voir également:

2 réponses

mugi347 Messages postés 3 Date d'inscription mercredi 9 juillet 2014 Statut Membre Dernière intervention 11 juillet 2014
9 juil. 2014 à 17:16
Voilà maintenant le rapport de Whocrashed :

On Wed 09/07/2014 12:58:43 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: 0xC7 (0x4, 0xFFFFF8000317F430, 0x0, 0x10000)
Error: TIMER_OR_DPC_INVALID
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
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 that cannot be identified at this time.


On Fri 04/07/2014 19:13:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-17628-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x7E34, 0x7E37, 0x7E36)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 that cannot be identified at this time.


On Sun 29/06/2014 16:57:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062914-22136-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030C98EA, 0xFFFFF8800A13F7F0, 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 that cannot be identified at this time.


On Fri 27/06/2014 13:48:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062714-21512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF80083307C78, 0x2, 0x0, 0xFFFFF800030D5395)
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 that cannot be identified at this time.


On Tue 24/06/2014 20:57:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062414-19266-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880031DBC70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 that cannot be identified at this time.


On Tue 24/06/2014 10:47:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062414-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030C0622, 0xFFFFF8800E6A9770, 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 that cannot be identified at this time.

On Tue 24/06/2014 10:36:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062414-15849-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x66F05)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88007EFDF05, 0xFFFFF8800D9B8B80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sun 15/06/2014 10:40:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061514-17986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x800, 0x2, 0x1, 0xFFFFF80003105622)
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 that cannot be identified at this time.

On Sun 15/06/2014 10:36:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061514-17347-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x801, 0x2, 0x0, 0xFFFFF80003089D5B)
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 that cannot be identified at this time.

On Sun 15/06/2014 10:11:26 GMT your computer crashed

crash dump file: C:\Windows\Minidump\061514-16364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030CAF8D, 0xFFFFF88009045FD0, 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 that cannot be identified at this time.

37 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found.
0
mugi347 Messages postés 3 Date d'inscription mercredi 9 juillet 2014 Statut Membre Dernière intervention 11 juillet 2014
11 juil. 2014 à 17:06
Une petite réponse serait la bienvenue SVP :'(
0