Wiederherstellen der MSSMBIOS.SYS bereitet Probleme!

hallo
wenn du diese fehlermeldung bekommst:
Self registration of the DLL c:\winnt\system32\inetcomm.dll failed
dann hilft dieser link:
http://support.microsoft.com/?scid=kb%3Ben-us%3B233219&x=14&y=1 ...

bei einer fehlermeldung, wie dieser:
"OUTLOOK verursachte einen Fehler durch eine ungültige Seite in Modul INETCOMM.DLL bei 0157:5e."
hilft dir dieser link:
http://support.microsoft.com/kb/184073/de
betrifft in deinem fall wohl den COM+ [Component] Configuration Catalog Server
und arbeitet mit catsrvut.dll zusammen, dem COM+ [Component] Setup
eine uebersicht ueber die Component Services bekommst du hier:
http://msdn2.microsoft.com/en-gb/library/ms687015.aspx
Das ist der Microsoft System Management BIOS Driver:
The Microsoft SMBIOS driver (mssmbios.sys) is a root-enumerated driver included with Windows XP SP2 and Windows Server 2003 SP1 and has two primary functions:
• To incorporate SMBIOS, ACPI, and CPU information to the crash dump file when a system crash occurs.
• To retrieve system identification information from SMBIOS and make it available to system components and applications.

There are two primary benefits to the Microsoft SMBIOS driver:
• Adding system firmware information to the crash dump aids in failure diagnosis. A given root cause may be linked to a specific system vendor or to specific hardware attributes, such as the type and size of memory modules. This information is available in SMBIOS.
• Identifying a given hardware platform. Scenarios such as branding, BIOS update, and targeted driver installation require a reliable, stable method for identifying the underlying hardware platform. These scenarios require information about basic attributes of the system, such as the system manufacturer and current BIOS version.

Data Collection
At system startup, the Microsoft SMBIOS driver collects the following information about the system hardware and stores it in memory allocated by the driver:
• SMBIOS data: The SMBIOS driver collects the entire contents of the SMBIOS table data except for unique identification information. To prevent the data that is collected from being able to uniquely identify a system, the driver reads the entire contents of the SMBIOS table data and then zeroes out the following SMBIOS data fields if they are present:
• System Information (Type 1 Table)
• Serial Number
• UUID
• Base Board Information (Type 2 Table)
• Serial Number
• Asset Tag
• System Enclosure Information (Type 3 Table)
• Serial Number
• Asset Tag
• Processor Information (Type 4 Table)
• Serial Number
• Asset Tag
• Memory Device Information (Type 17 Table)
• Serial Number
• Asset Tag
• Battery Information (Type 22 Table)
• Serial Number
• SBDS Serial Number
• Power Supply Information (Type 39 Table)
• Serial Number
• Asset Tag

After the driver has removed the contents of these fields, it stores the SMBIOS data in memory until a system crash occurs.

• ACPI information: The driver collects all ACPI table data except for the contents of the differentiated system description table (DSDT) and secondary system description table (SSDT), if they are present. The driver also collects the header data of the DSDT and SSDT and then stores this table data in memory until a system crash occurs.
• CPU information: The driver includes the entire contents of the CPU information key in the registry (HKLM\Hardware\Description\System\CentralProcessor\0). Some vendor-specific information about the processor, such as the current microcode update revision, is also collected. The driver then stores this data in memory until a system crash occurs.

The driver also stores this information in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mssmbios\Data. Although SMBIOS information is stored in the registry at this location, consumers should continue to use WMI or the GetSystemFirmwareTable() API to retrieve SMBIOS data. There is no guarantee that this information will be stored at this registry subkey for every subsequent release of Windows.
-kann den SMBIOS-Table nicht lesen...
-weil er die hardwarekonfiguration nicht auslesen kann
Das SP2 lässt
-ntoskernel.exe koennte korrupt sein.
welches betriebssystem war vorher auf dem rechner, gab es eine software die ntoskernel korrumpiert haben koennte, hast du vor der neuinstallation die platte auf null gesetzt, wo hatte deine freundin gechattet??

ueberprufe dein problem auch mal hinsichtlich der weiter oben genannten aspekte

saludos
gnarff