Crash with Error Code 000000ab

[Guest TonyCC]

System Spec:

OS: Win Server 2003 R2 Std Edition w/ SP2 fully updated.

 

My Terminal Server Restarted last night & I got the following message in the

Event Log.

 

Event Type: Error

Event Source: System Error

Event Category: (102)

Event ID: 1003

Date: 1/31/2008

Time: 10:34:54 AM

User: N/A

Computer: TERMServer

Description:

Error code 000000ab, parameter1 00000002, parameter2 00000428, parameter3

00000000, parameter4 00000004.

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 53 79 73 74 65 6d 20 45 System E

0008: 72 72 6f 72 20 20 45 72 rror Er

0010: 72 6f 72 20 63 6f 64 65 ror code

0018: 20 30 30 30 30 30 30 61 000000a

0020: 62 20 20 50 61 72 61 6d b Param

0028: 65 74 65 72 73 20 30 30 eters 00

0030: 30 30 30 30 30 32 2c 20 000002,

0038: 30 30 30 30 30 34 32 38 00000428

0040: 2c 20 30 30 30 30 30 30 , 000000

0048: 30 30 2c 20 30 30 30 30 00, 0000

0050: 30 30 30 34 0004

 

And also this:

 

Event Type: Warning

Event Source: USER32

Event Category: None

Event ID: 1076

Date: 1/31/2008

Time: 10:34:49 AM

User: Domain\administrator

Computer: TERMServer

Description:

The reason supplied by user COMCON\Administrator for the last unexpected

shutdown of this computer is: System Failure: Stop error

Reason Code: 0x805000f

Bug ID:

Bugcheck String: 0x000000ab (0x00000002, 0x00000428, 0x00000000, 0x00000004)

Comment: 0x000000ab (0x00000002, 0x00000428, 0x00000000, 0x00000004)

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 0f 00 05 08 ....

 

I've seen the Microsoft Info:

 

You may receive a “Stop 0x000000ab” error message when you log off a

Terminal Services session on a Windows Server 2003 SP1-based Terminal Server

 

http://support.microsoft.com/kb/901150/en-us

 

And

 

Error message when you log off from a Terminal Services session on a Windows

Server 2003 Service Pack 1-based terminal server: "Stop 0x000000AB

SESSION_HAS_VALID_POOL_ON_EXIT"

 

http://support.microsoft.com/?kbid=910362

 

These only seem to apply to 2003 with SP1 & I have R2 with SP2. I did check

the file versions of my gdi32.dll, updspapi.dll, & Win32k.sys & they are

newer then the hotfix file. The crash did, however, seem to happen at the

same time a user was logging off a Terminal Services session.

 

I saw another post mentioning disabling non-english language support, but I

am not using any of those.

 

Any ideas?

[Guest Vera Noest [MVP]]

Re: Crash with Error Code 000000ab

 

Here's the latest hotfix for STOP 0xAB. It includes all previous

(11 !) hotfixes for this error.

 

946068 - Stop error message on a terminal server that is running

Windows Server 2003 Service Pack 1 or Windows Server 2003 Service

Pack 2: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"

http://support.microsoft.com/?kbid=946068

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?VG9ueUND?= <TonyCC@discussions.microsoft.com> wrote on

31 jan 2008 in microsoft.public.windows.terminal_services:

> System Spec:

> OS: Win Server 2003 R2 Std Edition w/ SP2 fully updated.

>

> My Terminal Server Restarted last night & I got the following

> message in the Event Log.

>

> Event Type: Error

> Event Source: System Error

> Event Category: (102)

> Event ID: 1003

> Date: 1/31/2008

> Time: 10:34:54 AM

> User: N/A

> Computer: TERMServer

> Description:

> Error code 000000ab, parameter1 00000002, parameter2 00000428,

> parameter3 00000000, parameter4 00000004.

>

> For more information, see Help and Support Center at

> http://go.microsoft.com/fwlink/events.asp.

> Data:

> 0000: 53 79 73 74 65 6d 20 45 System E

> 0008: 72 72 6f 72 20 20 45 72 rror Er

> 0010: 72 6f 72 20 63 6f 64 65 ror code

> 0018: 20 30 30 30 30 30 30 61 000000a

> 0020: 62 20 20 50 61 72 61 6d b Param

> 0028: 65 74 65 72 73 20 30 30 eters 00

> 0030: 30 30 30 30 30 32 2c 20 000002,

> 0038: 30 30 30 30 30 34 32 38 00000428

> 0040: 2c 20 30 30 30 30 30 30 , 000000

> 0048: 30 30 2c 20 30 30 30 30 00, 0000

> 0050: 30 30 30 34 0004

>

> And also this:

>

> Event Type: Warning

> Event Source: USER32

> Event Category: None

> Event ID: 1076

> Date: 1/31/2008

> Time: 10:34:49 AM

> User: Domain\administrator

> Computer: TERMServer

> Description:

> The reason supplied by user COMCON\Administrator for the last

> unexpected shutdown of this computer is: System Failure: Stop

> error

> Reason Code: 0x805000f

> Bug ID:

> Bugcheck String: 0x000000ab (0x00000002, 0x00000428,

> 0x00000000, 0x00000004) Comment: 0x000000ab (0x00000002,

> 0x00000428, 0x00000000, 0x00000004)

