On the sys I reg'd, running XP SP-3, w/ automatic Windows updates set to download and prompt to install... downloaded updates automatically; then when shutting down, default "shut down" button automatically installs downloaded updates. Not sure which ones got downloaded, but I suspect maybe a .NET issue, bc I had all that updated w/ .NET v.3, but it caused Quickbooks Pro 2009 to crash, so had to roll back to .NET v.2 w/ all updates/patches (talk about a PITA). Had been running w/ no prob, installed some updates selectively avoiding the .NET v.3 and had no prob. But this last time, it all went on autopilot (even though I hadn't changed anything... so I'm thinking MS pushed it), and ever since that set of updates, I get BSOD @ startup, can't get past it via any of the safe modes or last known good config, can't get to C prompt.
Error message contents:
...
BAD_POOL_CALLER
...
Technical information:
*** STOP: 0x000000c2 (0x00000043, 0xD1311000, 0x00000000, 0x00000000)
Then it does the physical dump of memory
BIOS on this laptop is limited at best; it is not possible to disable caching/shadowing. There was no new HW installed, and the only new SW has been the Windows Updates.
FWIW, the 2nd string w/in the parenthesis varies depending on which option I take from the F8 list of load options. 0xD1311000 is displayed when doing last known good cfg option. 0xC62D1000 is displayed when trying to load safe mode.
Tried MS tech support website, found a procedure to get a hotfix, but I can't load the OS to install a hotfix, so what the rock...and MS is the culprit anyway.
(Of course, this would only happen when I'm crunching for a deadline, and the most recent backup attempt had failed, so the only source of data for the last 30 days is on the laptop that BSOD bad_ pool_caller, loop ad infinitum. )
Would greatly appreciate assistance.
Happy New Year,
Rinnie