Has this ever happened? Win 98

[tlmm]

I formatted a computer for someone and when I dropped it off, it worked fine.

Now they say they're getting an error:

Windows Protection Error
Press any key to restart

I haven't looked at it yet, so these are all the details that they could give me.

Thanks!

 

[Grenage]

Yes I've seen this a few times before. Have a read through Q149962

 

[DaveGoTech]

Windows Protection Errors can be caused by many things, such as an address conflict, registry corruption, bad/incompatible menory, CMOS settings, incorrect device drivers or a defective motherboard. A good place to start is to check Windows Control Panel, System, Device Manager.

 

[tlmm]

From what they are telling me, it doesn't seem as if they can start the computer. How will I be able to get to Control Panel.

 

[tlmm]

I just got more details about what is happening from the owner. This is the error:

Windows protection error, You need to restart your computer

It's now safe to turn off your computer

Microsoft windows 98 startup menu

1. Normal
2. logged
3. Safe mode (Which is highlighted)
4.
5.
(Keeps defaulting back to safe mode.)

Then you get a warning: Windows is running in safe mode.:
This special diagnostic mode of windows enables you to fix the problem that is keeping you from starting windows normally. The problem could caused by your network or hardware stiings. Make sure these ettings are corret in control panel, then restart windows again. For more information, see the trouble shooting guide in help. While in safe mode, some of your devices may not be available.

Any ideas? I will be looking at it later today or tomorrow and will check device manager.

Thanks.

 

[wolluf]

I'd start by disconnecting (or disabling in bios if onboard) as many hardware items as possible (and still be able to use 98) - sound. modem, network cards, CD/DVD drives, printer/scaneer, zip drivers etc. If it boots ok, connect them one at a time (to try to isolate possible culprit).

 

[edfair]

And zero length config.sys and autoexec.bat.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[Michael42]

I had this error too with an AMD K5 CPU. There was actually a patch created by Microsoft (on their site) that I used to fix it.

I believe it was listed as a bug with MS working with the AMD K5 chip.

Hope this helps,

Michael42

 

[tlmm]

Just a couple questions:

1. Do I physically disable the hardware items or just disable in device manager?

2. Zero length config.sys and autoexec.bat - does that mean set to '0'?

I know it's an AMD, so I'll have chekc out exactly what processor.

Thanks and I'll post back after I look at the computer this weekend.

 

[edfair]

Basically, rename config.sys and autoexec.bat to something else for the duration to eliminate anything loading from there that might be causing the problem.
Not likely, but I've run across it once or twice. Anything critical that normally loads thru either of them has another path for loading thru the OS if it isn't loaded in these two files.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[tlmm]

I just want to make sure I understand this correctly:

I should rename the two files and restart the computer to see if the error still exists. If it doesn't, can I tell what is causing the problem by looking at either of these files?

If that is not causing it, where do I go from there? I may be getting ahead of myself!

Thanks again.

 

[wolluf]

'I should rename the two files and restart the computer to see if the error still exists' - yes

'If it doesn't, can I tell what is causing the problem by looking at either of these files?' - probably (they look something like this after install (in UK)):-

Autoexec.bat

mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,C:\WINDOWS\COMMAND\keyboard.sys

Config.sys

device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
Country=044,850,C:\WINDOWS\COMMAND\country.sys

If there are any other entries, you can comment them out (type REM followed by a space at the beginning of the line) - so you could could comment them all out then reinstate them one at a time.

On the hardware side - physically disconnect actual devices (like sound cards, CD/DVD drives etc) and if functionality in 'onboard' ie, integrated into the motherboard, go into the bios settings, find the settings for the sound, network or whatever, and disable them there. POST screen (when machines boots) usually tells you which key(s) to press to access the bios settings.

If it now boots, reconnect one at a time.

If none of this gets you further forward, please post back for more suggestions.

 

[edfair]

You could do a google search for "windows protection error" and get a whole series of possible solutions along with a link to the MS KB article that is the definitive answer. (as much as MS has the definitive answer).
The autoexec and config changes were to eliminate possible driver conflicts, but there are others possible, within system.ini for one that I can remember.
Wolluf's UK example holds for the UK or somebody who is anglophiling, US generally is empty, depending on what has been added or how the OS was installed. But there are lots of them that have redundent stuff listed.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[swayda]

When you get your start menu you will have an option to load device drivers step by step. Try that and see if loading one of the device drivers gives you that message. Then you may have to relce the driver. At least give it a try, it may point you in the right direction. If you receive no error message then you will at least kno it's not a driver problem but maybe hardware related.

Don Swayser
swayser@optonline.net

 

[mradmin]

Hi, just to add to your troubleshooting list: don't forget external peripheral devices. I've seen this with Win98 and certain Canon printers (connected to parallel port) and a parallel port Zip drive (on the same port). So disconnect them, too, as you test. good luck,

---Will

 

[tlmm]

Thanks to everyone for their help.

I tried all the solutions you gave me and others that I found, but that error would not go away. I decided that the best thing to do would be format the computer again.