Bonjour,
J'ai deux disques dur sur mon pc un avec XP et l'autre avec Seven .
Sous XP tout fonctionne parfaitement alors que sous Seven j'ai plein d'écran bleu
pilote à jour !
Avez vous une idée merci
--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.01
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit
http://www.resplendence.com/supportTo check if an update of this program is available, click here.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should ge the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name:
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: D:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 3.40GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 3220496384 total
VM: 2147352576, free: 1957015552
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: D:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 23/04/2011 11:03:35 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042311-24250-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF87907323)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF87907323, 0xFFFFFFFF9D9B3B30, 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/04/2011 11:03:35 GMT your computer crashed
crash dump file: D:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetInstanceContext+0x11C)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF87907323, 0xFFFFFFFF9D9B3B30, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: D:\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 bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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 23/04/2011 10:30:17 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042311-25484-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFA8886574, 0xFFFFFFFFA8886150, 0xFFFFFFFF82C71DA2)
Error: NTFS_FILE_SYSTEM
file path: D:\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 Sat 23/04/2011 08:55:32 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042311-27484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x63DA2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C75DA2, 0xFFFFFFFFA453B728, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\Windows\system32\ntoskrnl.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 Fri 22/04/2011 15:05:15 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042211-23593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x63DA2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C65DA2, 0xFFFFFFFFA325B728, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\Windows\system32\ntoskrnl.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 Fri 22/04/2011 15:01:38 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042211-29312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x63DA2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CAADA2, 0xFFFFFFFF9D8C3728, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\Windows\system32\ntoskrnl.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 Fri 22/04/2011 14:58:24 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042211-27593-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8701F4E3)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8701F4E3, 0xFFFFFFFF80EEC9D0, 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 Fri 22/04/2011 14:51:24 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042211-27437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED57)
Bugcheck code: 0x50 (0xFFFFFFFFBB282B45, 0x1, 0xFFFFFFFF86F87FCB, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: D:\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 Fri 22/04/2011 07:32:12 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042211-20906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x63DA2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C6ADA2, 0xFFFFFFFFA48DF728, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\Windows\system32\ntoskrnl.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 Fri 22/04/2011 07:28:59 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042211-20687-01.dmp
This was probably caused by the following module: luafv.sys (luafv+0x88BC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF86FC31C3, 0xFFFFFFFF90B1BA94, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\Windows\system32\drivers\luafv.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de filtre de virtualisation de fichier LUA
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 Fri 22/04/2011 07:23:09 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042211-19859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x63DA2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C65DA2, 0xFFFFFFFF9E1C5728, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\Windows\system32\ntoskrnl.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 21/04/2011 15:42:37 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042111-19859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x63DA2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CB4DA2, 0xFFFFFFFF98116728, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\Windows\system32\ntoskrnl.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 21/04/2011 15:29:00 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042111-18843-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF87745800)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF87745800, 0xFFFFFFFFA3223740, 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 Thu 21/04/2011 15:01:23 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042111-19531-01.dmp
This was probably caused by the following module: luafv.sys (luafv+0x88BC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8700D7C3, 0xFFFFFFFF97322A94, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: D:\Windows\system32\drivers\luafv.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de filtre de virtualisation de fichier LUA
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 21/04/2011 07:48:53 GMT your computer crashed
crash dump file: D:\Windows\Minidump\042111-19484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED57)
Bugcheck code: 0x50 (0xFFFFFFFFBEB29735, 0x1, 0xFFFFFFFF858BD4CB, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: D:\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.
The following dump files were found but could not be read. These files may be corrupt:
D:\Windows\Minidump\042011-28187-01.dmp
D:\Windows\Minidump\042211-24250-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 30 crash dumps have been found. Only 28 could be analyzed. Only 15 are included in this report. 5 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:
unknown
unknown_module_10000230.sys
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.
Connexion
Inscription
Wiki
Rechercher
