Cooler94 Publié le 31 décembre 2012 Signalement Share Publié le 31 décembre 2012 Salut, j'espère que vous allez pouvoir m'aider assez rapidement car sa fait pas mal de temps que j'ai des soucis de crashs avec mon PC portable (MSI GT780) Apparement mes soucis de crashs proviendrais de pilotes (drivers ?) installés sur ce site ! (carte graphique, carte mère...) Voici tout mes derniers crashs analysés On Sun 30/12/2012 16:37:40 GMT your computer crashed crash dump file: C:\windows\Minidump\123012-14383-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0x4377, 0x2F004378FFFFFFFE) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. 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 Sun 30/12/2012 16:37:40 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: 0x1A (0x5002, 0xFFFFF70001080000, 0x4377, 0x2F004378FFFFFFFE) Error: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. 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 Sun 30/12/2012 20:22:49 GMT your computer crashed crash dump file: C:\windows\Minidump\123012-16988-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x21D5) Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0) 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 that cannot be identified at this time. On Sun 30/12/2012 20:22:49 GMT your computer crashed crash dump file: C:\windows\memory.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x21D5) Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0) 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 that cannot be identified at this time. On Sun 30/12/2012 22:38:15 GMT your computer crashed crash dump file: C:\windows\Minidump\123012-16161-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x19 (0x3, 0xFFFFF8A0033F1B40, 0xFFFFF8A0033F1B40, 0xCDFFF8A0033F1B40) 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 that cannot be identified at this time. On Sun 30/12/2012 22:38:15 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: 0x19 (0x3, 0xFFFFF8A0033F1B40, 0xFFFFF8A0033F1B40, 0xCDFFF8A0033F1B40) Error: BAD_POOL_HEADER 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 that cannot be identified at this time. On Sun 30/12/2012 23:24:02 GMT your computer crashed crash dump file: C:\windows\Minidump\123112-13041-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x1A (0x41790, 0xFFFFFA800444B430, 0xFFFF, 0x0) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. 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 Sun 30/12/2012 23:24:02 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: 0x1A (0x41790, 0xFFFFFA800444B430, 0xFFFF, 0x0) Error: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. 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. Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Cooler94 Publié le 31 décembre 2012 Auteur Signalement Share Publié le 31 décembre 2012 Des idées svp ? Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Mixbown Publié le 1 janvier 2013 Signalement Share Publié le 1 janvier 2013 Je ne suis pas très douée en informatique, donc je vais au plus simple: as-tu déjà formaté ton PC ?Ayant pas mal de pb ac des BSOD, c'est svt ce qu'on m'a conseillé de faire.Si tu le fais, n'oublies pas que tous tes fichiers seront perdus dc pense à faire une copie sur un DD externe!Un peu extrême comme réponse, mais au moins ac ça tes pb devraient disparaître Citer Lien vers le commentaire Partager sur d'autres sites More sharing options...
Publications recommandées
Joignez-vous à la conversation
Vous pouvez publier maintenant et vous inscrire plus tard. Si vous avez un compte, connectez-vous maintenant pour publier avec votre compte.