Please help with crash dumps - PC and Games Crashing Frequently

[solstrike]

Hi all - my computer is fairly new but I've had constant gaming and BSOD crashes sinve I've gotten it. It seems to happen at load but I cannot pin down the exact cause and I'm desperate for some assistance.

Hardware:
Mobo: ASRock Z270 Killer SLI/ac
Drive: 2 x Samsung EVO 960 500GB (not raid)
CPU: Intel Core i7 7700K (not overclocked)
GPU: Gigabyte G1 GTX 1080 (not overclocked beyond retail)
Memory: CORSAIR Vengeance LPX 16GB (2 x 8GB) 3000MHz
PSU: EVGA SuperNOVA 650W G3
Cooling: Corsair H100i v2; Corsair ML120 x 2
OS: Windows 10 PRO 64bit

Tests that I have tried:
- Memtest: no issues identified after several runs
- Chkdsk: no issues identified
- swapping ram slots: still crashing after
- reformatting with Windows on one drive, games on the other: still crashing after
- using DDU to uninstall Nvidia drivers: no apparent effect

The crashes have a variety of messages, most recently:
IRQL_NOT_LESS_OR_EQUAL

ntoskrnl.exe is identified as the causing module most of the time when I run WhoCrashed but it's not exclusively only that. I've also gotten ntfs.sys. Crashes often occur during gaming or stress tests.

My minidump is attached here. Any assistance would be greatly appreciated. Thank you!

 

[scout_03]

use gpu-z rendering and see if gpu will hold the stress test also you could use occt to stress test psu .

 

[solstrike]

use gpu-z rendering and see if gpu will hold the stress test also you could use occt to stress test psu .

How long should I run both tests for? I've tried GPU-Z Rendering for about 30 minutes and system wasn't stressed. Now running OCCT for PSU.

 

[scout_03]

if both test are ok check your driver one of them could be out of date or corrupted also do a malwares scan .

 

[solstrike]

Can anyone provide any insights on the minidumps?

 

[Calvin7]

3000MHz memory is for an overclocked CPU.

What is the memory currently running at?

 

[scout_03]

you could use whocrashed to have it in plain test and post result here .

 

[solstrike]

The ram is this one: https://www.corsair.com/ca/en/Categories/Products/Memory/VENGEANCE%C2%AE-LPX-16GB-%282x8GB%29-DDR4-DRAM-3000MHz-C15-Memory-Kit---Black/p/CMK16GX4M2B3000C15

I have not overclocked the CPU.

My whocrashed results are here:

On Thu 2018-07-12 2:31:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071218-4562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0x50 (0xFFFFF80F722C0070, 0x0, 0xFFFFF803BB8737CC, 0x0)
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 Thu 2018-07-12 2:31:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xFC8EA)
Bugcheck code: 0x50 (0xFFFFF80F722C0070, 0x0, 0xFFFFF803BB8737CC, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Wed 2018-07-11 7:42:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071118-4421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A0127)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801345A4127, 0xFFFF8F8DD9B822F8, 0xFFFF8F8DD9B81B40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Wed 2018-07-11 3:09:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071118-3843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0x50 (0xFFFFA5877F800068, 0x0, 0xFFFFF80320DFE4BB, 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 Wed 2018-07-11 12:01:04 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071118-3531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0xA (0x7F8000004AB0, 0x2, 0x0, 0xFFFFF800F9E4BD20)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[scout_03]

memtest ram https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x50--page-fault-in-nonpaged-area then https://support.microsoft.com/en-us/help/4028391/windows-how-to-fix-error-0xa-irqlnotlessorequal