Need a little help combating the "Blue Screen of Death" in Win NT

[JoLLyRoGer]

I'm having trouble doing a rebuild of a system. After trying to repair it using the install CD, I keep receiving a stop error, and a physical memory dump resulting in a complete system crash. Upon re-installing Win NT, under the network setup portion, testing of the NIC shows that everything passes except for the cable tx/rx test. So I tell it OK and continue on to TCP/IP. After entering the workstation's ID, IP, DNS, and domain,(wins is not used) I am receiving an error message stating that "Domain Controller can not be located" when trying to add the machine to our domain. Upon rebooting, immediately following the login screen, but before actually logging in, a stop error occours resulting the Blue Screen containing several addresses. Additional re-boots yeild the same results. I have determined this to be a hardware related error. Any advise??

I've tried to reload the drivers for the NIC, but the same results ensue. I've also double and triple checked the network cable for a good connection.

SIDE NOTE: The workstation runs stable, after a fresh re-install, under the local workgroup mode, until I enter the TCP/IP properties and try to add it to the domain. Upon restarting the computer after making the changes, I immediately get the stop error after the login screen again.

I have coordinated with my domain administrator to make sure that I have the proper tcp/ip values, and to ensure that a domain account that corresponds with the workstation ID and IP has been created.

Is it the NIC causing the problems?? It has worked before.
Any thoughts??

Thanks in advance..
JR.

 

[CTR]

It sounds like a hardware or file corruption issue. Try another NIC, preferably one that you know works for sure. You might also try posting this in Operating Systems for more ideas.

 

[desy]

You are adding the workstation name to the server manager right?
NT needs to know of new workstaions as they are in effect workgroup servers and have to be put in the domain before the Primary domain controller will grant access.
Even if it was in there before under the same workstation name you have to delete the old one and add it in again to get a new SID

 

[JoLLyRoGer]

hmmm. I'll have to double check that, but what about the stop error?? Any thoughts there??

 

[desy]

If you give me the whole Stop error I can check my Microsoft technet CD.

 

[JoLLyRoGer]

That could be a little bit. I'm in the midst of yet another re-install on the same machine. If, more like When, it comes up again, I'll copy it and PM you. Thank's for the offer, I hve a feeling I'll be taking you up on that pretty soon..

JR..

 

[CTR]

Don't forget the service pack...

 

[JoLLyRoGer]

Yeah, that goes without saying. Nothing goes on our network without SP6 in place. Thanks for the reminder though. I do tend to get into a hurry sometimes.

 

[JoLLyRoGer]

*** STOP: 0x0000000A (0x0066006A, 0x00000002, 0x00000001, 0x80128670)
IRQL_NOT_LESS_OR_EQUAL*** Address 80128670 has base at 80100000 - notskrnl.exe

CPUID: GenuineIntel 6.8.1 irql: 1f SYSVER 0XF0000565

Dll Base DateStmp - Name Dll Base DateStmp - Name
80100000 3255a915 - ntoskrnl.exe 80010000 31ee6c52 - hal.dll
80001000 32ed06b4 - atapi.sys 80006000 31ee6c74 - SCSIPORT.SYS
80274000 31ed237c - Disk.sys 80278000 31ec6c7a - CLASS2.SYS
F5D00000 31ecdd07 - fastfat.sys f5ae0000 31ec6c8d - Floppy.sys
f5d00000 31ec6ca5 - Sfloppy.SYS f5af0000 31ec6ca1 - Cdrom.sys
f5d0a000 31ec6df7 - Fs_Rec.SYS f5dc9000 31ec6c99 - Null.SYS
f5c64000 31ed868b - KSecDD.SYS f5dca000 31ec6c78 - Beep.SYS
f5b20000 31ec6c90 - i8042prt.sys f5c6c000 31ec6c97 - mouclass.sys
f5c74000 31ec6c94 - kbdclass.sys f5b38000 31f50722 - VIDEOPRT.SYS
f5c84000 31ec6c6d - vga.sys f5b50000 31ec6ccb - Msfs.SYS
f5800000 31ec6cc7 - Npfs.SYS f5792000 31eed262 - NDIS.SYS
a0000000 31f954f7 - win32k.sys f577c000 00000000 - vga.dll
f5754000 31ec6e6c - TDI.SYS f56c3000 31f130a7 - tcpip.sys
f56a7000 31f50a65 - netbt.sys f5830000 31f8f864 - afd.sys
f5c08000 31ec6e7a - netbios.sys f5728000 31ec6c9b - Parport.SYS
f5720000 31ec6c9b - Parallel.SYS f5d8e000 31ec6c9d - ParVdm.SYS
f5830000 31ec6cb1 - Serial.SYS f5640000 31f5003b - rdr.sys
f562f000 31f7a1ba - mup.sys


