tequila13

Bonjour tonton, Je m'excuse de ce retard(euh 10 jours) J'ai eu pas mal de problèmes avec mon pc, et l'ai mené à réparer. C'était bien les barrettes qui étaient Hors service. J'avais bien essayé de faire ==>le test RAM avec Memtest86+, ==>sfc /scannow mais à chaque fois j'avais des écrans bleus. Tous mes remerciements pour avoir quand même pris le temps de me répondre. Je classe donc l'affaire en résolu Encore merci

Bonjour Tonton, et merci de me répondre Toutes mes excuses, mais je ne pensais plus avoir de réponse à mon topic. J'ai donc zappé ma messagerie sur laquelle devait arriver l'alerte de suivi de mon problème. Bon alors, le CD d'installation de Windows Vista ,je ne l'ai pas puisque PC de Marque. Je vais donc démarrer un sfc /scannow directement en suivant la procédure. Et je vous tiens au courant. Quant au gestionnaire de périphériques: non aucune alerte ni ? ni ! Bon dimanche @+

Bonjour, Nouvelle venue, je ne sais pas trop le fonctionnement de votre forum. Je vous demande donc beaucoup d'indulgence. J'ai un PC portable Acer Extensa 5220 depuis 2008 sous Vista Basique SP2. Depuis 2010, il fait des bluescreen à répétitions: j'ai essayé avec beaucoup d'aide, il faut le dire, de remédier à ce souci. Mais rien n'y a fait. Depuis, pas mal d'eau a passé sous les ponts, mon pc est toujours là mais mes bluescreens aussi. Je me demande même comment il ne m'a pas encore lâché. J'ai fait dernièrement un CHKDSK qui m'a trouvé des fichiers manquants, des violations d'intégrité...etc J'ai essayé de réparer mais si quelques fichiers l'ont été, d'autres sont réapparus avec "cannot" donc non réparables. En désespoir de cause, j'ai décidé de réinstaller Vista, j'ai mis 2 jours à tout réinstaller(surtout les mises à jour) Mais malgré tout, depuis le 19.O2 date de réinstallation, il y a encore des bluescreens. Ce qui me fait dire que c'est mon matèriel qui va très très mal. J'ai fait un petit WhoCrashed pour voir un peu ce que ça donnait: System Information (local) -------------------------------------------------------------------------------- computer name: PC-DE-MAMAN windows version: Windows Vista Service Pack 2, 6.0, build: 6002 windows dir: C:\Windows CPU: GenuineIntel Intel® Celeron® CPU 540 @ 1.86GHz Intel586, level: 6 1 logical processors, active mask: 1 RAM: 2673537024 total VM: 2147352576, free: 2029228032 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 21/02/2012 10:01:09 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini022112-03.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDB3F) Bugcheck code: 0x4E (0x99, 0x90000, 0x2, 0x6FB3F) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. 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 21/02/2012 10:01:09 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E) Bugcheck code: 0x4E (0x99, 0x90000, 0x2, 0x6FB3F) Error: PFN_LIST_CORRUPT Bug check description: This indicates that the page frame number (PFN) list is corrupted. 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. 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: ntkrpamp.exe . Google query: ntkrpamp.exe PFN_LIST_CORRUPT On Tue 21/02/2012 07:43:07 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini022112-02.dmp This was probably caused by the following module: win32k.sys (win32k+0xA6BB7) Bugcheck code: 0xC2 (0x7, 0x110B, 0x18C00, 0xFFFFFFFFFF64615F) Error: BAD_POOL_CALLER 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 the current thread is making a bad pool request. 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 21/02/2012 05:50:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini022112-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x53023) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF81E89023, 0xFFFFFFFF89D33470, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\ntkrnlpa.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 Mon 20/02/2012 06:16:10 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini022012-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x7DE52) Bugcheck code: 0xA (0x4, 0x2, 0x0, 0xFFFFFFFF81EAC9A9) Error: IRQL_NOT_LESS_OR_EQUAL 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 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 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 Sun 19/02/2012 16:46:33 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini021912-02.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x7DE66) Bugcheck code: 0x4E (0x2, 0x6B731, 0x9F6CF, 0x2288) Error: PFN_LIST_CORRUPT 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 that the page frame number (PFN) list is corrupted. 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 Sun 19/02/2012 03:28:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini021912-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x8FDC4) Bugcheck code: 0xA (0xFFFFFFFFCFC01864, 0x2, 0x1, 0xFFFFFFFF82091728) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 7 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: ntkrpamp.exe If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. 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. Une âme charitable pourrait m'aider à y voir plus clair dans ce rapport ? merci et bonne fin d'après-midi. Je ne sais si c'est utile mais: Système d'exploitation Microsoft® Windows Vista™ Édition Familiale Basique Version 6.0.6002 Service Pack 2 Build 6002 Informations supplémentaires Non disponible Éditeur Microsoft Corporation Ordinateur PC-DE-MAMAN Fabricant Acer Modèle Extensa 5220 Type PC à base X86 Processeur Intel® Celeron® CPU 540 @ 1.86GHz, 1862 MHz, 1 cœur(s), 1 processeur(s) logique(s) Version du BIOS/Date Phoenix Technologies LTD V1.22, 22/10/2007 Version SMBIOS 2.4 Répertoire Windows C:\Windows Répertoire système C:\Windows\system32 Périphérique de démarrage \Device\HarddiskVolume2 Option régionale France Couche d'abstraction matérielle Version = "6.0.6002.18005" Utilisateur PC-de-maman\maman Fuseaux horaires Paris, Madrid Mémoire physique (RAM) installée 2,50 Go Mémoire physique totale 2,49 Go Mémoire physique disponible 1,20 Go Mémoire virtuelle totale 5,21 Go Mémoire virtuelle disponible 3,60 Go Espace pour le fichier d'échange 2,78 Go Fichier d'échange C:\pagefile.sys