When winnt crashes

[Christian Bellavance]

Hi!

What can we do to fix the problem (instead of reinstalling). when NT 4.0 (Server or Workstation) crashes at the blue screen when it boots.

Thanks.

[Rod Trent]

You can use the BSOD to determine what your problem is. The first 3 lines of the BSOD is your indication.

Here`s the basic breakdown of a STOP error:

The first line, first hex number, example: 0x0000000A, means that a kernel mode process or driver attempted to access a memory address that it did not have permission to access. Which is either a hardware problem or a software (driver) problem.

The first line, second hex number, example: 0x00000003, indicates the memory address that was referenced improperly.

The first line, third hex number, example: 0x0000001C, indicates the IRQL that was required to access the memory.

The first line, fourth hex number, example: 0x00000000, indicates that the type of access to the memory address was Read. As 0=Read and 1-Write.

The first line, fourth hex number, example: 0x00000003, indicates the address of the instruction which attempted to address the memory listed in line one.

The third line indicates the actual driver causing the problem.


On 8/27/98 8:43:10 AM, Christian Bellavance wrote:
> Hi!

What can we do to fix the problem (instead of reinstalling). when NT
> 4.0 (Server or Workstation) crashes at the blue screen when it boots.

Thanks.

[Mike Prince]

I had this problem with a batch of new servers and did everything in the world except upgrade the BIOS to try to fix it.
Of course, the BIOS was the problem. Not that your problem is the same, but it is worth a shot.
Below is a link that may help. Some where on your BSOD you will find a cryptic error written in plain english.
Try and find that error on the link below.

http://support.microsoft.com/support/kb/articles/q103/0/59.asp

On 8/27/98 8:43:10 AM, Christian Bellavance wrote:
> Hi!

What can we do to fix the problem (instead of reinstalling). when NT
> 4.0 (Server or Workstation) crashes at the blue screen when it boots.

Thanks.

[Jeff Thomas]

After having this type of thing happen at least on 30 some odd machines we deployed, one cause might be an improper Video Driver. Easiest way to check this out is to use the steps for analyzing your BSOD from reply#1 to see if the Video Driver is the cause.

Jeff

On 9/21/98 4:10:59 PM, Mike Prince wrote:
> I had this problem with a batch of new servers and did everything in the
> world except upgrade the BIOS to try to fix it.
Of course, the BIOS was
> the problem. Not that your problem is the same, but it is worth a shot.

> Below is a link that may help. Some where on your BSOD you will find a
> cryptic error written in plain english.
Try and find that error on the
> link
> below.

http://support.microsoft.com/support/kb/articles/q103/0/59.asp


> On 8/27/98 8:43:10 AM, Christian Bellavance wrote:
> Hi!

What can we
> do to fix the problem (instead of reinstalling). when NT
> 4.0 (Server or
> Workstation) crashes at the blue screen when it boots.

Thanks.