2003 Server crashing

October 14, 2007

Hi all,

I've got a Windows 2003 Server Std. Ed. running on a PowerEdge SC1420,

and it's been crashing a few minutes into bootup. It's an AD DC, as

well as an application server (running SQL 2000). At first I believed

it was a hardware issue (the LED indicator lights light up in a

certain sequence), but now believe it's OS-based. Server will crash

when booting into anything but Safe Mode or SM with Networking. I've

checked for a memory.dmp file, and there isn't one there, so it's

crashing without creating a dump file.

I've booted into Recovery Console several times, and run checkdisk /R,

but that doesn't seem to help either. I've also used msconfig in Safe

mode to set all non-Windows services to not start (as well as some of

the non-essential Windows services), and un-checked any programs

listed under the Startup tab, and that doesn't correct the problem.

I can let it boot up and then sit there at the logon screen, and it

will eventually tank after a few minutes, or I can login, it doesn't

seem to matter one way or the other. In the System Log, the last thing

that usually shows before the time the server crashes is a message

about the IPSec Driver being in Restricted mode, so I disabled IPSec

services, and that doesn't help, so I figure whatever the problem is

isn't related to IPSec.

I'm open to any suggestions of things to try, running a Repair from

the install CD or doing a format and a clean install are my last-ditch

options, and I really don't want to use them without trying

everything. I just feel certain it's a service or device driver

somewhere, since the server will stay up in Safe Mode without any

problem. Thanks for any suggestions.

October 14, 2007

Re: 2003 Server crashing

What does "crashing" mean? Blue screen stop error? If so you can turn off

the option to auto reboot. Control Panel|System|Advanced|Startup and

Recovery|Settings and uncheck 'Automatically restart' I would agree about

the driver(s). I check Device Manager for non-starting devices and or

devices with a bang. Also check the hardware manufacturer's web site for the

latest drivers for your devices.

--

Regards,

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

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect

<mbsmith81@gmail.com> wrote:

> Hi all,

> I've got a Windows 2003 Server Std. Ed. running on a PowerEdge SC1420,

> and it's been crashing a few minutes into bootup. It's an AD DC, as

> well as an application server (running SQL 2000). At first I believed

> it was a hardware issue (the LED indicator lights light up in a

> certain sequence), but now believe it's OS-based. Server will crash

> when booting into anything but Safe Mode or SM with Networking. I've

> checked for a memory.dmp file, and there isn't one there, so it's

> crashing without creating a dump file.

>

> I've booted into Recovery Console several times, and run checkdisk /R,

> but that doesn't seem to help either. I've also used msconfig in Safe

> mode to set all non-Windows services to not start (as well as some of

> the non-essential Windows services), and un-checked any programs

> listed under the Startup tab, and that doesn't correct the problem.

>

> I can let it boot up and then sit there at the logon screen, and it

> will eventually tank after a few minutes, or I can login, it doesn't

> seem to matter one way or the other. In the System Log, the last thing

> that usually shows before the time the server crashes is a message

> about the IPSec Driver being in Restricted mode, so I disabled IPSec

> services, and that doesn't help, so I figure whatever the problem is

> isn't related to IPSec.

>

> I'm open to any suggestions of things to try, running a Repair from

> the install CD or doing a format and a clean install are my last-ditch

> options, and I really don't want to use them without trying

> everything. I just feel certain it's a service or device driver

> somewhere, since the server will stay up in Safe Mode without any

> problem. Thanks for any suggestions.

>

October 14, 2007

Re: 2003 Server crashing

You may need to configure virtual memory for a large dump model. Any errors

in the Event Viewer? Or this post may help.

Server shutdown unexpected with ...Recently, the server has been shutdown

unexpected with different Reason Code: 0x806000c, 0x8000005 and 0x805000f.

He doesn't remember any thing change. ...

http://www.chicagotech.net/netforums/viewtopic.php?t=989&start=0&postdays=0&postorder=asc&highli

--

Bob Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN Troubleshooting on

http://www.ChicagoTech.net

How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com

<mbsmith81@gmail.com> wrote in message

news:1192388889.898953.206700@v29g2000prd.googlegroups.com...

> Hi all,

> I've got a Windows 2003 Server Std. Ed. running on a PowerEdge SC1420,

> and it's been crashing a few minutes into bootup. It's an AD DC, as

