I have a similar problem to Oosiriss I, too get this same blue screen with the memory dump. However, this is a single NT workstation, not part of a network. I had reinstalled NT workstation. However, now I can't get past this blue screen with the physical memory dump information. I have not yet loaded the SP4. Will this solve my problem? I doubt that updating the user profile will help me. What do you think?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Blue screen prior to logon
- Thread starter mblesko
- Start date
Please provide the first two lines of the Blue Screen.<br>
<br>
Has there been any hardware changes prior to this error condition? Is it a laptop or desktop? Is there a network adapter in the unit at all? Does it occur prior to pressing Ctrl-Alt-Del or immediately after?<br>
<br>
Since you cannot successfully boot into NT you will not be able to apply any Service Pack.
<br>
Has there been any hardware changes prior to this error condition? Is it a laptop or desktop? Is there a network adapter in the unit at all? Does it occur prior to pressing Ctrl-Alt-Del or immediately after?<br>
<br>
Since you cannot successfully boot into NT you will not be able to apply any Service Pack.
- Thread starter
- #3
dxd, in answer to your question, some of what is on the 1st 2 lines is: "KMODE_EXCEPTION_NOT_HANDLED***Address fab2e226 has base at fab21000 <br>
tcpip.sys".<br>
<br>
There have been no hardware changes. There is a network adapter, but I don't remember which one it is. This is a Dell Optiplex desktop purchased at end of 1999. Most of the configuration is Dell's standard. When reinstalling NT, I got 2 messages about 3com products being on the machine that Microsoft doesn't support. By the way, what started this snowball rolling was that the Dial-up networking somehow had been removed, and we couldn't connect to our ISP. Finally, the answer to your last question, the first time, this blue screen occurred immediately after the CTRL+ALT+DELETE. However, the 2nd time, it occurred just prior to that moment.<br>
tcpip.sys".<br>
<br>
There have been no hardware changes. There is a network adapter, but I don't remember which one it is. This is a Dell Optiplex desktop purchased at end of 1999. Most of the configuration is Dell's standard. When reinstalling NT, I got 2 messages about 3com products being on the machine that Microsoft doesn't support. By the way, what started this snowball rolling was that the Dial-up networking somehow had been removed, and we couldn't connect to our ISP. Finally, the answer to your last question, the first time, this blue screen occurred immediately after the CTRL+ALT+DELETE. However, the 2nd time, it occurred just prior to that moment.<br>
Well, by looking over the data you provided there appears to be issues surrounding networking (lan or RAS)as is indicated by the driver TCPIP.SYS.<br>
<br>
I assume that using the "Last Known Good Configuration" at boot does not let you in either???<br>
<br>
If it does not, then you really have a driver or system file issue. <br>
<br>
When you say re-installing NT, do you mean over the top of the original install? Does the install complete and let you into NT the first time? If you are able to get into NT at all, my first step would be to remove all networking components. Reboot and re-install the necessary components and apply whatever Service Pack you may be running.<br>
<br>
If re-installing NT still does not allow you in, try physically removing the modem and network adapter. Hopefully, if these drivers don't start it will not attempt to start any of the other network services. If that lets you in the door, follow the steps I indicated previously.<br>
<br>
dxd
<br>
I assume that using the "Last Known Good Configuration" at boot does not let you in either???<br>
<br>
If it does not, then you really have a driver or system file issue. <br>
<br>
When you say re-installing NT, do you mean over the top of the original install? Does the install complete and let you into NT the first time? If you are able to get into NT at all, my first step would be to remove all networking components. Reboot and re-install the necessary components and apply whatever Service Pack you may be running.<br>
<br>
If re-installing NT still does not allow you in, try physically removing the modem and network adapter. Hopefully, if these drivers don't start it will not attempt to start any of the other network services. If that lets you in the door, follow the steps I indicated previously.<br>
<br>
dxd
- Thread starter
- #5
- Thread starter
- #6
Well, my emergency repair disk didn't work, nor did "last known good" configuration. I ended up installing NT on a different drive, and finally was able to boot. All the reading I have done from Microsoft's Knowledge Base, thanks to hints from dxd pointing the way about the "stop" code, I have finally booted NT. Now I get to apply SP4. I have never done this before. The SP4 Readme.txt is quite daunting. I know I need to backup my system before I apply it. When installing NT to a new drive, I created the ERD. Do I need to modify it with the ERD with /s switch, using Rdisk.exe? After doing this, I will have applied this service pack to the NT OS on the new drive, right? The recommendations I've received say that I should fix the original NT problem and Uninstall this second version. Any further comments or recommendations?
- Status
Similar threads
