I too have experience the same problem. I would boot up my machine and
it would spontaneously crash core dump to the blue screen of death,
then reboot several times a day randomly. I finally realized that if I
turned off my wireless radio (disabling my wireless connection) it
would be stable the entire day.

After several months I found the following solution, I'm guessing you
have wireless on your machine as well.

Microsoft XP SP2 installs a Data Execution Prevention (DEP) function
that messes up the NIC adapter driver. You can edit the boot.ini to
DISABLE DEP by setting "/NoExecute=AlwaysOff" (mine originally had
"/NoExecute=Optin").

Goto My Computer, right-click and select Properties>Advanced
Tab>Settings (Startup and Recovery)>Edit
This will bring you to the boot.ini file. You might want to make a
backup copy and place it on your desktop. Where you see "/NoExecute=",
make sure it is changed to "AlwaysOff"

Hope this helps!

David Candy wrote:
> Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.
>
> If you can't start after enabling verifier
> choose Last Known Good Configuration at the Failed Boot menu (which will
> start without verifier).
>
>
> You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.
>
> Then
>
> If you have the XP SP2 Security Update CD (else see
> http://www.microsoft.com/whdc/*devto...ymbolpkg.m*spx
> )
>
>
> Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
>
> Download
> http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
>
> Load the crash dump file into windbg
> and read what it says. You may need to tell it where the symbols are. Read it.
> Type
> !Analyze -v
> into Windbg's command line.
> (this will hopefully tell you the faulty component)
>
> If the above is too technical then email the crash dump files to davidc @mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.
>
> You can look up specific details here
> http://msdn.microsoft.com/library/de...0bd501.xml.asp
>
> If it indicates faulty memory might be the cause you can get a memory tester
> here
> http://oca.microsoft.com/en/wi*ndiag.asp
>
>
> If it mentions a core windows system file, meaning it a MS fix is required,
> upload a minidump to
>
> http://oca.microsoft.com
>
> Also try typing the main error code in Help while online (ie,
> Stop 0x50
> and also try in the 8 digit form
> stop 0x00000050)
> and if there are too many hits use a filename if available. Generally memory
> addresses are different for each computer (as each computer has a different
> mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.p...tus.h?rev=1.2).
>
>
>
>
> --
> --------------------------------------------------------------------------------------------------
> http://webdiary.smh.com.au/archives/...nt/001075.html
> =================================================
> "Pierce Lynch" <Pierce Lynch@discussions.microsoft.com> wrote in message news:0D4DD74C-96D2-48B3-9183-6222DB6E002B@microsoft.com...
> > Hi,
> >
> > Currently have this description related to an error message listed within my
> > even viewer on a winxp PRO machine:
> > "The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2
> > (0x00000007, 0x00000cd4, 0x024c0010, 0x84e006f0). A dump was saved in:
> > C:\WINDOWS\Minidump\Mini092305-02.dmp."
> >
> > THe problem is, as mentioned - i am getting very random restarts, usually
> > either we a log off command is sent or a restart command, but sometimeson
> > the off occassion randonly for no reason at all. Each time this is the
> > reported error.
> >
> > So, can anyone shed any light on the meaning of this and the advice to fix.
> > I have attempted to view the contents of the DMP file in notepad only to get
> > the usual character mess. So am none the wiser at the moment
> >
> > Any help will be greatly appreciated.
> >
> > Thanks!
> >
> > Pierce Lynch

Hi Guys,

Not managed to fix it as it stands, and I dont have wireless active on this
machine (but thanks for the idea!) so thats that one out.

Have got a BSOD recently thought which says BAD_POOL_CALLER and halts my
machine. That mean anything? Sound like a RAM problem? Time to replace RAM
modules?

THanks for your help so far guys, been great

P


"5tifler" wrote:

