tremblez
Habitué
Bonjour,
J'ai un PC qui redémarre aléatoirement depuis qu'il est en fonction.
J'ai vérifier les RAM, le disque dur, mis à jour les drivers, windows... toujours le même problème.
J'ai pensé à une surchauffe mais le processeur peut suporter une température de 50° non ?
Voici le WhoCrash :
Si quelqu'un s'y connait, j'ai consulté google, appliqué un peu de tout mais toujours sans résultat. La seul chose que je n'ai pas encore fait, c'est réinstaller Windows.
Merci,
System Information (local)
--------------------------------------------------------------------------------
computer name: SAPTWO
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3690029056 total
VM: 2147352576, free: 1955422208
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 29/07/2011 06:07:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-14078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x11866E)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF858E4848, 0xFFFFFFFF858E4848, 0xFFFFFFFF858E0848)
Error: BAD_POOL_HEADER
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 29/07/2011 06:07:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!ExAllocatePoolWithTag+0x669)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF858E4848, 0xFFFFFFFF858E4848, 0xFFFFFFFF858E0848)
Error: BAD_POOL_HEADER
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 28/07/2011 10:42:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-16578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED67)
Bugcheck code: 0x50 (0xFFFFFFFFC05AE8C0, 0x0, 0xFFFFFFFF8315371A, 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 Thu 28/07/2011 07:04:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-16796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2428)
Bugcheck code: 0x4E (0x99, 0x7BAC2, 0x0, 0x7C4C2)
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 Thu 28/07/2011 05:53:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-16546-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA1D60)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF858E4530, 0xFFFFFFFF858E4530, 0xFFFFFFFF858E0530)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 27/07/2011 12:36:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-15328-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x76310)
Bugcheck code: 0xDE (0x2, 0xFFFFFFFFB0E232D8, 0xFFFFFFFFA573B88D, 0xFFFFFFFFB65698C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 a driver has corrupted pool memory that is used for holding pages destined for disk.
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 27/07/2011 12:07:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-15031-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA1D60)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFAB15F778, 0x0, 0xFFFFFFFFAB15F778)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Tue 26/07/2011 17:13:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-16546-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFAB1CB718, 0xFFFFFFFFAB1CB2F0, 0xFFFFFFFF8D181F52)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 26/07/2011 12:32:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-16531-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC2F8F)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFFE1CD568, 0xFFFFFFFFFE1CD568, 0xFFFFFFFFFE1C9568)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Mon 25/07/2011 12:05:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-17875-01.dmp
This was probably caused by the following module: immunetprotect.sys (ImmunetProtect+0x545)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF858E6790, 0xFFFFFFFF858E6790, 0xFFFFFFFF858E2790)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\immunetprotect.sys
product: Windows (R) Codename Longhorn DDK driver
company: Windows (R) Codename Longhorn DDK provider
description: Immunet Protect Driver
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.
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: immunetprotect.sys (Immunet Protect Driver, Windows (R) Codename Longhorn DDK provider).
Google query: immunetprotect.sys Windows (R) Codename Longhorn DDK provider BAD_POOL_HEADER
On Mon 25/07/2011 11:51:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-18593-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCA73E)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC000B758, 0xFFFFFFFFAF881847, 0xFFFFFFFFC001C23A)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 25/07/2011 08:39:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-19937-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFB32499BC, 0xFFFFFFFFB32495A0, 0xFFFFFFFF8D147F52)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 25/07/2011 05:15:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-17140-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFB0EF1AA4, 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 Sat 23/07/2011 13:47:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072311-16281-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC130D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9996130D, 0xFFFFFFFFBC90CB28, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 18/07/2011 13:30:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071811-20359-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC1D94)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFF9A030000, 0x322C, 0xFFFFFFFFFAAB7009)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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.
J'ai un PC qui redémarre aléatoirement depuis qu'il est en fonction.
J'ai vérifier les RAM, le disque dur, mis à jour les drivers, windows... toujours le même problème.
J'ai pensé à une surchauffe mais le processeur peut suporter une température de 50° non ?
Voici le WhoCrash :
Si quelqu'un s'y connait, j'ai consulté google, appliqué un peu de tout mais toujours sans résultat. La seul chose que je n'ai pas encore fait, c'est réinstaller Windows.
Merci,
System Information (local)
--------------------------------------------------------------------------------
computer name: SAPTWO
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3690029056 total
VM: 2147352576, free: 1955422208
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 29/07/2011 06:07:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072911-14078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x11866E)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF858E4848, 0xFFFFFFFF858E4848, 0xFFFFFFFF858E0848)
Error: BAD_POOL_HEADER
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 29/07/2011 06:07:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!ExAllocatePoolWithTag+0x669)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF858E4848, 0xFFFFFFFF858E4848, 0xFFFFFFFF858E0848)
Error: BAD_POOL_HEADER
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 28/07/2011 10:42:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-16578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED67)
Bugcheck code: 0x50 (0xFFFFFFFFC05AE8C0, 0x0, 0xFFFFFFFF8315371A, 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 Thu 28/07/2011 07:04:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-16796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD2428)
Bugcheck code: 0x4E (0x99, 0x7BAC2, 0x0, 0x7C4C2)
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 Thu 28/07/2011 05:53:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072811-16546-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA1D60)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF858E4530, 0xFFFFFFFF858E4530, 0xFFFFFFFF858E0530)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 27/07/2011 12:36:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-15328-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x76310)
Bugcheck code: 0xDE (0x2, 0xFFFFFFFFB0E232D8, 0xFFFFFFFFA573B88D, 0xFFFFFFFFB65698C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 a driver has corrupted pool memory that is used for holding pages destined for disk.
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 27/07/2011 12:07:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-15031-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA1D60)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFAB15F778, 0x0, 0xFFFFFFFFAB15F778)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Tue 26/07/2011 17:13:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-16546-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFAB1CB718, 0xFFFFFFFFAB1CB2F0, 0xFFFFFFFF8D181F52)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 26/07/2011 12:32:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-16531-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC2F8F)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFFE1CD568, 0xFFFFFFFFFE1CD568, 0xFFFFFFFFFE1C9568)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Mon 25/07/2011 12:05:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-17875-01.dmp
This was probably caused by the following module: immunetprotect.sys (ImmunetProtect+0x545)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF858E6790, 0xFFFFFFFF858E6790, 0xFFFFFFFF858E2790)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\immunetprotect.sys
product: Windows (R) Codename Longhorn DDK driver
company: Windows (R) Codename Longhorn DDK provider
description: Immunet Protect Driver
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.
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: immunetprotect.sys (Immunet Protect Driver, Windows (R) Codename Longhorn DDK provider).
Google query: immunetprotect.sys Windows (R) Codename Longhorn DDK provider BAD_POOL_HEADER
On Mon 25/07/2011 11:51:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-18593-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCA73E)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC000B758, 0xFFFFFFFFAF881847, 0xFFFFFFFFC001C23A)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 25/07/2011 08:39:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-19937-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFB32499BC, 0xFFFFFFFFB32495A0, 0xFFFFFFFF8D147F52)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 25/07/2011 05:15:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-17140-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFB0EF1AA4, 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 Sat 23/07/2011 13:47:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072311-16281-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC130D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9996130D, 0xFFFFFFFFBC90CB28, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 18/07/2011 13:30:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071811-20359-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC1D94)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFF9A030000, 0x322C, 0xFFFFFFFFFAAB7009)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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.
