eigenartiger systemerror - windows 2003 sbs

[fiffi 10]

hallo liebe mcseboard gemeinde !!

 

hab ein problem mit einem server, windows 2003 sbs. der server ist recht frisch aufgesetzt, nun schleichen sich fehler ein. das zweite mal innhalb einer woche, machte ich den bildschirm an und der server ist auf grund eines schweren systemfehlers runter gefahren :eek:

 

scrennshot: http://chrisi.homedns.org/fehlercode.jpg

 

hat jemand ne idee ?

 

google hat mich auch net gerade weiter gebracht, ist wohl nen fehler der bei xp öfters mal aufgetreten ist, aber mit dem hintergrund bin ich mir noch net sicher.

 

kann es sein dass: hab vor ner woche eine fritzkarte eingebaut, soll mal als faxdienst dienen, allerdings hab ich noch keine fritz cd gefunden (bei avm gibts nur updates) also ist die installation noch net vollständig, d.h. capi treiber.

 

danke im voraus

[zahni 524]

Aus der Online-Hilfe vom Windows-Debugger:

 

 

Common exception codes include:

 

0x80000002: STATUS_DATATYPE_MISALIGNMENT

An unaligned data reference was encountered.

 

0x80000003: STATUS_BREAKPOINT

A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.

 

0xC0000005: STATUS_ACCESS_VIOLATION

A memory access violation occurred.

 

 

For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows Driver Kit.

 

Resolving the Problem

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

 

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

 

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

 

If exception code 0x80000002 occurs, the trap frame will supply additional information.

 

If the specific cause of the exception is unknown, the following should be considered:

 

Hardware incompatibility. First, make sure that any new hardware installed is listed in the Microsoft Windows Catalog.

 

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

 

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, 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 by using the Recovery Console to access the file.

 

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

 

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

 

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You can also use another hard disk with more free space for the installation. BIOS problems can be resolved by upgrading the system BIOS version.

[GuentherH 61]

Hi.

 

kann es sein dass: hab vor ner woche eine fritzkarte eingebaut, soll mal als faxdienst dienen, allerdings hab ich noch keine fritz cd gefunden (bei avm gibts nur updates) also ist die installation noch net vollständig, d.h. capi treiber.

Wenn der Fehler seit diesem Zeitpunkt auftritt, würde ich das nicht ausschließen.

 

Du brauchst übrigens keine CD für die Installation der Fritz Card, die Treiber aus der AVM Seite sind schon genau die richtigen.

Im Gegenteil, du sollt auf keinen Fall mit der CD installieren.

 

http://www.sbspraxis.de/server/srvfax_002/srvfax_002.html

 

LG Günther