Windows 7 Crash Souvent
Posté : jeu. 20 sept. 2012 17:56
Bonjour ,
Voilà depuis quelque temps mon PC crash énormément et c'est agassant
Mon PC est à Jour et la Ram Pas infect
j'ai posté mon problème dans le forum HP , il m'on dit que je suis Infecté par un Virus ou malware
Merci de m'aidé
Voici ma config :
Champ Valeur
Ordinateur
Type de système PC avec processeur x86 ACPI
Système d'exploitation Microsoft Windows 7 Ultimate
Service Pack du système [ TRIAL VERSION ]
Internet Explorer 9.0.8112.16421
DirectX DirectX 11.0
Nom du système OKAN-PC
Nom de l'utilisateur okan
Domaine de connexion [ TRIAL VERSION ]
Date / Heure 2012-09-20 / 17:53
Carte mère
Type de processeur QuadCore Intel Core 2 Quad Q6600, 2400 MHz (9 x 267)
Nom de la carte mère Asus IPIBL-LB (Benicia) (1 PCI, 2 PCI-E x1, 1 PCI-E x16, 4 DDR2 DIMM, Audio, Video, Gigabit LAN, IEEE-1394)
Chipset de la carte mère Intel Bearlake G33
Mémoire système [ TRIAL VERSION ]
DIMM1: Hynix HYMP112U64CP8-S6 1 Go DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
DIMM2: Hynix HYMP112U64CP8-S6 [ TRIAL VERSION ]
DIMM3: Hynix HYMP112U64CP8-S6 [ TRIAL VERSION ]
Type de BIOS AMI (09/10/09)
Moniteur
Carte vidéo ATI Radeon HD 5450 (1024 Mo)
Carte vidéo ATI Radeon HD 5450 (1024 Mo)
Accélérateur 3D ATI EG Cedar Pro
Accélérateur 3D ATI Radeon HD 5450 (Cedar)
Moniteur HP w2216 [22" LCD] (CNT823L13C)
Multimédia
Carte audio ATI Radeon HDMI @ ATI Cedar/Park - High Definition Audio Controller
Carte audio Realtek ALC888/1200 @ Intel 82801IB ICH9 - High Definition Audio Controller [A-2]
Stockage
Contrôleur IDE Intel(R) ICH9 Family 2 port Serial ATA Storage Controller 2 - 2926
Contrôleur IDE Intel(R) ICH9R/DO/DH 4 port Serial ATA Storage Controller 1 - 2920
Disque dur WDC WD5000AAKS-65A7B0 ATA Device (465 Go, IDE)
Lecteur optique DTSOFT Virtual CdRom Device
Lecteur optique TSSTcorp CDDVDW TS-H653N ATA Device (DVD+R9:16x, DVD-R9:12x, DVD+RW:20x/8x, DVD-RW:20x/6x, DVD-RAM:12x, DVD-ROM:16x, CD:48x/32x/48x DVD+RW/DVD-RW/DVD-RAM)
État des disques durs SMART OK
Partitions
C: (NTFS) [ TRIAL VERSION ]
Taille totale [ TRIAL VERSION ]
Entrée
Clavier Clavier standard PS/2
Souris Souris Microsoft PS/2
Réseau
Adresse IP principale [ TRIAL VERSION ]
Adresse MAC principale 00-1F-C6-8B-21-9D
Carte réseau Anchorfree HSS Adapter
Carte réseau Realtek PCIe GBE Family Controller (192. [ TRIAL VERSION ])
Périphériques
Imprimante Fax
Contrôleur FireWire AT&T/Lucent IEEE1394 FireWire Controller (PHY: Agere LFW3226/3227)
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB2 Intel 82801IB ICH9 - USB2 Enhanced Host Controller [A-2]
Contrôleur USB2 Intel 82801IB ICH9 - USB2 Enhanced Host Controller [A-2]
Périphérique USB Realtek USB 2.0 Card Reader
DMI
Distributeur du BIOS American Megatrends Inc.
Version du BIOS 5.43
Fabricant du système HP-Pavilion
Nom du système FJ395AA-ABF a6547.fr
Version du système
Numéro de série du système [ TRIAL VERSION ]
UUID du système [ TRIAL VERSION ]
Fabricant de la carte mère PEGATRON CORPORATION
Nom de la carte mère Benicia
Version de la carte mère 1.01
Numéro de série de la carte mère [ TRIAL VERSION ]
Fabricant du châssis Hewlett-Packard
Version du châssis Chassis Version
Numéro de série du châssis [ TRIAL VERSION ]
Identifiant du châssis [ TRIAL VERSION ]
Type du châssis Desktop Case
Des infos des crash par Whocrashed
On Thu 20/09/2012 15:45:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-18236-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A43)
Bugcheck code: 0x1A (0x41287, 0x32, 0x0, 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 Thu 20/09/2012 15:45:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!MmDisableModifiedWriteOfSection+0x15F0)
Bugcheck code: 0x1A (0x41287, 0x32, 0x0, 0x0)
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 Thu 20/09/2012 15:40:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-18454-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFF83DFFFE4, 0x2, 0x1, 0xFFFFFFFF82CE2D2E)
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.
On Thu 20/09/2012 15:37:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-17128-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A43)
Bugcheck code: 0xBE (0xFFFFFFFFC003E308, 0xFFFFFFFFAEE1A025, 0xFFFFFFFF9E904C3C, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Thu 20/09/2012 03:54:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-27315-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1F714)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFA90A61B8, 0xFFFFFFFFA90A6350, 0xA330437)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a pool header is corrupt.
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 Wed 19/09/2012 03:37:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-18189-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFF882ABA9)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFF882ABA9, 0xFFFFFFFF9E60F279, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
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: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Wed 19/09/2012 03:32:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-21668-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFF839FFFCC, 0x2, 0x1, 0xFFFFFFFF82AAEE45)
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.
On Wed 19/09/2012 03:30:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-21450-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8C888AFF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8C888AFF, 0xFFFFFFFF8EABD219, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
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: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 18/09/2012 18:48:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-31340-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x91C4C)
Bugcheck code: 0x4E (0x7, 0x65B35, 0x151, 0x0)
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 18/09/2012 15:06:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-18345-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xF9D9)
Bugcheck code: 0xDA (0x504, 0xFFFFFFFFC047BA00, 0x20, 0xF740)
Error: SYSTEM_PTE_MISUSE
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
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 18/09/2012 15:04:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-17674-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0xBE (0xFFFFFFFFC03ABC30, 0x64180025, 0xFFFFFFFF8CCBAC3C, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 18/09/2012 10:25:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-17503-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0xBE (0xFFFFFFFFC03ABF88, 0x646FF025, 0xFFFFFFFF93AEFC3C, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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.
Voilà depuis quelque temps mon PC crash énormément et c'est agassant
Mon PC est à Jour et la Ram Pas infect
j'ai posté mon problème dans le forum HP , il m'on dit que je suis Infecté par un Virus ou malware
Merci de m'aidé
Voici ma config :
Champ Valeur
Ordinateur
Type de système PC avec processeur x86 ACPI
Système d'exploitation Microsoft Windows 7 Ultimate
Service Pack du système [ TRIAL VERSION ]
Internet Explorer 9.0.8112.16421
DirectX DirectX 11.0
Nom du système OKAN-PC
Nom de l'utilisateur okan
Domaine de connexion [ TRIAL VERSION ]
Date / Heure 2012-09-20 / 17:53
Carte mère
Type de processeur QuadCore Intel Core 2 Quad Q6600, 2400 MHz (9 x 267)
Nom de la carte mère Asus IPIBL-LB (Benicia) (1 PCI, 2 PCI-E x1, 1 PCI-E x16, 4 DDR2 DIMM, Audio, Video, Gigabit LAN, IEEE-1394)
Chipset de la carte mère Intel Bearlake G33
Mémoire système [ TRIAL VERSION ]
DIMM1: Hynix HYMP112U64CP8-S6 1 Go DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
DIMM2: Hynix HYMP112U64CP8-S6 [ TRIAL VERSION ]
DIMM3: Hynix HYMP112U64CP8-S6 [ TRIAL VERSION ]
Type de BIOS AMI (09/10/09)
Moniteur
Carte vidéo ATI Radeon HD 5450 (1024 Mo)
Carte vidéo ATI Radeon HD 5450 (1024 Mo)
Accélérateur 3D ATI EG Cedar Pro
Accélérateur 3D ATI Radeon HD 5450 (Cedar)
Moniteur HP w2216 [22" LCD] (CNT823L13C)
Multimédia
Carte audio ATI Radeon HDMI @ ATI Cedar/Park - High Definition Audio Controller
Carte audio Realtek ALC888/1200 @ Intel 82801IB ICH9 - High Definition Audio Controller [A-2]
Stockage
Contrôleur IDE Intel(R) ICH9 Family 2 port Serial ATA Storage Controller 2 - 2926
Contrôleur IDE Intel(R) ICH9R/DO/DH 4 port Serial ATA Storage Controller 1 - 2920
Disque dur WDC WD5000AAKS-65A7B0 ATA Device (465 Go, IDE)
Lecteur optique DTSOFT Virtual CdRom Device
Lecteur optique TSSTcorp CDDVDW TS-H653N ATA Device (DVD+R9:16x, DVD-R9:12x, DVD+RW:20x/8x, DVD-RW:20x/6x, DVD-RAM:12x, DVD-ROM:16x, CD:48x/32x/48x DVD+RW/DVD-RW/DVD-RAM)
État des disques durs SMART OK
Partitions
C: (NTFS) [ TRIAL VERSION ]
Taille totale [ TRIAL VERSION ]
Entrée
Clavier Clavier standard PS/2
Souris Souris Microsoft PS/2
Réseau
Adresse IP principale [ TRIAL VERSION ]
Adresse MAC principale 00-1F-C6-8B-21-9D
Carte réseau Anchorfree HSS Adapter
Carte réseau Realtek PCIe GBE Family Controller (192. [ TRIAL VERSION ])
Périphériques
Imprimante Fax
Contrôleur FireWire AT&T/Lucent IEEE1394 FireWire Controller (PHY: Agere LFW3226/3227)
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB1 Intel 82801IB ICH9 - USB Universal Host Controller [A-2]
Contrôleur USB2 Intel 82801IB ICH9 - USB2 Enhanced Host Controller [A-2]
Contrôleur USB2 Intel 82801IB ICH9 - USB2 Enhanced Host Controller [A-2]
Périphérique USB Realtek USB 2.0 Card Reader
DMI
Distributeur du BIOS American Megatrends Inc.
Version du BIOS 5.43
Fabricant du système HP-Pavilion
Nom du système FJ395AA-ABF a6547.fr
Version du système
Numéro de série du système [ TRIAL VERSION ]
UUID du système [ TRIAL VERSION ]
Fabricant de la carte mère PEGATRON CORPORATION
Nom de la carte mère Benicia
Version de la carte mère 1.01
Numéro de série de la carte mère [ TRIAL VERSION ]
Fabricant du châssis Hewlett-Packard
Version du châssis Chassis Version
Numéro de série du châssis [ TRIAL VERSION ]
Identifiant du châssis [ TRIAL VERSION ]
Type du châssis Desktop Case
Des infos des crash par Whocrashed
On Thu 20/09/2012 15:45:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-18236-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A43)
Bugcheck code: 0x1A (0x41287, 0x32, 0x0, 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 Thu 20/09/2012 15:45:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!MmDisableModifiedWriteOfSection+0x15F0)
Bugcheck code: 0x1A (0x41287, 0x32, 0x0, 0x0)
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 Thu 20/09/2012 15:40:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-18454-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFF83DFFFE4, 0x2, 0x1, 0xFFFFFFFF82CE2D2E)
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.
On Thu 20/09/2012 15:37:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-17128-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A43)
Bugcheck code: 0xBE (0xFFFFFFFFC003E308, 0xFFFFFFFFAEE1A025, 0xFFFFFFFF9E904C3C, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Thu 20/09/2012 03:54:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-27315-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1F714)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFA90A61B8, 0xFFFFFFFFA90A6350, 0xA330437)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a pool header is corrupt.
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 Wed 19/09/2012 03:37:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-18189-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFF882ABA9)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFF882ABA9, 0xFFFFFFFF9E60F279, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
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: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Wed 19/09/2012 03:32:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-21668-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFF839FFFCC, 0x2, 0x1, 0xFFFFFFFF82AAEE45)
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.
On Wed 19/09/2012 03:30:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-21450-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8C888AFF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8C888AFF, 0xFFFFFFFF8EABD219, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
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: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 18/09/2012 18:48:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-31340-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x91C4C)
Bugcheck code: 0x4E (0x7, 0x65B35, 0x151, 0x0)
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 18/09/2012 15:06:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-18345-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xF9D9)
Bugcheck code: 0xDA (0x504, 0xFFFFFFFFC047BA00, 0x20, 0xF740)
Error: SYSTEM_PTE_MISUSE
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
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 18/09/2012 15:04:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-17674-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0xBE (0xFFFFFFFFC03ABC30, 0x64180025, 0xFFFFFFFF8CCBAC3C, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 18/09/2012 10:25:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-17503-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0xBE (0xFFFFFFFFC03ABF88, 0x646FF025, 0xFFFFFFFF93AEFC3C, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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.