Server 2003 Blue Screen at Logon

[Guest Rick Clapp]

I have a Dell 700 Server running Windows 2003 SP1 and acting as a domain

control on the other side of the world. The server works fine unless you

attempt to logon remotely (RPD) or locally. If you do it crashes and creates

a memory.dmp file. When you attempt to logon in again you get the crash

message.

 

System Failure: Stop Error

0x00000008 (0xc0000005, 0x809413c4, 0xf29098dc, 0x00000000)

 

No module or process is shown. The system doesn't have symbols loaded so

the crash analyser I have doesn't help.

 

The right thing to do is contact MS to get assistance. My manager won't let

me use one of our MS incidents because then she has to explain to her

management why she did it. (Big Company BS) :-(

 

So I've spend many hours trying to solve this remotely without help.

 

The server is up and running just fine. I can look at the event logs. I

can RCMD into the system so I have command line access. I also can remotely

mount drives and the registry. I can also access the Dell Server Assistant

and don't see any hardware errors. No drive problems or memory issues are

being reported.

 

So far nothing I've looked at has given me a clue.

 

As to what has been done to the box....

 

I'm not positive since SMS rolls out a number of patches and software

changes. I know that it has the most current version of Dell's firmware and

drivers. those were installed weeks ago and the system worked afterwards.

This same software has been installed on 7 other servers and haven't caused a

problem.

 

I did contact Dell and they have no known issues with the firmware or driver

updates.

 

Looking at the MS Patch log it looks like it's been missed for a number of

patches. It may have had some of the new patches and missed some of the

older ones. Maybe one needed an old patch and had issues because it was

missing. Just a thought of course.

 

Does it have a good backup? Maybe but since I can't log in I can't check.

Many of these servers have issues with the backup software because of a

change made by another admin. He's been fixing them but he's has a lot of

work to do since we have so many servers around the world.

 

So do you have any suggestions on how I can determine the issue and get this

rsolved over the network?

 

Any suggestions would be great.

 

Thanks

Rick Clapp (former SNA MVP)

[Guest Dave Patrick]

Re: Server 2003 Blue Screen at Logon

 

Maybe this one helps.

 

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

 

 

 

--

 

Regards,

 

Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect

 

"Rick Clapp" wrote:

>I have a Dell 700 Server running Windows 2003 SP1 and acting as a domain

> control on the other side of the world. The server works fine unless you

> attempt to logon remotely (RPD) or locally. If you do it crashes and

> creates

> a memory.dmp file. When you attempt to logon in again you get the crash

> message.

>

> System Failure: Stop Error

> 0x00000008 (0xc0000005, 0x809413c4, 0xf29098dc, 0x00000000)

>

> No module or process is shown. The system doesn't have symbols loaded so

> the crash analyser I have doesn't help.

>

> The right thing to do is contact MS to get assistance. My manager won't

> let

> me use one of our MS incidents because then she has to explain to her

> management why she did it. (Big Company BS) :-(

>

> So I've spend many hours trying to solve this remotely without help.

>

> The server is up and running just fine. I can look at the event logs. I

> can RCMD into the system so I have command line access. I also can

> remotely

> mount drives and the registry. I can also access the Dell Server

> Assistant

> and don't see any hardware errors. No drive problems or memory issues are

> being reported.

>

> So far nothing I've looked at has given me a clue.

>

> As to what has been done to the box....

>

> I'm not positive since SMS rolls out a number of patches and software

> changes. I know that it has the most current version of Dell's firmware

> and

> drivers. those were installed weeks ago and the system worked afterwards.

> This same software has been installed on 7 other servers and haven't

> caused a

> problem.

>

> I did contact Dell and they have no known issues with the firmware or

> driver

> updates.

>

> Looking at the MS Patch log it looks like it's been missed for a number of

> patches. It may have had some of the new patches and missed some of the

> older ones. Maybe one needed an old patch and had issues because it was

> missing. Just a thought of course.

>

> Does it have a good backup? Maybe but since I can't log in I can't check.

> Many of these servers have issues with the backup software because of a

> change made by another admin. He's been fixing them but he's has a lot of

> work to do since we have so many servers around the world.

>

> So do you have any suggestions on how I can determine the issue and get

> this

> rsolved over the network?

>

> Any suggestions would be great.

>

> Thanks

> Rick Clapp (former SNA MVP)

>

>

[Guest Thee Chicago Wolf]

Re: Server 2003 Blue Screen at Logon

 

>I have a Dell 700 Server running Windows 2003 SP1 and acting as a domain

>control on the other side of the world. The server works fine unless you

>attempt to logon remotely (RPD) or locally. If you do it crashes and creates

>a memory.dmp file. When you attempt to logon in again you get the crash

>message.

>

>System Failure: Stop Error

>0x00000008 (0xc0000005, 0x809413c4, 0xf29098dc, 0x00000000)

>

>No module or process is shown. The system doesn't have symbols loaded so

>the crash analyser I have doesn't help.

>

>The right thing to do is contact MS to get assistance. My manager won't let

>me use one of our MS incidents because then she has to explain to her

>management why she did it. (Big Company BS) :-(

>

>So I've spend many hours trying to solve this remotely without help.

>

>The server is up and running just fine. I can look at the event logs. I

>can RCMD into the system so I have command line access. I also can remotely

>mount drives and the registry. I can also access the Dell Server Assistant

>and don't see any hardware errors. No drive problems or memory issues are

>being reported.

>

>So far nothing I've looked at has given me a clue.

>

>As to what has been done to the box....

>

>I'm not positive since SMS rolls out a number of patches and software

>changes. I know that it has the most current version of Dell's firmware and

>drivers. those were installed weeks ago and the system worked afterwards.

>This same software has been installed on 7 other servers and haven't caused a

>problem.

>

>I did contact Dell and they have no known issues with the firmware or driver

>updates.

>

>Looking at the MS Patch log it looks like it's been missed for a number of

>patches. It may have had some of the new patches and missed some of the

>older ones. Maybe one needed an old patch and had issues because it was

>missing. Just a thought of course.

>

>Does it have a good backup? Maybe but since I can't log in I can't check.

>Many of these servers have issues with the backup software because of a

>change made by another admin. He's been fixing them but he's has a lot of

>work to do since we have so many servers around the world.

>

>So do you have any suggestions on how I can determine the issue and get this

>rsolved over the network?

>

>Any suggestions would be great.

>

>Thanks

>Rick Clapp (former SNA MVP)

 

You should really be on SP2 by now. Also, are you using the RDP 6

client?

 

- Thee Chicago Wolf

[Guest Rick Clapp]

Re: Server 2003 Blue Screen at Logon

 

SP2 is currently being tested with our main application. It should get

rolled out in the next few months.

 

I'm using RDP6 on my desktop.

 

Rick

 

"Thee Chicago Wolf" wrote:

> >I have a Dell 700 Server running Windows 2003 SP1 and acting as a domain

> >control on the other side of the world. The server works fine unless you

> >attempt to logon remotely (RPD) or locally. If you do it crashes and creates

> >a memory.dmp file. When you attempt to logon in again you get the crash

> >message.

> >

> >System Failure: Stop Error

> >0x00000008 (0xc0000005, 0x809413c4, 0xf29098dc, 0x00000000)

> >

> >No module or process is shown. The system doesn't have symbols loaded so

> >the crash analyser I have doesn't help.

> >

> >The right thing to do is contact MS to get assistance. My manager won't let

> >me use one of our MS incidents because then she has to explain to her

> >management why she did it. (Big Company BS) :-(

> >

> >So I've spend many hours trying to solve this remotely without help.

> >

> >The server is up and running just fine. I can look at the event logs. I

> >can RCMD into the system so I have command line access. I also can remotely

> >mount drives and the registry. I can also access the Dell Server Assistant

> >and don't see any hardware errors. No drive problems or memory issues are

> >being reported.

> >

> >So far nothing I've looked at has given me a clue.

> >

> >As to what has been done to the box....

> >

> >I'm not positive since SMS rolls out a number of patches and software

> >changes. I know that it has the most current version of Dell's firmware and

> >drivers. those were installed weeks ago and the system worked afterwards.

> >This same software has been installed on 7 other servers and haven't caused a

> >problem.

> >

> >I did contact Dell and they have no known issues with the firmware or driver

> >updates.

> >

> >Looking at the MS Patch log it looks like it's been missed for a number of

> >patches. It may have had some of the new patches and missed some of the

> >older ones. Maybe one needed an old patch and had issues because it was

> >missing. Just a thought of course.

> >

> >Does it have a good backup? Maybe but since I can't log in I can't check.

> >Many of these servers have issues with the backup software because of a

> >change made by another admin. He's been fixing them but he's has a lot of

> >work to do since we have so many servers around the world.

> >

> >So do you have any suggestions on how I can determine the issue and get this

> >rsolved over the network?

> >

> >Any suggestions would be great.

> >

> >Thanks

> >Rick Clapp (former SNA MVP)

>

> You should really be on SP2 by now. Also, are you using the RDP 6

> client?

>

> - Thee Chicago Wolf

>

[Guest Thee Chicago Wolf]

Re: Server 2003 Blue Screen at Logon

 

>SP2 is currently being tested with our main application. It should get

>rolled out in the next few months.

>

>I'm using RDP6 on my desktop.

>

>Rick

 

RDP 6.1 is being integrated into the forthcoming XP SP3 so you have

about 4+ weeks before you get to use it. It is amazing fast. Hopefully

Redmond finalizes the RDC 6.1 by the end of this Month to support

Server 2003 SP2.

 

Couple things of note regarding Server 2003 SP2. It is HIGHLY

recommended that you have the latest NIC driver installed before or

immediately after installing. Is the problematic Server already using

current NIC drivers?

 

Take a peek at some of these KB article as they might be things to try

or lead to a resolution:

 

http://support.microsoft.com/kb/947773

http://support.microsoft.com/kb/946056

 

And some of these related article:

http://support.microsoft.com/search/default.aspx?mode=r&query=0x00000008&catalog=LCID%3D1033&1033comm=1&spid=3198

 

- Thee Chicago Wolf

[Guest Rick Clapp]

Re: Server 2003 Blue Screen at Logon

 

This happens even if the staff attempts to logon locally. So I don't think

it's and RDP issue. The Stop Code is 0x00000008 not 0x0000007f. It crashes

at the same point so it doesn't look like a memory or processor issues. If I

login I get the Pop up with the last crash information. Once I enter a

description and click on OK then it crashes within a 2 seconds. I wish I

could get an idea of what module crashed or what it's attempting to do at

this point. The I could have a direction to troubleshoot. The next thing

I'm going to do is dump a directory list of the exe's and DLL's from this

server and another simlar server and see if I can spot some differences.

 

"Thee Chicago Wolf" wrote:

> >SP2 is currently being tested with our main application. It should get

> >rolled out in the next few months.

> >

> >I'm using RDP6 on my desktop.

> >

> >Rick

>

> RDP 6.1 is being integrated into the forthcoming XP SP3 so you have

> about 4+ weeks before you get to use it. It is amazing fast. Hopefully

> Redmond finalizes the RDC 6.1 by the end of this Month to support

> Server 2003 SP2.

>

> Couple things of note regarding Server 2003 SP2. It is HIGHLY

> recommended that you have the latest NIC driver installed before or

> immediately after installing. Is the problematic Server already using

> current NIC drivers?

>

> Take a peek at some of these KB article as they might be things to try

> or lead to a resolution:

>

> http://support.microsoft.com/kb/947773

> http://support.microsoft.com/kb/946056

>

> And some of these related article:

> http://support.microsoft.com/search/default.aspx?mode=r&query=0x00000008&catalog=LCID%3D1033&1033comm=1&spid=3198

>

> - Thee Chicago Wolf

>

[Guest Thee Chicago Wolf]

Re: Server 2003 Blue Screen at Logon

 

>This happens even if the staff attempts to logon locally. So I don't think

>it's and RDP issue. The Stop Code is 0x00000008 not 0x0000007f. It crashes

>at the same point so it doesn't look like a memory or processor issues. If I

>login I get the Pop up with the last crash information. Once I enter a

>description and click on OK then it crashes within a 2 seconds. I wish I

>could get an idea of what module crashed or what it's attempting to do at

>this point. The I could have a direction to troubleshoot. The next thing

>I'm going to do is dump a directory list of the exe's and DLL's from this

>server and another simlar server and see if I can spot some differences.

 

Yes, these niggling little crashes are a pain to diagnose some times.

Anything of interest in the event viewer?

 

- Thee Chicago Wolf

[Guest Rick Clapp]

RE: Server 2003 Blue Screen at Logon

 

I'm getting old and my eyes are failing me! :-(

 

Here's the correct error codes...

 

0x0000008e (0xc0000005, 0x809413c4, 0xf364c8dc, 0x00000000)

 

"Rick Clapp" wrote:

> I have a Dell 700 Server running Windows 2003 SP1 and acting as a domain

> control on the other side of the world. The server works fine unless you

> attempt to logon remotely (RPD) or locally. If you do it crashes and creates

> a memory.dmp file. When you attempt to logon in again you get the crash

> message.

>

> System Failure: Stop Error

> 0x00000008 (0xc0000005, 0x809413c4, 0xf29098dc, 0x00000000)

>

> No module or process is shown. The system doesn't have symbols loaded so

> the crash analyser I have doesn't help.

>

> The right thing to do is contact MS to get assistance. My manager won't let

> me use one of our MS incidents because then she has to explain to her

> management why she did it. (Big Company BS) :-(

>

> So I've spend many hours trying to solve this remotely without help.

>

> The server is up and running just fine. I can look at the event logs. I

> can RCMD into the system so I have command line access. I also can remotely

> mount drives and the registry. I can also access the Dell Server Assistant

> and don't see any hardware errors. No drive problems or memory issues are

> being reported.

>

> So far nothing I've looked at has given me a clue.

>

> As to what has been done to the box....

>

> I'm not positive since SMS rolls out a number of patches and software

> changes. I know that it has the most current version of Dell's firmware and

> drivers. those were installed weeks ago and the system worked afterwards.

> This same software has been installed on 7 other servers and haven't caused a

> problem.

>

> I did contact Dell and they have no known issues with the firmware or driver

> updates.

>

> Looking at the MS Patch log it looks like it's been missed for a number of

> patches. It may have had some of the new patches and missed some of the

> older ones. Maybe one needed an old patch and had issues because it was

> missing. Just a thought of course.

>

> Does it have a good backup? Maybe but since I can't log in I can't check.

> Many of these servers have issues with the backup software because of a

> change made by another admin. He's been fixing them but he's has a lot of

> work to do since we have so many servers around the world.

>

> So do you have any suggestions on how I can determine the issue and get this

> rsolved over the network?

>

> Any suggestions would be great.

>

> Thanks

> Rick Clapp (former SNA MVP)

>

>

[Guest Thee Chicago Wolf]

Re: Server 2003 Blue Screen at Logon

 

>I'm getting old and my eyes are failing me! :-(

>

>Here's the correct error codes...

>

>0x0000008e (0xc0000005, 0x809413c4, 0xf364c8dc, 0x00000000)

 

Ok, that helps a bit more. Is this by chance a dual-core or quad core

set up of some kind? I found a couple KB articles that are explore

0x0000008e 0xc0000005 related crashes and the problem seems to be in

the ntkrnl file set or the win32k.sys file.

Have a look:

http://support.microsoft.com/kb/840216

http://support.microsoft.com/kb/885450

http://support.microsoft.com/kb/947479

http://support.microsoft.com/kb/939001

http://support.microsoft.com/kb/907966

 

I would recommend getting the current ntkrnl set from this KB and

giving it a shot first: http://support.microsoft.com/kb/944984

 

This update wouldn't hurt either:

http://support.microsoft.com/kb/936357

 

- Thee Chicago Wolf

[Guest MrHusy]

Re: Server 2003 Blue Screen at Logon

 

Hi Rick

I would suggest either using the following symbol path(Microsoft Symbol

Server) for dump analysis or upload it and submit here a link to analyze. It

would show us the exact image module that causes BSOD and narrows the issue.

 

..sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols

 

Regards

--

MrHusy

http://www.experts-exchange.com/M_3788926.html

 

 

 

"Thee Chicago Wolf" wrote:

> >I'm getting old and my eyes are failing me! :-(

> >

> >Here's the correct error codes...

> >

> >0x0000008e (0xc0000005, 0x809413c4, 0xf364c8dc, 0x00000000)

>

> Ok, that helps a bit more. Is this by chance a dual-core or quad core

> set up of some kind? I found a couple KB articles that are explore

> 0x0000008e 0xc0000005 related crashes and the problem seems to be in

> the ntkrnl file set or the win32k.sys file.

> Have a look:

> http://support.microsoft.com/kb/840216

> http://support.microsoft.com/kb/885450

> http://support.microsoft.com/kb/947479

> http://support.microsoft.com/kb/939001

> http://support.microsoft.com/kb/907966

>

> I would recommend getting the current ntkrnl set from this KB and

> giving it a shot first: http://support.microsoft.com/kb/944984

>

> This update wouldn't hurt either:

> http://support.microsoft.com/kb/936357

>

> - Thee Chicago Wolf

>