When I boot the computer I get "windows protection error"
after the windows splash screen. The bootlog.txt shows
everything loading successfully and the final line is
"Initializing kernel". I have been through article 273738
and followed the procedure up to checking for Protect Mode
Drivers, at which point I asked myself 'what will I do if
this is the case? I have spent 30+ hours debugging this
trying to isolate the problem. I will most likely have to
re-format/re-install anyway (YUCK!), so why not start now?'.

This had been a very happy system until I tried to remedy
the Norton Live Update fiasco. I took the system off the
'Net (unplugged cable). I have removed all Norton stuff
and ZoneAlarm (as there seemed to be some possible conflict
here). I ran a hard disk scan (from safe mode - there were
a lot of cross referenced files with those in _RESTORE) and
virus checking (from diskette - nothing found).

As I hate to 'fix' a problem before knowing what is causing
it, I am wondering if anyone has knowledge of what may be
causing the symptoms that I see, i.e., no error in
bootlog.txt but BSOD.

Re: bootlog.txt has no errors, but Windows doesn't start by Mike

Mike
Sun Feb 29 12:30:03 CST 2004

If you have lots of cross linked files then I feel that you may well not to be
able to get your system going without formatting the disk and reinstalling the
operating system. Have you run SCANDISK or CHKDSK from a DOS prompt after
booting from a floppy? What do they have to say about the state of your hard
disk? However since you appear to be able to boot to Safe Mode it is possible
you will be able to get the system going again, even if only long enough to
back up your data before formatting and reinstalling the operating system.

You won't get a fail entry if the system BSODs as the system will have crashed
before it can write any error log.

What happens if you boot to Safe Mode, open MSConfig and uncheck all of the
entries on the Startup tab? Can you now boot into Normal Mode? If still no
go try bringing up the boot menu when booting (gently tap Ctrl as you boot,
failing that try F8) and choose Selective Startup and see if by trial and
error you can determine the device driver that is perhaps causing you your
problems. If you can find this then you could try replacing it with a new
copy from the Win Me cab set.
--
Mike Maltby MS-MVP
mcmaltby@hotmail.com


CJBennett <anonymous@discussions.microsoft.com> wrote:

> When I boot the computer I get "windows protection error"
> after the windows splash screen. The bootlog.txt shows
> everything loading successfully and the final line is
> "Initializing kernel". I have been through article 273738
> and followed the procedure up to checking for Protect Mode
> Drivers, at which point I asked myself 'what will I do if
> this is the case? I have spent 30+ hours debugging this
> trying to isolate the problem. I will most likely have to
> re-format/re-install anyway (YUCK!), so why not start now?'.
>
> This had been a very happy system until I tried to remedy
> the Norton Live Update fiasco. I took the system off the
> 'Net (unplugged cable). I have removed all Norton stuff
> and ZoneAlarm (as there seemed to be some possible conflict
> here). I ran a hard disk scan (from safe mode - there were
> a lot of cross referenced files with those in _RESTORE) and
> virus checking (from diskette - nothing found).
>
> As I hate to 'fix' a problem before knowing what is causing
> it, I am wondering if anyone has knowledge of what may be
> causing the symptoms that I see, i.e., no error in
> bootlog.txt but BSOD.



Re: bootlog.txt has no errors, but Windows doesn't start by CJ

CJ
Sun Feb 29 16:36:36 CST 2004

Unchecking all the startup entries is 'boot option D' as I
recall and boot failed then too. I tried again and it
still failed. :(

Upon reflection, the last drivers I updated were for the
graphics adapter so on a lark (I mean, what else could go
wrong) I forced a re-install from Display Properties
(R-click, etc.). When I booted after that, it succeeded
albeit with nearly no startup entries active (I had left
startup unchecked from above and now the only ones checked
were NvMediaCenter, NvCplDaemon, nwiz, NVSvc - presumably
all NVIDIA stuff).

Although I am still not at "normal" mode I am slowly
bringing the system back online. Funny thing this. After
the boot following the reinstall, I went to change the
display settings (not enough space at 640x480x16) and the
best I could do was 1024x768x256. So I selected this.
After the NEXT reboot I was back to 1280x1024xmillions.
These are my ORIGINAL SETTINGS!

All I can figure now is that one of those cross-linked
files that I had scan 'clean up' was part of the graphics
adapter code.

Thanks to Mike M for such a quick response to my first post
and on a Sunday too.

Re: bootlog.txt has no errors, but Windows doesn't start by Mike

Mike
Sun Feb 29 16:52:58 CST 2004

Wow - that really is good news and I'm so pleased to read that you've managed
to recover your system without having to go through a reformat and uninstall.
Undoing the mess created by cross-linked files can be quite a chore and often
not at all successful.

Since earlier you mentioned cross linked files in he C:\_RESTORE folder may I
suggest you flush this folder and reset system restore so as to start clean.
You can do this as follows:
a) Boot to DOS using a floppy. Do NOT choose "Minimal Boot" from the menu
when booting from a floppy but rather choose "Start computer with (or without)
CD-ROM support" otherwise the ATTRIB command will not be available.
b) At the DOS A:\> prompt, type:

A:\> ATTRIB -H -S -R C:\_RESTORE
A:\> REN C:\_RESTORE OLDREST

c) Remove the floppy
d) Reboot your PC
e) Delete the folder C:\OLDREST
f) Check that an automatic system restore checkpoint was created.
g) Finally adjust the space allocated to the restore folder:
System | Performance | File System | Hard Disk and adjust the restore slider
to your preferred setting. A figure of 200MB is normally more than adequate
for day to day use allowing perhaps a week of checkpoints to be available
although increasing this to perhaps 400MB for a few days during periods of
large installs such Microsoft Office is advisable.


Finally you may want to carry out a quick test of system restore to check that
all is now OK;
a) Create a shortcut on your desktop to a file.
b) Create a manual checkpoint
c) Delete the shortcut
d) Restore you PC to the checkpoint you created.
Was the shortcut restored? Did you see any error messages?
--
Mike Maltby MS-MVP
mcmaltby@hotmail.com


CJ Bennett <anonymous@discussions.microsoft.com> wrote:

> Unchecking all the startup entries is 'boot option D' as I
> recall and boot failed then too. I tried again and it
> still failed. :(
>
> Upon reflection, the last drivers I updated were for the
> graphics adapter so on a lark (I mean, what else could go
> wrong) I forced a re-install from Display Properties
> (R-click, etc.). When I booted after that, it succeeded
> albeit with nearly no startup entries active (I had left
> startup unchecked from above and now the only ones checked
> were NvMediaCenter, NvCplDaemon, nwiz, NVSvc - presumably
> all NVIDIA stuff).
>
> Although I am still not at "normal" mode I am slowly
> bringing the system back online. Funny thing this. After
> the boot following the reinstall, I went to change the
> display settings (not enough space at 640x480x16) and the
> best I could do was 1024x768x256. So I selected this.
> After the NEXT reboot I was back to 1280x1024xmillions.
> These are my ORIGINAL SETTINGS!
>
> All I can figure now is that one of those cross-linked
> files that I had scan 'clean up' was part of the graphics
> adapter code.
>
> Thanks to Mike M for such a quick response to my first post
> and on a Sunday too.