Ecran bleu sous 7
avojc
Messages postés
316
Statut
Membre
-
athena223 Messages postés 14406 Date d'inscription Statut Contributeur Dernière intervention -
athena223 Messages postés 14406 Date d'inscription Statut Contributeur Dernière intervention -
Bonjour, depuis ke jai effectuer les mise a jour de mon windows 7, apparait un ecran bleu sur lekel il es ecrit pa textuellement mais en gros ca di ki stop la machine
"a problem has been detected and windows has been shut down prevent damage to your computer
page_fault_in_nonpaged_area
check to make sure any new hardware or software is properly installed
techmical information
stop:0X00000050(0X80000004,0X00000001,0X82DF067,0X00000000)
collecting data for crash dump...
initializing disk for crash dump...
begining dump of physical memory
dumping physical memory to disk: 100
physical memory dump complete
contact your system admin or technical support group for further assistance "
lorske ce message apparait je ne peux rien fer si ce nes ke redemarrer ma machine j'utilse en ce moment google chrome. windows 7 ultimate.
lorsque jai redemarrer voici ce ki est revenue
check to be sure you have adequate disk space. if a driver is identified in the stop message disable the driver or check with the manufacturer for driver updates. try changing video adapters
technical information
stop: 0X0000008E(0XC0000005,0X82E84731,0XAD203704,0X00000000)
merci de votre aide
"a problem has been detected and windows has been shut down prevent damage to your computer
page_fault_in_nonpaged_area
check to make sure any new hardware or software is properly installed
techmical information
stop:0X00000050(0X80000004,0X00000001,0X82DF067,0X00000000)
collecting data for crash dump...
initializing disk for crash dump...
begining dump of physical memory
dumping physical memory to disk: 100
physical memory dump complete
contact your system admin or technical support group for further assistance "
lorske ce message apparait je ne peux rien fer si ce nes ke redemarrer ma machine j'utilse en ce moment google chrome. windows 7 ultimate.
lorsque jai redemarrer voici ce ki est revenue
check to be sure you have adequate disk space. if a driver is identified in the stop message disable the driver or check with the manufacturer for driver updates. try changing video adapters
technical information
stop: 0X0000008E(0XC0000005,0X82E84731,0XAD203704,0X00000000)
merci de votre aide
A voir également:
- Ecran bleu sous 7
- Supprimer rond bleu whatsapp - Guide
- Photofiltre 7 - Télécharger - Retouche d'image
- Clé windows 7 - Guide
- Double ecran - Guide
- Écran bleu - Guide
16 réponses
Fait une recherche sur google ou sur le site de Microsft de ton code erreur.
Et évite d'utiliser du language SMS.
Il vaut mieux demander de l'aide à un grand groupe de personnes que celui d'un informaticien.
Et évite d'utiliser du language SMS.
Il vaut mieux demander de l'aide à un grand groupe de personnes que celui d'un informaticien.
avojc
Messages postés
316
Statut
Membre
4
je sui d'accord pour faire le recherche sur google mais je ne connais meme pa la signification des abreviation de bsod. merci pr ton aide
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Moi j'ai trouvé ceci sur ce forum par exemple :
http://www.google.fr/url?sa=t&source=web&cd=3&ved=0CC0QFjAC&url=http%3A%2F%2Fwww.infos-du-net.com%2Fforum%2F3670-53-bsod-erreur-dgxmms1&ei=LHg-TZuIGMa3hQfitMyvDw&usg=AFQjCNEyzFUP1OcS6-sJYuuMO71CWXZx3g
http://www.google.fr/url?sa=t&source=web&cd=3&ved=0CC0QFjAC&url=http%3A%2F%2Fwww.infos-du-net.com%2Fforum%2F3670-53-bsod-erreur-dgxmms1&ei=LHg-TZuIGMa3hQfitMyvDw&usg=AFQjCNEyzFUP1OcS6-sJYuuMO71CWXZx3g
jai jetter un coup d'oeil mais je ne trouve pas satisfaction merci je sui entrain d'essayer de voir aussi sur les plattes formes de microsoft mais je ne mi retrouve pa. merci encore
voici le rapport de whocrashed merci de ton aide
System Information (local)
--------------------------------------------------------------------------------
computer name: JCHRISTIAN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2002067456 total
VM: 2147352576, free: 2008293376
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 1/25/2011 4:05:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-16816-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF4E8)
Bugcheck code: 0x1A (0x41289, 0xFFFFFFFFCBABE001, 0x800C758, 0xFFFFFFFF80000000)
Error: MEMORY_MANAGEMENT
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 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 Tue 1/25/2011 4:05:56 PM 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: 0x1A (0x41289, 0xFFFFFFFFCBABE001, 0x800C758, 0xFFFFFFFF80000000)
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.
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 MEMORY_MANAGEMENT
On Tue 1/25/2011 12:35:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-15724-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF4E8)
Bugcheck code: 0x4E (0x99, 0x486B7, 0x0, 0x48737)
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 1/25/2011 12:30:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-22542-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xBC4C4)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0802064, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 Tue 1/25/2011 6:06:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-16551-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAF19E)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x384A7B, 0xFFFFFFFFA57DBAC0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 Mon 1/24/2011 10:59:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-16208-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF4E8)
Bugcheck code: 0x4E (0x99, 0x165DC, 0x2, 0x4695B)
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 Mon 1/24/2011 9:37:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-19203-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD703)
Bugcheck code: 0x4E (0x99, 0x12191, 0x2, 0x42C90)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 Mon 1/24/2011 11:22:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012411-17144-01.dmp
This was probably caused by the following module: eamon.sys (eamon+0x5933)
Bugcheck code: 0x50 (0xFFFFFFFF80000000, 0x0, 0xFFFFFFFF82D5D795, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: eamon.sys .
Google query: eamon.sys PAGE_FAULT_IN_NONPAGED_AREA
On Tue 1/18/2011 8:29:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011811-18626-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x242731)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E84731, 0xFFFFFFFFAD203704, 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 Tue 1/18/2011 8:16:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011811-21512-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x88258)
Bugcheck code: 0x50 (0xFFFFFFFF80000004, 0x1, 0xFFFFFFFF82D2F067, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Sun 1/16/2011 8:00:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011711-16754-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xAEFD9)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC000C9E8, 0x1664F025, 0xFFFFFFFF85644D38)
Error: MEMORY_MANAGEMENT
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 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 Sun 1/16/2011 6:34:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011711-16208-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF4E8)
Bugcheck code: 0x4E (0x99, 0x2773E, 0x2, 0x2774F)
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 Sat 1/15/2011 2:09:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011511-19624-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x88258)
Bugcheck code: 0x50 (0xFFFFFFFFC25FFFFC, 0x0, 0xFFFFFFFF82C7FD78, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Mon 1/10/2011 8:22:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011111-17222-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDD0)
Bugcheck code: 0x4E (0x99, 0x4923E, 0x2, 0x61A3D)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
14 crash dumps have been found and analyzed. 2 third party drivers have 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:
eamon.sys
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.
System Information (local)
--------------------------------------------------------------------------------
computer name: JCHRISTIAN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2002067456 total
VM: 2147352576, free: 2008293376
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 1/25/2011 4:05:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-16816-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF4E8)
Bugcheck code: 0x1A (0x41289, 0xFFFFFFFFCBABE001, 0x800C758, 0xFFFFFFFF80000000)
Error: MEMORY_MANAGEMENT
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 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 Tue 1/25/2011 4:05:56 PM 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: 0x1A (0x41289, 0xFFFFFFFFCBABE001, 0x800C758, 0xFFFFFFFF80000000)
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.
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 MEMORY_MANAGEMENT
On Tue 1/25/2011 12:35:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-15724-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF4E8)
Bugcheck code: 0x4E (0x99, 0x486B7, 0x0, 0x48737)
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 1/25/2011 12:30:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-22542-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xBC4C4)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0802064, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 Tue 1/25/2011 6:06:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-16551-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAF19E)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x384A7B, 0xFFFFFFFFA57DBAC0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 Mon 1/24/2011 10:59:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-16208-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF4E8)
Bugcheck code: 0x4E (0x99, 0x165DC, 0x2, 0x4695B)
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 Mon 1/24/2011 9:37:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-19203-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD703)
Bugcheck code: 0x4E (0x99, 0x12191, 0x2, 0x42C90)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 Mon 1/24/2011 11:22:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012411-17144-01.dmp
This was probably caused by the following module: eamon.sys (eamon+0x5933)
Bugcheck code: 0x50 (0xFFFFFFFF80000000, 0x0, 0xFFFFFFFF82D5D795, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: eamon.sys .
Google query: eamon.sys PAGE_FAULT_IN_NONPAGED_AREA
On Tue 1/18/2011 8:29:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011811-18626-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x242731)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E84731, 0xFFFFFFFFAD203704, 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 Tue 1/18/2011 8:16:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011811-21512-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x88258)
Bugcheck code: 0x50 (0xFFFFFFFF80000004, 0x1, 0xFFFFFFFF82D2F067, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Sun 1/16/2011 8:00:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011711-16754-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xAEFD9)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC000C9E8, 0x1664F025, 0xFFFFFFFF85644D38)
Error: MEMORY_MANAGEMENT
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 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 Sun 1/16/2011 6:34:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011711-16208-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF4E8)
Bugcheck code: 0x4E (0x99, 0x2773E, 0x2, 0x2774F)
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 Sat 1/15/2011 2:09:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011511-19624-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x88258)
Bugcheck code: 0x50 (0xFFFFFFFFC25FFFFC, 0x0, 0xFFFFFFFF82C7FD78, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Mon 1/10/2011 8:22:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011111-17222-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDD0)
Bugcheck code: 0x4E (0x99, 0x4923E, 0x2, 0x61A3D)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
14 crash dumps have been found and analyzed. 2 third party drivers have 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:
eamon.sys
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.
Vous pouvez réparer eamon.sys en 3 étapes : système d'erreur écran bleu.
comme vous avez obtenu Eamon. sys système d'erreur écran bleu, puis il ya 94% de chance que votre PC ai des problèmes de registre.
Vous devriez donc y remédier immédiatement.
Le logiciel suivant est un eamon fixer professionnelle, sys écran bleu d'erreur, puis vous pouvez corriger de nombreuses erreurs de PC.
Je pense que vous devriez l'essayer, car cela peut vous aider:
Etape 1) Télécharger un Eamon. sys outil de réparation d'écran bleu d'erreur, d'installer cet outil de réparation d'erreur.
Etape 2) Ouvrir le Eamon système de réparation, outil bleu écran d'erreur puis numériser votre PC gratuitement
Etape 3) Cliquer ensuite sur le bouton Réparer tout puis l'effectuer.
Voici l'url de Eamon. sys : outil de réparation d'écran bleu d'erreur: http://ww1.fixerror2010.com/ttfix-eamon._sys_blue_screen_error-zz0001
Source (s):
http://ww1.fixerror2010.com/ttfix-eamon._sys_blue_screen_error-zz0001 http://ww1.fixerror2010.com/ttfix-eamon._sys_blue_screen_error-zz0001
comme vous avez obtenu Eamon. sys système d'erreur écran bleu, puis il ya 94% de chance que votre PC ai des problèmes de registre.
Vous devriez donc y remédier immédiatement.
Le logiciel suivant est un eamon fixer professionnelle, sys écran bleu d'erreur, puis vous pouvez corriger de nombreuses erreurs de PC.
Je pense que vous devriez l'essayer, car cela peut vous aider:
Etape 1) Télécharger un Eamon. sys outil de réparation d'écran bleu d'erreur, d'installer cet outil de réparation d'erreur.
Etape 2) Ouvrir le Eamon système de réparation, outil bleu écran d'erreur puis numériser votre PC gratuitement
Etape 3) Cliquer ensuite sur le bouton Réparer tout puis l'effectuer.
Voici l'url de Eamon. sys : outil de réparation d'écran bleu d'erreur: http://ww1.fixerror2010.com/ttfix-eamon._sys_blue_screen_error-zz0001
Source (s):
http://ww1.fixerror2010.com/ttfix-eamon._sys_blue_screen_error-zz0001 http://ww1.fixerror2010.com/ttfix-eamon._sys_blue_screen_error-zz0001
jai le pc depui le debut de l'annee 2011 et le processeur je l'acheter le jour ou je montai ma machine. je vien d'installer Eamon. Sys Blue Screen Error et jai scanner la machine 46 erreurs on ete trouver mais pr les reparer il ma demander de payer pr beneficier de la version complete. ke doi je fer alors. merci encore de ton aide
Bonjour ,
Trop de réponse on déja etait faite pour des probleme similaire .
A noté qu'une des derniére mise a jour windows fait planté le systeme .
Je te conseil :
démarrage en mode sans echec puis restauration systeme .
remonte a la veille de la mise a jour et ne la fait pas .
Ca evitera le probleme comme ca .
Trop de réponse on déja etait faite pour des probleme similaire .
A noté qu'une des derniére mise a jour windows fait planté le systeme .
Je te conseil :
démarrage en mode sans echec puis restauration systeme .
remonte a la veille de la mise a jour et ne la fait pas .
Ca evitera le probleme comme ca .
Sinon la solution est la :
https://forums.commentcamarche.net/forum/affich-662466-xp-stop-0x00000050
https://forums.commentcamarche.net/forum/affich-662466-xp-stop-0x00000050
