Depuis quelques temps j'ai des plantages a répétition, apres avoir fais ttes les mises a jours nécéssaire, flaché le bios et fais plusieurs mem test, je reste un peu perplexe. j'ai un athlon 2, 3 Go ram, carte mere Asus, temperature 25 degres.
je poste le rapport de crash.
merci de votre aide.
- Code: Tout sélectionner
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 09/04/2011 16:29:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040911-17518-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD7E3)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFFFFFFFA10018)
Error: BAD_POOL_CALLER
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 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 Fri 08/04/2011 11:02:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040811-15849-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB214E)
Bugcheck code: 0x50 (0xFFFFFFFF9E0A0024, 0x0, 0xFFFFFFFF943C20CE, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 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 Fri 08/04/2011 06:48:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040811-15069-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4681B)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFFFFF8186DED1)
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 07/04/2011 19:51:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040711-17238-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120232)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF81954B40, 0xFFFFFFFF8195EF40, 0xFFFFFFFF81954B40)
Error: BAD_POOL_HEADER
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 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 07/04/2011 17:16:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040711-18220-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5C111)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF81874111, 0xFFFFFFFFA3FABBE4, 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 Thu 07/04/2011 10:37:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040711-15927-01.dmp
This was probably caused by the following module: afd.sys (afd+0x2924D)
Bugcheck code: 0xC5 (0x41FA, 0x2, 0x0, 0xFFFFFFFF8196146A)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\afd.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 06/04/2011 17:32:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040611-15990-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x4AA6)
Bugcheck code: 0xD1 (0x57005F, 0x2, 0x1, 0xFFFFFFFF8A593AA6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 04/04/2011 20:06:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040411-18673-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4681B)
Bugcheck code: 0xA (0xFFFFFFFF8B253004, 0x2, 0x1, 0xFFFFFFFF8186B27A)
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 Mon 04/04/2011 18:37:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040411-16879-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xB0711)
Bugcheck code: 0x34 (0x1DE, 0xFFFFFFFFC0000420, 0x0, 0x0)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 04/04/2011 17:21:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040411-13884-01.dmp
This was probably caused by the following module: nvm62x32.sys (nvm62x32+0x4616)
Bugcheck code: 0xD1 (0x65517E6B, 0x2, 0x0, 0xFFFFFFFF8A677E01)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvm62x32.sys
product: NVIDIA Networking Driver
company: NVIDIA Corporation
description: NVIDIA MCP Networking Function Driver.
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: nvm62x32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation).
Google query: nvm62x32.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 04/04/2011 06:53:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040411-38594-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4681B)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFFFFF818D26D9)
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 Sun 03/04/2011 18:56:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040311-38282-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCE960)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFFFFF818D66D9)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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 Sun 03/04/2011 10:20:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040311-29608-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDFC)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x4A13, 0x4A0A026)
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 03/04/2011 07:20:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040311-16988-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4681B)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFFFFF81873ECF)
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 Sun 03/04/2011 06:54:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040311-20030-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB3182)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF818C9182, 0xFFFFFFFF9F807BCC, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
38 crash dumps have been found and analyzed. Only 15 are included in this report. 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
nvm62x32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation)
