5
Windows Server 2003 SBS - BlueScreen 0x000000d1
Hallo zusammen,
wir haben bei einem Kunden einen Windows 2003 SBS stehen. Dieser bekommt zwischendrin einen BlueScreen mit folgender Fehlermeldung:
000000d1, 1. Parameter b9e379b8, 2. Parameter d0000009, 3. Parameter 00000000, 4. Parameter ba2163e8
Was kann das sein ?
SP2 ist installiert.
Bei MS steht, daß das bei hoher Auslastung vorkommen kann. Nur wie kann man dem entgegenwirken ?
Hatte schon den RAM im Verdacht
Vielen Dank schonmal im voraus
Kai
wir haben bei einem Kunden einen Windows 2003 SBS stehen. Dieser bekommt zwischendrin einen BlueScreen mit folgender Fehlermeldung:
000000d1, 1. Parameter b9e379b8, 2. Parameter d0000009, 3. Parameter 00000000, 4. Parameter ba2163e8
Was kann das sein ?
SP2 ist installiert.
Bei MS steht, daß das bei hoher Auslastung vorkommen kann. Nur wie kann man dem entgegenwirken ?
Hatte schon den RAM im Verdacht
Vielen Dank schonmal im voraus
Kai
Auf Facebook teilen
Auf Twitter teilen
Auf Reddit teilen
Auf Linkedin teilenBitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 72341
Url: https://administrator.de/forum/windows-server-2003-sbs-bluescreen-0x000000d1-72341.html
Ausgedruckt am: 23.12.2024 um 04:12 Uhr
5 Kommentare
Neuester Kommentar
Hier noch die Lösung der Bluescreen-Fehlermeldung aus dem Technet:
Stop message 0x000000D1 Descriptive text: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual cause: An attempt was made to touch pageable memory at a process internal request level (IRQL) that was too high. This is usually caused by drivers using improper addresses. Kernel-mode drivers are forbidden to access pageable memory at a high IRQL.
Solution:
1.
Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.
2.
Use the File Signature Verification tool, which identifies unsigned drivers and incompatible system files on your computer. The system files and device driver files that are provided with the Windows Server 2003 family have a Microsoft digital signature, which indicates that the files are original, unaltered system files or that they have been approved by Microsoft for use with Windows. For more information, see Using File Signature Verification.
3.
Use Device Manager to roll back to a previous version of the driver. For more information, see Roll back to the previous version of a driver.
4.
Disable the driver identified in the Stop message or any newly installed drivers.
5.
If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.
Important•
When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.
6.
Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.
Stop message 0x000000D1 Descriptive text: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual cause: An attempt was made to touch pageable memory at a process internal request level (IRQL) that was too high. This is usually caused by drivers using improper addresses. Kernel-mode drivers are forbidden to access pageable memory at a high IRQL.
Solution:
1.
Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.
2.
Use the File Signature Verification tool, which identifies unsigned drivers and incompatible system files on your computer. The system files and device driver files that are provided with the Windows Server 2003 family have a Microsoft digital signature, which indicates that the files are original, unaltered system files or that they have been approved by Microsoft for use with Windows. For more information, see Using File Signature Verification.
3.
Use Device Manager to roll back to a previous version of the driver. For more information, see Roll back to the previous version of a driver.
4.
Disable the driver identified in the Stop message or any newly installed drivers.
5.
If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.
Important•
When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.
6.
Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.
Was anderes habe ich auch nicht behauptet 
Danke erstmal für die Antwort...
habe mal die MiniDumps angeschaut und durch den Debugger gejagt.
Der Fehler hängt mit dem Treiber der Fritz! Karte zusammen - seltsam nur, daß auf dem Server gar keine Fritz! Karte installiert ist.
Könnte es auch durch einen VPN Zugriff dazuführen, daß der Server den Stop Fehler bringt ?
habe mal die MiniDumps angeschaut und durch den Debugger gejagt.
Der Fehler hängt mit dem Treiber der Fritz! Karte zusammen - seltsam nur, daß auf dem Server gar keine Fritz! Karte installiert ist.
Könnte es auch durch einen VPN Zugriff dazuführen, daß der Server den Stop Fehler bringt ?
