Freeze PC problème UC ?
devientfou
Messages postés
31
Statut
Membre
-
jlpjlp Messages postés 52399 Statut Contributeur sécurité -
jlpjlp Messages postés 52399 Statut Contributeur sécurité -
Bonjour,
Mon PC freeze très régulièrement. Si je regarde une vidéo, le son continue d'être en fonction par contre l'image saute. Si je suis sur internet ou sur word, il freeze, il ne note pas ce que j'écris et dès qu'il se débloque, il note tout d'un coup. Les programmes "ne répondent pas" pendant quelques secondes. Les période de freeze peuvent durer plus de 10 minutes.
Le PC m'affiche parfois un écran bleu avec "dumping crash memory" ou un truc dans ce goût là, puis il redémarre automatiquement (ça arrive en gros une fois par jour).
J'ai regardé le gestionnaire de tâche pendant un freeze et il indique que l'UC n'est utilisée qu'entre 0 et 15% de manière très irrégulière (ce qui doit correspondre au passage d'une image à l'autre pendant une vidéo par exemple).
J'ai réalisé un memtest de 1 heure ou deux et il n'y a aucun soucis.
Avez-vous une piste pour savoir quelle pièce je dois changer ?
Merci par avance !
Mon PC freeze très régulièrement. Si je regarde une vidéo, le son continue d'être en fonction par contre l'image saute. Si je suis sur internet ou sur word, il freeze, il ne note pas ce que j'écris et dès qu'il se débloque, il note tout d'un coup. Les programmes "ne répondent pas" pendant quelques secondes. Les période de freeze peuvent durer plus de 10 minutes.
Le PC m'affiche parfois un écran bleu avec "dumping crash memory" ou un truc dans ce goût là, puis il redémarre automatiquement (ça arrive en gros une fois par jour).
J'ai regardé le gestionnaire de tâche pendant un freeze et il indique que l'UC n'est utilisée qu'entre 0 et 15% de manière très irrégulière (ce qui doit correspondre au passage d'une image à l'autre pendant une vidéo par exemple).
J'ai réalisé un memtest de 1 heure ou deux et il n'y a aucun soucis.
Avez-vous une piste pour savoir quelle pièce je dois changer ?
Merci par avance !
A voir également:
- Freeze PC problème UC ?
- Pc freeze - Guide
- Deep freeze - Télécharger - Sécurité
- Reinitialiser pc - Guide
- Pc lent - Guide
- Downloader for pc - Télécharger - Téléchargement & Transfert
37 réponses
Je l'ai depuis hier soir, j'avais un message ds le centre de maintenance windows. Lorsque j'ai cliqué sur le lien il y avait une mise à jour à faire mais j'avais une errer. En tapant le code de l'erreur sur google j'ai trouvé un site qui disait que ce logiciel pouvait réparer l'erreur.
J'ai remarqué aussi qu'avec les jeux il ne freezait jamais (jeux vidéo de moto etc...). Je ne sais pas si cela peut t'être utile ?
A+
J'ai remarqué aussi qu'avec les jeux il ne freezait jamais (jeux vidéo de moto etc...). Je ne sais pas si cela peut t'être utile ?
A+
Non il ne plante pas quand je joue.
Il plante quand je suis sur internet, quand je bosse sur word. Les freezes font buguer windows media player (le son continue mais je peux plus afficher la page ou changer de piste)
C'est à dire la quasi totalité de mes activités finalement.
Il plante quand je suis sur internet, quand je bosse sur word. Les freezes font buguer windows media player (le son continue mais je peux plus afficher la page ou changer de piste)
C'est à dire la quasi totalité de mes activités finalement.
pas facile à distance...
mais au vu des rapports zhpdiag, du formatage éffectué, des mises à jour logiciels ... un souci materiel semble être la cause
regarde l'utilisation de la mémoire vive pendant tes activités pour voir si elle est beaucoup utilisé pendant tes jeux ou pas... pour s'orienter vers la ram eventuellement
maintenant sans tester une autre RAM, un autre processeur... pas facile de trouver l'origine... commence par nettoyer le pc et enlever la poussière
mais au vu des rapports zhpdiag, du formatage éffectué, des mises à jour logiciels ... un souci materiel semble être la cause
regarde l'utilisation de la mémoire vive pendant tes activités pour voir si elle est beaucoup utilisé pendant tes jeux ou pas... pour s'orienter vers la ram eventuellement
maintenant sans tester une autre RAM, un autre processeur... pas facile de trouver l'origine... commence par nettoyer le pc et enlever la poussière
J'imagine effectivement que le diagnostic est difficile à distance !
Quand il y a des freezes, le gestionnaire de tâches m'indique que l'UC est utilisée à 0%, 2%, 5%,... très peu utilisée.
Pourtant tous les tests que j'ai fait avec OCCT ou CPU tester pro n'indiquent rien de particulier. J'ai essayé avec une seule des deux barrettes de RAM et les freezes sont toujours là.
Je doute que ce soit le DD qui est endommagé puisque j'ai fait l'installation de win 7 sur 2 DD différents. A moins que ce soit le K:// qui bug.
Quand il y a des freezes on dirait que le PC est à bloc et il fait des "bruits" comme quand il charge quelque chose.
Quand il y a des freezes, le gestionnaire de tâches m'indique que l'UC est utilisée à 0%, 2%, 5%,... très peu utilisée.
Pourtant tous les tests que j'ai fait avec OCCT ou CPU tester pro n'indiquent rien de particulier. J'ai essayé avec une seule des deux barrettes de RAM et les freezes sont toujours là.
Je doute que ce soit le DD qui est endommagé puisque j'ai fait l'installation de win 7 sur 2 DD différents. A moins que ce soit le K:// qui bug.
Quand il y a des freezes on dirait que le PC est à bloc et il fait des "bruits" comme quand il charge quelque chose.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Who crashed ne prend pas en compte les freezes :
On Mon 17/09/2012 18:06:31 GMT your computer crashed
crash dump file: D:\Windows\Minidump\091712-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8001FE8E30, 0xFFFFFA8001FE8F00, 0x40D3BF0)
Error: BAD_POOL_HEADER
file path: D:\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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 17/09/2012 18:06:31 GMT your computer crashed
crash dump file: D:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x181C0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8001FE8E30, 0xFFFFFA8001FE8F00, 0x40D3BF0)
Error: BAD_POOL_HEADER
file path: D:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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.
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 12/09/2012 10:39:18 GMT your computer crashed
crash dump file: D:\Windows\Minidump\091212-18252-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002ADA136)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\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 Tue 11/09/2012 18:16:56 GMT your computer crashed
crash dump file: D:\Windows\Minidump\091112-42681-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002C609E0, 0x0, 0xFFFFF80002C609E0)
Error: BAD_POOL_HEADER
file path: D:\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.
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 05/09/2012 10:58:40 GMT your computer crashed
crash dump file: D:\Windows\Minidump\090512-44631-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A8B496, 0xFFFFF88003975EE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Tue 04/09/2012 11:42:32 GMT your computer crashed
crash dump file: D:\Windows\Minidump\090412-409299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xC5 (0x8, 0x2, 0x1, 0xFFFFF80002BB990D)
Error: DRIVER_CORRUPTED_EXPOOL
file path: D:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid 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. 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 Tue 04/09/2012 06:26:40 GMT your computer crashed
crash dump file: D:\Windows\Minidump\090412-19968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BB4F8C, 0xFFFFF8800759CFE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Wed 13/06/2012 16:05:02 GMT your computer crashed
crash dump file: D:\Windows\Minidump\061312-21762-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x1090, 0x2, 0x0, 0xFFFFF80002ACC225)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\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 Sun 03/06/2012 09:39:37 GMT your computer crashed
crash dump file: D:\Windows\Minidump\060312-18205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002A87136)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\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 31/05/2012 18:23:48 GMT your computer crashed
crash dump file: D:\Windows\Minidump\053112-20701-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8003C5F840, 0xBF7C00BED88EC0, 0xFFFFFA8003C5F840)
Error: BAD_POOL_HEADER
file path: D:\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.
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/05/2012 19:05:55 GMT your computer crashed
crash dump file: D:\Windows\Minidump\052312-21777-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880032F7018, 0xFFFFF880032F6880, 0xFFFFF80002BB8F8C)
Error: NTFS_FILE_SYSTEM
file path: D:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 15/05/2012 10:18:22 GMT your computer crashed
crash dump file: D:\Windows\Minidump\051512-24086-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002BBAF8C, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: D:\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 06/04/2012 10:24:19 GMT your computer crashed
crash dump file: D:\Windows\Minidump\040612-19921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002ADC636)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\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 Mon 02/04/2012 18:17:47 GMT your computer crashed
crash dump file: D:\Windows\Minidump\040212-20092-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BAFF8C, 0xFFFFF880033BA910, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Sat 03/12/2011 23:18:57 GMT your computer crashed
crash dump file: D:\Windows\Minidump\120411-19078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A97AA6, 0xFFFFF88007074EE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Mon 17/09/2012 18:06:31 GMT your computer crashed
crash dump file: D:\Windows\Minidump\091712-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8001FE8E30, 0xFFFFFA8001FE8F00, 0x40D3BF0)
Error: BAD_POOL_HEADER
file path: D:\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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 17/09/2012 18:06:31 GMT your computer crashed
crash dump file: D:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x181C0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8001FE8E30, 0xFFFFFA8001FE8F00, 0x40D3BF0)
Error: BAD_POOL_HEADER
file path: D:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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.
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 12/09/2012 10:39:18 GMT your computer crashed
crash dump file: D:\Windows\Minidump\091212-18252-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002ADA136)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\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 Tue 11/09/2012 18:16:56 GMT your computer crashed
crash dump file: D:\Windows\Minidump\091112-42681-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002C609E0, 0x0, 0xFFFFF80002C609E0)
Error: BAD_POOL_HEADER
file path: D:\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.
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 05/09/2012 10:58:40 GMT your computer crashed
crash dump file: D:\Windows\Minidump\090512-44631-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A8B496, 0xFFFFF88003975EE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Tue 04/09/2012 11:42:32 GMT your computer crashed
crash dump file: D:\Windows\Minidump\090412-409299-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xC5 (0x8, 0x2, 0x1, 0xFFFFF80002BB990D)
Error: DRIVER_CORRUPTED_EXPOOL
file path: D:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid 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. 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 Tue 04/09/2012 06:26:40 GMT your computer crashed
crash dump file: D:\Windows\Minidump\090412-19968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BB4F8C, 0xFFFFF8800759CFE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Wed 13/06/2012 16:05:02 GMT your computer crashed
crash dump file: D:\Windows\Minidump\061312-21762-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x1090, 0x2, 0x0, 0xFFFFF80002ACC225)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\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 Sun 03/06/2012 09:39:37 GMT your computer crashed
crash dump file: D:\Windows\Minidump\060312-18205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002A87136)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\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 31/05/2012 18:23:48 GMT your computer crashed
crash dump file: D:\Windows\Minidump\053112-20701-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8003C5F840, 0xBF7C00BED88EC0, 0xFFFFFA8003C5F840)
Error: BAD_POOL_HEADER
file path: D:\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.
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/05/2012 19:05:55 GMT your computer crashed
crash dump file: D:\Windows\Minidump\052312-21777-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880032F7018, 0xFFFFF880032F6880, 0xFFFFF80002BB8F8C)
Error: NTFS_FILE_SYSTEM
file path: D:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 15/05/2012 10:18:22 GMT your computer crashed
crash dump file: D:\Windows\Minidump\051512-24086-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002BBAF8C, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: D:\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 06/04/2012 10:24:19 GMT your computer crashed
crash dump file: D:\Windows\Minidump\040612-19921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002ADC636)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\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 Mon 02/04/2012 18:17:47 GMT your computer crashed
crash dump file: D:\Windows\Minidump\040212-20092-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BAFF8C, 0xFFFFF880033BA910, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Sat 03/12/2011 23:18:57 GMT your computer crashed
crash dump file: D:\Windows\Minidump\120411-19078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A97AA6, 0xFFFFF88007074EE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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.
se recoupe un problème de periphérique et de ram : tente de démarrer en virant le maximum de périphérique (dont carte reseau...) , mettre à jour tous les pilotes (mais déjà fait). sinon trouver une ram equivalente sur un autre pc pour tenter de voir si cela règle le problème
IRQL_NOT_LESS_OR_EQUAL
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
Error: SYSTEM_SERVICE_EXCEPTION
https://www.0xc0000005.com/index.fr.html
https://support.microsoft.com/fr-fr/help/980932/stop-error-code-0x0000003b-system-service-exception-on-a-computer-that
BAD_POOL_HEADER
https://www.commentcamarche.net/faq/4674-erreur-bad-pool-caller-header-0x000000c2
https://forums.commentcamarche.net/forum/affich-1505201-ecran-bleu
IRQL_NOT_LESS_OR_EQUAL
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
Error: SYSTEM_SERVICE_EXCEPTION
https://www.0xc0000005.com/index.fr.html
https://support.microsoft.com/fr-fr/help/980932/stop-error-code-0x0000003b-system-service-exception-on-a-computer-that
BAD_POOL_HEADER
https://www.commentcamarche.net/faq/4674-erreur-bad-pool-caller-header-0x000000c2
https://forums.commentcamarche.net/forum/affich-1505201-ecran-bleu
Salut,
J'ai installé le service pack windows 7 et en 15 minutes d'internet, pas un seul lag. Je reprends espoir.
J'ai installé le service pack windows 7 et en 15 minutes d'internet, pas un seul lag. Je reprends espoir.
Je fais tourner un memtest ce matin. Là je suis au bolot. Il faut que je le laisse tourner combien de temps ?
J'ai l'impression que ça vient du fichier minidump en fait le problème.
Lorsque je retire ce dossier (je le déplace et renomme sur le bureau), j'ai les freezes puissance 10. Dans une fiche explicative que tu m'as envoyé, il était marqué que ce dossier devait se refaire automatiquement et ce n'est pas le cas chez moi ! De plus, ce dosier ne contient qu'une vingtaine de fichier dmp mais pas de fichier wr31 (ou un truc comme ça) comme il est indiqué dans l'explication.
Des suggestions ?
J'ai l'impression que ça vient du fichier minidump en fait le problème.
Lorsque je retire ce dossier (je le déplace et renomme sur le bureau), j'ai les freezes puissance 10. Dans une fiche explicative que tu m'as envoyé, il était marqué que ce dossier devait se refaire automatiquement et ce n'est pas le cas chez moi ! De plus, ce dosier ne contient qu'une vingtaine de fichier dmp mais pas de fichier wr31 (ou un truc comme ça) comme il est indiqué dans l'explication.
Des suggestions ?
nouveau whocrashed avec écran bleu
On Fri 28/09/2012 09:28:46 GMT your computer crashed
crash dump file: D:\Windows\Minidump\092812-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E119BC, 0xFFFFF88008933590, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Fri 28/09/2012 09:28:46 GMT your computer crashed
crash dump file: D:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x3149)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E119BC, 0xFFFFF88008933590, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software SYSTEM_SERVICE_EXCEPTION
On Fri 28/09/2012 09:28:46 GMT your computer crashed
crash dump file: D:\Windows\Minidump\092812-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E119BC, 0xFFFFF88008933590, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\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 Fri 28/09/2012 09:28:46 GMT your computer crashed
crash dump file: D:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x3149)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E119BC, 0xFFFFF88008933590, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software SYSTEM_SERVICE_EXCEPTION
slt toujours la même chose je ne peux rien de plus , un souci materiel surement
dans ce cas avast est signalé : tente de le désinstaller pour voir si cela persiste au cas où
dans ce cas avast est signalé : tente de le désinstaller pour voir si cela persiste au cas où
OK, merci pour ta patience et toute l'aide que tu m'as apporté. Je vais essayer de choper un autre PC, c'est trop insupportable de bosser là dessus.
A bientôt
A bientôt
de rien mais dans ton cas pas de solution sans tester des pièces autres (RAM, CPU, Alimentation...)
bonne suite
bonne suite
il plante quand tu fais quoi?