Re: Démarrage Windows LENT et blue screen occasionnels
le 26 Fév 2014 18:45
Bonne nouvelle, en tout cas pour moi, j'ai trouvé la solution à mon problème de téléchargements impossibles. Voici la procédure que j'ai suivie :
"In order to get help with this issue, you need to go to registry editor by pressing windows+R together, Type "Regedit"and press enter to open registry editor.
Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Attachment
One you have found the Attachment folder click on it to locate ScanWithAntivirus on the right side, right click on ScanWithAntivirus, select modify and put the value as "1" (i.e equals "off")."
J'ai donc pu télécharger WhocrashedSetup.
Je Tiens à préciser que j'ai rencontré un écran bleu après le démarrage de mon pc ce midi.
Voici le rapport du logiciel :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 26/02/2014 12:31:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022614-7425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0x6A15C, 0x7, 0x60)
Error: PFN_LIST_CORRUPT
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 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 that cannot be identified at this time.
On Wed 26/02/2014 12:31:50 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: 0x4E (0x99, 0x6A15C, 0x7, 0x60)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
_____________________________________________________________________________________________
Voilà. Donc apperement il n'a détecté que les crashs de ce midi, qui seraients causés par deux differents fichiers...
Je te laisse tirer les conclusions de cette analyse si tu le veux bien...
Merci encore
Bastex
EDIT : J'ai également résolu le problème du message d'erreur que j'avais quand j'ouvrais google chrome. Je crois que c'est le fait de le réinstallé qui a corrigé le problème.