Sujet Précédent Sujet Suivant

Bluescreen aléatoire sur Windows Vista

kiwifred -  
 kiwifred -
Bonjour,

J'ai dépanné un pote qui avait depuis un certain temps un faux logiciel d'analyse antivirus sur son PC (Personal Shiel Pro) ; un rogue en fait.

il bloquait complètement tout et redémarré le PC au bout de quelques secondes.

évidemmment le logiciel antivirus Norton internet security n'avait jamais été activé pour l'abonnement donc pasz de protection ...

J'ai fais le nécessaire pour le supprimer et donc maintenant le PC n'est plus bloqué...

J'ai désinstallé Norton pour mettre Antivir de Avira.

Mais aléatoirement on a un Bluescreen avec un décompte de quelques secondes et le PC redémarre.

http://uppix.net/e/b/8/be6752d52fd3efaa7923853fdba34.jpg

http://uppix.net/4/3/6/5dbd815c0c19d664fe7ca844ea5b5.jpg

http://uppix.net/3/5/1/3adecebe6edf69ea3a3987bb5a8ff.jpg

Peut être reste t'il des traces de virus ou autre mais quand je lance Malwarebytes, on a au bout d'un moment le buescreen qui apparait et donc le PC redémarre.

Si je lance Malwarebytes en mode sans échec cela serait peut être mieux, non ?

et éventuellement une analyse antivirus online.

Merci de votre aide.
A voir également:

2 réponses

Réponse 1 / 2
kiwifred
 
voici Les rapports obtenus avec le logiciel BlueScreenView :

==================================================
Dump File : Mini100211-01.dmp
Crash Time : 02/10/2011 14:17:01
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x000039ee
Parameter 3 : 0x00000003
Parameter 4 : 0x0004dd04
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+d8dd1
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6000.21226 (vista_ldr.100218-0019)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+d8dd1
Stack Address 1 : ntkrnlpa.exe+e4073
Stack Address 2 : ntkrnlpa.exe+118ed
Stack Address 3 : ntkrnlpa.exe+1183e
Computer Name :
Full Path : C:\Windows\Minidump\Mini100211-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6000
Dump File Size : 140 040
==================================================

==================================================
Filename : fltmgr.sys
Address In Stack : fltmgr.sys+243e7c34
From Address : 0x80754000
To Address : 0x80785000
Size : 0x00031000
Time Stamp : 0x4549acc2
Time String : 02/11/2006 10:30:58
Product Name : Système d'exploitation Microsoft® Windows®
File Description : Gestionnaire de filtres de système de fichiers Microsoft
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Company : Microsoft Corporation
Full Path : C:\Windows\system32\drivers\fltmgr.sys
==================================================

==================================================
Filename : Ntfs.sys
Address In Stack : Ntfs.sys+22a7cc00
From Address : 0x820bf000
To Address : 0x821c7000
Size : 0x00108000
Time Stamp : 0x4764f079
Time String : 16/12/2007 11:31:37
Product Name : Système d'exploitation Microsoft® Windows®
File Description : Pilote du système de fichiers NT
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Company : Microsoft Corporation
Full Path : C:\Windows\system32\drivers\Ntfs.sys
==================================================

==================================================
Filename : ntkrnlpa.exe
Address In Stack : ntkrnlpa.exe+e4073
From Address : 0x81c00000
To Address : 0x81fa2000
Size : 0x003a2000
Time Stamp : 0x4b7d2336
Time String : 18/02/2010 13:23:34
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 6.0.6000.21226 (vista_ldr.100218-0019)
Company : Microsoft Corporation
Full Path : C:\Windows\system32\ntkrnlpa.exe
==================================================
0
Réponse 2 / 2
kiwifred
 
et un dernier rapport obtenu avec le logiciel WhoCrashed :

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: PC-DE-LOÏC
windows version: Windows Vista , 6.0, build: 6000
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 2011037696 total
VM: 2147352576, free: 1998753792

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 02/10/2011 12:11:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100211-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9CB4D)
Bugcheck code: 0x4E (0x99, 0x39EE, 0x3, 0x4DD04)
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 02/10/2011 12:11:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9CB4D)
Bugcheck code: 0x4E (0x99, 0x39EE, 0x3, 0x4DD04)
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.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed.
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.
0