BAD_POOL_CALLER problem - SOLUTION

[Andrew Kluchevsky]

I know that many people have the following problem: when Windows XP
starts, the blue screen appears with the following error message:
BAD_POOL_CALLER ... and then the system reboots and loads without problems
and then the message appears that system has recovered from serious error.
The reason of this two error messages is that the file pagefile.sys is
corrupted. In order to solve the problem You must recreate the file
pagefile.sys. You can do this by the following way: load as Administrator,
click on Start ---> right-click on My computer, then choose Properties, then
choose Advanced tab. Then click on "Settings" button in the "Visual effects,
processor scheduling, memory usage and virtual memory item". Then choose
Advanced tab. Then click on "Change" button in "Virtual memory" item. Then
remember Your virtual memory settings. Then choose "No paging file" item and
click on "Set" button. Then click on "OK" and "OK" again. Then click on
"Apply" and then on "OK" and again "OK". On the question "Do you want to
restart your computer now ?" answer "Yes". Your computer begins to reboot.
Press F8 when it begins to load. Then choose Safe Mode and boot in it as
administrator. Then press Start ---> Control Panel ---> System then choose
Advanced tab. Then press on "Settings" button in the "Visual effects,
processor scheduling, memory usage and virtual memory item". Then choose
Advanced tab. Then press on "Change" button in
"Virtual memory" item. Then restore Your virtual memory settings You
remembered and press on "Set" button. Then press on "OK" and "OK" again.
Then press on "Apply" and then on "OK" and again on "OK". On the question
"Do you want to restart your computer now ?" answer "Yes". If no message
appears then restart Your computer using Start ---> Turn Off Computer. Your
computer
begins to reboot. Boot as usual. Now, the problem is fixed.
I would appreciate any Your questions, suggestions or comments connected
with my advise about BAD_POOL_CALLER problem. I thank You in advance for
them. I personally answer on any Your question, suggestion, comment or give
You and advise if You have any difficulties. You can contact with me via
newsgroup or via E-mail: akl...@unicom.cv.ua

Kind regards,
Andriy Kluchevsky.
E-mail: akl...@unicom.cv.ua

[Andrew Kluchevsky]

Note (why it is better to boot in Safe Mode than in normal mode when You
return the correct settings of page file in order to complete the fix of
BAD_POOL_CALLER problem): If You have a small amount of RAM (32, 64 Mb or
so) it is impossible to boot in the normal mode without page file after You
set it to zero in order to fix the problem. In the normal mode the swapping
for small volume of RAM will not work with zero size page file so You can't
boot and to set the page file to correct state again (because Windows XP
hasn't enough memory to load all drivers, DLLs and programs and to perform
the operation on setting the page file - all at the same time). That's why I
recommend to boot in the Safe Mode when only necessary drivers and
applications are loaded and You have enough RAM to perform the operation on
setting the page file settings to correct state in order to complete the
fix.

[Mark L. Ferguson]

Thanks, interesting side effect bug. The Windows Update has a Critical patch
for 'error on startup..", as of March 14th.

--

Mark L. Ferguson MS-MVP Expert Associate
marfer's notes for XP - http://www.geocities.com/marfer_mvp/xp_notes.htm
.
(reply address mar...@msn.com is a no bounce output to the nul device)
..
"Andrew Kluchevsky" <akl...@unicom.cv.ua> wrote in message news:efh40xRzBHA.2520@tkmsftngp02...