J'ai troqué mon vieux disque dur qui contenait Windows 7 pour du SSD et j'ai suivis un tutoriel pour "optimiser" son utilisation. A part quelques changements dans des logiciels ( Photoshop notamment), c'est + rapide, le bruit en - et aucune différence sur le plan de l'utilisation. Oui mais voilà.. depuis, j'ai tout un tas monstrueux d'écrans bleu de la mort ( bluescreen ) ... certains arrivent alors que je manipule des fichiers lourds comme des contenus multimédias (vidéos) mais à d'autres moments il fait des plantages monumentales alors qu'il n'y a que Firefox d'ouvert ou alors quand l'ordinateur n'est même pas utilisé.
Ci-joint le rapport "whocrashed".
merci pour votre aide.
Code : Tout sélectionner
------------------------------------------------------------
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8531673088 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 13/10/2015 08:13:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101315-9812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x50 (0x4982DA4, 0x1, 0x70F86F3B, 0x8)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 that cannot be identified at this time.
On Tue 13/10/2015 08:13:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0x4982DA4, 0x1, 0x70F86F3B, 0x8)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 that cannot be identified at this time.
On Tue 13/10/2015 07:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101315-10483-01.dmp
This was probably caused by the following module: luafv.sys (0xFFFFF88005A12FB8)
Bugcheck code: 0x50 (0xFFFFFA805CDA366A, 0x1, 0xFFFFF88005A12FB8, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\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 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 that cannot be identified at this time.
On Thu 08/10/2015 09:28:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100815-10280-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4CB3)
Bugcheck code: 0xA (0xFFFFFA80278EC138, 0x2, 0x1, 0xFFFFF800033352E6)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\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 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 that cannot be identified at this time.
On Thu 01/10/2015 17:19:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100115-24242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x1A (0x41287, 0x30, 0x0, 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 Thu 01/10/2015 17:09:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100115-15459-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA80095F9060, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 Thu 01/10/2015 14:38:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100115-14944-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x1A (0x61940, 0x48C3000, 0x268BAAAC0ECDD09E, 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 Thu 01/10/2015 13:16:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100115-17425-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x4E (0x99, 0x130A90, 0x0, 0x151090)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.
On Fri 18/09/2015 10:47:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091815-22776-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000357915F, 0xFFFFF8800B5C8160, 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 Thu 17/09/2015 18:25:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091715-16863-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x14E961)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600017E961, 0xFFFFF880081C41B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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.