Address Dword dump Build[1381] - Name
f5733c50 80128670 80128670 f5733c28 ffffffff f5733ce4 80138264 - ntoskrnl.exe
f5733c60 801382d4 801382d4 80142138 ffffffff f5733ca8 80109db4 - ntoskrnl.exe
f5733c64 80142138 80142138 ffffffff f5733ca8 80109db4 00000246 - ntoskrnl.exe
f5733c70 80109db4 80109db4 00000246 80109f20 e1261994 8097d2bc - ntoskrnl.exe
f5733c78 80109f20 80109f20 e1261994 8097d2bc 80160000 80970023 - ntoskrnl.exe
f5733c84 80160000 80160000 80970023 00000023 0052005d f5733d7c - ntoskrnl.exe
f5733cbc 80128670 80128670 00000008 00010206 f5733d0c 8014a4c0 - ntoskrnl.exe
f5733ccc 8014a4c0 8014a4c0 80974000 00000000 8097d2b8 f5733cbc - ntoskrnl.exe
f5733ce8 8010a6b0 8010a6b0 80974000 0014c43c 80974124 8011314e - ntoskrnl.exe
f5733cf8 8011314e 8011314e 00000000 80974003 00000000 01015a00 - ntoskrnl.exe
f5733d10 8010a373 8010a373 80974008 00000000 8011320b 80974008 - ntoskrnl.exe
f5733d1c 8011320b 8011320b 80974008 8097d288 8097e8e0 8011314e - ntoskrnl.exe
f5733d2c 8011314e 8011314e 8097e8e0 8097e8e0 8097d2a8 00000001 - ntoskrnl.exe
f5733d5c 801382d4 801382d4 80141a88 ffffffff f5733da0 80118e25 - ntoskrnl.exe
f5733d60 80141a88 80141a88 ffffffff f5733da0 80118e25 8097d288 - ntoskrnl.exe
f5733d6c 80118e25 80118e25 8097d288 f5733d9c f5733d98 f5733d94 - ntoskrnl.exe
f5733da0 8001003b 8001003b 8013f45c 00000000 00000000 00000000 - hal.dll

Restart and set the recovery options in the system control panel
or the /CRASHDEBUG system start option. If this message reappears,
contact your system administrator or technical support group.


That's it, that's the stop message I'm getting.

What does it mean. To me it seems like the kernel took a dump.

 

[Panther505]

#1-Are you loading the Network properties during the installation?

#2- Are you loading with an original NT4 CD (ie one that does not install any SPs)?

If you are loading the network drivers during the initial install-don't. IF you are loading with a CD that installs the ORIGINAL NT4 (No service packs) then got to SP4 (if you want the Active DT. Then go to SP6. After SP6 is installed then add the Network Drivers and see if you have any trouble (Don't forget to re install the SP afterwards)

Let me know how it goes

 

[JoLLyRoGer]

Just wanted to say thanks to everyone that replied to my thread. Especially desy. Thanks for the advice. I was finally able to do a full system recovery and re-establish the workstation on the domain. Panther, you nailed the problem dead center also.

Oh well, lesson learned:

Service Packs BEFORE Network Services.

And now... Everyone sing it with me:

Ding Dong The Screen Is Dead.
Which Old Screen?
The Big Blue Screen.
Ding Dong The Screen Of Death Is Dead!!!