AMD64 Reboot Fix!

My original problem was that after installing SP2 and
rebooting, the reboot would crash and and endless reboot-
crash cycle would follow. I was able to boot into safe
mode, however, and use system restore to get back to my
previous working version of SP1 with little harm done.
The cycle can be broken by turning off the auto-reboot
feature in control panel*system*advanced. That allowed
me to see the "blue screen of death" that told me I had
error "stop:0X0000007E". Didn't mean much to me or to
the MS support tech I was emailing either. He was nice
but of little help. Turns out, my problem is that I have
some sort of driver/device/hardware that offends the new
DEP (Data Execution Prevention) "feature" enabled by SP2
on AMD64 systems (hard to understand as I have a 4 month
old PC with all the latest hardware, bios, drivers). NO
idea what the underlying problem is, but the workaround
is to disable DEP. Hey, it's not there under SP1 anyway
so there's no losing much. To fix this, you have to semi-
manually disable DEP. Here's what to do (you'll have to
do this under safe mode after installing SP2 - assuming
you can get there):
1. Open Control Panel
2. Go into System
3. Select Advanced Tab
4. Click Settings under Startup and Recover
5. Click Edit to edit the startup options file
6. On the last line, change:
from "NoExecute=OptIn"
to "NoExecute=AlwaysOff"
7. Save and close
8. Reboot
After doing that, I was able to fully boot into SP2 and
everything worked great. SP2 even recognized that I had
Zonealarm and agreed to use that and turn off the native
WinXP firewall - nice. My greatest quibble, again, is
that the "blue screen of death" didn't give me any useful
info as to what driver/hardware/etc. was causing the
problem in the first place. DEP is, potentially, a very
useful feature and it's bugging me that I had to turn it
off to get my system to boot. Note: I didn't include any
other hardware info on my system such as mobo, ram, etc.
because it's irrelivent. This is solely a
driver/hardware problem (as far as I can tell). Anyone
saying that SP2 WON'T work on AMD or a particular bios or
mobo or whatever with this particular problem is
misinformed. Please spread the word, I've seen a LOT of
posting all over the internet about this recurrent boot
problem and a lot of crazy assertions...
-BP

PS: I DID find one additional problem. Opening control
panel more than once caused an error screen to popup
telling me that there was a problem with "netsetup.pcl".
Annoying but nothing deadly - after ackowledging the
error, control panel opened fine. To fix this (copied
from a newsgroup somewhere after googling "netsetup.pcl"):

"Microsoft came thru with a solution via email. It seems
that at startup I was loading IPmon32 that apparently
caused the conflict. I disabled IPmon32 via msconfig and
do not have the netsetup.cpl error."

Worked for me...
-BP

"BP" wrote:

