SMP BSOD ExFreeMemoryWithTag

[serga]

Problem is the follow:
try to unload driver on smp-somputer and system gets bsod (in ExFreeMemoryWithTag), on uni-processor computer evererything is ok.
Look through driver’s sources and see that memory is freed only once in that line, but debuger gets that ExFreeMemoryWithTag couses BAD_POOL_CALLER. Please tell, how could be fixed this problem or give some clue where to search solve of problem. thnaks a lot))

[Vadim Smirnov]

try to unload driver on smp-somputer and system gets bsod (in ExFreeMemoryWithTag), on uni-processor computer evererything is ok.

Probably syncronization problem…

but debuger gets that ExFreeMemoryWithTag couses BAD_POOL_CALLER

Memory was already released or your memory pointer was corrupted. Put the breakpoint on the pointer access and trace all operations with it during your driver unload.

[Asterisk]

@serga wrote:

Problem is the follow:
try to unload driver on smp-somputer and system gets bsod (in ExFreeMemoryWithTag), on uni-processor computer evererything is ok.
Look through driver’s sources and see that memory is freed only once in that line, but debuger gets that ExFreeMemoryWithTag couses BAD_POOL_CALLER. Please tell, how could be fixed this problem or give some clue where to search solve of problem. thnaks a lot))

This is not an SMP problem. Memory pool syncronized by internal kernel code. BAD_POOL_CALLER appear in ExFreeMemoryWithTag, when you try to free pool with wrong Tag parameter. In some kernels you got such BSOD in one processor systems. Some times you can get this bugcheck in WXP builds of yours driver caused by driver verifyer. For more information search DDK / IFS headers for ExFreePool redefines.

[Author]

Posts