Bonjour,
Voila mon probleme. Hier en prenant soin de mon pc j'ai lancé une defrag à l'aide du logiciel "Auslogics disk defrag" Ceci à provoqué un crash de mon ordi avec un bluescreen parfaitement illisible.
Depuis il est lent, pour ne pas dire trèèèès lent et recrash inopinément. en cherchant la solution sur internet j'ai entendu parler d'un logiciel "whocrashed" qui donne des informations utiles sur ce genre de probleme. Voici son rapport. Je pense que toutes les informations utiles y compris sur mon systeme y sont indiquées.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: LUKA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6296174592 total
VM: 2147352576, free: 1960841216
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 23/06/2012 15:05:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062312-68515-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008E20168, 0xFFFFF88008E1F9C0, 0xFFFFF800035C41F9)
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 Sat 23/06/2012 15:05:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008E20168, 0xFFFFF88008E1F9C0, 0xFFFFF800035C41F9)
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 Sat 23/06/2012 14:37:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062312-69170-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x7FEF09D2F70, 0x2, 0x0, 0xFFFFF880012ABF2B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 22/06/2012 09:13:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062212-67423-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x400000003E0, 0x2, 0x0, 0xFFFFF8800124EF2B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed.
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.
Voila qui est clair. Si Quelqu'un a la solution ou le moindre indice je suis prenneur. Par ailleur j'indique que j'ai tenté d'effectuer une restauration sans succes. Aucun point de restauration n'étais valable.
Merci d'avance.
