Ecrans Bleus VRAIMENT TRES ENERVANT !!!

World-Editor Messages postés 1153 Date d'inscription   Statut Membre Dernière intervention   -  
World-Editor Messages postés 1153 Date d'inscription   Statut Membre Dernière intervention   -
Bonjour, voilà, ça un bon moment que mon PC se coupe de façon aléatoire en affichant des écrans bleus ayant des messages d'erreur différents, j'ai télécharger le logicial "Who Crashed" qui permet d'analyser et d'interpréter ces messages, le soucis c'est que je ne sais pas comment les résoudres.

Voici mon rapport "Who Crashed" :

On Sun 27/03/2011 18:44:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032711-18236-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x4E (0x99, 0x74F47, 0x2, 0x82846)
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 which cannot be identified at this time.

On Sun 27/03/2011 18:44:01 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, 0x74F47, 0x2, 0x82846)
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 which cannot be identified at this time.

On Sun 27/03/2011 17:43:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032711-17066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41289, 0x204E6001, 0xE07, 0x205E6C05)
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 which cannot be identified at this time.

On Sat 26/03/2011 08:57:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032611-23899-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A006E8D100, 0xFFFFF8A007032939, 0x751668C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.
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 25/03/2011 10:09:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032511-18018-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFE8, 0x0, 0xFFFFF8800554358B, 0x0)
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 Fri 25/03/2011 06:17:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032511-18626-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680001518C0, 0xB3A000008394D847, 0xFFFFFA80057FA510)
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 which cannot be identified at this time.

On Wed 23/03/2011 20:56:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032311-17815-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF90081C0D63C, 0x0, 0xFFFFF96000194603, 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 Tue 22/03/2011 17:24:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032211-16551-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x4E (0x99, 0x6919E, 0x0, 0x6F09E)
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 which cannot be identified at this time.

On Mon 21/03/2011 17:50:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032111-17784-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x4E (0x99, 0x86164, 0x0, 0x84964)
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 which cannot be identified at this time.

Si quelqu'un pourrait me dire de quoi ça vient je lui en serait très reconnaîssant, car c'est vraiment très ENERVANT !!!

Mon OS : Windows 7 Pro 64 bits

Cordialement World-Editor

an

2 réponses

chai1310 Messages postés 331 Statut Membre 84
 
j'ai exactement le meme probleme que toi !
si quelqu'un peut nous aider ca serait trés sympa
0
World-Editor Messages postés 1153 Date d'inscription   Statut Membre Dernière intervention   75
 
Je sais que ça ne vient pas de la RAM car elle est neuve.
0
World-Editor Messages postés 1153 Date d'inscription   Statut Membre Dernière intervention   75
 
UP
0
World-Editor Messages postés 1153 Date d'inscription   Statut Membre Dernière intervention   75
 
UP
0
World-Editor Messages postés 1153 Date d'inscription   Statut Membre Dernière intervention   75
 
3 ème UP j'en ai marre d'attendre une réponse
0