>

> For more information, see Help and Support Center at

> http://go.microsoft.com/fwlink/events.asp.

> Data:

> 0000: 0f 00 05 08 ....

>

> I've seen the Microsoft Info:

>

> You may receive a “Stop 0x000000ab” error message when you

> log off a

> Terminal Services session on a Windows Server 2003 SP1-based

> Terminal Server

>

> http://support.microsoft.com/kb/901150/en-us

>

> And

>

> Error message when you log off from a Terminal Services session

> on a Windows Server 2003 Service Pack 1-based terminal server:

> "Stop 0x000000AB SESSION_HAS_VALID_POOL_ON_EXIT"

>

> http://support.microsoft.com/?kbid=910362

>

> These only seem to apply to 2003 with SP1 & I have R2 with SP2.

> I did check the file versions of my gdi32.dll, updspapi.dll, &

> Win32k.sys & they are newer then the hotfix file. The crash

> did, however, seem to happen at the same time a user was logging

> off a Terminal Services session.

>

> I saw another post mentioning disabling non-english language

> support, but I am not using any of those.

>

> Any ideas?

[Guest TonyCC]

Re: Crash with Error Code 000000ab

 

Thanks Vera. The hotfix does have a newer Win32k.sys. Hopefully this will

fix the issue.

 

"Vera Noest [MVP]" wrote:

> Here's the latest hotfix for STOP 0xAB. It includes all previous

> (11 !) hotfixes for this error.

>

> 946068 - Stop error message on a terminal server that is running

> Windows Server 2003 Service Pack 1 or Windows Server 2003 Service

> Pack 2: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"

> http://support.microsoft.com/?kbid=946068

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?VG9ueUND?= <TonyCC@discussions.microsoft.com> wrote on

> 31 jan 2008 in microsoft.public.windows.terminal_services:

>

> > System Spec:

> > OS: Win Server 2003 R2 Std Edition w/ SP2 fully updated.

> >

> > My Terminal Server Restarted last night & I got the following

> > message in the Event Log.

> >

> > Event Type: Error

> > Event Source: System Error

> > Event Category: (102)

> > Event ID: 1003

> > Date: 1/31/2008

> > Time: 10:34:54 AM

> > User: N/A

> > Computer: TERMServer

> > Description:

> > Error code 000000ab, parameter1 00000002, parameter2 00000428,

> > parameter3 00000000, parameter4 00000004.

> >

> > For more information, see Help and Support Center at

> > http://go.microsoft.com/fwlink/events.asp.

> > Data:

> > 0000: 53 79 73 74 65 6d 20 45 System E

> > 0008: 72 72 6f 72 20 20 45 72 rror Er

> > 0010: 72 6f 72 20 63 6f 64 65 ror code

> > 0018: 20 30 30 30 30 30 30 61 000000a

> > 0020: 62 20 20 50 61 72 61 6d b Param

> > 0028: 65 74 65 72 73 20 30 30 eters 00

> > 0030: 30 30 30 30 30 32 2c 20 000002,

> > 0038: 30 30 30 30 30 34 32 38 00000428

> > 0040: 2c 20 30 30 30 30 30 30 , 000000

> > 0048: 30 30 2c 20 30 30 30 30 00, 0000

> > 0050: 30 30 30 34 0004

> >

> > And also this:

> >

> > Event Type: Warning

> > Event Source: USER32

> > Event Category: None

> > Event ID: 1076

> > Date: 1/31/2008

> > Time: 10:34:49 AM

> > User: Domain\administrator

> > Computer: TERMServer

> > Description:

> > The reason supplied by user COMCON\Administrator for the last

> > unexpected shutdown of this computer is: System Failure: Stop

> > error

> > Reason Code: 0x805000f

> > Bug ID:

> > Bugcheck String: 0x000000ab (0x00000002, 0x00000428,

> > 0x00000000, 0x00000004) Comment: 0x000000ab (0x00000002,

> > 0x00000428, 0x00000000, 0x00000004)

> >

> > For more information, see Help and Support Center at

> > http://go.microsoft.com/fwlink/events.asp.

> > Data:

> > 0000: 0f 00 05 08 ....

> >

> > I've seen the Microsoft Info:

> >

> > You may receive a “Stop 0x000000ab� error message when you

> > log off a

> > Terminal Services session on a Windows Server 2003 SP1-based

> > Terminal Server

> >

> > http://support.microsoft.com/kb/901150/en-us

> >

> > And

> >

> > Error message when you log off from a Terminal Services session

> > on a Windows Server 2003 Service Pack 1-based terminal server:

> > "Stop 0x000000AB SESSION_HAS_VALID_POOL_ON_EXIT"

> >

> > http://support.microsoft.com/?kbid=910362

> >

> > These only seem to apply to 2003 with SP1 & I have R2 with SP2.

> > I did check the file versions of my gdi32.dll, updspapi.dll, &

> > Win32k.sys & they are newer then the hotfix file. The crash

> > did, however, seem to happen at the same time a user was logging

> > off a Terminal Services session.

> >

> > I saw another post mentioning disabling non-english language

> > support, but I am not using any of those.

> >

> > Any ideas?

>