IRQL_NOT_LESS_OR_EQUAL BSOD on Rocket League

[MyNamesYev]

· OS - Windows 10
· x64
· Original installed OS: Windows 10
· Full Retail Version
· Age of System: 3 months
· Age of OS: 5 months

· CPU Ryzen 5 2600x
· Video Card Radeon RX 480
· MotherBoard - MSI x470 Gaming Pro
· Power Supply - Thermaltake 600W

· Self Built

· Desktop

Already did Driver Verifier, also seems to happens to Warface (test), Updated BIOS to latest firmware, and disabled HPET. Updated all drivers. Tried with Ethernet and WiFi. Disabled all other USB components except mouse and keyboard. Did Hard Drive Tests, and memtest86, no errors, and ran a Windows FCC scan. Not overclocked, and temps are normal. No 3rd Party Antivirus. Also re-seated my RAM sticks and switched spots.

 

[Sysnative Windows Update]

Hello and welcome! Does the crash happen only in rocket league? What are the temps like before the crash?

 

[MyNamesYev]

Yes only rocket league. I play more intensive games and they never BSOD or overheat my PC. Idle temps are low and the game crashes faster than the CPU can gain some heat, but CPU temps under stress never go above 80

 

[Sysnative Windows Update]

Then I am inclined to believe it is a Rocket League issue and not your PC.

 

[MyNamesYev]

Out of 20+ games i've tried only one game had the same error. Warface. But don't really play that game so much so it doesn't matter.

 

[Sysnative Windows Update]

I see that other people experience BSODs with the same games. It may be best to get in touch with the developers of the games and troubleshoot the issue, but I would first and foremost launch some kind of a monitoring software while playing to ensure that this isn't just another case of overheating under load.

 

[Jared]

It's extremely difficult for a game to cause a blue screen. Usually it's a bug with the game that a driver mistakenly tries to use, but when the data sent back isn't correct, the driver spews garbage.

The dump is very limited in what it shows, but it's looking like some driver is passing a bad DPC address.

It would probably be worth checking the rest of the driver verifier options. Could you upload a full memory dump somewhere? That would help in searching for the driver.

 

[Sysnative Windows Update]

I'm suspecting a bug as well, as there have been numerous reports of issues with these two.