> My original problem was that after installing SP2 and
> rebooting, the reboot would crash and and endless reboot-
> crash cycle would follow. I was able to boot into safe
> mode, however, and use system restore to get back to my
> previous working version of SP1 with little harm done.
> The cycle can be broken by turning off the auto-reboot
> feature in control panel*system*advanced. That allowed
> me to see the "blue screen of death" that told me I had
> error "stop:0X0000007E". Didn't mean much to me or to
> the MS support tech I was emailing either. He was nice
> but of little help. Turns out, my problem is that I have
> some sort of driver/device/hardware that offends the new
> DEP (Data Execution Prevention) "feature" enabled by SP2
> on AMD64 systems (hard to understand as I have a 4 month
> old PC with all the latest hardware, bios, drivers). NO
> idea what the underlying problem is, but the workaround
> is to disable DEP. Hey, it's not there under SP1 anyway
> so there's no losing much. To fix this, you have to semi-
> manually disable DEP. Here's what to do (you'll have to
> do this under safe mode after installing SP2 - assuming
> you can get there):
> 1. Open Control Panel
> 2. Go into System
> 3. Select Advanced Tab
> 4. Click Settings under Startup and Recover
> 5. Click Edit to edit the startup options file
> 6. On the last line, change:
> from "NoExecute=OptIn"
> to "NoExecute=AlwaysOff"
> 7. Save and close
> 8. Reboot
> After doing that, I was able to fully boot into SP2 and
> everything worked great. SP2 even recognized that I had
> Zonealarm and agreed to use that and turn off the native
> WinXP firewall - nice. My greatest quibble, again, is
> that the "blue screen of death" didn't give me any useful
> info as to what driver/hardware/etc. was causing the
> problem in the first place. DEP is, potentially, a very
> useful feature and it's bugging me that I had to turn it
> off to get my system to boot. Note: I didn't include any
> other hardware info on my system such as mobo, ram, etc.
> because it's irrelivent. This is solely a
> driver/hardware problem (as far as I can tell). Anyone
> saying that SP2 WON'T work on AMD or a particular bios or
> mobo or whatever with this particular problem is
> misinformed. Please spread the word, I've seen a LOT of
> posting all over the internet about this recurrent boot
> problem and a lot of crazy assertions...
> -BP
>
> PS: I DID find one additional problem. Opening control
> panel more than once caused an error screen to popup
> telling me that there was a problem with "netsetup.pcl".
> Annoying but nothing deadly - after ackowledging the
> error, control panel opened fine. To fix this (copied
> from a newsgroup somewhere after googling "netsetup.pcl"):
>
> "Microsoft came thru with a solution via email. It seems
> that at startup I was loading IPmon32 that apparently
> caused the conflict. I disabled IPmon32 via msconfig and
> do not have the netsetup.cpl error."
>
> Worked for me...
> -BP
>

Hey BP I did what your said about the netsetup.cpl error and it worked
great!!!
Thanks for the tid bit
but I am wondering .............what does the IPmon32 do and if it is
disabled on startup is is gonna cause me a problem down the road?

If you can help let me know thanks


Paul

"superpt" wrote:

>
>
> "BP" wrote:
>
> > My original problem was that after installing SP2 and
> > rebooting, the reboot would crash and and endless reboot-
> > crash cycle would follow. I was able to boot into safe
> > mode, however, and use system restore to get back to my
> > previous working version of SP1 with little harm done.
> > The cycle can be broken by turning off the auto-reboot
> > feature in control panel*system*advanced. That allowed
> > me to see the "blue screen of death" that told me I had
> > error "stop:0X0000007E". Didn't mean much to me or to
> > the MS support tech I was emailing either. He was nice
> > but of little help. Turns out, my problem is that I have
> > some sort of driver/device/hardware that offends the new
> > DEP (Data Execution Prevention) "feature" enabled by SP2
> > on AMD64 systems (hard to understand as I have a 4 month
> > old PC with all the latest hardware, bios, drivers). NO
> > idea what the underlying problem is, but the workaround
> > is to disable DEP. Hey, it's not there under SP1 anyway
> > so there's no losing much. To fix this, you have to semi-
> > manually disable DEP. Here's what to do (you'll have to
> > do this under safe mode after installing SP2 - assuming
> > you can get there):
> > 1. Open Control Panel
> > 2. Go into System
> > 3. Select Advanced Tab
> > 4. Click Settings under Startup and Recover
> > 5. Click Edit to edit the startup options file
> > 6. On the last line, change:
> > from "NoExecute=OptIn"
> > to "NoExecute=AlwaysOff"
> > 7. Save and close
> > 8. Reboot
> > After doing that, I was able to fully boot into SP2 and
> > everything worked great. SP2 even recognized that I had
> > Zonealarm and agreed to use that and turn off the native
> > WinXP firewall - nice. My greatest quibble, again, is
> > that the "blue screen of death" didn't give me any useful
> > info as to what driver/hardware/etc. was causing the
> > problem in the first place. DEP is, potentially, a very
> > useful feature and it's bugging me that I had to turn it
> > off to get my system to boot. Note: I didn't include any
> > other hardware info on my system such as mobo, ram, etc.
> > because it's irrelivent. This is solely a
> > driver/hardware problem (as far as I can tell). Anyone
> > saying that SP2 WON'T work on AMD or a particular bios or
> > mobo or whatever with this particular problem is
> > misinformed. Please spread the word, I've seen a LOT of
> > posting all over the internet about this recurrent boot
> > problem and a lot of crazy assertions...
> > -BP
> >
> > PS: I DID find one additional problem. Opening control
> > panel more than once caused an error screen to popup
> > telling me that there was a problem with "netsetup.pcl".
> > Annoying but nothing deadly - after ackowledging the
> > error, control panel opened fine. To fix this (copied
> > from a newsgroup somewhere after googling "netsetup.pcl"):
> >
> > "Microsoft came thru with a solution via email. It seems
> > that at startup I was loading IPmon32 that apparently
> > caused the conflict. I disabled IPmon32 via msconfig and
> > do not have the netsetup.cpl error."
> >
> > Worked for me...
> > -BP
> >
>
> Hey BP I did what your said about the netsetup.cpl error and it worked
> great!!!
> Thanks for the tid bit
> but I am wondering .............what does the IPmon32 do and if it is
> disabled on startup is is gonna cause me a problem down the road?
>
> If you can help let me know thanks
>
>
> Paul


