System Information (local)
--------------------------------------------------------------------------------
Computer name: IFTEKHAR-PC
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: Inspiron 5537, Dell Inc., 02T8TW
CPU: GenuineIntel Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2577657856 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 11/12/2016 3:33:25 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111216-21109-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x39DC6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFEF8974BC9DC6, 0xFFFFC601A1162FF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base 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 Sat 11/12/2016 3:33:25 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!NtDCompositionGetFrameSurfaceUpdates+0x1946)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFEF8974BC9DC6, 0xFFFFC601A1162FF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base 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 Tue 11/8/2016 9:01:01 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\110816-23296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x335, 0x26E6320, 0xFFFF8C015076A000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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 11/8/2016 2:28:20 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\110816-26281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x1A (0x3F, 0x100D9, 0x8F476A3B, 0x8F47EA3B)
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. This problem might also be caused because of overheating (thermal issue).
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 11/6/2016 10:53:47 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\110616-27921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x139 (0x3, 0xFFFF8C0023138840, 0xFFFF8C0023138798, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
43 crash dumps have been found and analyzed. Only 5 are included in this report.
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.
Facebook
Twitter
Instagram