PC - Win 10 - Stop Codes Crashing

[Hakak33n]

So PC been having some issues with regular crashes over a week.
The stop codes change each time so far I have:
VIDEO_DXGKRNL_FATAL_ERROR
SYSTEM_SERVICE_EXCEPTION
CACHE_MANAGER
SYSTEM_SERVICE_EXCEPTION (this time stating that the failure was: dxgmms2.sys)
FAULTY_HARDWARE_CORRUPTED_PAGE
MEMORY_MANAGEMENT
CRITICAL_STRUCTURE_CORRUPTION
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
KERNEL_DATA_INPAGE_ERROR


I realise that there is clearly something very seriously wrong, any thoughts on what?

 

[Colif]

update graphics drivers (should fix dx errors)

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

 

[ahnilated]

I would also run memtest86 on the system.

 

[Hakak33n]

So gfx updated. Memory test is scheduled for next restart.

WhoCrashed:
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH Z77
CPU: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17121558528 bytes total


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

On Sat 11/03/2017 03:03:29 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031117-5140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80131628BE2, 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 11/03/2017 03:03:29 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x1EB38)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80131628BE2, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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 Fri 10/03/2017 20:28:33 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031017-5265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x7A (0x1, 0xFFFFFFFFC0000005, 0xFFFFE68FE3A35080, 0xFFFF81BEFE420000)
Error: KERNEL_DATA_INPAGE_ERROR
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 the requested page of kernel data from the paging file could not be read into memory.
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 10/03/2017 15:04:57 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031017-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1A (0x61948, 0xD4F29, 0x1, 0xD4F29)
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 Wed 08/03/2017 21:20:23 your computer crashed
crash dump file: C:\WINDOWS\Minidump\030817-5531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80129EFC043, 0xFFFF8C018DC6ED90, 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.

 

[Hakak33n]

Additional error codes:
Critical_process_died
IRQL_not_less_or_equal
Kernel_security_check_failure
Kmode_exception_not_handled

 

[Colif]

I think the top error involving ntfs.sys might be your chipset or sata drivers need an update.

The rest are blaming windows which doesn't really help us,
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[Hakak33n]

It was awhile ago, but I think the actual problem was that I had the RAM chips inserted in the wrong slots for 2 chips,