Windows 10: BSOD 'IRQL NOT LESS OR EQUAL' on Opening Phantasy Star Online 2

I have been getting BSOD with IRQL NOT LESS OR EQUAL error for 2 weeks and only when I opened a specific game, the MMORPG 'Phantasy Star Online 2'.

Important points :
- PC operates normally. BSOD only occurs if I try opening the game
- Sometimes, no BSOD occurred and the game works normally. However, trying to reopen the game will not work
- There's 2 version of this game, one for South East Asia server and one for Japan server, with both having different content (SEA version is behind) but with the same GameGuard. Yet, BSOD occurs on both (dump file will only include crashes from JP version, as I'm trying to reinstall the SEA version)
- Most people say this error is caused by your driver, and because of that I've tried updating/reinstalling some driver (Display, Audio, Wireless Network Adapter). BSOD still occurs

Attachment 110827

:)

 

BSOD when opening Phantasy Star Online 2 (SEA) with Windows 10

Normally, I would not receive BSODs when opening PSo2. However, since an update for windows 10 today, I have been receiving these BSODs every time I attempt to open PSo2 (crashes immediately after Gameguard attempts to do something, 3 times).

Here are the dmp files:

1. 121315-22406-01.dmp

2. 121315-25343-01.dmp

3. 121315-27312-01.dmp

soo...any ideas?

 

BSOD when opening Phantasy Star Online 2 (SEA) with Windows 10

Hi Alvin,

Thank you for posting your query in Microsoft Community.

I understand the issue that you are currently facing, we will try the best we can to resolve your issue.

This issue is better suited in Xbox forum, we have a dedicated team with advanced tools and permissions to help you with this type of issues, I suggest you to post your query in Xbox
forum from the below link for specialized assistance. http://forums.xbox.com/xbox_support/default.aspx

Hope the information helps. Please keep us posted on Windows related queries and we will be happy to assist you further.

 

Both dumps indicate memory corruption:
Code: BugCheck A, {28, 2, 0, fffff8036281785b} Probably caused by : memory_corruption Followup: memory_corruption[/quote] Use memtest86+ please.
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

 

Use memtest86+ please.[/quote] Just done with memtest86+
11 passes in total, no error

Attachment 110971

 

Try enabling Driver Verifier and see if that yields any information:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.

 

For some unknown reason, the error code change to 'PAGE_FAULT_BEYOND_END_OF_ALLOCATION' while Driver Verifier is running (tested twice, but somehow only 1 DMP file is there) and the game simply crashed while trying to open it normally.

EDIT : I've tried again to open the game with the Driver Verifier off. While it does crash, after waiting a few seconds for Windows Diagnostic to analyze the crash, BSOD occurs with the same error code (IRQL NOT LESS OR EQUAL)

Attachment 111007

 

The dump says:
Code: When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen[/quote] Were you able to see what was displayed on the BSOD screen?

 

As I've said before, it only said 'PAGE_FAULT_BEYOND_END_OF_ALLOCATION'

I've tried again just to make sure since the dumps said it pinpoint a certain driver, but there's nothing (unless I've missed something)
Attachment 111132

Here's the dump file from the last test if you want to check
Attachment 111135

 

Nothing useful in the dump, again.

Looking at the drivers on your PC I did see two I don't like.

ASMMAP64 2009/07/02 04:13:26 PM \??\C:\Program Files (x86)\ASUS\ATK Package\ATKG
ATKWMIACPIIO 2013/07/02 03:35:32 PM \??\C:\Program Files (x86)\ASUS\ATK Package\ATK

They belong to ASUS Memory Mapping Driver. Some info here: Exploit

See if you can this and if so, uninstall or disable it and see what happens. This is memory mapping code and all the dumps indicate memory_corruption, so just maybe this is the cause.

 

So far, I can't find any devices that use them. Also, I can't find asmmap64 file at all.
Since both are in the ATK Package folder, I tried uninstalling ATK Package and reinstalling it using the ATKPackage listed on Asus' website (link
). However, BSOD still occurs.

Here's the new dump file if you want to check (the older one didn't have any ATK Package installed)
Attachment 111328

EDIT : Do you think I should try removing the atkwmiacpi64.sys while keeping a backup somewhere else?

 

The new dumps also indicate memory_corruption_large.

So, even though you've tested you memory, you might want to think about replacing it. For now, try removing then reinstering the currently installed ram 8GB DIMM. See the manual: ROG GL552VX | Notebooks | ASUS Global


It says
Memory DDR4 2133 MHz SDRAM, 2 x SO-DIMM socket for expansion up to 32 GB SDRAM

Do you have any other devices plugged in besides mouse, keyboard, speakers and display?

If the BSODs are happening enough then you can try doing a Clean Boot and see how it runs:

See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

 

Sorry for the really late reply. I've been busy last week.

As for the result, reinserting the RAM and Clean Boot didn't work. It simply gives the same error code (IRQL NOT LESS OR EQUAL) like before. I've attached the dump files below for you to check

Attachment 112603

 

Dumps seem pretty useless, just memory_corruption again.

Looking at your installed software, I see a ton of Nvidia stuff. Try following these instructions:

Remove and install latest Nvidia drivers:

I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

Then do a custom install of only the NVidia graphics driver and the PhysX driver.

See if that gets rid of the problem.:

 

Doesn't work, unfortunately. Dump files at the bottom as usual

My friends has also raised the chance of a compatibility issue. I've tried running the Compatibility Troubleshooter on both the launcher and the exe file. Unfortunately, BSOD still happens. I suspect that this is actually caused by the game being incompatible with Windows 10 new update (another friend of mine said anything above Build 1550 causes many problem to games. This might be the case). I'll see what I can find in other sites.

Attachment 112797