S
Steve N.
I've been seeing several brand new and fairly new XP Pro sp1 machines
randomly go into reboot loops after login to Novell 6.5 (using latest
Novell client) and workstation login as Limited user and once the
problem starts it is very consistent. These machines were previously
working fine with no new software or unnecesary updates installed.
After several cold starts I can finally get to the desktop in Safe Mode
as an administrator and turn off Automatically Restart under startup and
recovery. If I then login to Novell and as Limited user I get consistent
BSODs (sorry I don't have the exact error at hand but is something like
"KERNEL_APC_PENDING_DURING_EXIT") indicating a device or driver issue
and the hex numbers change with each subsequent BSOD.
If then I do a Workstation Only login with admin rights I can get a
normal startup but I get between 5 and 7 "Windows has recovered from a
serious error" messages. I choose to send each report and get taken to
the OCA site which for the first several errors reports that a device
driver is at fault (no details), the final two OCA pages report problems
with a graphics driver (no further details). I have checked with the
manufacturer (SiS) for driver updates, these appear to be current.
I then schedule a disk check, which finds and corrects "minor
inconsistencies" and about 30 "unused index entries" and everything is
normal no matter how I login.
I do appreciate the effort MS has put into XP crash recovery and the
OCA, but this is damned silly. It is obvious that the file system errors
are the cause of the problem, not a device or driver problem since I
have verified that CHKDSK /F fixes the condition. What is damned silly
about it is the fact that I have to spend about 30 minutes barging my
way into the OS to fix a minor problem that the OS and file system
SHOULD be able to correct on its own and the fact that the OCA reports
are misleading, innacurate and virtually useless.
Even in Win9x a scandisk would automatically execute after a crash and
restart, and I've NEVER seen this sort of problem with Win2K Pro either.
Sorry folks, but Windows XP is NOT "the most stable version of
Windows..." and still half-baked at best when it comes to issues such as
this. Additionally, we do NOT need Windows to automatically restart the
damned PC by default to "protect" the system when a problem occurs, we
need to be able to get into the OS and determine what is wrong. It chaps
my @ss to no end that I have to jump through these flaming hoops JUST to
be able to fix a simple file system problem.
Steve
randomly go into reboot loops after login to Novell 6.5 (using latest
Novell client) and workstation login as Limited user and once the
problem starts it is very consistent. These machines were previously
working fine with no new software or unnecesary updates installed.
After several cold starts I can finally get to the desktop in Safe Mode
as an administrator and turn off Automatically Restart under startup and
recovery. If I then login to Novell and as Limited user I get consistent
BSODs (sorry I don't have the exact error at hand but is something like
"KERNEL_APC_PENDING_DURING_EXIT") indicating a device or driver issue
and the hex numbers change with each subsequent BSOD.
If then I do a Workstation Only login with admin rights I can get a
normal startup but I get between 5 and 7 "Windows has recovered from a
serious error" messages. I choose to send each report and get taken to
the OCA site which for the first several errors reports that a device
driver is at fault (no details), the final two OCA pages report problems
with a graphics driver (no further details). I have checked with the
manufacturer (SiS) for driver updates, these appear to be current.
I then schedule a disk check, which finds and corrects "minor
inconsistencies" and about 30 "unused index entries" and everything is
normal no matter how I login.
I do appreciate the effort MS has put into XP crash recovery and the
OCA, but this is damned silly. It is obvious that the file system errors
are the cause of the problem, not a device or driver problem since I
have verified that CHKDSK /F fixes the condition. What is damned silly
about it is the fact that I have to spend about 30 minutes barging my
way into the OS to fix a minor problem that the OS and file system
SHOULD be able to correct on its own and the fact that the OCA reports
are misleading, innacurate and virtually useless.
Even in Win9x a scandisk would automatically execute after a crash and
restart, and I've NEVER seen this sort of problem with Win2K Pro either.
Sorry folks, but Windows XP is NOT "the most stable version of
Windows..." and still half-baked at best when it comes to issues such as
this. Additionally, we do NOT need Windows to automatically restart the
damned PC by default to "protect" the system when a problem occurs, we
need to be able to get into the OS and determine what is wrong. It chaps
my @ss to no end that I have to jump through these flaming hoops JUST to
be able to fix a simple file system problem.
Steve