Crash/Blue screen "Bad pool caller" when i launch the game.

[Proxy]

When I launch MHW Wild, I get a blue screen with the error "Bad Pool Caller." I tried everything people suggested, like running it as an administrator, reinstalling the game, and changing the launch options (-dx11/-dx12, etc.), but nothing worked. I always get the blue screen as soon as I press play or launch the game from the desktop or folder.

I tried other games, and they run without any issues. I updated my Nvidia drivers, but the problem persists. I even rolled back to the previous version, but it made no difference. Everything on my PC is up to date, and I did a clean install two weeks ago. Everything else is working fine.

[AmaiAmai]

Bad_Pool_Caller is not from the game, it usually means you have either:

1. A real hardware issue with a disk/RAM (or a bad RAM overclock/bus overclock)

2. Windows Update ran without you knowing (or is running) and/or data was corrupted (you can use SFC or DISM tool), or

3. There is a kernel-mode driver causing the issue that allocates memory or storage space.

When the storage / memory was accessed there was no data found after multiple attempts causing the OS to shut the device off. When the primary HDD/SSD is shut off, Windows can no longer run so it bluescreened.

Not sure what hardware you have, but you know it better than a rando on the forums.

[Proxy]

I have many games installed with no issues whatsoever, including Doom Eternal, No Man's Sky, Path of Exile, Ever Crisis, and Octopath Traveler 2, all on the same disk. The only time I get a blue screen is when I try to launch MH Wild.

I have updated everything on my computer, uninstalled and reinstalled MHW three times, and tried everything I could find, yet I still have this issue.

[Proxy]

Windows 11 Professionnel ‎(X64)‎ 24H2
AMD Ryzen 9 5900X
NVIDIA GeForce RTX 4070 SUPER
32 Go RAM
1T NVME

[Proxy]

i I formatted the PC clean all the disk and reinstalled Windows along with all the drivers. I still have the problem as soon as I launch MH Wilds Installer on my NVMe. I have installed other games, and I have no issues when launching and playing them.

I check everything disk error/ram ect ... everything is fine so i guess it's the game but why ...

[Proxy]

when the game is on my "Fikwot FN950 1To Disque SSD Interne M.2 PCIe Gen4 " i get the blue screen when i press play.

On my regular SSD (way slower) game work fine ...

[AmaiAmai]

Originally posted by Proxy:

when the game is on my "Fikwot FN950 1To Disque SSD Interne M.2 PCIe Gen4 " i get the blue screen when i press play.

On my regular SSD (way slower) game work fine ...

That might be a sign that disk has an issue...just a heads up.

But if that disk is the same as your Windows drive, it could just be that the game's buggy code is causing the disk to be stopped (the drive is unloaded for protection, Windows cannot access the drive and bluescreens).

You should still make sure you backup any important information on that disk just in case it is a hardware issue -- with SSDs you don't know they have an issue until they fail esp. if it's from overheating or an electrical issue and not an issue with the chips themselves.

But I haven't had any SSD fail yet, even 14 year old ones still running strong.

I doubt it is a driver issue if it otherwise works fine, unless you use RAID or other drive modes outside of standard use, or use a file system that needs driver support in Windows like ZFS or Ext or you have that disk encrypted with full disk encryption other than Bitlocker.

[Czeszko]

i got same problem. played yesterday 10 hours with game on ssd sata but later on i got delyed audio in cutscenes. i had once this problem in ubisoft avatar and i moved game to ssd m.2 where i got windows and i got 2 blue screens after 2 hours of playing. now i moved back game to ssd sata and i will tell if problem still ocurss

[Stone Cold Stavros Flatley]

My PC rebooted itself four times playing the game after installing to a larger, secondary SSD that both Steam and Windows aren’t on that use for games.

I’ve since reinstalled it on the same drive and don’t seem to have the same problem, but I’ll see how that goes. Game is a genuine disaster for optimisation and background coding.

[AmaiAmai]

Originally posted by Czeszko:

i got same problem. played yesterday 10 hours with game on ssd sata but later on i got delyed audio in cutscenes. i had once this problem in ubisoft avatar and i moved game to ssd m.2 where i got windows and i got 2 blue screens after 2 hours of playing. now i moved back game to ssd sata and i will tell if problem still ocurss

Originally posted by Stone Cold Stavros Flatley:

My PC rebooted itself four times playing the game after installing to a larger, secondary SSD that both Steam and Windows aren’t on that use for games.

I’ve since reinstalled it on the same drive and don’t seem to have the same problem, but I’ll see how that goes. Game is a genuine disaster for optimisation and background coding.

For both, when it crashed did it only say BAD_POOL_CALLER or did it list the faulting driver as one of these drivers "STORPORT.SYS" ? I am certain it's that driver doing it for ya'll.

Also, internal or external (USB) NvME , Laptop or Desktop?

[Black Flame]

I also got the same issue, similar PC setup. Im pretty sure that its an issue on the game side. I will try to unistall it and then install it on a separate older ssd on which windows is not installed. Maybe tha game has this crash if its installed on the same ssd that the windows is installed. Ill check and let you know.

[Black Flame]

Ok so now it works. Seems like if mh wilds is installed on the same ssd as the one on which windows is installed it crashes it somehow. I recommend using a separate ssd on which you got nothing system related.

[icezapt]

Hi All,
I had the same problem, i found the solution for this, the cause of this problem is AMD program called AMD StoreMI, i did not get BSOD anymore after i uninstall it