Bonjour,
je reviens vers vous car je n'ai toujours pas réussi à trouver de solution à mon problème. Du coup j'ai télécharger un logiciel "whocrashed".
Du coup je vous colle les résultats affichés si ça peut vous aider à trouver une solution à mon problème :
System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., P8Z77-V LX
CPU: GenuineIntel Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8266752000 total
VM: 2147352576, free: 1914961920
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 16/12/2013 11:13:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121613-14040-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80000146D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Mon 16/12/2013 11:13:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x16DC)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80000146D0, 0xFFFF, 0x0)
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 that cannot be identified at this time.
On Sun 15/12/2013 21:44:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121513-11497-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003091E94, 0xFFFFF88008547DE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Sat 14/12/2013 08:34:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121413-14804-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800C161A28, 0xFFFFF8800C161280, 0xFFFFF800030F6C97)
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 that cannot be identified at this time.
