HELP - XP SP2 Hangs on COLD BOOT (Sorry, LONG)

[Kerry Brown]

And it is a sure bet you will get the usual bash for even having the
audacity to point out the audacity. Just watch the replies and see.
They are so predictable which rules out any of what you call common
sense.

Need I guess which one is so known for spitting venom when their master
M$ is questioned?

NIK

Does anybody even look at the headers let alone read the posts. I'll ask
again, which MVP even posted to this thread? Until Jupiter Jones posted
(well after Shooter's post) I don't see any posts from a MVP.

Kerry

 

[Guest]

Kerry -

An update. The printer is back. I was right, the printer problem was a
fallout of changing BIOS. The new BIOS was defaulted to turn parallel port
OFF. when I turned it back on (and reinstalled the printer drivers since I
didn't know which address it was originally set for in the old BIOS) the
printer came back.

Additional troubleshooting data. The only driver that was out of date was
the Intel Network driver. I installed the latest version with no joy. Then
I went into msconfig and set it for selective startup. I turned off
EVERYTHING and still the system will not come back from a shutdown. So it
would seem that, as I originally said, it is not a driver or hardware
problem. It is a primitive problem in SP2 with my MB, CPU or chipset. Given
that the MB is ASUS, a major manufacturer, and the CPU and chipset are both
Intel, it would seem that some level of compatibility testing could have been
done. I have an e-mail into ASUS. Maybe tomorrow I will try a debug startup
so I can see where the system hangs. There are no significant events in the
system event log.

I'm about out of ideas.

 

[Kerry Brown]

Kerry -

An update. The printer is back. I was right, the printer problem was a
fallout of changing BIOS. The new BIOS was defaulted to turn parallel
port
OFF. when I turned it back on (and reinstalled the printer drivers since
I
didn't know which address it was originally set for in the old BIOS) the
printer came back.

Additional troubleshooting data. The only driver that was out of date was
the Intel Network driver. I installed the latest version with no joy.
Then
I went into msconfig and set it for selective startup. I turned off
EVERYTHING and still the system will not come back from a shutdown. So it
would seem that, as I originally said, it is not a driver or hardware
problem. It is a primitive problem in SP2 with my MB, CPU or chipset.
Given
that the MB is ASUS, a major manufacturer, and the CPU and chipset are
both
Intel, it would seem that some level of compatibility testing could have
been
done. I have an e-mail into ASUS. Maybe tomorrow I will try a debug
startup
so I can see where the system hangs. There are no significant events in
the
system event log.

I'm about out of ideas.

Good luck, hope you get it figured out. Let us know what happens.

Kerry

 

[Leythos]

Additional troubleshooting data. The only driver that was out of date was
the Intel Network driver. I installed the latest version with no joy. Then
I went into msconfig and set it for selective startup. I turned off
EVERYTHING and still the system will not come back from a shutdown. So it
would seem that, as I originally said, it is not a driver or hardware
problem. It is a primitive problem in SP2 with my MB, CPU or chipset. Given
that the MB is ASUS, a major manufacturer, and the CPU and chipset are both
Intel, it would seem that some level of compatibility testing could have been
done. I have an e-mail into ASUS. Maybe tomorrow I will try a debug startup
so I can see where the system hangs. There are no significant events in the
system event log.

I'm about out of ideas.

Boot into safe mode, remove the device from the config (computer
management, device manager, uninstall), shutdown, remove the device
itself, boot system in safe mode - make sure device is not in device
manager again, reboot in normal mode.

Now, the device is no in your computer, go out and purchase a cheap (sub
$10) NIC from anywhere. Install it according to vendors instructions.

You could also try to put the old NIC back in, reboot, have it auto-
detect, but, DO NOT LET IT PICK THE DRIVER, manually pick the driver
from your new one you have.

Also, you might want to see if the "Intel Application Accelerator" needs
updated, I've seen this cause problems with older SP2 machines.

 

[Shooter]

And it is a sure bet you will get the usual bash for even having the
audacity to point out the audacity.

I wouldn't expect anything less. You did mention predictability,
didn't you?

Regards,

 

[health_wellness]

Ah, "Predictability", hallmark characteristic of a Clone. That's why
they are such fun to watch and even more fun to throw a bone now and
then to watch the "Predictable" reaction. You could make book on them
in Vegas.

NIK