Re: sfc problems?
- From: "gregski" <gregski@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 Jan 2006 11:44:01 -0800
Thanks for the reply.
I've been using Device Manager and Event Viewer as my starting point. I
then update the video, audio, and nic drivers and resolve any unknown
devices. From there I try dissect the crash error codes and minidump files.
These are production desktops, so it's not easy getting a lot of time on
them. Getting users to run in safe mode really isn't an option.
Our software updates are downloaded and installed via a WSUS server on our
network. I test them first before approving the downloads. After that, they
are auto downloaded and installed. Workstation hardware varies, so I can't
cover all variables there during testing.
The crashes have slowed in the past few days, so we're getting there!
"Gerry Cornell" wrote:
> You might do best to troubleshoot a single or a strictly limited number of
> machines. The experience may help resolve all but you can better control
> what you have done and determine what measures work.
>
> Are the Stop Error messages occurring during the boot process, the
> Shutdown or otherwise? Is there a defined pattern?
>
> Some suggestions:
>
> 1. Turn off automatic restart whilst troubleshooting. That way you get the
> chance to record all Stop Error Messages.
>
> 2. Monitor all Warning and Error Reports in Event Viewer particularly
> those within a minute or so of the Stop Error message appearing.
>
> 3. Test to see if the Errors appear in Safe mode.
>
> 4. Check in Device Manager for yellow question marks.
>
> 5. Use sigverif to determine which drivers are unsigned ( this approach
> may get you too many drivers to check out ).
>
> 6. Post copies of full Error messages / Reports -partial reports invariably
> leave out bits others find helpful even if you do not.
>
> How have the latest Windows Updates been applied? Is it from a central
> source? Could there be a problem there?
>
> You could try uninstall the updates and reinstalling to the local machine
> and observe the effect.
>
> --
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
>
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
> "gregski" <gregski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:FB15D5DA-5A62-4AD3-AE97-A946072591F9@xxxxxxxxxxxxxxxx
> > Thanks for the reply.
> > No, there is no common hardware among them. The boxes are a mix of P3 and
> > P4's. Makes are IBM, Dell, and no-names we've assembled ourselves. The
> > other common software among them is VNC. Also, our WSUS only downloads
> > critical updates.
> > Any good guide out there for using windg? I think this is my best chance
> > for troubleshooting. I've downloaded XP SP2 retail symbols, but still get
> > many missing symbols when running windbg. Are there any more I can get?
> > Thanks!
> >
> > "Galen" wrote:
> >
> >> In news:F3653770-2194-4B29-8E0D-65950B0B5479@xxxxxxxxxxxxx,
>
>
>
.
- References:
- Re: sfc problems?
- From: Gerry Cornell
- Re: sfc problems?
- Prev by Date: Re: Windows XP Pro registry enteries
- Next by Date: Re: Can't access Task Manager
- Previous by thread: Re: sfc problems?
- Next by thread: Backups too
- Index(es):
Relevant Pages
|
Loading
