Re: Stop errors
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Tue, 06 Dec 2005 02:48:51 GMT
Hi Eric,
Thanks for posting in this newsgroup! Also thanks for Cjobes's input.
>From the post, I understand that this is a server crash issue. Regarding
this problem, I would like to recommend that you contact MS CSS directly
for assistance. To troubleshoot such server crash problem, the analysis of
a memory dump is needed. Unfortunately, debugging is beyond what we can do
in the newsgroups. A support call to our product service team is necessary
for the debugging service.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
What is more, I would like to give you the following suggestion to resolve
the issue:
Bad_Pool_Call
Stop 0x000000c2 (0x00000007, 0x00001153, 006F0064, 0x862200348)
Based on my research, the stop error may occur if the AppCompat cache tries
to free a cache entry with a null file name.
It seems that you need to obtain the hotfix 888431 from MS CSS for your
Windows Server 2003. For details regarding this hotfix, please refer to the
following MS KB article::
888431 "Stop 0x000000C2 BAD_POOL_CALLER" error message in Windows Server
2003
http://support.microsoft.com/?id=888431
After applied the hotfix and then test to see if the issue be fixed.
If the issue persists, please also check the following articles to see if
they can resolve your issue:
This stop error may caused by some device drivers. For example, the problem
described in the following Microsoft Knowledge Base article is caused by
Winnov Videum AVI video capture adapter.
310527 Stop Error When You Upgrade from Windows 2000: Bad_Pool_Caller 0xC2
http://support.microsoft.com/?id=310527
309155 "STOP 0x000000c2" Error Message Appears on a Blue Screen After You
http://support.microsoft.com/?id=309155
To trouble shoot this problem efficiently, please refer to the following
Microsoft Knowledge Base article:
265879 How to Debug "Stop 0xC2" or "Stop 0x000000C2" Error Messages
http://support.microsoft.com/?id=265879
In addition, I suggest that you refer to the following Microsoft Knowledge
Base article to use the Driver Verifier to trouble shoot device driver
problems:
244617 How to Use Driver Verifier to Troubleshoot Device Drivers in Windows
2000
http://support.microsoft.com/?id=244617
Hope above information helps! I am happy to be assistance of you-)!
Have a nice day!
Sincerely,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "cjobes" <cjobes@xxxxxxxxxxxxx>
>References: <ugmoggf#FHA.264@xxxxxxxxxxxxxxxxxxxx>
>Subject: Re: Stop errors
>Date: Mon, 5 Dec 2005 21:03:08 -0500
>Lines: 28
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>X-RFC2646: Format=Flowed; Response
>Message-ID: <uOHkxkg#FHA.160@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: ip68-100-24-109.dc.dc.cox.net 68.100.24.109
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:227945
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>This link might help you to determine a bit more:
>http://support.microsoft.com/kb/314492/EN-US/
>it's for XP but quite helpful. On the top of the KB is also a link to 2000
>with some useful information.
>
>Claus
>
>
>"TV-Engineer" <eric-address@xxxxxxxxxxxxxxxx> wrote in message
>news:ugmoggf%23FHA.264@xxxxxxxxxxxxxxxxxxxxxxx
>> Server running SBS 2003. After saving Word files to the to a shared
>> directory on the server, the server blue screens with a stop error,
always
>> different. Problem does not occur when saving Excel files (at least so
>> far). Last error was:
>> Bad_Pool_Call
>> Stop 0x000000c2 (0x00000007, 0x00001153, 006F0064, 0x862200348)
>> Stop errors vary, most with a header (Bad_Pool_Call). System has been
>> re-installed, with all updates except SP1. It was running fine until
this
>> started a couple of weeks ago with a 'crash'. The operating system was
>> re-installed due to problems caused by one client (which has also been
>> re-installed - spyware).
>> Looking for all help to get this thing runnung again. My client is an
>> accountant and tax season is coming.
>> TIA,
>> Eric
>>
>
>
>
.
- Follow-Ups:
- Re: Stop errors
- From: "Jenny wu [MSFT]"
- Re: Stop errors
- References:
- Stop errors
- From: TV-Engineer
- Re: Stop errors
- From: cjobes
- Stop errors
- Prev by Date: RE: Fax on companyweb
- Next by Date: Re: SBS2003 - Cannot restore GPO following Article 888943
- Previous by thread: Re: Stop errors
- Next by thread: Re: Stop errors
- Index(es):
Relevant Pages
|
