Hallo zusammen,
ich habe wiederholte BSOD-Abstürze auf meinem RS 8000 G12 Server mit Windows Server 2022 und habe die Grundursache durch WinDbg-Analyse identifiziert. Ich poste hier, falls andere das gleiche Problem hatten oder Lösungen kennen.
**Server-Spezifikationen:**
- RS 8000 G12 (64GB RAM, Ryzen 9 7950X)
- Windows Server 2022 (vollständig aktualisiert)
- Alle Virtio-Treiber korrekt installiert
**Problem:**
Häufige Bluescreens mit Fehler 0x0000000A (IRQL_NOT_LESS_OR_EQUAL), die bei verschiedenen Vorgängen auftreten, einschließlich grundlegender Nutzung mit nur 2 Chrome-Browserfenstern.
**Durchgeführte Fehlerbehebung:**
✓ Alle fehlenden Virtio-Treiber installiert (Balloon, Console, QEMU ACPI)
✓ Chrome GPU-Hardwarebeschleunigung deaktiviert
✓ Auf anderen Hardware-Node migriert (Problem besteht weiterhin)
✓ Keine Gerätefehler im Geräte-Manager festgestellt
✓ Alle Windows-Updates installiert
**WinDbg Absturzanalyse-Ergebnisse:**
- Bug Check Code: 0x0000000A (IRQL_NOT_LESS_OR_EQUAL)
- Failure Bucket: AV_nt!MiUserFault
- Fehlerhafte Komponente: ntoskrnl.exe (Windows NT Kernel)
- Fehlerhafte Funktion: MiUserFault (Memory Manager User Fault Handler)
**Grundursache:**
Der Absturz tritt im Speicherverwaltungscode des Windows-Kernels auf, wenn Page Faults behandelt werden. Dies deutet auf ein Kompatibilitätsproblem zwischen dem Kernel-Speichermanager von Windows Server 2022 und der KVM/QEMU-Virtualisierungsumgebung hin.
**Fragen:**
1. Hat jemand erfolgreich Windows Server 2022 auf RS 8000 Serie ohne diese Abstürze betrieben?
2. Gibt es spezifische KVM/Hypervisor-Einstellungen oder Virtio-Treiberversionen, die dies beheben?
3. Hat jemand eine Problemumgehung oder Lösung für diese Art von Absturz gefunden?
Für jeden Hinweis dankbar!
**Systemdetails:**
- Arbeitsspeicher wird als "QEMU"-Hersteller angezeigt (emuliert statt Virtio-paravirtualisiert)
- Get-Tpm zeigt TpmPresent: False
- Abstürze treten auf mehreren Hardware-Nodes auf
- Selbst leichte Workloads (2 Chrome-Browser) lösen den Absturz aus
Hello,
I'm experiencing repeated BSOD crashes on my RS 8000 G12 server running Windows Server 2022 and have identified the root cause through WinDbg analysis. Posting here in case others have encountered this or have solutions.
**Server Specs:**
- RS 8000 G12 (64GB RAM, Ryzen 9 7950X)
- Windows Server 2022 (fully updated)
- All Virtio drivers installed correctly
**Issue:**
Frequent bluescreens with error 0x0000000A (IRQL_NOT_LESS_OR_EQUAL), occurring during various operations including basic usage with as few as 2 Chrome browser windows.
**Troubleshooting Completed:**
✓ Installed all missing Virtio drivers (Balloon, Console, QEMU ACPI)
✓ Disabled Chrome GPU hardware acceleration
✓ Migrated to different hardware node (issue persists)
✓ Verified no device errors in Device Manager
✓ All Windows updates applied
**WinDbg Crash Analysis Results:**
- Bug Check Code: 0x0000000A (IRQL_NOT_LESS_OR_EQUAL)
- Failure Bucket: AV_nt!MiUserFault
- Faulting Module: ntoskrnl.exe (Windows NT Kernel)
- Faulting Function: MiUserFault (Memory Manager User Fault Handler)
**Root Cause:**
The crash occurs in Windows kernel's memory management code when handling page faults. This indicates a compatibility issue between Windows Server 2022's kernel memory manager and the KVM/QEMU virtualization environment.
**Questions:**
1. Has anyone successfully run Windows Server 2022 on RS 8000 series without these crashes?
2. Are there specific KVM/hypervisor settings or Virtio driver versions that resolve this?
3. Has anyone found a workaround or solution for this type of crash?
Any insights appreciated!
**System Details:**
- Memory shows as "QEMU" manufacturer (emulated rather than Virtio paravirtualized)
- Get-Tpm shows TpmPresent: False
- Crashes occur across multiple hardware nodes
- Even light workloads (2 Chrome browsers) trigger the crash
Windowsdbg:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.047 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 29
Microsoft (R) Windows Debugger Version 10.0.26100.6584 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010926-5234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 20348 MP (16 procs) Free x64
Product: Server, suite: TerminalServer MultiUserTS
Edition build lab: 20348.2849.amd64fre.fe_release_svc_prod1.241101-1732
Kernel base = 0xfffff803`16e00000 PsLoadedModuleList = 0xfffff803`17a33b30
Debug session time: Fri Jan 9 21:38:30.473 2026 (UTC + 0:00)
System Uptime: 0 days 0:36:46.070
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000052`b928b018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffce0113900a80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80317117f8c, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1639
Key : Analysis.Elapsed.mSec
Value: 5656
Key : Analysis.IO.Other.Mb
Value: 5
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 11
Key : Analysis.Init.CPU.mSec
Value: 2515
Key : Analysis.Init.Elapsed.mSec
Value: 82042
Key : Analysis.Memory.CommitPeak.Mb
Value: 89
Key : Bugcheck.Code.LegacyAPI
Value: 0xa
Key : Failure.Bucket
Value: AV_nt!MiUserFault
Key : Failure.Hash
Value: {ebaa4318-8301-ca38-45f3-29102df77128}
Key : Hypervisor.Enlightenments.Value
Value: 8388980
Key : Hypervisor.Enlightenments.ValueHex
Value: 800174
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 0
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 0
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 1
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 536745
Key : Hypervisor.Flags.ValueHex
Value: 830a9
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 0
Key : Hypervisor.RootFlags.AccessStats
Value: 0
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 0
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0
Key : Hypervisor.RootFlags.MceEnlightened
Value: 0
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0
Key : Hypervisor.RootFlags.Value
Value: 0
Key : Hypervisor.RootFlags.ValueHex
Value: 0
Key : WER.OS.Branch
Value: fe_release_svc_prod1
Key : WER.OS.Version
Value: 10.0.20348.2849
BUGCHECK_CODE: a
BUGCHECK_P1: ffffce0113900a80
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80317117f8c
FILE_IN_CAB: 010926-5234-01.dmp
READ_ADDRESS: fffff80317b0f3d8: Unable to get MiVisibleState
c0000005 Exception in ext.analyze debugger extension.
PC: 00007ffb`ff3d06f5 VA: 00007ffb`ff63d000 R/W: 1 Parameter: 00000000`00000000
