Re: Systemabsturz im SBS mit Fehler 1003 Kat. 102

Vielleicht ein "Stromproblem"? Versuche mal eine andre Verteilerdose.



"Tobias Redelberger" schrieb:

> Hi,
>
> hier ein kurzer Abriß der Ergebnisse:
>
> > Ereignistyp: Fehler
> > Ereignisquelle: System Error
> > Ereigniskategorie: (102)
> > Ereigniskennung: 1003
> > Datum: 23.10.2005
> > Zeit: 16:29:34
> > Benutzer: Nicht zutreffend
> > Computer: SERVERDC1
> > Beschreibung:
> > Fehlercode 0000007f, 1. Parameter 0000000d, 2. Parameter 00000000, 3.
> > Parameter 00000000, 4. Parameter 00000000.
>
> -> Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP
>
> Parameters
> The first parameter displayed on the blue screen specifies the trap number.
> [..]
> 0x0000000D - An exception not covered by some other exception; a protection
> fault that pertains to access violations for applications
> [..]
> Cause
> Bug check 0x7F usually occurs after the installation of faulty or mismatched
> hardware (especially memory) or in the event that installed hardware fails.
> [..]
> Troubleshooting: If hardware was recently added to the system, remove it to
> see if the error recurs. If existing hardware has failed, remove or replace
> the faulty component. Run hardware diagnostics supplied by the system
> manufacturer, to determine which hardware component has failed. The memory
> scanner is especially important; faulty or mismatched memory can cause this
> bug check. For details on these procedures, see the owner's manual for your
> computer. Check that all adapter cards in the computer are properly seated.
> Use an ink eraser or an electrical contact treatment, available at
> electronics supply stores, to ensure adapter card contacts are clean.
>
> If the error appears on a newly installed system, check the availability of
> updates for the BIOS, the SCSI controller or network cards. Updates of this
> kind are typically available on the Web site or BBS of the hardware
> manufacturer.
>
> Confirm that all hard disks, hard disk controllers, and SCSI adapters are
> listed in the Microsoft Windows Catalog.
>
> If the error occurred after the installation of a new or updated device
> driver, the driver should be removed or replaced. If, under this
> circumstance, the error occurs during the startup sequence and the system
> partition is formatted with NTFS, you might be able to use Safe Mode to
> rename or delete the faulty driver. If the driver is used as part of the
> system startup process in Safe Mode, you need to start the computer using
> the Recovery Console in order to access the file. Also try restarting your
> computer, and press F8 at the character-based menu that displays the
> operating system choices. At the resulting Windows Advanced Options menu,
> choose the Last Known Good Configuration option. This option is most
> effective when only one driver or service is added at a time.
>
> Overclocking (setting the CPU to run at speeds above the rated
> specification) can cause this error. If this has been done to the computer
> experiencing the error, return the CPU to the default clock speed setting.
>
> Check the System Log in Event Viewer for additional error messages that
> might help pinpoint the device or driver that is causing the error.
> Disabling memory caching of the BIOS might also resolve it.
>
> If you encountered this error while upgrading to a new version of Windows,
> it might be caused by a device driver, a system service, a virus scanner, or
> a backup tool that is incompatible with the new version. If possible, remove
> all third-party device drivers and system services and disable any virus
> scanners prior to upgrading. Contact the software manufacturer to obtain
> updates of these tools. Also make sure that you have installed the latest
> Windows Service Pack.
>
> Finally, if all the above steps fail to resolve the error, take the system
> motherboard to a repair facility for diagnostic testing. A crack, a
> scratched trace, or a defective component on the motherboard can also cause
> this error.
>
> Source:
> http://msdn.microsoft.com/library/en-us/DevTest_g/hh/DevTest_g/t05_bugs_60_6e8bf56a-1b93-454b-9cf8-ab912bbd2157.xml.asp
>
>
> Meine Schlußfolgerung bzw. weiteres Vorgehen würde sein, dass ich die beiden
> Systeme vergleichen und die gemeinsamen Komponenten und Systemnahen
> Treiber/Software genauer unter die Lupe nehmen und ggf. durch Deinstallieren
> bzw. in einer Testumgebung durch Einzelschrittanalyse das fehlerhafte
> Element extrahieren würde.
>
>
> P.S.: Zertifizierte Hard- + Software erspart einem sehr viel Zeit, Mühe und
> vor allem Kosten .. ;)
>
> --
> Tobias Redelberger
>
> StarNET Services (HomeOffice)
> Schoenbornstr. 57
> D-97440 Werneck
>
> Tel: +49-(0)9722-4835
> Mobil: +49-(0)179-25 98 341
> Email: T.Redelberger@xxxxxxxxxxxxxxxxxxxx
>
>
>
>
.

Relevant Pages

  • Re: Systemabsturz im SBS mit Fehler 1003 Kat. 102
    ... >> Ereignistyp: Fehler ... > hardware or in the event that installed hardware fails. ... > driver, the driver should be removed or replaced. ... wurde kein Fehler angezeigt. ...
    (microsoft.public.de.german.backoffice.smallbiz)
  • Re: Blue error screen then reboot
    ... Check to make sure any new hardware or software is properly ... Is there any mention of a driver, ... install or, as you suggest, a clean installation. ... If you've had to reinstall XP on this laptop before you can ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Blue error screen then reboot
    ... Check to make sure any new hardware or software is properly ... Is there any mention of a driver, ... install or, as you suggest, a clean installation. ... If you've had to reinstall XP on this laptop before you can ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Systemabsturz im SBS mit Fehler 1003 Kat. 102
    ... > Ereignistyp: Fehler ... Bug check 0x7F usually occurs after the installation of faulty or mismatched ... hardware or in the event that installed hardware fails. ... driver, the driver should be removed or replaced. ...
    (microsoft.public.de.german.backoffice.smallbiz)
  • Re: Systemabsturz im SBS mit Fehler 1003 Kat. 102
    ... >> Bug check 0x7F usually occurs after the installation of faulty or mismatched ... >> hardware or in the event that installed hardware fails. ... >> driver, the driver should be removed or replaced. ... >> it might be caused by a device driver, a system service, a virus scanner, or ...
    (microsoft.public.de.german.backoffice.smallbiz)