C
Chad Harris
I'm on an XP Pro SP2 box. This is the kind of problem--the fix for my
non-descript stop error -- you wish you could have Kelly and Ramesh sitting
at your box to grapple with.
What I want to ask is since installations were causing the crash and I had
to go to Safe Mode to install a Mouse driver and to get XP SP2 installed
back to the XP SP1 box I had when I repaired with an XP SP1 CD. I was able
to do this but I always thought that the MSI did not load in safe mode. And
for good reason. I went into safe mode to install a couple other apps and
up pops a big box MSI not availalbe in Safe Mode. So I understand that
Emerson said "consistency is the hobgoblin of little minds" and Redmond
takes this literally. If one does an msiexec command in the run box then
the MSI info comes up in safe mode.
I had a CX04 crash that was keeping me from booting to Windows so I did a
repair install and actually had to repeat it X3.
The error was:
Stop Error: 0x000000c4
(0x00000090,0xFFDFF120,0x00000000,0x00000000)
and the text of the BSOD was your PC is being shut down because of a corrupt
driver. I'm not asking for help with that now. I'm going to put that up in
a separate post because after a week of "research" I think the solution is
complicated and not well handled by MSFT at Redmond nor by Symantec at
Cupertion and Oregon.
Since there are 160 kernel stack drivers on a driverquery cmd and using
Driver Verifier is a byzantine convoluted mish mosh of steps to say the
least, this stop error like many from MSFT is of little help. This
statement is supported by reading the following links ( the first is my
error; the second is close). Reading the KB that warns before lol you use
the Driver Verifier tool is also a sign that a fix and its definition is
dicey to say the least.
The answer may be by adlibbing from the info below and simply (time will
tell)
*On Windows NT 4 and Windows 2000 workstations, changing the REG_DWORD value
for "Start" to 4 for the following registry key reportedly solves the
problem:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NAVAP****
http://www.osronline.com/showThread.cfm?link=42909
http://support.microsoft.com/default.aspx?scid=kb;en-us;325672
http://service1.symantec.com/SUPPOR...88256a220026aa4d?OpenDocument&src=bar_sch_nam
Best,
Chad Harris
non-descript stop error -- you wish you could have Kelly and Ramesh sitting
at your box to grapple with.
What I want to ask is since installations were causing the crash and I had
to go to Safe Mode to install a Mouse driver and to get XP SP2 installed
back to the XP SP1 box I had when I repaired with an XP SP1 CD. I was able
to do this but I always thought that the MSI did not load in safe mode. And
for good reason. I went into safe mode to install a couple other apps and
up pops a big box MSI not availalbe in Safe Mode. So I understand that
Emerson said "consistency is the hobgoblin of little minds" and Redmond
takes this literally. If one does an msiexec command in the run box then
the MSI info comes up in safe mode.
I had a CX04 crash that was keeping me from booting to Windows so I did a
repair install and actually had to repeat it X3.
The error was:
Stop Error: 0x000000c4
(0x00000090,0xFFDFF120,0x00000000,0x00000000)
and the text of the BSOD was your PC is being shut down because of a corrupt
driver. I'm not asking for help with that now. I'm going to put that up in
a separate post because after a week of "research" I think the solution is
complicated and not well handled by MSFT at Redmond nor by Symantec at
Cupertion and Oregon.
Since there are 160 kernel stack drivers on a driverquery cmd and using
Driver Verifier is a byzantine convoluted mish mosh of steps to say the
least, this stop error like many from MSFT is of little help. This
statement is supported by reading the following links ( the first is my
error; the second is close). Reading the KB that warns before lol you use
the Driver Verifier tool is also a sign that a fix and its definition is
dicey to say the least.
The answer may be by adlibbing from the info below and simply (time will
tell)
*On Windows NT 4 and Windows 2000 workstations, changing the REG_DWORD value
for "Start" to 4 for the following registry key reportedly solves the
problem:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NAVAP****
http://www.osronline.com/showThread.cfm?link=42909
http://support.microsoft.com/default.aspx?scid=kb;en-us;325672
http://service1.symantec.com/SUPPOR...88256a220026aa4d?OpenDocument&src=bar_sch_nam
Best,
Chad Harris