Windows NT crashes HARD
-
I still have to test this piece-o-junk antiquated operating system. But here's my problem. I can reproduce a scenario that brings NT to its knees. When you reboot, the Windows Login process quits unexpectedly and causes a bluescreen. IF you reboot, you get a blue screen. I cannot figure out a way to get into this machine to see what's going on. I have tried booting in VGA mode, but it still causes the same problem. Any ideas? My next step will be to try and use a recovery disk, we'll see how that goes. It might not get me the information I need - I am not so much interested in *fixing* this machine, as I am interested in what is causing it to crash in the first place. Thanks. "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
-
I still have to test this piece-o-junk antiquated operating system. But here's my problem. I can reproduce a scenario that brings NT to its knees. When you reboot, the Windows Login process quits unexpectedly and causes a bluescreen. IF you reboot, you get a blue screen. I cannot figure out a way to get into this machine to see what's going on. I have tried booting in VGA mode, but it still causes the same problem. Any ideas? My next step will be to try and use a recovery disk, we'll see how that goes. It might not get me the information I need - I am not so much interested in *fixing* this machine, as I am interested in what is causing it to crash in the first place. Thanks. "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
Navin wrote: I still have to test this piece-o-junk antiquated operating system Funny, as with all M$ products it was advertised as the OS to end all OS's when it was released, just like 95! There have been problems with some of the recent hotfixes, mainly to do with RAS and in my case dual boot failing. Or your problem "might" be to do with a hardware failure or a corrupt file on the hard disk, I sometimes get problems on one of my NT boxes during startup, a kick hard boot usually "fixes" it.
If I have seen further it is by standing on the shoulders of Giants. - Isaac Newton 1676
-
I still have to test this piece-o-junk antiquated operating system. But here's my problem. I can reproduce a scenario that brings NT to its knees. When you reboot, the Windows Login process quits unexpectedly and causes a bluescreen. IF you reboot, you get a blue screen. I cannot figure out a way to get into this machine to see what's going on. I have tried booting in VGA mode, but it still causes the same problem. Any ideas? My next step will be to try and use a recovery disk, we'll see how that goes. It might not get me the information I need - I am not so much interested in *fixing* this machine, as I am interested in what is causing it to crash in the first place. Thanks. "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
Figured out the problem. It's amazing what kind of funky state your system can get in when you try and delete msvcrt.dll after a reboot. :-O :-D "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
-
I still have to test this piece-o-junk antiquated operating system. But here's my problem. I can reproduce a scenario that brings NT to its knees. When you reboot, the Windows Login process quits unexpectedly and causes a bluescreen. IF you reboot, you get a blue screen. I cannot figure out a way to get into this machine to see what's going on. I have tried booting in VGA mode, but it still causes the same problem. Any ideas? My next step will be to try and use a recovery disk, we'll see how that goes. It might not get me the information I need - I am not so much interested in *fixing* this machine, as I am interested in what is causing it to crash in the first place. Thanks. "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
Navin wrote: the Windows Login process quits unexpectedly and causes a bluescreen. That's what happens when winlogon.exe dies. If you can't log in, the system bluescreens since... well, you can't log in. ;) --Mike-- Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber Latest art~!@#2rDFA#@(#*%$Rfa39f3fqwf--= NO CARRIER
-
I still have to test this piece-o-junk antiquated operating system. But here's my problem. I can reproduce a scenario that brings NT to its knees. When you reboot, the Windows Login process quits unexpectedly and causes a bluescreen. IF you reboot, you get a blue screen. I cannot figure out a way to get into this machine to see what's going on. I have tried booting in VGA mode, but it still causes the same problem. Any ideas? My next step will be to try and use a recovery disk, we'll see how that goes. It might not get me the information I need - I am not so much interested in *fixing* this machine, as I am interested in what is causing it to crash in the first place. Thanks. "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
Thats what I love about windows, if you do what it wants you to it'll end up breaking it :P For example today I was using the Microsoft Base Security Analyzer (see earlier thread) and it told me I shouldn't be using Builtin\Administrators as an Adminstrator on SQL Server, I thought I guess it makes sense. I followed its instructions and guess what, I can no longer even access the Server because SA is not associated with a trusted connection, :wtf: I guess it was a sign to just uninstall it. I haven't been using it and my new 2k3 Server should be finished soon ;P :jig: ;P As for your problem, I've never used NT 4, but I would suggested backing up the HD and being prepared for a re-install or OS upgrade. Matt Newman
Sonork: 100:11179 "Jokes should at least try to be intelligent - this is just toilet humor" - Heath Stewart -
Figured out the problem. It's amazing what kind of funky state your system can get in when you try and delete msvcrt.dll after a reboot. :-O :-D "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
Please tell me you didn't!:omg::~ :laugh:
"Welcome to Arizona!
Drive Nice - We're Armed..."
- Proposed Sign at CA/AZ Border -
Thats what I love about windows, if you do what it wants you to it'll end up breaking it :P For example today I was using the Microsoft Base Security Analyzer (see earlier thread) and it told me I shouldn't be using Builtin\Administrators as an Adminstrator on SQL Server, I thought I guess it makes sense. I followed its instructions and guess what, I can no longer even access the Server because SA is not associated with a trusted connection, :wtf: I guess it was a sign to just uninstall it. I haven't been using it and my new 2k3 Server should be finished soon ;P :jig: ;P As for your problem, I've never used NT 4, but I would suggested backing up the HD and being prepared for a re-install or OS upgrade. Matt Newman
Sonork: 100:11179 "Jokes should at least try to be intelligent - this is just toilet humor" - Heath StewartMatt Newman wrote: As for your problem, I've never used NT 4, but I would suggested backing up the HD and being prepared for a re-install or OS upgrade. THat's just it - this machine is DriveImaged, so it is trivial to get it back up and running. My problem was that I wanted to know *why* it was crashing, becuase obviously something in my app caused it to start crashing. Windows didn't help me at all in this scenario. I looked through my debug log files and figured out what was going on. (As noted in a thread above, Windows NT will do strange things if you remove msvcrt.dll. :-O) "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
-
Matt Newman wrote: As for your problem, I've never used NT 4, but I would suggested backing up the HD and being prepared for a re-install or OS upgrade. THat's just it - this machine is DriveImaged, so it is trivial to get it back up and running. My problem was that I wanted to know *why* it was crashing, becuase obviously something in my app caused it to start crashing. Windows didn't help me at all in this scenario. I looked through my debug log files and figured out what was going on. (As noted in a thread above, Windows NT will do strange things if you remove msvcrt.dll. :-O) "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
Navin wrote: Windows didn't help me at all in this scenario. I looked through my debug log files and figured out what was going on. (As noted in a thread above, Windows NT will do strange things if you remove msvcrt.dll. :laugh: Matt Newman
Sonork: 100:11179 "Jokes should at least try to be intelligent - this is just toilet humor" - Heath Stewart -
Thats what I love about windows, if you do what it wants you to it'll end up breaking it :P For example today I was using the Microsoft Base Security Analyzer (see earlier thread) and it told me I shouldn't be using Builtin\Administrators as an Adminstrator on SQL Server, I thought I guess it makes sense. I followed its instructions and guess what, I can no longer even access the Server because SA is not associated with a trusted connection, :wtf: I guess it was a sign to just uninstall it. I haven't been using it and my new 2k3 Server should be finished soon ;P :jig: ;P As for your problem, I've never used NT 4, but I would suggested backing up the HD and being prepared for a re-install or OS upgrade. Matt Newman
Sonork: 100:11179 "Jokes should at least try to be intelligent - this is just toilet humor" - Heath StewartMatt Newman wrote: SA is not associated with a trusted connection I had this problem until I enabled mixed mode authentication in SQL. Apparently it's set to NT authentication by default. HTH :-D Paul ;)
Garfield.Bark(); **---Configuration: garfield - Win32 Deworm---** C:\garfield.cpp(9) : error C2039: 'Bark' : is not a member of 'CCat'