Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various errors when running Steam-Games from ZFS-Pool/Dataset #459

Open
besterino opened this issue Mar 7, 2025 · 1 comment
Open

Various errors when running Steam-Games from ZFS-Pool/Dataset #459

besterino opened this issue Mar 7, 2025 · 1 comment

Comments

@besterino
Copy link

Win11 Pro for Workstations (German)
24H2 (Build 26100.3194)
OpenZFSOnWindows-debug-2.3.0rc6g

System:
CPU: AMD 9800X3D
Mainboard: MSI X870E Tomahawk Wifi
GPU: NVIDIA 5090
ZFS-Storage Hardware: 2x Lexar NVME NM790 4TB

ZFS-Layout:
Basic Pool over 2 NVME SSD with one dataset, all data resides in dataset (no data directly on pool).

(This is partly related to my post here: #458)

I am currently using ZFS in my "everyday gaming desktop" for real-life (stress) testing purposes.

Issues I experienced so far since testing for 2 days:

  1. Certain games (e.g. Pax Dei) will only launch, if the relevant dataset has its own driveletter. Only assigning a driveletter to the pool does not work.

  2. Age of Empires IV won't start all.

  3. Computer crashed last time I closed Pax Dei. Since then starting the game fails with blue screen "unexpected kernel mode trap". Moving the game to a NTFS-filesystem and starting from there works.

@besterino
Copy link
Author

More information (for what it's worth): minidump also points to ZFS being the Problem:

`*******************************************************************************

  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a portion of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffe28032dfde70
Arg3: fffff40df9111000
Arg4: fffff806e3ebe164

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 859

Key  : Analysis.Elapsed.mSec
Value: 1815

Key  : Analysis.IO.Other.Mb
Value: 12

Key  : Analysis.IO.Read.Mb
Value: 1

Key  : Analysis.IO.Write.Mb
Value: 23

Key  : Analysis.Init.CPU.mSec
Value: 468

Key  : Analysis.Init.Elapsed.mSec
Value: 16445

Key  : Analysis.Memory.CommitPeak.Mb
Value: 88

Key  : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key  : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key  : Analysis.Version.Ext
Value: 1.2410.2.2

Key  : Bugcheck.Code.LegacyAPI
Value: 0x1000007f

Key  : Bugcheck.Code.TargetModel
Value: 0x1000007f

Key  : Dump.Attributes.AsUlong
Value: 0x1808

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0x0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 0

Key  : Failure.Bucket
Value: 0x7f_8_OpenZFS!unknown_function

Key  : Failure.Hash
Value: {4fdb4ed0-b6d3-cb72-31fe-819f29cba343}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 0x7497cf94

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: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

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: 38408431

Key  : Hypervisor.Flags.ValueHex
Value: 0x24a10ef

Key  : Hypervisor.Flags.VpAssistPage
Value: 1

Key  : Hypervisor.Flags.VsmAvailable
Value: 1

Key  : Hypervisor.RootFlags.AccessStats
Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key  : Hypervisor.RootFlags.Value
Value: 1015

Key  : Hypervisor.RootFlags.ValueHex
Value: 0x3f7

BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffe28032dfde70

BUGCHECK_P3: fffff40df9111000

BUGCHECK_P4: fffff806e3ebe164

FILE_IN_CAB: 030725-10656-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffc00d430af340

STACK_OVERFLOW: Stack Limit: fffff40df9111000. Use (kF) and (!stackusage) to investigate stack usage.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff40df9111000 fffff806e3eba979 : 0000000000050005 0000000000033411 fffff40df91113a0 fffff806e3e1223c : nt!output_l+0x6c
fffff40df91112c0 fffff80678aafba8 : 0000000000000000 0000000000007300 fffff80678ab2a40 ffffc00d430af340 : nt!snprintf+0x69
fffff40df9111350 0000000000000000 : 0000000000007300 fffff80678ab2a40 ffffc00d430af340 ffffc00d5f200000 : OpenZFS+0x52fba8

SYMBOL_NAME: OpenZFS+52fba8

MODULE_NAME: OpenZFS

IMAGE_NAME: OpenZFS.sys

STACK_COMMAND: .process /r /p 0xffffc00d1b572040; .thread 0xffffc00d430af340 ; kb

BUCKET_ID_FUNC_OFFSET: 52fba8

FAILURE_BUCKET_ID: 0x7f_8_OpenZFS!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4fdb4ed0-b6d3-cb72-31fe-819f29cba343}

Followup: MachineOwner
---------`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant