(URGENT) Crash, écrans bleus.
frozie
Messages postés
7
Statut
Membre
-
frozie Messages postés 7 Statut Membre -
frozie Messages postés 7 Statut Membre -
Bonjour,
Depuis que j'ai mon nouveau PC (1 mois), j'ai sans cesse des écrans bleus, que je sois en train de play, de coder, d'être sur Facebook, de regarder un film ou même de ne rien faire.
J'ai déjà contacté plusieurs fois le SAV mais ils ont du mal à résoudre mon problème. De plus, si je dois le renvoyer, c'est à 500km de chez moi, donc déjà le temps d'attente, les frais de port, etc.
Bref, j'ai fais une analyse avec WhoCrashed, et voilà ce que ça donne:
Vous remarquerez que c'est à chaque fois un problème dû au ntoskrnl.exe, donc je suppose au Kernel (la déduction). Mais je ne vois pas du tout ce que cela signifie.
Je peux avoir plein de motifs de crash différents.
IRQL_NOT_LESS_OR_EQUAL
INACCESSIBLE_BOOT_DEVICE
PAGE_FAULT_IN_NONPAGED_AREA
BAD_POOL_HEADER
etc.
Je remercie d'avance de m'avoir lu et vous remercie si vous pouvez m'aider, car je commence à saturer de ces 5-10 crash par jour.
Axel Rayet.
Depuis que j'ai mon nouveau PC (1 mois), j'ai sans cesse des écrans bleus, que je sois en train de play, de coder, d'être sur Facebook, de regarder un film ou même de ne rien faire.
J'ai déjà contacté plusieurs fois le SAV mais ils ont du mal à résoudre mon problème. De plus, si je dois le renvoyer, c'est à 500km de chez moi, donc déjà le temps d'attente, les frais de port, etc.
Bref, j'ai fais une analyse avec WhoCrashed, et voilà ce que ça donne:
On Sun 22/07/2012 22:11:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\072312-36363-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x19 (0x3, 0xFFFFF800032264F0, 0xFFFFFA8026BA0D40, 0xFFFFF800032264F0) 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. 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 22/07/2012 03:08:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\072212-31699-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800033E38C2, 0xFFFFF88007272F90, 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 which cannot be identified at this time. On Fri 20/07/2012 20:54:17 GMT your computer crashed crash dump file: C:\Windows\Minidump\072012-28672-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0x7FFFFFE5, 0x2, 0x1, 0xFFFFF800030E3266) 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 which cannot be identified at this time. On Thu 19/07/2012 20:58:25 GMT your computer crashed crash dump file: C:\Windows\Minidump\071912-28579-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800E82AAF8, 0xFFFFF8800E82A350, 0xFFFFF880042B6D20) Error: NTFS_FILE_SYSTEM file path: C:\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 17/07/2012 14:20:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\071712-30108-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800033E1FC1, 0xFFFFF8800DC0AC10, 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 which cannot be identified at this time. On Mon 16/07/2012 21:08:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\071612-41168-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x50 (0xFFFFE9FF3D9D1470, 0x1, 0xFFFFF800033E70CF, 0x7) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 16/07/2012 15:36:58 GMT your computer crashed crash dump file: C:\Windows\Minidump\071612-30217-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x50 (0xFFFFF800063E5D10, 0x8, 0xFFFFF800063E5D10, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 15/07/2012 22:41:07 GMT your computer crashed crash dump file: C:\Windows\Minidump\071612-30888-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF800033A41CA, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 Sun 15/07/2012 20:54:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\071512-31044-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x50 (0xFFFFFFFFFD60178D, 0x0, 0xFFFFF800033251C2, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 14/07/2012 16:48:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\071412-36597-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033A31D3, 0xFFFFF8800ACFFD10, 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 which cannot be identified at this time. ------- 10 crash dumps have been found and analyzed. 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.
Vous remarquerez que c'est à chaque fois un problème dû au ntoskrnl.exe, donc je suppose au Kernel (la déduction). Mais je ne vois pas du tout ce que cela signifie.
Je peux avoir plein de motifs de crash différents.
IRQL_NOT_LESS_OR_EQUAL
INACCESSIBLE_BOOT_DEVICE
PAGE_FAULT_IN_NONPAGED_AREA
BAD_POOL_HEADER
etc.
Je remercie d'avance de m'avoir lu et vous remercie si vous pouvez m'aider, car je commence à saturer de ces 5-10 crash par jour.
Axel Rayet.
A voir également:
- (URGENT) Crash, écrans bleus.
- 2 écrans - Guide
- Yeux bleus - Guide
- Windows crash - Guide
- Nvlddmkm crash ✓ - Forum Windows
- Crash helper.exe - Forum Mozilla Firefox
4 réponses
Bonjour
Le processus ntoskrnl.exe (ntoskrnl signifiant Windows Boot-Up Kernel) est un processus critique de Windows servant au démarrage (boot-up) de Microsoft Windows.
Est- ce que tu a le DVD de ton Windows.
Si oui ! essaie le réparation du système.
Qui aime l'instruction ! trouve la connaissance qui vient de la réflexion !
PS. Créez souvent un point de restauration ! cela résous pas mal de problèmes.
Le processus ntoskrnl.exe (ntoskrnl signifiant Windows Boot-Up Kernel) est un processus critique de Windows servant au démarrage (boot-up) de Microsoft Windows.
Est- ce que tu a le DVD de ton Windows.
Si oui ! essaie le réparation du système.
Qui aime l'instruction ! trouve la connaissance qui vient de la réflexion !
PS. Créez souvent un point de restauration ! cela résous pas mal de problèmes.
J'ai déjà reformaté tout le système et les disques durs plusieurs fois. Dans ce cas-là, vaut-il la peine d'essayer une réparation du système? (oui j'ai le DVD)
Je ne pense pas que si tu a formaté et réinstallé le système que cela serve a quelque chose de réparer.
Mais cela ne coûte rien d'essayer. mettre ton DVD dans le lecteur et redémarrer et au départ tu as a gauche de ton écran la fonction >Réparer.
Windows réparer le démarrage si cela est possible.
Vois le résultat.
Windows n'a pas pu démarrer car le fichier suivant est manquant ou endommagé:
Winnt_root \ System32 \ Ntoskrnl.exe
Il se peut que ton DVD soit aussi endommagé et que ce fichier est manquant ou corrompu.
Essaie aussi dans l'invite de commande la console chkdsk /r
Qui aime l'instruction ! trouve la connaissance qui vient de la réflexion !
PS. Créez souvent un point de restauration ! cela résous pas mal de problèmes.
Mais cela ne coûte rien d'essayer. mettre ton DVD dans le lecteur et redémarrer et au départ tu as a gauche de ton écran la fonction >Réparer.
Windows réparer le démarrage si cela est possible.
Vois le résultat.
Windows n'a pas pu démarrer car le fichier suivant est manquant ou endommagé:
Winnt_root \ System32 \ Ntoskrnl.exe
Il se peut que ton DVD soit aussi endommagé et que ce fichier est manquant ou corrompu.
Essaie aussi dans l'invite de commande la console chkdsk /r
Qui aime l'instruction ! trouve la connaissance qui vient de la réflexion !
PS. Créez souvent un point de restauration ! cela résous pas mal de problèmes.