FATAL EXCEPTION OE at 0167:BFF90223 is drivin' me nuts!!!!!

mcd007

Junior Member
Aug 21, 2000
4
0
0
Everytime I try to boot into win98SE i get this blue screen fatal exception OE at 0167:BFF90223. There is no file mentioned. I can get into safe mode and i went into MSCONFIG and did selective startup and unchecked everything and still got the message. I went as far as deleting everything in the win98 RUN folder in the registry but still no cigar. I have two memory dimms in my MB and i tried running each one on its own to see if that was the problem, but they weren't it. I have searched the web for my exact error and similar ones but haven't come up with anything. Anyone have any ideas? I just formatted last week and dont want to go through backing up again. TIA! :)
 

Slikkster

Diamond Member
Apr 29, 2000
3,141
0
0
Hi...I noticed a little typo that will cause you to have inadequate search results...it's actually fatal exception "Zero-E", vs. the letter "O". Nevertheless, there's still not a lot of info on your EXACT error. However, when you get the blue screen, it usually gives more info than just the address...it might look like gibberish, but it can be very helpful in trying to track down the problem. Please type out word-for-word the exact error message on the blue screen that comes up. Is there any mention of modules or vxd's? Are you running ZoneAlarm, by any chance?
 

mcd007

Junior Member
Aug 21, 2000
4
0
0
Slikkster: No there isn't any mention of VXD. its just the fatal error line and the statement the program will be terminated. I dont have zone alarm either. I tried Norton emergency virus scan but that didnt come up with anything. This thing is drivin' me up the wall!
 

Ryukumu

Senior member
Feb 23, 2001
397
0
0
I've been getting similar errors on boot-up on my Win98 system after I installed Nero. Oddly enough, nine out of ten times if you hit 'enter' the computer will continue booting up as normal and will otherwise function near-perfectly. As irritating and nerveracking as BSODs during bootup are, I'm going to try to live with this until something else breaks before I do a Windows reinstall, put it in the shop, or whatever I feel is the best course of action at the time.

PS: My BSOD errors don't mention any VXD files either, and the most common ones I get are 0157:0000663D and 0177:BFF83BEA. Again, it's easily remedied by just hitting the 'enter' key, as nine out of ten times the computer will finish booting normally.