Windows 10: IRQL_NOT_LESS_OR_EQUAL BSOD while playing games

After 10-30mins I'm getting BSOD IRQL_NOT_LESS_OR_EQUAL while Im playing lineage 2. I got new PC ASUS ROG GL553VD. I was playing GTA V and Mass Effect before and didnt have got such a problem. I can normally use my PC.

I've checked hardware and memory with Windows 10 tools. Normally Im solving problems by myself but this one is really hard to me.

Can someone help me with this?

http://www71.zippyshare.com/v/3bPFOtEC/file.html - DMP

Bluescreen view:

==================================================
Dump File : 051517-22031-01.dmp
Crash Time : 15.05.2017 23:22:50
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000028
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff803`65610843
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14a3b0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14a3b0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\051517-22031-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 843 236
Dump File Time : 15.05.2017 23:24:02
==================================================

Extra link from another forum, person posted me debugger:

GardenMan - Pastebin.com

Can you read dmp for me and check whats the problem of BSOD?

:)

 

Multiple BSoDs

Plagued by multiple BSoDs:

PFN_List_Corrupt

IRQL_Not_Less_Or_Equal

Driver_Overran_Stack_Buffer

Been having this problem for a while, sparingly, but now it has become much more common when trying to play games. Computer was previously taken to the shop and problem identified as "Windows 7 Shell", but symptoms persist.

 

Memory diagnostic results

My pc crashes on a multitude of games, while on others it never seems to crash at all. Most of the time it simply crashes to desktop while other times I get IRQL_NOT_LESS_OR_EQUAL bsod.

 

Please read How to upload files

 

I uploaded dmp with the instruction. Ive edited the first post.

I'm waiting for the answer *Smile

 

Remove these programs, known for BSOD issues and revert back any driver installation done by Driver Booster.
Code: Start Menu\Programs\DAEMON Tools Lite Public:Start Menu\Programs\DAEMON Tools Lite Public Start Menu\Programs\Driver Booster 4 Public:Start Menu\Programs\Driver Booster 4 Public[/quote]

 

[/quote] I dont know if thats the issue because I did system restore and it didnt help *Sad

and Ive installed that programs after bluescreen appeared for memtest and drivers

 

They do can contribute to the problem, the only source of drivers for laptop owners is the manufacturer of the laptop and Windows Update

 

I've deleted them and there is still such a problem? what does DMP files say?

 

Just to inform, 1 of the first things I do is check for software that may contribute to the issue.
Removal is a priority, because most of the times (including now) it is about driver update utilities which are known to cause/contribute to the problem, reverting back the driver installation is also important (or reinstall drivers from the right source) since it is the drivers what it is about with driver update utilities.

In regards to the dump files, we'll need driver verifier to identify the driver causing the issue. Every dump is pointing to the exact same address attempted to reference which AFAIK is most likely a bug in a driver.






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.