Blue Screen of Deah: BAD_POOL_HEADER before match starts or after match ends.

(signofzeta) #1

I have joined many matches, and have finished many matches, and have had no problems, but in only 3 instances out of many, when the map tries to load or when the match finishes, and the lobby screen tries to load, the game hangs, and I get a BSOD saying something like a BAD_POOL_HEADER. What is going on here? The instances when I had this error was 5 days after the Phoenix update, once yesterday, and once again this morning. The first 2 times was when the match ended and the lobby screen was loading, and the third time was when I was trying to get into a match.

I read that BAD_POOL_HEADER is related to driver issues, so I want to know what drivers this game communicates with.

Does anyone else have the same problem, even if it didn’t consistently happen?

(wheatCube) #2

Hi there, I have been having BSOD events while playing dirty bomb since very early on. Some times I get 3-5 BSOD events in one gaming session. Quite often I have the BAD_POOL_HEADER but sometimes I also get “IRQL_NOT_LESS_OR_EQUAL”.

I have tried a few things unrelated to dirty bomb but the problem is I have never had a BSOD event without Dirty Bomb running. I have had this computer for 2-3 years played many games and still do but BSOD only happens when dirty bomb is running.

I posted on the SD forums a while ago, no replies. http://forums.warchest.com/showthread.php/45145-I-think-Dirty-Bomb-is-causing-my-windows-to-crash-(blue-screen)?highlight=blue+screen

I don’t have this problem every time I play DB either, some days I can play hours of DB without a BSOD event but on others I have many BSOD events.

(signofzeta) #3

[quote=“wheatCube;104369”]Hi there, I have been having BSOD events while playing dirty bomb since very early on. Some times I get 3-5 BSOD events in one gaming session. Quite often I have the BAD_POOL_HEADER but sometimes I also get “IRQL_NOT_LESS_OR_EQUAL”.

I have tried a few things unrelated to dirty bomb but the problem is I have never had a BSOD event without Dirty Bomb running. I have had this computer for 2-3 years played many games and still do but BSOD only happens when dirty bomb is running.

I posted on the SD forums a while ago, no replies. http://forums.warchest.com/showthread.php/45145-I-think-Dirty-Bomb-is-causing-my-windows-to-crash-(blue-screen)?highlight=blue+screen

I don’t have this problem every time I play DB either, some days I can play hours of DB without a BSOD event but on others I have many BSOD events.[/quote]

Do you have any BAD_POOL_HEADER BSOD when you play any other game running on the Unreal 3 engine?

(wheatCube) #4

[quote=“signofzeta;104821”]

Do you have any BAD_POOL_HEADER BSOD when you play any other game running on the Unreal 3 engine?[/quote]

Nope, I have played Batman Arkham Asylum and Borderlands 2 which run on the unreal 3 engine without any problems whatsoever let alone BSOD events, BAD_POOL_HEADER or otherwise.

(signofzeta) #5

I recently got another type of BSOD. I disconnected my internet to see if the game can even run without an internet connection. It can’t. So I reconnected to the internet, started the game up, quick joined an execution match, and the loading screen was taking too long, so I decided to alt tab out to do something else. BSOD happened, and this time it was a DPC_WATCHDOG_VIOLATION.

Even after my previous BSOD’s, my hard drive started to spin up slower than before, not slow enough that my hard drive is busted, but it was slower than before, before the BSOD.

I don’t want this game to be that game where if I play it, it would shorten the life of my laptop. Because of this, I only play one match at a time, and then quit the game, and I don’t go through long sessions anymore.

(signofzeta) #6

Ok, the bad_pool_header BSOD happened again. I think it might have something to do with the match ending, and my computer having to do a scheduled virus scan or maintenanace at the same time. It’s as if my computer can’t take the load of a scheduled scan and playing dirty bomb at the same time.