Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Win 2000 BSOD after Windows installer 3.1


  • Please log in to reply

#1
gimeshen

gimeshen

    New Member

  • Member
  • Pip
  • 3 posts
I've installed Windows Installer 3.1 (through Automatic Updates) on my Win 2000 Pro box, after the prompted reboot, the BSOD appeared:

STOP: 0x0000001E (...) KMODE_EXCEPTION_NOT_HANDLED
*** Address 8041FAA4 base at 80400000 DateStamp 384d9b17 - ntoskrnl.exe

Restarted in the Safe Mode, uninstalled Windows Installer 3.1. Had to uninstall it again (it *appears* I had both KB893803 and KB893803v2 hotfixes). Same BSOD during normal reboot.

Booted from the original Win 2000 Pro installation CD (~4 years old), during startup chose to repair the system. Did Quick repair. Same BSOD.

Booted from the CD again, during startup chose Manual repair, this time it found a lot of "non-original" files, including ntoskrnl.exe, chose to fix them all. After startup preceeded, got the same BSOD. Still can reboot in the Safe Mode.

Any suggestions on where and how to look for the problem (other than to reinstall the system)?

Thanks.
g.
  • 0

Advertisements


#2
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
Do u have the latest Service Pack i.e. 4

STOP: 0x0000001E (...)

Can u provide more info. on what was inside the bracket.

Edited by darth_ash, 21 July 2005 - 10:53 AM.

  • 0

#3
gimeshen

gimeshen

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Here's the full first line:

*** STOP: 0x0000001E (0xC0000005, 0x8041FAA4, 0x00000000, 0x0000001D) KMODE_EXCEPTION_NOT_HANDLED

I am running Win 2000 5.00.2195 Service Pack 4

512M RAM
21G free HDD space

And I've been diligently installing all the hotfixes through Automatic Updates.

Edited by gimeshen, 21 July 2005 - 12:11 PM.

  • 0

#4
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
Check out this MS article (link).
It says that if u get STOP: 0x0000001E (0xc0000005, 0x804b2185, 0x00000000, 0x000000b0) KMODE_EXCEPTION_NOT_HANDLED.
U to need to get a hotfix (u will have to ask MS tech support as mentioned in the article)

Note: The 4th parameter is a memory address, and that is why it is different from ur message, and it can vary.

Edited by darth_ash, 21 July 2005 - 12:44 PM.

  • 0

#5
gimeshen

gimeshen

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Thanks for the help.

I read the article. I do not have the first two lines like in the sample examples. My blue screen starts with "*** STOP: ..." without anything preceeding it, but hopefully the hotfix can help.

Now, following the link in the article to get the hotfix gets me to the MS pruduct support page and after few more screens I figure it'll cost me $99 to get support through e-mail. Is that how it is??? If so, can I get the fotfix from somewhere else?

g.
  • 0

#6
darth_ash

darth_ash

    Member 1K

  • Member
  • PipPipPipPip
  • 1,382 posts
The article says either u get Message1 or Message2.
And the 3rd message is whats in ur System Log, but u cant see that because u cant log in.
Ya, there is no direct download link for the hotfix, u will have to contact customer care.
Why would u have to pay $99?
Don't know if u can get it from somewhere else
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP