Blue Screen of Death à répétition. - SAV - Ordinateurs portables
MarshPosté le 03-11-2015 à 12:59:36
Bonjour, depuis quelques temps j'ai des BSOD à répétition, j'ai essayé de mettre à jours mes drivers (avec Driver Cloud ou en passant directement par les periph windows... Au passage j'ai W10.
J'ai aussi fait un WhoCrashed que je vous met en copie ici !
Je pense que cela peut venir de mon ventillo qui chauffe beaucoup et donc engendrer un shutdown d'urgence... Si c'est le cas, vous avez des idées de comment régler ce problème ?
Encore merci à vous !
System Information (local) --------------------------------------------------------------------------------
Computer name: LPORTABLE Windows version: Windows 10 , 10.0, build: 10240 Windows dir: C:\WINDOWS Hardware: Aspire V3-772, Acer, VA70_HW CPU: GenuineIntel Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz Intel586, level: 6 8 logical processors, active mask: 255 RAM: 8229515264 bytes total
On Mon 02/11/2015 20:50:04 GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x337D) Bugcheck code: 0x139 (0x3, 0xFFFFD00025575DA0, 0xFFFFD00025575CF8, 0x0) Error: KERNEL_SECURITY_CHECK_FAILURE file path: C:\WINDOWS\system32\drivers\dxgmms2.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: The kernel has detected the corruption of a critical data structure. 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 Mon 02/11/2015 12:33:28 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\110215-35234-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0) Bugcheck code: 0xA (0x0, 0xFF, 0x0, 0xFFFFF80307569D57) Error: 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 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 that cannot be identified at this time.
On Mon 02/11/2015 12:11:46 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\110215-34546-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0) Bugcheck code: 0xA (0x5DC8, 0xFF, 0xB9, 0xFFFFF8034E4855D6) Error: 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 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 that cannot be identified at this time.
On Mon 02/11/2015 08:39:25 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\110215-35218-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0) Bugcheck code: 0x50 (0xFFFFE00387845709, 0x10, 0xFFFFE00387845709, 0x2) 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 Sat 31/10/2015 21:29:47 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\103115-35359-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8026840B518, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 that cannot be identified at this time.
On Sat 31/10/2015 18:04:19 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\103115-36125-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0) Bugcheck code: 0x1A (0x403, 0xFFFFF6802D905B60, 0xAF40000018EEA867, 0x7FFFF68029905B60) 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 Sat 31/10/2015 17:09:51 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\103115-48031-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0) Bugcheck code: 0x18 (0x0, 0xFFFFC001ACB574D0, 0x2, 0xFFFFFFFFFFFFFC00) Error: REFERENCE_BY_POINTER 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 reference count of an object is illegal for the current state of the object. 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 30/10/2015 19:08:43 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\103015-42906-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0) Bugcheck code: 0xA (0x5DC8, 0xFF, 0x86, 0xFFFFF800DAA175D6) Error: 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 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 that cannot be identified at this time.
On Thu 29/10/2015 15:52:54 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\102915-37125-01.dmp This was probably caused by the following module: hiber_iastora.sys (hiber_iaStorA+0xCBA79) Bugcheck code: 0xD1 (0x1DC01C, 0xFF, 0x48, 0xFFFFF801C747BA79) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL 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. 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: hiber_iastora.sys . Google query: hiber_iastora.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 29/10/2015 14:32:59 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\102915-36968-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0) Bugcheck code: 0xA (0xFFFFFFFF8B485046, 0xFF, 0xF3, 0xFFFFF80381C9E836) Error: 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 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 that cannot be identified at this time.
Marsh Posté le 03-11-2015 à 12:59:36
Bonjour,
depuis quelques temps j'ai des BSOD à répétition, j'ai essayé de mettre à jours mes drivers (avec Driver Cloud ou en passant directement par les periph windows...
Au passage j'ai W10.
J'ai aussi fait un WhoCrashed que je vous met en copie ici !
Je pense que cela peut venir de mon ventillo qui chauffe beaucoup et donc engendrer un shutdown d'urgence... Si c'est le cas, vous avez des idées de comment régler ce problème ?
Encore merci à vous !
System Information (local)
--------------------------------------------------------------------------------
Computer name: LPORTABLE
Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\WINDOWS
Hardware: Aspire V3-772, Acer, VA70_HW
CPU: GenuineIntel Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8229515264 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 02/11/2015 20:50:04 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x337D)
Bugcheck code: 0x139 (0x3, 0xFFFFD00025575DA0, 0xFFFFD00025575CF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Mon 02/11/2015 12:33:28 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110215-35234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0xA (0x0, 0xFF, 0x0, 0xFFFFF80307569D57)
Error: 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 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 that cannot be identified at this time.
On Mon 02/11/2015 12:11:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110215-34546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0xA (0x5DC8, 0xFF, 0xB9, 0xFFFFF8034E4855D6)
Error: 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 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 that cannot be identified at this time.
On Mon 02/11/2015 08:39:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110215-35218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x50 (0xFFFFE00387845709, 0x10, 0xFFFFE00387845709, 0x2)
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 Sat 31/10/2015 21:29:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\103115-35359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8026840B518, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 that cannot be identified at this time.
On Sat 31/10/2015 18:04:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\103115-36125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6802D905B60, 0xAF40000018EEA867, 0x7FFFF68029905B60)
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 Sat 31/10/2015 17:09:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\103115-48031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x18 (0x0, 0xFFFFC001ACB574D0, 0x2, 0xFFFFFFFFFFFFFC00)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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 30/10/2015 19:08:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\103015-42906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0xA (0x5DC8, 0xFF, 0x86, 0xFFFFF800DAA175D6)
Error: 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 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 that cannot be identified at this time.
On Thu 29/10/2015 15:52:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102915-37125-01.dmp
This was probably caused by the following module: hiber_iastora.sys (hiber_iaStorA+0xCBA79)
Bugcheck code: 0xD1 (0x1DC01C, 0xFF, 0x48, 0xFFFFF801C747BA79)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
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: hiber_iastora.sys .
Google query: hiber_iastora.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 29/10/2015 14:32:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102915-36968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0xA (0xFFFFFFFF8B485046, 0xFF, 0xF3, 0xFFFFF80381C9E836)
Error: 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 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 that cannot be identified at this time.