Solved

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

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
28 answers Last reply Best Answer
More about bsod playing games ntskornl exe
  1. Download and run this: http://www.resplendence.com/whocrashed
    it will scan error logs and present them in a fashion I can read
    it might show us what cause is, as its not ntoskrnl as that is a vital part of windows itself, it just gets the blame a lot.

    Paste results in here if its not obvious who did it.
  2. Colif said:
    Download and run this: http://www.resplendence.com/whocrashed
    it will scan error logs and present them in a fashion I can read
    it might show us what cause is, as its not ntoskrnl as that is a vital part of windows itself, it just gets the blame a lot.

    Paste results in here if its not obvious who did it.


    THanks a lot.
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Sat 16.04.2016 19:25:51 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041616-7968-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803984BF4F6, 0xFFFFD00021F85C10, 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 Sat 16.04.2016 19:25:51 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: 0x3B (0xC0000005, 0xFFFFF803984BF4F6, 0xFFFFD00021F85C10, 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 Sat 16.04.2016 18:44:55 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041616-7812-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xA (0x13, 0x2, 0x1, 0xFFFFF800BC907B9F)
    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.


    On Sat 16.04.2016 17:06:01 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041616-7984-01.dmp
    This was probably caused by the following module: win32kbase.sys (win32kbase!GreReleaseSemaphoreInternal+0xF)
    Bugcheck code: 0xA (0x400000000000, 0x2, 0x0, 0xFFFFF803B00ED86B)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\win32kbase.sys
    product: Operační systém Microsoft® Windows®
    company: Microsoft Corporation
    description: Základní ovladač jádra Win32k
    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 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 Thu 14.04.2016 15:48:02 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041416-8218-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8011C5EE8F6, 0xFFFFD0002328EE30, 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 13.04.2016 21:33:28 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041316-8937-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xD1 (0x7FF7ABEE09D0, 0x2, 0x8, 0x7FF7ABEE09D0)
    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 Wed 13.04.2016 21:30:19 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041316-7828-01.dmp
    This was probably caused by the following module: tcpip.sys (tcpip!TcpPeriodicTimeoutHandler+0x4C0)
    Bugcheck code: 0xA (0x31C7EE08, 0x2, 0x0, 0xFFFFF803F96CC4D6)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\drivers\tcpip.sys
    product: Operační systém Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP Driver
    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 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 13.04.2016 15:25:17 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041316-8046-01.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 Fri 08.04.2016 20:45:30 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\040816-7671-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xEEB44)
    Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80050642EC4, 0xFFFFF80050996740, 0xFFFFFD8000001390)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 364.72
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 364.72
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 364.72 , NVIDIA Corporation).
    Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED


    On Thu 07.04.2016 21:06:23 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\040716-8109-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8037C46DF38)
    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.


    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    11 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:

    nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 364.72 , NVIDIA Corporation)

    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.

    They wrote me this.
  3. All of them are parts of windows except the Nvidia driver...

    Try this to fix Nvidia: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

    might want to update motherboard drivers too, you might need new LAN drivers.
  4. Colif said:
    All of them are parts of windows except the Nvidia driver...

    Try this to fix Nvidia: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

    might want to update motherboard drivers too, you might need new LAN drivers.


    Hey, thanks for responding again... :)
    I tried ddu, after it I had even more bsod even though I wasn't playing...
    So now I'm wiping my sdd and hdd with dban and I will do a full clean reinstalation of windows and all drivers, I'm not patient enough but it already takes 4 weeks and my pc is still not running, first those hw troubles and now this. I will do the memtest86 after the reinstalation if it doesn't work again...
    I hope dban can help me, do you think it can? Have you got any advises for me?
    Thanks a lot!
  5. just hope it works out for you. You could have wiped all your drives using the win 10 installer, the extra step isn't really necessary.

    here is win 10 install file for when you are ready: Win 10 Media Creation Tool

    Most of the errors looked like they caused by drivers, so try get new ones next time.
  6. Colif said:
    just hope it works out for you. You could have wiped all your drives using the win 10 installer, the extra step isn't really necessary.

    here is win 10 install file for when you are ready: Win 10 Media Creation Tool

    Most of the errors looked like they caused by drivers, so try get new ones next time.


    Thanks again, I will let you know if worked or not, hope it's gonna be fine :)
    Thanks!
  7. many of your buchecks indicated bad memory addresses passed to windows drivers. One indicated a attempt to execute a illegal instruction.

    I would be looking for memory corruption issues, IE overclocking, overheating, power problems. These can also occur with malware or old drivers that are corrupting memory data structures.

    You might consider putting the actual memory dump file on a server and post a link.
  8. johnbl said:
    many of your buchecks indicated bad memory addresses passed to windows drivers. One indicated a attempt to execute a illegal instruction.

    I would be looking for memory corruption issues, IE overclocking, overheating, power problems. These can also occur with malware or old drivers that are corrupting memory data structures.

    You might consider putting the actual memory dump file on a server and post a link.


    Hey, thanks for responding.
    As I wrote, I already reinstalled windows, I have to install a game and test if the problem is still here, if yes, I will post the minidump again and I was thinking about memtest86, I've never worked with it, but it's written on some forums that this can solve some problems as well.
    Thanks guys!
  9. Just happened to have this on a tab: http://www.memtest86.com/

    Though john wasn't saying it was RAM precisely. He suggested overheating, overclocking and power... Memory management errors can be hardware or software.

    Try running malwarebytes in future, reduce chance of it being malware causing it - helps to have anti virus as well. Defender isn't the best
  10. Colif said:
    Just happened to have this on a tab: http://www.memtest86.com/

    Though john wasn't saying it was RAM precisely. He suggested overheating, overclocking and power... Memory management errors can be hardware or software.

    Try running malwarebytes in future, reduce chance of it being malware causing it - helps to have anti virus as well. Defender isn't the best


    OK, so I will download and buy this software if I need it, I bought eset as well, so I hope it's gonna help a little, but as I said, this computer is quite new, I thought it should be alright, I'm almost done with the reinstalling (takes some time cause of my Internet connection) so as soon as I can turn witcher on I will now what's gonna happen, hope that this gonna fix this...
  11. its free, not sure what pro version offers over free one.
  12. so reinstalled everything, error is here again, i´m quite desperate...

    On Tue 19.04.2016 17:12:10 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041916-9703-01.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 Tue 19.04.2016 17:12:10 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 Tue 19.04.2016 10:34:26 GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041916-8796-01.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801528588F6, 0xFFFFD00023245E30, 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.
  13. Since the driver responsible is not revealing itself, you might be best running this and see if we can find it.:

    Quote:
    Driver Verifier is a tool included in Microsoft Windows that replaces the default operating system subroutines with ones that are specifically developed to catch device driver bugs.[1] Once enabled, it monitors and stresses drivers to detect illegal function calls or actions that may be causing system corruption. It acts within the kernel mode and can target specific device drivers for continual checking or make driver verifier functionality multithreaded, so that several device drivers can be stressed at the same time
    http://www.tenforums.com/tutorials/5470-driver-verifier-enable-disable-windows-10-a.html

    Don't run it too long but make sure to test all non Microsoft drivers. It probably bsod before long anyway, as it says, disable it when it does.
  14. I´ve been running this, it showed me that everything is alright, so should i keep it turned on?
    Can i get stuck somehow? BSOD comes only when i play, so shell i play with the verifier? I also turned on the full minidump...
    Thanks again for responding...
  15. i wouldn't suggest running it when you play a game. this driver is a pain, it only plays up when you want to play...

    stop it, i didn't know you already tried it.
  16. Best answer
    try updating bios, is your mobo the killer or the professional?

    Killer bios: http://www.asrock.com/MB/AMD/Fatal1ty%20990FX%20Killer/?cat=Download&os=BIOS
    Professional: http://www.asrock.com/mb/AMD/Fatal1ty%20990FX%20Professional/?cat=Download&os=BIOS

    one guy on the Fatality H170 had system exception Feb and was solved by new bios. Asrock warn not to update if everything working fine.. its not though

    System service exception:

    Cause

    This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

    damn it Nvidia!!
  17. I tried it and played a game, it gave me the bsod, now i have it off already.
    It gave me, or i think so a 15,6gb dump report, is it possible?
  18. ok i will try to update the bios via Windows possibility, fingers cross :D
  19. i would do it via bios, not windows.a random BSOD during it would be fatal

    how long you run verifier for? 15.9gb seems a little big, and too big to upload
  20. I risked it and it worked just fine, bios is updated.
    So now i should try play game?
  21. Is this game online? It could be Ethernet drivers as well.... Hmm, Killer LAN, they have a bad name too.

    These are newer than the ones on Asrock site: http://www.killernetworking.com/support/driver-downloads - they only 2 days old.

    you did have a tcpip error once before the reinstall.
  22. Yes that's what I did, uninstalled this one.
    Now I'm playing and still no bsod, hope it's gonna work, will let ya know.
  23. Thank you so much, it looks that it finally works, no more BSOD after the BIOS update..

    However i had a faint without the blue death, it was just the faint, guessing what it should be i was playing like three hours, so may be CPU, have no idea have to download cpu z

    Thanks again, i will keep ya informed after some time if the problém is solved, thanks maaaan!
    I can play finally after a month!! :)
  24. Yay!

    Only way to tell if a problem is fixed is the lack of errors. No sign saying "You win"
  25. 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.
  26. 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
  27. 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?
  28. 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.
Ask a new question

Read More

windows 10 Blue Screen Games