> well as an application server (running SQL 2000). At first I believed

> it was a hardware issue (the LED indicator lights light up in a

> certain sequence), but now believe it's OS-based. Server will crash

> when booting into anything but Safe Mode or SM with Networking. I've

> checked for a memory.dmp file, and there isn't one there, so it's

> crashing without creating a dump file.

>

> I've booted into Recovery Console several times, and run checkdisk /R,

> but that doesn't seem to help either. I've also used msconfig in Safe

> mode to set all non-Windows services to not start (as well as some of

> the non-essential Windows services), and un-checked any programs

> listed under the Startup tab, and that doesn't correct the problem.

>

> I can let it boot up and then sit there at the logon screen, and it

> will eventually tank after a few minutes, or I can login, it doesn't

> seem to matter one way or the other. In the System Log, the last thing

> that usually shows before the time the server crashes is a message

> about the IPSec Driver being in Restricted mode, so I disabled IPSec

> services, and that doesn't help, so I figure whatever the problem is

> isn't related to IPSec.

>

> I'm open to any suggestions of things to try, running a Repair from

> the install CD or doing a format and a clean install are my last-ditch

> options, and I really don't want to use them without trying

> everything. I just feel certain it's a service or device driver

> somewhere, since the server will stay up in Safe Mode without any

> problem. Thanks for any suggestions.

>

October 15, 2007

Re: 2003 Server crashing

On Oct 14, 4:35 pm, "Dave Patrick" <DSPatr...@nospam.gmail.com> wrote:

> What does "crashing" mean? Blue screen stop error? If so you can turn off

> the option to auto reboot. Control Panel|System|Advanced|Startup and

> Recovery|Settings and uncheck 'Automatically restart' I would agree about

> the driver(s). I check Device Manager for non-starting devices and or

> devices with a bang. Also check the hardware manufacturer's web site for the

> latest drivers for your devices.

>

> --

>

> Regards,

>

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

> Microsoft Certified Professional

> Microsoft MVP [Windows]http://www.microsoft.com/protect

>

> <mbsmit...@gmail.com> wrote:

> > Hi all,

> > I've got a Windows 2003 Server Std. Ed. running on a PowerEdge SC1420,

> > and it's been crashing a few minutes into bootup. It's an AD DC, as

> > well as an application server (running SQL 2000). At first I believed

> > it was a hardware issue (the LED indicator lights light up in a

> > certain sequence), but now believe it's OS-based. Server will crash

> > when booting into anything but Safe Mode or SM with Networking. I've

> > checked for a memory.dmp file, and there isn't one there, so it's

> > crashing without creating a dump file.

>

> > I've booted into Recovery Console several times, and run checkdisk /R,

> > but that doesn't seem to help either. I've also used msconfig in Safe

> > mode to set all non-Windows services to not start (as well as some of

> > the non-essential Windows services), and un-checked any programs

> > listed under the Startup tab, and that doesn't correct the problem.

>

> > I can let it boot up and then sit there at the logon screen, and it

> > will eventually tank after a few minutes, or I can login, it doesn't

> > seem to matter one way or the other. In the System Log, the last thing

> > that usually shows before the time the server crashes is a message

> > about the IPSec Driver being in Restricted mode, so I disabled IPSec

> > services, and that doesn't help, so I figure whatever the problem is

> > isn't related to IPSec.

>

> > I'm open to any suggestions of things to try, running a Repair from

> > the install CD or doing a format and a clean install are my last-ditch

> > options, and I really don't want to use them without trying

> > everything. I just feel certain it's a service or device driver

> > somewhere, since the server will stay up in Safe Mode without any

> > problem. Thanks for any suggestions.- Hide quoted text -

>

> - Show quoted text -

Sorry, I should have been more specific. When I say crash, it doesn't

blue screen, the monitor screen just goes black, and a few of the

indicator LEDs on the front of the server change color, which is what

made me think it was a hardware issue, but I'm shying away from that

assumption since it can stay up in Safe Mode. I've tried booting into

VGA in case it was just the graphics driver, but that was a no-go as

well. There was a SCSI device attached to a controller card that had a

bang in Device Manager, and I disabled it to see if that would help,

but it didn't. I'm going to try removing any un-used hardware in DM,

then shutting down and removing it physically. I'll increase the size

of the dump as well, to see if that will allow it to complete. Thanks

for the help guys.

October 15, 2007