very often having bsod, only while i´m playing games ntskornl.exe

[Frankie222]

My computers gets stuck after like 15 minutes of playing witcher 3, i haven´t tried any other games, cause my PC is quite new

It´s:
msi gtx 960 4gb
amd 8370
asrock fatality 990x
hyperx ddr3 1866mhz 2x8gb ram
corsair cx 850m
Seagate desktop sshd 2gb
ssd intel 128gb
edimax ac1200

I´ve updated all the drivers, had my pc in servis, because it didn´t run properly in the begining it couldn´t boot up, everything was running when i had my old cpu in, but before i had no signal from the computer, my keyboard didn´t light up and the Picture didn ´t come in my monitor, then it returned from the servis and it was running but i had to put win 10 in, i only had old 64bit vista, in my rig before, so they fixed the hw bt not the sw which i did myself, i also choosed te components myself, so may be i did some faults even though i was checking whether it´s compatible or not.
Now i have this stupi issue with those bsod, i have my computer only 4 weeks, but i can´t use it properly, because of those fails.
I´ve quit all the overclocking, which was only small, it looked it only had good affect for performance, but the falls came as well.

I´m also sending those minidumps which i found you need to see what happenned.
Hope that somebody will be able to help me.
thanks guys and sorry for my noobish english

https://docs.google.com/document/d/1aebsoMzNFHaxhOOIg0imSaozYkgjtEBxv__umWY3CuQ/pub
irql not less or equal

 

[Frankie222]

Grrr. it looks it´s back...

On Thu 21.04.2016 8:22:45 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: 0xD1 (0x0, 0x2, 0x8, 0x0)
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.
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 21.04.2016 7:47:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-106390-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80310817246, 0xFFFFD00023148070, 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.



On Wed 20.04.2016 17:52:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042016-103453-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockIpiRoutine+0x2A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8025E3E19DA, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 Wed 20.04.2016 17:07:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042016-103281-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFE001747391A0, 0xFF, 0x36, 0xFFFFF803CA02A21B)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

 

[Colif]

can i just ignore this post and pretend its okay??

try the fixes in this thread you haven't already: http://www.tomshardware.com/answers/id-2103915/kmode-exception-handled-hal-dll-669a-ntoskrnl-exe-19ed47.html

ntkrnimp appears to be part of the kernal, I just want to know what the imp stands for
hal = hardware allocation layer, the interface between drivers and hardware

 

[Colif]

what we know so far:
Its not win 10 as it happens on win 7
its not the drivers as driver verifier showed they are okay
its not the ram - that is if you tested one stick at a time
it wasn't fixed by bios update
its not an overclock
It only happens when pc is running a game

Unknowns

did you look at temps? its not an overheating issue?
power supply... its tier 4 on here: http://www.tomshardware.com/forum/id-2547993/psu-tier-list.html John said power could be reason, if it can't handle the power needed to run games it could be the reason.
have you run seatools on your sshd to see if its okay?

 

[johnbl]

you should put up the actual memory dump file. The windows debugger only takes a second or two to scan for corruption of the drivers.
the suberror code 0xC0000005 coming out of a windows component indicated that its data is corrupted. looking at the memory dump might provide clues to why.