Ecran bleu redemarrage automatique
christ
-
christ -
christ -
Bonjour,
depuis deux/trois mois j ai des crashs bleus avec redemarrage automatique.
voici ce que "whoscrashed" me dit :
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3755552768 total
VM: 2147352576, free: 1979035648
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 31/07/2011 04:56:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073111-02.dmp
This was probably caused by the following module: nvmfdx32.sys (nvmfdx32+0x160C2)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\nvmfdx32.sys
product: NVIDIA Networking Driver
company: NVIDIA Corporation
description: NVIDIA MCP Networking Function Driver.
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: nvmfdx32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation).
Google query: nvmfdx32.sys NVIDIA Corporation UNEXPECTED_KERNEL_MODE_TRAP
On Sun 31/07/2011 04:56:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvmfdx32.sys (nvmfdx32!_ADAPTER_CMD_InitClient@8+0x36CC)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\nvmfdx32.sys
product: NVIDIA Networking Driver
company: NVIDIA Corporation
description: NVIDIA MCP Networking Function Driver.
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: nvmfdx32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation).
Google query: nvmfdx32.sys NVIDIA Corporation UNEXPECTED_KERNEL_MODE_TRAP
On Sun 31/07/2011 00:39:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073111-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB6BA8)
Bugcheck code: 0x1A (0x402, 0xFFFFFFFFC002F340, 0xFFFFFFFF8ED4B824, 0xFFFFFFFFAABB44A0)
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 Sat 30/07/2011 09:27:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-05.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3FD64)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC0017F00, 0xFFFFFFFF8EEF7867, 0xFFFFFFFF88728D28)
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 Sat 30/07/2011 09:24:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-04.dmp
This was probably caused by the following module: cdrom.sys (cdrom+0xEFB9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFFFF8FBB4FB9, 0xFFFFFFFF8C944854, 0xFFFFFFFF8C944550)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\cdrom.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI CD-ROM Driver
Bug check description: This indicates that a system thread 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 Sat 30/07/2011 05:18:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x24, 0x2, 0x0, 0xFFFFFFFF8267E4E1)
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 Sat 30/07/2011 05:04:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-02.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x95043)
Bugcheck code: 0xA (0x4060011, 0x2, 0x0, 0xFFFFFFFF826FB796)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Sat 30/07/2011 05:02:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0xBC, 0x2, 0x1, 0xFFFFFFFF826E2C88)
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 Fri 29/07/2011 16:19:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072911-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0xC, 0x2, 0x0, 0xFFFFFFFF826914E7)
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 Fri 29/07/2011 15:34:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072911-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x68D13)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9BD58D13, 0xFFFFFFFFA8AD8A38, 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 Thu 28/07/2011 11:04:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072811-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x1010124, 0x2, 0x0, 0xFFFFFFFF826854E1)
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 28/07/2011 10:35:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072811-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDB3F)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF89790000, 0xFFFFFFFF89790048, 0x8090000)
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 Wed 27/07/2011 16:33:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072711-04.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x21153, 0x2, 0x0, 0xFFFFFFFF826CE0D4)
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 27/07/2011 04:34:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072711-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0xF48C, 0x2, 0x0, 0xFFFFFFFF826874E7)
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 27/07/2011 04:31:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072711-02.dmp
This was probably caused by the following module: avgntflt.sys (avgntflt+0xFAD4)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF83126AC4, 0xFFFFFFFF8C953E2C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avgntflt.sys
product: AntiVir Workstation
company: Avira GmbH
description: Avira Minifilter Driver
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: avgntflt.sys (Avira Minifilter Driver, Avira GmbH).
Google query: avgntflt.sys Avira GmbH KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\Mini072711-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 31 crash dumps have been found. Only 30 could be analyzed. Only 15 are included in this report. 6 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:
hcwbt8xx.sys (Hauppauge WDM Driver for Bt848, Bt878, Hauppauge Computer Works)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 275.33 , NVIDIA Corporation)
avgntflt.sys (Avira Minifilter Driver, Avira GmbH)
nvmfdx32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation)
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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
j'ai mis tout mes drivers a jour,testé ma memoire(pas de prob) je vois pas du tout quoi faire pour arranger ce probleme.
une aide serait la vienvenue.
merci ;)
depuis deux/trois mois j ai des crashs bleus avec redemarrage automatique.
voici ce que "whoscrashed" me dit :
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3755552768 total
VM: 2147352576, free: 1979035648
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 31/07/2011 04:56:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073111-02.dmp
This was probably caused by the following module: nvmfdx32.sys (nvmfdx32+0x160C2)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\nvmfdx32.sys
product: NVIDIA Networking Driver
company: NVIDIA Corporation
description: NVIDIA MCP Networking Function Driver.
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: nvmfdx32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation).
Google query: nvmfdx32.sys NVIDIA Corporation UNEXPECTED_KERNEL_MODE_TRAP
On Sun 31/07/2011 04:56:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvmfdx32.sys (nvmfdx32!_ADAPTER_CMD_InitClient@8+0x36CC)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\nvmfdx32.sys
product: NVIDIA Networking Driver
company: NVIDIA Corporation
description: NVIDIA MCP Networking Function Driver.
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: nvmfdx32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation).
Google query: nvmfdx32.sys NVIDIA Corporation UNEXPECTED_KERNEL_MODE_TRAP
On Sun 31/07/2011 00:39:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073111-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB6BA8)
Bugcheck code: 0x1A (0x402, 0xFFFFFFFFC002F340, 0xFFFFFFFF8ED4B824, 0xFFFFFFFFAABB44A0)
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 Sat 30/07/2011 09:27:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-05.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x3FD64)
Bugcheck code: 0x1A (0x41201, 0xFFFFFFFFC0017F00, 0xFFFFFFFF8EEF7867, 0xFFFFFFFF88728D28)
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 Sat 30/07/2011 09:24:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-04.dmp
This was probably caused by the following module: cdrom.sys (cdrom+0xEFB9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFFFF8FBB4FB9, 0xFFFFFFFF8C944854, 0xFFFFFFFF8C944550)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\cdrom.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI CD-ROM Driver
Bug check description: This indicates that a system thread 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 Sat 30/07/2011 05:18:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x24, 0x2, 0x0, 0xFFFFFFFF8267E4E1)
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 Sat 30/07/2011 05:04:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-02.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x95043)
Bugcheck code: 0xA (0x4060011, 0x2, 0x0, 0xFFFFFFFF826FB796)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Sat 30/07/2011 05:02:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini073011-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0xBC, 0x2, 0x1, 0xFFFFFFFF826E2C88)
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 Fri 29/07/2011 16:19:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072911-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0xC, 0x2, 0x0, 0xFFFFFFFF826914E7)
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 Fri 29/07/2011 15:34:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072911-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x68D13)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9BD58D13, 0xFFFFFFFFA8AD8A38, 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 Thu 28/07/2011 11:04:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072811-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x1010124, 0x2, 0x0, 0xFFFFFFFF826854E1)
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 28/07/2011 10:35:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072811-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDB3F)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF89790000, 0xFFFFFFFF89790048, 0x8090000)
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 Wed 27/07/2011 16:33:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072711-04.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x21153, 0x2, 0x0, 0xFFFFFFFF826CE0D4)
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 27/07/2011 04:34:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072711-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0xF48C, 0x2, 0x0, 0xFFFFFFFF826874E7)
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 27/07/2011 04:31:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini072711-02.dmp
This was probably caused by the following module: avgntflt.sys (avgntflt+0xFAD4)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF83126AC4, 0xFFFFFFFF8C953E2C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avgntflt.sys
product: AntiVir Workstation
company: Avira GmbH
description: Avira Minifilter Driver
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: avgntflt.sys (Avira Minifilter Driver, Avira GmbH).
Google query: avgntflt.sys Avira GmbH KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\Mini072711-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 31 crash dumps have been found. Only 30 could be analyzed. Only 15 are included in this report. 6 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:
hcwbt8xx.sys (Hauppauge WDM Driver for Bt848, Bt878, Hauppauge Computer Works)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 275.33 , NVIDIA Corporation)
avgntflt.sys (Avira Minifilter Driver, Avira GmbH)
nvmfdx32.sys (NVIDIA MCP Networking Function Driver., NVIDIA Corporation)
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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
j'ai mis tout mes drivers a jour,testé ma memoire(pas de prob) je vois pas du tout quoi faire pour arranger ce probleme.
une aide serait la vienvenue.
merci ;)
A voir également:
- Ecran bleu redemarrage automatique
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Réponse automatique thunderbird - Guide
- Forcer redemarrage windows - Guide
