BAD_POOL_CALLER

Check if this software bug applies to your system:

During an upgrade from 2000 to XP, this error occurs when the computer has a Winnov Videum AVI video capture adapter with the Videum software version 2.9.2. This is commonly found on the Compaq Professional Workstation AP550 computer. Fix instructions are available from Microsoft article 310527.

Using the ATI Fury Maxx Video Adapter with XP can cause this problem. Upgrade to the latest ATI video driver (Microsoft article 307151).

You may have a defective memory. This is even more likely if it only occurs when the system is cold or hot, but not all the time. Use a memory tester to confirm if it is defective or if you have spare memory, try replacement.

Windows 7 and Vista include a Memory Test program when booting from the Windows Installation DVD. Step-by-step instructions with screen shots are available at Using System Restore on 7/Vista/2008 as part of System Recovery.

Several software products that also provide memory and video diagnostics includes Fix-It Utilities Professional and SystemSuite Professional. Other diagnostic products include Eurosoft's PC Check and Iolo's System Mechanic.

Additional Memory Solutions:

• Confirm all the memory is of the same type and speed. Many motherboards only work correctly when the memory is installed with matched sets and matched speeds.
• If you added or changed your memory just before this problem occurred, try reverting to the prior memory configuration to confirm it's the source of the problem.
• Check that the memory is fully seated in the sockets. Memory sockets often have side latches that need to be upright to indicate the memory is correctly locked in place.
• Confirm the memory resides in the correct slots on the motherboard. You'll need to refer to the motherboard manual to confirm this. There is little consistency, even within a single vendor. Some systems require that memory is installed as matched pairs, but not always adjacent to each other!
• It's also possible the memory problem is on the video card, as they often contain additional memory. The video card should be tested and/or try a different video card to see if the problem goes away.

Reinstall a clean version of Windows using the installation CD/DVD. This may erase all your data, so be sure to have a valid backup before starting.

Install the latest Windows software updates. Don't forget to check for non-critical updates too!

To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).

For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.

For IE 7 and older: Click on Tools, then Windows Update. Follow the instructions.

Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.

You can use a product like Driver Genius or Radar Sync to verify you have the latest drivers and help keep all your drivers up-to-date. If you're comfortable with driver installations, you can individually find and install current drivers.

A some of the most popular driver download sites:

• CPU and Chipset Drivers: AMD, Intel, Via
• Video Drivers: ATI, Intel, Nvida
• Computer and other hardware manufacturers

Check out what others say about this issue and review or add your own comments and solutions!

The current thread is making a bad pool request.

After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.

Parameter 1 specifies the cause of the issue.

0x00000000	The current thread requested a zero-byte pool allocation.
0x00000001	The pool header has been corrupted.
0x00000002	The pool header has been corrupted.
0x00000004	The pool header has been corrupted.
0x00000006	The current thread attempted to free the pool, which was already freed.
0x00000007	The current thread attempted to free the pool, which was already freed.
0x00000008	The current thread attempted to allocate the pool at an invalid IRQL (Interrupt Request Level).
0x00000009	The current thread attempted to free the pool at an invalid IRQL.
0x0000000A	The current thread attempted to free pool memory by using the wrong tag. (The memory might belong to another component.)
0x0000000B	The current thread attempted to release a quota on a corrupted pool allocation.
0x0000000C	The current thread attempted to release a quota on a corrupted pool allocation.
0x0000000D	The current thread attempted to release a quota on a corrupted pool allocation.
0x00000040	The current thread attempted to free the kernel pool at a user-mode address.
0x00000041	The current thread attempted to free a non-allocated nonpaged pool address.
0x00000042	The current thread attempted to free a virtual address that was never in any pool.
0x00000043	The current thread attempted to free a virtual address that was never in any pool.
0x00000044	The current thread attempted to free a non-allocated nonpaged pool address.
0x00000046	The current thread attempted to free an invalid pool address.
0x00000047	The current thread attempted to free a non-allocated nonpaged pool address.
0x00000048	The current thread attempted to free a non-allocated paged pool address.
0x00000050	The current thread attempted to free a non-allocated paged pool address.
0x00000060	The current thread attempted to free an invalid contiguous memory address (The caller of MmFreeContiguousMemory is passing a bad pointer.)
0x00000099	The current thread attempted to free pool with an invalid address (This code can also indicate corruption in the pool header.)
0x0000009A	The current thread marked an allocation request MUST_SUCCEED (This pool type is no longer supported.)
0x0000009B	The current thread attempted to allocate a pool with a tag of 0 (This would be untrackable, and possibly corrupt the existing tag tables.)
0x0000009C	The current thread attempted to allocate a pool with a tag of "BIG" (This would be untrackable and could possibly corrupt the existing tag tables.)
0x0000009D	The current thread attempted to allocate a pool with a tag that does not contain any letters or digits. Using such tags makes tracking pool issues difficult.
0x00041286	The current thread attempted to free a paged pool address in the middle of an allocation.

Parameter 2 depends on the value of Parameter 1.

Parameter 3 depends on the value of Parameter 1.

Parameter 4 depends on the value of Parameter 1.