Oh and what all did Microsoft say in the e-mail they sent you?

Thanks again BP you came threw with bells on


Paul

"superpt" <> wrote in message
news:76347DE2-340B-4DD9-80C6-...
>
>
> "BP" wrote:
>
>> My original problem was that after installing SP2 and
>> rebooting, the reboot would crash and and endless reboot-
>> crash cycle would follow. I was able to boot into safe
>> mode, however, and use system restore to get back to my

SNIP


>> "Microsoft came thru with a solution via email. It seems
>> that at startup I was loading IPmon32 that apparently
>> caused the conflict. I disabled IPmon32 via msconfig and
>> do not have the netsetup.cpl error."
>>
>> Worked for me...
>> -BP
>>
>
> Hey BP I did what your said about the netsetup.cpl error and it worked
> great!!!
> Thanks for the tid bit
> but I am wondering .............what does the IPmon32 do and if it is
> disabled on startup is is gonna cause me a problem down the road?
>
> If you can help let me know thanks
>
>
> Paul

BP,

Thanks for going to the trouble to post this info.
I had posted yesterday 'SP2- data execution protection - help please',
and not had a reply.
here's my post >>>>>>>>>>

Having followed Jupiter Jones' excellent advice to prepare for SP2 update, I
did the update from Microsoft's CD.
My computer went into the 'restart loop' which I had read about, the only
device which I hadn't disconnected was my A4 Tech cordless optical mouse. It
appears to be this device which is causing my problem. If I try to boot with
it conected I get the restart loop, if I connect it whilst running XP (Home)
Windows crashes.
From here http://www3.telus.net/dandemar/xpsp2.htm I found Microsoft
KB 878474 and from the 2 'causes' given, I think I may need to disable DEP.
Being unsure though, can anyone confirm that this would be the correct thing
to do and that it would solve my mouse problem?
A 'contact us' message to A4 Tech has been returned 'undeliverable'
Thank you
dfrog
Having followed Jupiter Jones' excellent advice to prepare for SP2 update, I
did the update from Microsoft's CD.
My computer went into the 'restart loop' which I had read about, the only
device which I hadn't disconnected was my A4 Tech cordless optical mouse. It
appears to be this device which is causing my problem. If I try to boot with
it conected I get the restart loop, if I connect it whilst running XP (Home)
Windows crashes.
From here http://www3.telus.net/dandemar/xpsp2.htm I found Microsoft
KB 878474 and from the 2 'causes' given, I think I may need to disable DEP.
Being unsure though, can anyone confirm that this would be the correct thing
to do and that it would solve my mouse problem?
A 'contact us' message to A4 Tech has been returned 'undeliverable'
Thank you
dfrog
>
>
>
I didn't even know that DEP was something new! Your post gives me the
confidence to follow this through

dfrog