Error: 17053, Severity: 16, State: 1. Exception 0xAE

I have recieved billions of:
2006-09-22 02:07:06.76 spid11s Error: 17053, Severity: 16, State: 1.
2006-09-22 02:07:06.76 spid11s High priority system task thread:
Operating system error Exception 0xAE encountered.
in my log and it has grown enormous. What is causing this, how can I stop it
and how can i cut my log file out so i can keep it running until we find a
solution?
Bryan
What version and service pack of SQL?
Look at sp_cycle_errorlog to restart the log...
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Bryan Aldrich" <BryanAldrich@.discussions.microsoft.com> wrote in message
news:45F47E8B-4060-418F-8385-1081C52C8D18@.microsoft.com...
>I have recieved billions of:
> 2006-09-22 02:07:06.76 spid11s Error: 17053, Severity: 16, State: 1.
> 2006-09-22 02:07:06.76 spid11s High priority system task thread:
> Operating system error Exception 0xAE encountered.
> in my log and it has grown enormous. What is causing this, how can I stop
> it
> and how can i cut my log file out so i can keep it running until we find a
> solution?
> Bryan
|||It was on SP1 Enterprise Edition.
We called PSS and they recommended putting on hotfix 2153. It has not come
back since. We are still monitoring. Thanks for the tip about rotating the
log.
Bryan
"Kevin3NF" wrote:

> What version and service pack of SQL?
> Look at sp_cycle_errorlog to restart the log...
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Bryan Aldrich" <BryanAldrich@.discussions.microsoft.com> wrote in message
> news:45F47E8B-4060-418F-8385-1081C52C8D18@.microsoft.com...
>
>
|||Hotfix rollup .2187 is better and more stable. Surprised they didn't take
you there instead.
I assume you meant SQL 2000 sp4, not sp1
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Bryan Aldrich" <BryanAldrich@.discussions.microsoft.com> wrote in message
news:5584B7BB-4211-4B2E-96AD-D5323CA959C1@.microsoft.com...[vbcol=seagreen]
> It was on SP1 Enterprise Edition.
> We called PSS and they recommended putting on hotfix 2153. It has not come
> back since. We are still monitoring. Thanks for the tip about rotating the
> log.
> Bryan
> "Kevin3NF" wrote:
|||This is Sql 2005, not 2000. We still have the option to goto 2187 if we need
to. We don't have much information on it though.
Is where somewhere where we can get a list of fixes in 2187?
Bryan
"Kevin3NF" wrote:

> Hotfix rollup .2187 is better and more stable. Surprised they didn't take
> you there instead.
> I assume you meant SQL 2000 sp4, not sp1
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Bryan Aldrich" <BryanAldrich@.discussions.microsoft.com> wrote in message
> news:5584B7BB-4211-4B2E-96AD-D5323CA959C1@.microsoft.com...
>
>
|||The only .2187 I know of is a post sp4 rollup.
But, I am completely ignorant in terms of 2005
Email whoever helped you in PSS. THey should answer that qestion without
any haslle, even if the case is already closed.
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Bryan Aldrich" <BryanAldrich@.discussions.microsoft.com> wrote in message
news:33727070-BAC8-49C3-8222-5AFF0B9738E5@.microsoft.com...[vbcol=seagreen]
> This is Sql 2005, not 2000. We still have the option to goto 2187 if we
> need
> to. We don't have much information on it though.
> Is where somewhere where we can get a list of fixes in 2187?
> Bryan
> "Kevin3NF" wrote: