BSOD on start-up

Lately when I boot up I've been opening up to a BSOD with the message "A
fatal exception has occurred at 034F: 00000E07". At first I thought this was
an isolated event, but now it seems to be occurring fairly often.

I have no idea what the error message means, but since most of the problems
I experience on this machine (which really aren't very many) are
graphics-related, I seem to be able to fix things by going into safe mode
and rebooting with 16 colors and other minimal graphics settings, then
rebooting and selecting my normal settings, which would be 32 bit true
color, 1024x768 pixels, optimal refresh, and one less than full
acceleration. This description of the procedure may not be exactly accurate,
but I think it's basically correct.

The software/hardware is Windows 98SE, 512mb SDRAM, Athlon XP-2000 cpu,
nVidia GeForce2 MX/MX 400, and a Mitsubishi 21" CRT monitor.

I haven't played around with the nVidia settings because I don't know much
about them and, moreover, I haven't really proved that the problem is
graphics-related. Hopefully someone who understands the error message can
clear this up and help me get things back to normal.

I don't know. Does it all go away, if you suppress the Windows logo? Here is a way to edit MSDOS.sys. This is an important file.

(1) You won't even see it, unless "START, Settings, Folder Options, View
tab" is bolted "Show all files"; may as well uncheck "Hide file
extensions..." too.
(2) Find "C:\MSDOS.sys" and back it up. Call the backup MSDOS.bck, in
C:\.
(3) Then, R-Clk "C:\MSDOS.sys", Properties, and uncheck Read-Only.

(4) Open it in Notepad, &
(a) Put "Logo=0" in the [Options] section
This will suppress the logo & avoid "video mode switching" at boot.
(b) Save it & Exit Notepad

(5) Then, R-Clk MSDOS.sys again, and make it Read-Only. Reboot.
(6) Can't reboot? Then, in DOS, copy the backup over the one you've
mussed.
(a) ATTRIB -R -S -H C:\MSDOS.sys
(b) COPY C:\MSDOS.bck C:\MSDOS.sys
(c) ATTRIB +R +S +H C:\MSDOS.sys

NOTE: If you have a "C:\Winboot.ini", it will override MSDOS.sys,
though. So, check for that too. It has the same format/instruction set
as the other.

http://support.microsoft.com/kb/q118579/
Contents of the Windows Msdos.sys File


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Roger Fink" wrote in message ...
| Lately when I boot up I've been opening up to a BSOD with the message "A
| fatal exception has occurred at 034F: 00000E07". At first I thought this was
| an isolated event, but now it seems to be occurring fairly often.
|
| I have no idea what the error message means, but since most of the problems
| I experience on this machine (which really aren't very many) are
| graphics-related, I seem to be able to fix things by going into safe mode
| and rebooting with 16 colors and other minimal graphics settings, then
| rebooting and selecting my normal settings, which would be 32 bit true
| color, 1024x768 pixels, optimal refresh, and one less than full
| acceleration. This description of the procedure may not be exactly accurate,
| but I think it's basically correct.
|
| The software/hardware is Windows 98SE, 512mb SDRAM, Athlon XP-2000 cpu,
| nVidia GeForce2 MX/MX 400, and a Mitsubishi 21" CRT monitor.
|
| I haven't played around with the nVidia settings because I don't know much
| about them and, moreover, I haven't really proved that the problem is
| graphics-related. Hopefully someone who understands the error message can
| clear this up and help me get things back to normal.
|
|

Hi PCR and thanks for taking a shot at this.

I think I have a little more insight into the cause of the problem than I
did this a.m., although everything is still a total guess.

First, the Windows logo has been out of the boot sequence for quite awhile,
so that shouldn't be a factor. I think the problem has 1/2 to do with still
image monitor, which has always been problematic with this OS, or this
hardware, or both in combination. Since the particular scanner I have needs
stimon running to work, but since that occasionally causes problems in
Explorer when stimon is active but no scanning is going on, my solution was
to leave stimon unchecked in msconfig and activate it when I needed it,
which of course entails rebooting. This hasn't been a problem in the past
but about a week ago I changed my desktop to a graphic intensive photo image
(the awesome 920' high Millau Bridge with the clouds wafting below, by the
way) from a simple grayscale drawing I copped from Publisher 98. I just
hooked up the scanner a little while ago, and got the same BSOD as I got
this morning when I hooked it up, so I'm guessing it's a combination of the
new desktop and still image monitor that's doing it. Having Kerio, Spybot
Teatimer, and especially GoBack, in the startup group likely isn't helping
either.

Unless there is reason to suspect a corrupted Windows file, one that I could
identify (with help) and replace, I have a feeling I'm bumping up against
the limits of what is possible with this set-up.

It may just be a question of learning to peacefully coexist with your
ailments.


PCR wrote:
I don't know. Does it all go away, if you suppress the Windows logo?
Here is a way to edit MSDOS.sys. This is an important file.

(1) You won't even see it, unless "START, Settings, Folder Options,
View
tab" is bolted "Show all files"; may as well uncheck "Hide file
extensions..." too.
(2) Find "C:\MSDOS.sys" and back it up. Call the backup MSDOS.bck, in
C:\.
(3) Then, R-Clk "C:\MSDOS.sys", Properties, and uncheck Read-Only.

(4) Open it in Notepad, &
(a) Put "Logo=0" in the [Options] section
This will suppress the logo & avoid "video mode
switching" at boot.
(b) Save it & Exit Notepad

(5) Then, R-Clk MSDOS.sys again, and make it Read-Only. Reboot.
(6) Can't reboot? Then, in DOS, copy the backup over the one you've
mussed.
(a) ATTRIB -R -S -H C:\MSDOS.sys
(b) COPY C:\MSDOS.bck C:\MSDOS.sys
(c) ATTRIB +R +S +H C:\MSDOS.sys

NOTE: If you have a "C:\Winboot.ini", it will override MSDOS.sys,
though. So, check for that too. It has the same format/instruction set
as the other.

http://support.microsoft.com/kb/q118579/
Contents of the Windows Msdos.sys File


Lately when I boot up I've been opening up to a BSOD with the
message "A
fatal exception has occurred at 034F: 00000E07". At first I thought
this was
an isolated event, but now it seems to be occurring fairly often.

I have no idea what the error message means, but since most of the
problems
I experience on this machine (which really aren't very many) are
graphics-related, I seem to be able to fix things by going into safe
mode
and rebooting with 16 colors and other minimal graphics settings,
then
rebooting and selecting my normal settings, which would be 32 bit
true
color, 1024x768 pixels, optimal refresh, and one less than full
acceleration. This description of the procedure may not be exactly
accurate,
but I think it's basically correct.

The software/hardware is Windows 98SE, 512mb SDRAM, Athlon XP-2000
cpu,
nVidia GeForce2 MX/MX 400, and a Mitsubishi 21" CRT monitor.

I haven't played around with the nVidia settings because I don't
know much
about them and, moreover, I haven't really proved that the problem is
graphics-related. Hopefully someone who understands the error
message can
clear this up and help me get things back to normal.

On Sun, 16 Apr 2006 12:16:23 -0400, "Roger Fink"
wrote:

Lately when I boot up I've been opening up to a BSOD with the message "A
fatal exception has occurred at 034F: 00000E07". At first I thought this was
an isolated event, but now it seems to be occurring fairly often.

I have no idea what the error message means, but since most of the problems
I experience on this machine (which really aren't very many) are
graphics-related, I seem to be able to fix things by going into safe mode
and rebooting with 16 colors and other minimal graphics settings, then
rebooting and selecting my normal settings, which would be 32 bit true
color, 1024x768 pixels, optimal refresh, and one less than full
acceleration. This description of the procedure may not be exactly accurate,
but I think it's basically correct.

The software/hardware is Windows 98SE, 512mb SDRAM, Athlon XP-2000 cpu,
nVidia GeForce2 MX/MX 400, and a Mitsubishi 21" CRT monitor.

I haven't played around with the nVidia settings because I don't know much
about them and, moreover, I haven't really proved that the problem is
graphics-related. Hopefully someone who understands the error message can
clear this up and help me get things back to normal.

Roger,

Try this:
Boot to the Dos Start Menu and select Logged Boot. Then look at the
Bootlog.txt file in the root. The last few lines may tell you where
the boot stopped. Do this until you get the BSOD. Then get back into
Windows and copy/paste the last 5 lines into a reply here.

There will be another file, Bootlog.prv there, it's a copy of the
previous Bootlog.txt file. If the Bootlog.txt file was created with
the BSOD and the next one with a good boot, or visa-versa then
comparing the Bootlog.txt file with the Bootlog.prv file may provide
good information.

There will probably be some "Load Fails" for some devices you don't
have installed and that is normal.

Regards,

Bill Watt
Win98 Computer Help & Other Information http://home.ptd.net/~bwatt/


Regards,

Bill Watt
Win98 Computer Help & Other Information http://home.ptd.net/~bwatt/

I'll second Watt's suggestion, then, although Bootlog.txt is a monstrosity...

http://www.aumha.org/a/bootlog.htm Bootlog Analyzer
You will need to do a logged boot, by selecting it from the Startup
Menu. Turn that on at "START button, Run, MSConfig, Advanced button".
Or, hold CTRL as you boot for the Startup Menu. Remember,
"C:\Bootlog.txt" is only generated freshly when a new Logged Boot is
done. A backup of the prior one is put into "C:\Bootlog.prv".

http://support.microsoft.com/support.../q127/9/70.asp Bootlog
failures

Ensure you are looking a current "Bootlog.txt" file. Remember a new one is only generated when a new Logged Boot is done. You have to select it from the Startup Menu each time (or code it into MSDOS.sys).

.......Quote Troubleshooter screen.....
Is the problem listed in the Bootlog.txt file?

To pinpoint the problem in the Bootlog.txt file

1. Use any text editor, such as Notepad, to examine the Bootlog.txt file for Terminate= entries. These entries are located at the end of the file and may provide clues to the cause of the problem.

2. For each Terminate= entry, find a matching EndTerminate= entry.

+ If the last line in the Bootlog.txt file is EndTerminate=KERNEL, Windows 98 shut down successfully.

+ If the last line in the Bootlog.txt file is one of the following entries, check the listed possible cause:

Last line Possible cause
===================== =====================================
Terminate=Query Drivers Memory manager problem.
Terminate=Unload Network Conflict with real-mode network driver
in the Config.sys file.
Terminate=Reset Display Video shadowing may need to be disabled.
May also need an updated video driver.
Terminate=RIT Timer-related problems with the sound card
or an old mouse driver.
Terminate=Win32 Problem with a 32-bit program blocking a thread.
......EOQ Troubleshooter screen........


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Roger Fink" wrote in message ...
| Hi PCR and thanks for taking a shot at this.
|
| I think I have a little more insight into the cause of the problem than I
| did this a.m., although everything is still a total guess.
|
| First, the Windows logo has been out of the boot sequence for quite awhile,
| so that shouldn't be a factor. I think the problem has 1/2 to do with still
| image monitor, which has always been problematic with this OS, or this
| hardware, or both in combination. Since the particular scanner I have needs
| stimon running to work, but since that occasionally causes problems in
| Explorer when stimon is active but no scanning is going on, my solution was
| to leave stimon unchecked in msconfig and activate it when I needed it,
| which of course entails rebooting. This hasn't been a problem in the past
| but about a week ago I changed my desktop to a graphic intensive photo image
| (the awesome 920' high Millau Bridge with the clouds wafting below, by the
| way) from a simple grayscale drawing I copped from Publisher 98. I just
| hooked up the scanner a little while ago, and got the same BSOD as I got
| this morning when I hooked it up, so I'm guessing it's a combination of the
| new desktop and still image monitor that's doing it. Having Kerio, Spybot
| Teatimer, and especially GoBack, in the startup group likely isn't helping
| either.
|
| Unless there is reason to suspect a corrupted Windows file, one that I could
| identify (with help) and replace, I have a feeling I'm bumping up against
| the limits of what is possible with this set-up.
|
| It may just be a question of learning to peacefully coexist with your
| ailments.
|
|
| PCR wrote:
| I don't know. Does it all go away, if you suppress the Windows logo?
| Here is a way to edit MSDOS.sys. This is an important file.
|
| (1) You won't even see it, unless "START, Settings, Folder Options,
| View
| tab" is bolted "Show all files"; may as well uncheck "Hide file
| extensions..." too.
| (2) Find "C:\MSDOS.sys" and back it up. Call the backup MSDOS.bck, in
| C:\.
| (3) Then, R-Clk "C:\MSDOS.sys", Properties, and uncheck Read-Only.
|
| (4) Open it in Notepad, &
| (a) Put "Logo=0" in the [Options] section
| This will suppress the logo & avoid "video mode
| switching" at boot.
| (b) Save it & Exit Notepad
|
| (5) Then, R-Clk MSDOS.sys again, and make it Read-Only. Reboot.
| (6) Can't reboot? Then, in DOS, copy the backup over the one you've
| mussed.
| (a) ATTRIB -R -S -H C:\MSDOS.sys
| (b) COPY C:\MSDOS.bck C:\MSDOS.sys
| (c) ATTRIB +R +S +H C:\MSDOS.sys
|
| NOTE: If you have a "C:\Winboot.ini", it will override MSDOS.sys,
| though. So, check for that too. It has the same format/instruction set
| as the other.
|
| http://support.microsoft.com/kb/q118579/
| Contents of the Windows Msdos.sys File
|
|
| Lately when I boot up I've been opening up to a BSOD with the
| message "A
| fatal exception has occurred at 034F: 00000E07". At first I thought
| this was
| an isolated event, but now it seems to be occurring fairly often.
|
| I have no idea what the error message means, but since most of the
| problems
| I experience on this machine (which really aren't very many) are
| graphics-related, I seem to be able to fix things by going into safe
| mode
| and rebooting with 16 colors and other minimal graphics settings,
| then
| rebooting and selecting my normal settings, which would be 32 bit
| true
| color, 1024x768 pixels, optimal refresh, and one less than full
| acceleration. This description of the procedure may not be exactly
| accurate,
| but I think it's basically correct.
|
| The software/hardware is Windows 98SE, 512mb SDRAM, Athlon XP-2000
| cpu,
| nVidia GeForce2 MX/MX 400, and a Mitsubishi 21" CRT monitor.
|
| I haven't played around with the nVidia settings because I don't
| know much
| about them and, moreover, I haven't really proved that the problem is
| graphics-related. Hopefully someone who understands the error
| message can
| clear this up and help me get things back to normal.
|
|

For occasional failed boots, maybe try a Scandisk (Thorough, usually w/o write testing) & a Defrag. Don't let them constantly restart, though, you know.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Roger Fink" wrote in message ...
| Hi PCR and thanks for taking a shot at this.
|
| I think I have a little more insight into the cause of the problem than I
| did this a.m., although everything is still a total guess.
|
| First, the Windows logo has been out of the boot sequence for quite awhile,
| so that shouldn't be a factor. I think the problem has 1/2 to do with still
| image monitor, which has always been problematic with this OS, or this
| hardware, or both in combination. Since the particular scanner I have needs
| stimon running to work, but since that occasionally causes problems in
| Explorer when stimon is active but no scanning is going on, my solution was
| to leave stimon unchecked in msconfig and activate it when I needed it,
| which of course entails rebooting. This hasn't been a problem in the past
| but about a week ago I changed my desktop to a graphic intensive photo image
| (the awesome 920' high Millau Bridge with the clouds wafting below, by the
| way) from a simple grayscale drawing I copped from Publisher 98. I just
| hooked up the scanner a little while ago, and got the same BSOD as I got
| this morning when I hooked it up, so I'm guessing it's a combination of the
| new desktop and still image monitor that's doing it. Having Kerio, Spybot
| Teatimer, and especially GoBack, in the startup group likely isn't helping
| either.
|
| Unless there is reason to suspect a corrupted Windows file, one that I could
| identify (with help) and replace, I have a feeling I'm bumping up against
| the limits of what is possible with this set-up.
|
| It may just be a question of learning to peacefully coexist with your
| ailments.
|
|
| PCR wrote:
| I don't know. Does it all go away, if you suppress the Windows logo?
| Here is a way to edit MSDOS.sys. This is an important file.
|
| (1) You won't even see it, unless "START, Settings, Folder Options,
| View
| tab" is bolted "Show all files"; may as well uncheck "Hide file
| extensions..." too.
| (2) Find "C:\MSDOS.sys" and back it up. Call the backup MSDOS.bck, in
| C:\.
| (3) Then, R-Clk "C:\MSDOS.sys", Properties, and uncheck Read-Only.
|
| (4) Open it in Notepad, &
| (a) Put "Logo=0" in the [Options] section
| This will suppress the logo & avoid "video mode
| switching" at boot.
| (b) Save it & Exit Notepad
|
| (5) Then, R-Clk MSDOS.sys again, and make it Read-Only. Reboot.
| (6) Can't reboot? Then, in DOS, copy the backup over the one you've
| mussed.
| (a) ATTRIB -R -S -H C:\MSDOS.sys
| (b) COPY C:\MSDOS.bck C:\MSDOS.sys
| (c) ATTRIB +R +S +H C:\MSDOS.sys
|
| NOTE: If you have a "C:\Winboot.ini", it will override MSDOS.sys,
| though. So, check for that too. It has the same format/instruction set
| as the other.
|
| http://support.microsoft.com/kb/q118579/
| Contents of the Windows Msdos.sys File
|
|
| Lately when I boot up I've been opening up to a BSOD with the
| message "A
| fatal exception has occurred at 034F: 00000E07". At first I thought
| this was
| an isolated event, but now it seems to be occurring fairly often.
|
| I have no idea what the error message means, but since most of the
| problems
| I experience on this machine (which really aren't very many) are
| graphics-related, I seem to be able to fix things by going into safe
| mode
| and rebooting with 16 colors and other minimal graphics settings,
| then
| rebooting and selecting my normal settings, which would be 32 bit
| true
| color, 1024x768 pixels, optimal refresh, and one less than full
| acceleration. This description of the procedure may not be exactly
| accurate,
| but I think it's basically correct.
|
| The software/hardware is Windows 98SE, 512mb SDRAM, Athlon XP-2000
| cpu,
| nVidia GeForce2 MX/MX 400, and a Mitsubishi 21" CRT monitor.
|
| I haven't played around with the nVidia settings because I don't
| know much
| about them and, moreover, I haven't really proved that the problem is
| graphics-related. Hopefully someone who understands the error
| message can
| clear this up and help me get things back to normal.
|
|

Bill Watt wrote:
On Sun, 16 Apr 2006 12:16:23 -0400, "Roger Fink"
wrote:

Lately when I boot up I've been opening up to a BSOD with the
message "A fatal exception has occurred at 034F: 00000E07". At first
I thought this was an isolated event, but now it seems to be
occurring fairly often.

I have no idea what the error message means, but since most of the
problems I experience on this machine (which really aren't very
many) are graphics-related, I seem to be able to fix things by going
into safe mode and rebooting with 16 colors and other minimal
graphics settings, then rebooting and selecting my normal settings,
which would be 32 bit true color, 1024x768 pixels, optimal refresh,
and one less than full acceleration. This description of the
procedure may not be exactly accurate, but I think it's basically
correct.

The software/hardware is Windows 98SE, 512mb SDRAM, Athlon XP-2000
cpu, nVidia GeForce2 MX/MX 400, and a Mitsubishi 21" CRT monitor.

I haven't played around with the nVidia settings because I don't
know much about them and, moreover, I haven't really proved that the
problem is graphics-related. Hopefully someone who understands the
error message can clear this up and help me get things back to
normal.

Roger,

Try this:
Boot to the Dos Start Menu and select Logged Boot. Then look at the
Bootlog.txt file in the root. The last few lines may tell you where
the boot stopped. Do this until you get the BSOD. Then get back into
Windows and copy/paste the last 5 lines into a reply here.

There will be another file, Bootlog.prv there, it's a copy of the
previous Bootlog.txt file. If the Bootlog.txt file was created with
the BSOD and the next one with a good boot, or visa-versa then
comparing the Bootlog.txt file with the Bootlog.prv file may provide
good information.

There will probably be some "Load Fails" for some devices you don't
have installed and that is normal.

Regards,

Bill Watt
Win98 Computer Help & Other Information http://home.ptd.net/~bwatt/


Regards,

Bill Watt
Win98 Computer Help & Other Information http://home.ptd.net/~bwatt/

Bill, thanks for that very informative post, which looks like a good place
to begin in approaching this analytically. The BSOD problem is still there,
even after unchecking stimon, but now seems to be confined to first bootup
in the morning, and furthermore no razzle-dazzle is required on my part to
fix it - I just accept safe mode on reboot and then restart and things are
back to normal. Unfortunately, you've got me wading through totally foreign
territory here. I fully intend to follow through, but given some of the
other things I'm dealing with right now and what I'd be getting into I can't
give it the time it deserves right now. I've saved the thread and will post
back in a new thread flagged to you and PCR. Sorry, but it's the best I can
do at the moment.

You are welcome. Take your time. Keep us informed, especially him.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Roger Fink" wrote in message ...
| Bill Watt wrote:
| On Sun, 16 Apr 2006 12:16:23 -0400, "Roger Fink"
| wrote:
|
| Lately when I boot up I've been opening up to a BSOD with the
| message "A fatal exception has occurred at 034F: 00000E07". At first
| I thought this was an isolated event, but now it seems to be
| occurring fairly often.
|
| I have no idea what the error message means, but since most of the
| problems I experience on this machine (which really aren't very
| many) are graphics-related, I seem to be able to fix things by going
| into safe mode and rebooting with 16 colors and other minimal
| graphics settings, then rebooting and selecting my normal settings,
| which would be 32 bit true color, 1024x768 pixels, optimal refresh,
| and one less than full acceleration. This description of the
| procedure may not be exactly accurate, but I think it's basically
| correct.
|
| The software/hardware is Windows 98SE, 512mb SDRAM, Athlon XP-2000
| cpu, nVidia GeForce2 MX/MX 400, and a Mitsubishi 21" CRT monitor.
|
| I haven't played around with the nVidia settings because I don't
| know much about them and, moreover, I haven't really proved that the
| problem is graphics-related. Hopefully someone who understands the
| error message can clear this up and help me get things back to
| normal.
|
| Roger,
|
| Try this:
| Boot to the Dos Start Menu and select Logged Boot. Then look at the
| Bootlog.txt file in the root. The last few lines may tell you where
| the boot stopped. Do this until you get the BSOD. Then get back into
| Windows and copy/paste the last 5 lines into a reply here.
|
| There will be another file, Bootlog.prv there, it's a copy of the
| previous Bootlog.txt file. If the Bootlog.txt file was created with
| the BSOD and the next one with a good boot, or visa-versa then
| comparing the Bootlog.txt file with the Bootlog.prv file may provide
| good information.
|
| There will probably be some "Load Fails" for some devices you don't
| have installed and that is normal.
|
| Regards,
|
| Bill Watt
| Win98 Computer Help & Other Information http://home.ptd.net/~bwatt/
|
|
| Regards,
|
| Bill Watt
| Win98 Computer Help & Other Information http://home.ptd.net/~bwatt/
|
| Bill, thanks for that very informative post, which looks like a good place
| to begin in approaching this analytically. The BSOD problem is still there,
| even after unchecking stimon, but now seems to be confined to first bootup
| in the morning, and furthermore no razzle-dazzle is required on my part to
| fix it - I just accept safe mode on reboot and then restart and things are
| back to normal. Unfortunately, you've got me wading through totally foreign
| territory here. I fully intend to follow through, but given some of the
| other things I'm dealing with right now and what I'd be getting into I can't
| give it the time it deserves right now. I've saved the thread and will post
| back in a new thread flagged to you and PCR. Sorry, but it's the best I can
| do at the moment.
|
|