computer stuff

[rm]

Okay, today I am prepared to do what must be done. Plan 1: Get this thing fixed.

Here's the deal. I boot and I get this error message:

STOP KMODE_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this Stop error screen, restart the computer. If this screen appears again, follow these steps:

Check to be sure you have adequate disk space. If a driver is identified in the Stop message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press f8 to select Advanced Startup Options, and then select SAfe MOde.

Refer to your Getting Started manual for more information on troubleshooting Stop errors.

Okay, I've gotten this screen more than once.
I have not recently installed any new hardware.
While F8 works, booting into and of the versions of Safe Mode or "Last Known Good Configuration" results in the same error.
I do not have a system disk or a working CD drive.

What do I do or need to ask someone who is more current with this sort of stuff than I am to do?

Comments

[ladyofthelog.livejournal.com]

http://support.microsoft.com/?kbid=294728

The first hit I got for this error message. It has some suggestions for resolution, but they require a parallel install, meaning a system disk and a working CD drive.

Do you have a working USB port?

Is there a possiblity of getting a friend to download a copy of your OS, put it onto a large USB storage medium or external hard drive, and load it that way?

[rm.livejournal.com]

I do have working USB port and hub.

Dunno, but this also sounds like what delchi was suggesting. I suppose I could buy the things required to do this, download at work and bring home, reading instructions online through the dialup while doing it. RIght now I am looking for a professional with the gear.

[ladyofthelog.livejournal.com]

Makes sense to me. What version of Windows are you running?

[rm.livejournal.com]

2000

[ladyofthelog.livejournal.com]

It should be pretty easy to find a copy of that.

[rm.livejournal.com]

Let me ammend that Windows 2000 Professional.

I wonder if we have it at the office.

[ladyofthelog.livejournal.com]

Probably. And there's certainly a bevy of hacked CD keys & registration info on the internet.

[rahalia-cat.livejournal.com]

I don't suppose Windows Update ran shortly before you got this error, did it? I'm finding one of two issues regarding that error message online. One happens after a certain Windows Update is installed on a Windows 2000 machine, the other has a longer error message, ending in KMODE_EXCEPTION_NOT_HANDLED in Win32k.sys and is caused by a virus.

[rm.livejournal.com]

Nope. I just had my machine on all day, as I so, the net connection was frozen, I rebooted and boom!

[rahalia-cat.livejournal.com]

Ugh. I just wondered if you had Windows Update configured to run automatically that's what might have happened.

The link given in the first comment was the KMODE_EXCEPTION_NOT_HANDLED in Win32k.sys one that I found. The dodgy update link solution is here:

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B898114

Someone asked the same question as you (they had an XP install disc and a working drive, though) and was given a walkthrough on this forum:

http://www.vmware.com/community/message.jspa?messageID=372379

It might be worth registering and asking if there's any way to fix this without a working drive etc.

[delchi.livejournal.com]

There really isin't a way to fix it w/out a working CD rom drive - Kernel exceptions are tricky buggers. The most likely culprit given what I know so far is a corrupted system file, which can be caused by any number of untild virii / worms / or various system failures ( old/bad HD ..etc..etc.. )

[dacuteturtle.livejournal.com]

This is a corruption error, as others have already stated.

Let's follow the logic:
1. The driver is corrupt. (unlikely).
2. The disk's file table is bad. (Somewhat likely).
2. The disk is bad and corrupting the driver. (Most likely).

Froze, then crashed, then won't work in "safe mode" usually points to a faulty hard drive.

Let's assume that your data is more valuable than a new drive. The "better safe than sorry" route is to get a replacement drive, install everything onto it, then copy your data off the old drive. (I make the assumption that the drive is going bad, and that further use of it may destroy data.)

Good luck on getting this fixed quickly.

[singjook.livejournal.com]

Not a techie, but just wanted to give you my sympathies! I've had a techie friend that will show up for emergencies only, but I don't have any resources.

BTW, I *have* noticed that Staples Superstores now advertise that they do repairs and stuff, but I've also seen similar (and evidently well integrated) services at CompUSA. They do require that you bring in the equipment and stuff, though.

Also, you reminded me I haven't backed up all summer. *eeps*