BSOD from latest windows update

[NotANumber]

Hey everyone,

I obtained the latest windows update patches for my win2000 system over the weekend. Now on startup, I get a BSOD that looks like this:
Error code: 0x1E (KMODE_EXCEPTION_NOT_HANDLED)
Exception code: 0xC0000005
module: ntoskrnl.exe

Performing a repair install (not the quick repair, the one which deletes and replaces all system files) leaves me with the same problem. Booting into safe mode also yields the same problem.

The only thing I have changed in my computer was getting the latest patches from microsoft. I know my computer isn't dying because I've been booting into BartPE for three days now.

I know this condition is probably due to one updated file. How do I find this file? I've tried turning on boot logging but all I get is "Setup is being restarted...".

How do I solve this problem besides doing a full reinstall???

Thanks.

 

[FlyingPenguin]

You can try uninstalling the latest updates. You'll have to look them up to see which ones they were. Then re-install them. However I doubt that's your problem.

This error is very common if you have a flaky driver.

When you did the updates, did you happen to install any of the drivers offered by Windows update? If so I would consider it likely that's your problem. Never use the generic drivers offered by Windows Update - I've seen a lot of systems trashed by them. Install the latest manufacture's driver.

It's also possible that one of the updates "broke" an old driver you're using. Try installing the latest updates for all your major hardware (Mobo drivers, video, sound card, NIC).

Hope this helps...

 

[imported_Phil]

Call Microsoft. When one of their patches breaks your system, they'll support it for free.

 

[FlyingPenguin]

"Hello, Microsoft tech support. Please hold for 4 hours..."

 

[Smilin]

Originally posted by: FlyingPenguin
"Hello, Microsoft tech support. Please hold for 4 hours..."

What an absolute crock of shit.

The Average wait time for the EPS setup team, the one that handles this particular issue is usually -30 minutes. That's MINUS thirty minutes which means a support tech has been waiting thirty minutes for you to call him! The worst I've ever seen over there is when a call center went down during a hurricane and the wait time reached about 40 minutes. This spike disappeared after new resources arrived at the other call centers.

In all likelyhood you'll get through immediately.

Spare us your FUD.



As to the original problem:

You're not going to get a Stop 1E from a Microsoft update. Yeah, there's some other horribleness (tm) that you might get but a Stop 1E ain't one of them. You've got something else going on that the update simply brought to the surface.

A Stop 1E is often a driver. Boot to recovery console, use listsvc to see what drivers are starting. Use disable to stop them from loading. Where you are getting the error will help determine what drivers to look at. If it's during the splash screen where the 80-dot bar across the bottom is, look for Boot drivers. After that look for system drivers. If you see the ctrl-alt-del screen flash, then Winlogon has started and you should be looking at automatic drivers. While you're in recovery console, run a chkdsk /p to fix any corruption the repeated reboots you've been having may have caused.

If you have already gotten yourself in a reboot loop with gui-mode setup attempting to run then the MS tech may have you use a repair hive or parallel install to edit your registry to manually knock you out of the setup process and back into a normal boot.

Although a Stop 1E is a common bugcheck, it's NOT that common during setup. Is there a BIOS update available for your machine?

Don't spend too much time trying to do this yourself. Give the MS dudes a call. Simply mention that your box is in a domain environment and you'll be speaking with the Enterprise Platforms team - some of the best techs on the planet.

 

[NotANumber]

Problem fixed!

Smilin's excellent post got me on the right track. I was stuck in the gui-mode setup loop and so none of my driver disables were doing anything. Smilin mentioned that I needed to reset the registry to get out of the loop. Fortunately, I had a backup in the repair\regback directory. Using BartPE, it's a simple file copy to the system32\config directory. Once I was out of the loop, I just had to find the offending driver by process of elimination. The blue screen was right after the console splash screen so I looked at all the system drivers. Just my luck, it was the first three!
cdr4vsd.sys
cdralw2k.sys
cdr4_2k.sys
They are all Adaptec drivers and are all really old. Disabling them got rid of the STOP error. I had to reapply all the win2k patches since I started an in-place upgrade. A couple of (fixable) errors later and everything was copasetic.

Well, thanks for your help guys! I learned a lot.

 

[Smilin]

Sweeeeeet.

Glad you're working man.