Thanks for the offer to go over the logs. It was a 7E stop error. I have had them on occasion before and many times they just resolved themselves.
I have the crud today, so it may be a few days before I can get back to the home system. From: Ken Schaefer [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 19, 2008 19:23 PM To: NT System Admin Issues Subject: RE: Vista SP1 Rebooting problem? Hi, 0x7B is INACCESSIBLE_BOOT_DEVICE which is what ASB might be referring to But if you are seeing 0x7E then that's simply "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" which means that something running in kernel mode crashed, and there was no handler configured to deal with the resulting error. Get hold of the dump files that you should have (either memory.dmp or in c:\windows\minidump) and I'm happy to have a look for you. Cheers Ken From: Steve Kelsay [mailto:[EMAIL PROTECTED] Sent: Wednesday, 20 February 2008 6:10 AM To: NT System Admin Issues Subject: RE: Vista SP1 Rebooting problem? Thanks. That will give me a place to start when I re-apply the SP. All the other machines are paying nicely. From: ASB [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 19, 2008 12:28 PM To: NT System Admin Issues Subject: Re: Vista SP1 Rebooting problem? The 0x000007x series of STOP errors is typically drive or drive controller related. -- -ASB FAST, CHEAP, SECURE: Pick Any TWO ------------------------------------------------------------------------ ----------- http://Home.ASBzone.com/ http://www.linkedin.com/in/AndrewBaker ------------------------------------------------------------------------ ----------- On Feb 19, 2008 9:55 AM, Steve Kelsay <[EMAIL PROTECTED]> wrote: OK, I guess I am the only one with this problem, so I will make the presumption is NOT SP1 related. After installing SP! on several machines with no apparent problems, I had one that installed just fine, rebooted normally during the setup, then went into a continuous reboot mode after a day of running nicely. There was a stop 7E number that flashes by too fast to see, so some device driver is not quite right. Booting into Safe mode, and eventually uninstalling and rolling back to the pre-sp1 state fixed it. This is on a home network, with lots of test devices and playthings installed, so it is full of strange devices which could be causing the conflict. Not really looking for a solution, although that would be nice, but just posting in case it is more frequent than the current postings make it seem. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
