IRQL NOT LESS OR EQUAL. What do I do?

Brawlers9901

Reputable
Aug 19, 2015
1
0
4,510
Hey y'all magnificent people, thanks in advance for helping me out. So I've had my computer for about a year now and it's been wonderful but now my motherboard has started breaking so, but that's not the main problem.

Recently I've been getting frequent blue screens (around 1 per week) which is sometimes incredibely annoying when playing i.e. CS:GO or League since it leaves the team in a very big disadvantage for minutes since I usually have to plug the power out of the comp to fix it.

I have no actual idea how to provide a crash dump, so I'd like some info on that too so I can know exactly how to provide all the knowledge you need!

Thanks in advance <3.
 
Solution
this is a very common driver problem, it is caused because the driver tried to access a memory address that it should not have.
(driver bug) or the data in the memory of the system has been corrupted. (invalid memory address used by the drive)

you need the subcodes in the mindump files to figure out the problem.
the files are located at c:\windows\minidump directory with a .dmp file extension.
you can put these on a server like microsoft onedrive, mark them as public and post a link.

you can also try to run whocrashed.exe or bluescreenview.exe and see if a automated tool can read your memory dumps for you.
(they are ok if the system breaks in a 3rd party driver but not too useful if it names a windows driver)

for memory corruption...
this is a very common driver problem, it is caused because the driver tried to access a memory address that it should not have.
(driver bug) or the data in the memory of the system has been corrupted. (invalid memory address used by the drive)

you need the subcodes in the mindump files to figure out the problem.
the files are located at c:\windows\minidump directory with a .dmp file extension.
you can put these on a server like microsoft onedrive, mark them as public and post a link.

you can also try to run whocrashed.exe or bluescreenview.exe and see if a automated tool can read your memory dumps for you.
(they are ok if the system breaks in a 3rd party driver but not too useful if it names a windows driver)

for memory corruption problems a good start is to update the bios and run memtest86 to confirm your physical ram settings are ok.
 
Solution