Citation :
System Information (local)
Computer name: PC-METB
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., A88XM-PLUS
CPU: AuthenticAMD AMD Athlon(tm) X4 860K Quad Core Processor AMD586, level: 21
4 logical processors, active mask: 15
RAM: 17119449088 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 10/04/2016 20:39:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-7562-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!ExpScanGeneralLookasideList+0x40) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80363133290, 0xFFFFD0013D9138B8, 0xFFFFD0013D9130D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread 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 Sun 10/04/2016 20:39:46 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: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80363133290, 0xFFFFD0013D9138B8, 0xFFFFD0013D9130D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 10/04/2016 20:31:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-8531-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!MAPPER::bFoundExactMatch+0x1DE) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9603464194E, 0xFFFFD0006D57DC00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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. On Sun 10/04/2016 20:30:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-8296-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!ComposeWindowIfNeeded+0x1C) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF961CBA98838, 0xFFFFD00023AE9140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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. On Sun 10/04/2016 20:28:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-8796-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8030FE86AE9, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Sun 10/04/2016 17:51:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-8500-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80372D5B7B0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Sun 10/04/2016 07:38:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-9359-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x31, 0xFFFFE001483B0C40, 0xFFFFD00152173000, 0xFFFFC00200CA370F)
Error: MEMORY_MANAGEMENT
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 Sun 10/04/2016 07:08:30 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-9281-01.dmp
This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR
On Sat 09/04/2016 16:59:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040916-8296-02.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsWriteFileSizes+0x197) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006EEB8B54, 0xFFFFD00129013770, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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. On Sat 09/04/2016 15:34:56 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040916-8281-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8032D647EE0, 0xFFFFD000609FC670, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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. Conclusion
34 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has 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: amd_sata.sys (AHCI 1.3 Device Driver, Advanced Micro Devices)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
|