> I too have experience the same problem. I would boot up my machine and
> it would spontaneously crash core dump to the blue screen of death,
> then reboot several times a day randomly. I finally realized that if I
> turned off my wireless radio (disabling my wireless connection) it
> would be stable the entire day.
>
> After several months I found the following solution, I'm guessing you
> have wireless on your machine as well.
>
> Microsoft XP SP2 installs a Data Execution Prevention (DEP) function
> that messes up the NIC adapter driver. You can edit the boot.ini to
> DISABLE DEP by setting "/NoExecute=AlwaysOff" (mine originally had
> "/NoExecute=Optin").
>
> Goto My Computer, right-click and select Properties>Advanced
> Tab>Settings (Startup and Recovery)>Edit
> This will bring you to the boot.ini file. You might want to make a
> backup copy and place it on your desktop. Where you see "/NoExecute=",
> make sure it is changed to "AlwaysOff"
>
> Hope this helps!
>
> David Candy wrote:
> > Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.
> >
> > If you can't start after enabling verifier
> > choose Last Known Good Configuration at the Failed Boot menu (which will
> > start without verifier).
> >
> >
> > You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.
> >
> > Then
> >
> > If you have the XP SP2 Security Update CD (else see
> > http://www.microsoft.com/whdc/Â*devt...mbolpkg.mÂ*spx
> > )
> >
> >
> > Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
> >
> > Download
> > http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
> >
> > Load the crash dump file into windbg
> > and read what it says. You may need to tell it where the symbols are. Read it.
> > Type
> > !Analyze -v
> > into Windbg's command line.
> > (this will hopefully tell you the faulty component)
> >
> > If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.
> >
> > You can look up specific details here
> > http://msdn.microsoft.com/library/de...0bd501.xml.asp
> >
> > If it indicates faulty memory might be the cause you can get a memory tester
> > here
> > http://oca.microsoft.com/en/wiÂ*ndiag.asp
> >
> >
> > If it mentions a core windows system file, meaning it a MS fix is required,
> > upload a minidump to
> >
> > http://oca.microsoft.com
> >
> > Also try typing the main error code in Help while online (ie,
> > Stop 0x50
> > and also try in the 8 digit form
> > stop 0x00000050)
> > and if there are too many hits use a filename if available. Generally memory
> > addresses are different for each computer (as each computer has a different
> > mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.p...tus.h?rev=1.2).
> >
> >
> >
> >
> > --
> > --------------------------------------------------------------------------------------------------
> > http://webdiary.smh.com.au/archives/...nt/001075.html
> > =================================================
> > "Pierce Lynch" <Pierce Lynch@discussions.microsoft.com> wrote in message news:0D4DD74C-96D2-48B3-9183-6222DB6E002B@microsoft.com...
> > > Hi,
> > >
> > > Currently have this description related to an error message listed within my
> > > even viewer on a winxp PRO machine:
> > > "The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2
> > > (0x00000007, 0x00000cd4, 0x024c0010, 0x84e006f0). A dump was saved in:
> > > C:\WINDOWS\Minidump\Mini092305-02.dmp."
> > >
> > > THe problem is, as mentioned - i am getting very random restarts, usually
> > > either we a log off command is sent or a restart command, but sometimes on
> > > the off occassion randonly for no reason at all. Each time this is the
> > > reported error.
> > >
> > > So, can anyone shed any light on the meaning of this and the advice to fix.
> > > I have attempted to view the contents of the DMP file in notepad only to get
> > > the usual character mess. So am none the wiser at the moment
> > >
> > > Any help will be greatly appreciated.
> > >
> > > Thanks!
> > >
> > > Pierce Lynch
>
>

Information on STOP: 0xC2 errors (BAD_POOL_CALLER)
http://www.aumha.org/win5/kbestop.php#0xc2

--
Ted Zieglar
"You can do it if you try."

