 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows NT / Setup / March 2005NT crashes on boot after patch
3/12/05 Dear Folks, I've got an NT boot problem that I *think* is fixable with your help. Here's the situation: Something got munched while I was installing a bunch of Microsoft patches, and NT gets hung on boot. This happens immediately after the startup chords play-- it goes to the blue screen of death. This is repeatable, and it happens even if I try booting into VGA safe mode. For several reasons, I'd rather not restore the system partition from my backup; I'd much prefer to repair this one. The good news is: 1) The crash happens really late in the boot process, so I figure it can't be anything very low-level. 2) I have a 'legacy' NT system partition on this machine that I *CAN* boot into, so I can get access to the current system partition with all of NT's tools. 3) I have a backup of the present (munched) state of the current system partition, so if I screw anything up trying to repair it, I can revert and try something else. So, I think I'm in the best of all possible worlds, assuming this is repairable. Given this, here are my questions: 1) What's failing? What execs should I be looking at; namely, what is it likely loading right after the startup sounds? If I had to make a half-assed guess, I'd bet on some patch post-installer cleanup routine that got corrupted. But what file names should I be hunting for? 2) Can I figure (1) out by searching the registry or some other ini file? If so, what entries should I look at? 3) Assuming I can fix this by hacking the registry, can I direct regedit when booted into my legacy partition to edit the registry in my broken partition? If not, will running the copy of regedit in the broken partition get me into that partition's registry, or will it automatically go to the active system's registry? If the latter, is there another registry-editing tool people can recommend? BTW, I can provide info from the blue screen o'Death, if that would be of help. Just let me know what entries you want. Any and all suggestions welcome. Thanks! pax / Ctein ========================================== -- Ctein's Online Gallery http://www.ctein.com -- Digital Restorations http://photo-repair.com ========================================== > Something got munched while I was installing a bunch of Microsoft > patches, and NT gets hung on boot. This happens immediately after the > startup chords play-- it goes to the blue screen of death. > [...] My first idea is HotFix KB835732. See e.g.: http://groups.google.de/groups?hl=de&lr=&q=835732&meta=group%3Dcomp.os.ms-window s.nt.misc You might find more by searching for 835732 and ntokrnl... > BTW, I can provide info from the blue screen o'Death, if that would be > of help. If KB835732 isn't your problem more detailed information might be helpful. Stephan Stephan wrote: Ctein wrote: >> Something got munched while I was installing a bunch of Microsoft >> patches, and NT gets hung on boot... >My first idea is HotFix KB835732. >See e.g.: http://groups.google.de/groups?hl=de&lr=&q=835732&meta=group%3Dcomp.os.ms-wi ndows.nt.misc >You might find more by searching for 835732 and ntokrnl... >If KB835732 isn't your problem more detailed information might be helpful. Stephan Dear Stephan, Thank you very much for your prompt response. Although I am not certain, it seems very likely that I applied patch 835732, given Microsoft's description of it. (It had been some months since I had done a security update to this install.) My problem isn't any of the specific ones that KB 835732 described, but you said on the Web that there are reports of people having other problems with this patch, so it's a good place for me to start. I don't know how much information to give you from the Blue Screen; I doubt you want the entire dump. Here's the first line that describes the error. (If there are any later entries from the dump that you would like, just let me know): ***STOP: 0x0000001E (0xC0000005, 0x8010AA3E, 0x00000001, 0x00000004) KMODE EXCEPTION_NOT_HANDLED*** Address 8010aa3e has base at 80100000 - ntoskrnl.exe So, what I'm thinking of (after reading Microsoft's suggested fixes for other patch problems) is boot up from my legacy partition, look for the most recent "uninstall" folder, and copy ntoskrnl.exe from there into my broken system folder. Or, if I can't find a copy of the kernel file in the uninstall folder, copy the one over from my legacy partition. Does this sound like a plausible course of action, or is it likely to break something even worse than things are broken now? pax / Ctein [[ Please excuse any word-salad. ViaVoice in training! ]] ========================================= -- Ctein's Online Gallery http://www.ctein.com -- Digital Restorations http://photo-repair.com ========================================= > [...] Although I am not certain, it > seems very likely that I applied patch 835732, given Microsoft's description > of it. (It had been some months since I had done a security update to this > install.) Maybe I haven't understood you right here, didn't you say: "Something got munched while I was installing a bunch of Microsoft patches..."? > My problem isn't any of the specific ones that KB 835732 described, but you > said on the Web that there are reports of people having other problems with > this patch, so it's a good place for me to start. Yes, there aren't any official reports concerning this, but as you may have already found you wouldn't be the first to run into these or very similar problems after having applied this patch. However, I cannot refer to my own experience - I did apply this patch to a couple of PCs but never had a STOP 0x1E (or other obvious troubles) through it. > I don't know how much information to give you from the Blue Screen; I doubt > you want the entire dump. Here's the first line that describes the error. [quoted text clipped - 4 lines] > KMODE EXCEPTION_NOT_HANDLED*** Address 8010aa3e has base at 80100000 - > ntoskrnl.exe First, this is a good hint for HotFix 835732. I guess there are some third party driver/services on your machine not compatible with this fix. I've googled around myself a little bit and found as possible reasons printer drivers, ASPI-Layers or other multimedia extensions, NIC-drivers, virus scanners, other security related services and so on. Maybe you'll see on your BSOD a non-vital, non-standard driver that has been loaded and causes the crash... > So, what I'm thinking of (after reading Microsoft's suggested fixes for > other patch problems) is boot up from my legacy partition, look for the most > recent "uninstall" folder, and copy ntoskrnl.exe from there into my broken > system folder. Or, if I can't find a copy of the kernel file in the > uninstall folder, copy the one over from my legacy partition. I think this is a good idea to start from. However, I wouldn't recommend to use the original ntoskrnl.exe from a clean install (without any SPs). I've just looked into the folders of an NT4 installations with nearly all official fixes applied and found the "active" ntoskrnl.exe to be dated 03/23/2004 whereas the newest (pre-)835732 version is dated 01/14/03 (may vary a bit for you as this is a German version). You should find this version in the unistall folder of this (or maybe some other) hotfix. > Does this sound like a plausible course of action, or is it likely to break > something even worse than things are broken now? Sounds reasonable (of course, you should backup the latest active ntoskrnl.exe first). And of course you will break something else - at least the hotfix itself. Maybe some other files that has been replaced by this pretty large hotfix do also rely on this new version - I don't know. However, I really can't imagine that things become worse for you. Either you are able boot again and then look for the deeper cause of your troubles if you like - or not - but that is where you are now, isn't it? Stephan Try disconnecting all non-essential hardware such as printers, scsi scanners, etc... and then once you are at the login screen, use another computer to access this computer via server manager. Turn off all non essential services, delete anything out of the admin profile that is non-essential, and try logging in. Good Luck. JayJay > > [...] Although I am not certain, it > > seems very likely that I applied patch 835732, given Microsoft's description [quoted text clipped - 58 lines] > > Stephan |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.