"Pierce Lynch" <PierceLynch@discussions.microsoft.com> wrote in message
news:F6BC8308-A95F-43A7-B5D4-3BAB7AF82291@microsoft.com...
> Hi Guys,
>
> Not managed to fix it as it stands, and I dont have wireless active on
this
> machine (but thanks for the idea!) so thats that one out.
>
> Have got a BSOD recently thought which says BAD_POOL_CALLER and halts my
> machine. That mean anything? Sound like a RAM problem? Time to replace RAM
> modules?
>
> THanks for your help so far guys, been great
>
> P
>
>
> "5tifler" wrote:
>
> > I too have experience the same problem. I would boot up my machine and
> > it would spontaneously crash core dump to the blue screen of death,
> > then reboot several times a day randomly. I finally realized that if I
> > turned off my wireless radio (disabling my wireless connection) it
> > would be stable the entire day.
> >
> > After several months I found the following solution, I'm guessing you
> > have wireless on your machine as well.
> >
> > Microsoft XP SP2 installs a Data Execution Prevention (DEP) function
> > that messes up the NIC adapter driver. You can edit the boot.ini to
> > DISABLE DEP by setting "/NoExecute=AlwaysOff" (mine originally had
> > "/NoExecute=Optin").
> >
> > Goto My Computer, right-click and select Properties>Advanced
> > Tab>Settings (Startup and Recovery)>Edit
> > This will bring you to the boot.ini file. You might want to make a
> > backup copy and place it on your desktop. Where you see "/NoExecute=",
> > make sure it is changed to "AlwaysOff"
> >
> > Hope this helps!
> >
> > David Candy wrote:
> > > Type verifier in Start Run, follow the wizard but choose All Drivers.
This will slow down your computer and cause more blue screen crashes but
will pinpoint what is causing the crash (if the original error message
didn't). Once you fix it you rerun verifier and turn it off.
> > >
> > > If you can't start after enabling verifier
> > > choose Last Known Good Configuration at the Failed Boot menu (which
will
> > > start without verifier).
> > >
> > >
> > > You will be creating a crash dump file in c:\windows\minidump every
blue screen. Make sure you are set to record minidumps (Small Memory
Dumps) - type it in Help to see how.
> > >
> > > Then
> > >
> > > If you have the XP SP2 Security Update CD (else see
> > > http://www.microsoft.com/whdc/Â*devt...mbolpkg.mÂ*spx
> > > )
> > >
> > >
> > > Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
> > >
> > > Download
> > > http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
> > >
> > > Load the crash dump file into windbg
> > > and read what it says. You may need to tell it where the symbols are.
Read it.
> > > Type
> > > !Analyze -v
> > > into Windbg's command line.
> > > (this will hopefully tell you the faulty component)
> > >
> > > If the above is too technical then email the crash dump files to
davidc @ mvps.org. Don't send me lots of them. Just the one from your last
crash after you turn verifier on. And only one per mail.
> > >
> > > You can look up specific details here
> > >
http://msdn.microsoft.com/library/de...0bd501.xml.asp
> > >
> > > If it indicates faulty memory might be the cause you can get a memory
tester
> > > here
> > > http://oca.microsoft.com/en/wiÂ*ndiag.asp
> > >
> > >
> > > If it mentions a core windows system file, meaning it a MS fix is
required,
> > > upload a minidump to
> > >
> > > http://oca.microsoft.com
> > >
> > > Also try typing the main error code in Help while online (ie,
> > > Stop 0x50
> > > and also try in the 8 digit form
> > > stop 0x00000050)
> > > and if there are too many hits use a filename if available. Generally
memory
> > > addresses are different for each computer (as each computer has a
different
> > > mix of drivers) so parameters that are memory addresses aren't that
useful for searching, but NTStatus codes are (plus you can look them up here
http://cvs.sourceforge.net/viewcvs.p...tus.h?rev=1.2).
> > >
> > >
> > >
> > >
> > > --
> >
> --------------------------------------------------------------------------
------------------------
> > > http://webdiary.smh.com.au/archives/...nt/001075.html
> > > =================================================
> > > "Pierce Lynch" <Pierce Lynch@discussions.microsoft.com> wrote in
message news:0D4DD74C-96D2-48B3-9183-6222DB6E002B@microsoft.com...
> > > > Hi,
> > > >
> > > > Currently have this description related to an error message listed
within my
> > > > even viewer on a winxp PRO machine:
> > > > "The computer has rebooted from a bugcheck. The bugcheck was:
0x000000c2
> > > > (0x00000007, 0x00000cd4, 0x024c0010, 0x84e006f0). A dump was saved
in:
> > > > C:\WINDOWS\Minidump\Mini092305-02.dmp."
> > > >
> > > > THe problem is, as mentioned - i am getting very random restarts,
usually
> > > > either we a log off command is sent or a restart command, but
sometimes on
> > > > the off occassion randonly for no reason at all. Each time this is
the
> > > > reported error.
> > > >
> > > > So, can anyone shed any light on the meaning of this and the advice
to fix.
> > > > I have attempted to view the contents of the DMP file in notepad
only to get
> > > > the usual character mess. So am none the wiser at the moment
> > > >
> > > > Any help will be greatly appreciated.
> > > >
> > > > Thanks!
> > > >
> > > > Pierce Lynch
> >
> >

You were told how to find out. Do the procedure or live with it.

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/...nt/001075.html
=================================================
"Pierce Lynch" <PierceLynch@discussions.microsoft.com> wrote in message news:F6BC8308-A95F-43A7-B5D4-3BAB7AF82291@microsoft.com...
> Hi Guys,
>
> Not managed to fix it as it stands, and I dont have wireless active on this
> machine (but thanks for the idea!) so thats that one out.
>
> Have got a BSOD recently thought which says BAD_POOL_CALLER and halts my
> machine. That mean anything? Sound like a RAM problem? Time to replace RAM
> modules?
>
> THanks for your help so far guys, been great
>
> P
>
>
> "5tifler" wrote:
>
>> I too have experience the same problem. I would boot up my machine and
>> it would spontaneously crash core dump to the blue screen of death,
>> then reboot several times a day randomly. I finally realized that if I
>> turned off my wireless radio (disabling my wireless connection) it
>> would be stable the entire day.
>>
>> After several months I found the following solution, I'm guessing you
>> have wireless on your machine as well.
>>
>> Microsoft XP SP2 installs a Data Execution Prevention (DEP) function
>> that messes up the NIC adapter driver. You can edit the boot.ini to
>> DISABLE DEP by setting "/NoExecute=AlwaysOff" (mine originally had
>> "/NoExecute=Optin").
>>
>> Goto My Computer, right-click and select Properties>Advanced
>> Tab>Settings (Startup and Recovery)>Edit
>> This will bring you to the boot.ini file. You might want to make a
>> backup copy and place it on your desktop. Where you see "/NoExecute=",
>> make sure it is changed to "AlwaysOff"
>>
>> Hope this helps!
>>
>> David Candy wrote:
>> > Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.
>> >
>> > If you can't start after enabling verifier
>> > choose Last Known Good Configuration at the Failed Boot menu (which will
>> > start without verifier).
>> >
>> >
>> > You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.
>> >
>> > Then
>> >
>> > If you have the XP SP2 Security Update CD (else see
>> > http://www.microsoft.com/whdc/Â*devt...mbolpkg.mÂ*spx
>> > )
>> >
>> >
>> > Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
>> >
>> > Download
>> > http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
>> >
>> > Load the crash dump file into windbg
>> > and read what it says. You may need to tell it where the symbols are. Read it.
>> > Type
>> > !Analyze -v
>> > into Windbg's command line.
>> > (this will hopefully tell you the faulty component)
>> >
>> > If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.
>> >
>> > You can look up specific details here
>> > http://msdn.microsoft.com/library/de...0bd501.xml.asp
>> >
>> > If it indicates faulty memory might be the cause you can get a memory tester
>> > here
>> > http://oca.microsoft.com/en/wiÂ*ndiag.asp
>> >
>> >
>> > If it mentions a core windows system file, meaning it a MS fix is required,
>> > upload a minidump to
>> >
>> > http://oca.microsoft.com
>> >
>> > Also try typing the main error code in Help while online (ie,
>> > Stop 0x50
>> > and also try in the 8 digit form
>> > stop 0x00000050)
>> > and if there are too many hits use a filename if available. Generally memory
>> > addresses are different for each computer (as each computer has a different
>> > mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.p...tus.h?rev=1.2).
>> >
>> >
>> >
>> >
>> > --
>> > --------------------------------------------------------------------------------------------------
>> > http://webdiary.smh.com.au/archives/...nt/001075.html
>> > =================================================
>> > "Pierce Lynch" <Pierce Lynch@discussions.microsoft.com> wrote in message news:0D4DD74C-96D2-48B3-9183-6222DB6E002B@microsoft.com...
>> > > Hi,
>> > >
>> > > Currently have this description related to an error message listed within my
>> > > even viewer on a winxp PRO machine:
>> > > "The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2
>> > > (0x00000007, 0x00000cd4, 0x024c0010, 0x84e006f0). A dump was saved in:
>> > > C:\WINDOWS\Minidump\Mini092305-02.dmp."
>> > >
>> > > THe problem is, as mentioned - i am getting very random restarts, usually
>> > > either we a log off command is sent or a restart command, but sometimes on
>> > > the off occassion randonly for no reason at all. Each time this is the
>> > > reported error.
>> > >
>> > > So, can anyone shed any light on the meaning of this and the advice to fix.
>> > > I have attempted to view the contents of the DMP file in notepad only to get
>> > > the usual character mess. So am none the wiser at the moment
>> > >
>> > > Any help will be greatly appreciated.
>> > >
>> > > Thanks!
>> > >
>> > > Pierce Lynch
>>
>>