Share via

BSOD when playing VR using Virtual Desktop.

Anonymous
2024-07-24T16:56:19+00:00

When playing with VR using Virtual Desktop streaming app, I will get an error from 5min to 1hour into my gaming session. This happens with any game that I play. The error is The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x000000000000002d, 0x0000000000000002, 0x0000000000000000, 0xfffff8010b617538). A dump was saved in: C:\Windows\Minidump\072524-15218-01.dmp. Report Id: 141b74e2-2a35-437e-9325-6c96fd6c6561. And the dumpfile state " 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: 000000000000002d, 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: fffff8010b617538, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1515 Key : Analysis.Elapsed.mSec Value: 8225 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 1 Key : Analysis.Init.CPU.mSec Value: 202 Key : Analysis.Init.Elapsed.mSec Value: 30135 Key : Analysis.Memory.CommitPeak.Mb Value: 102 Key : Bugcheck.Code.LegacyAPI Value: 0xa Key : Bugcheck.Code.TargetModel Value: 0xa Key : Dump.Attributes.AsUlong Value: 808 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: AV_nt!RtlpHpLfhSubsegmentDecommitPages Key : Failure.Hash Value: {3ea916f4-98f1-2e2d-978b-851f95bd1f17} Key : Hypervisor.Enlightenments.ValueHex Value: 1497cf94 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: 4853999 Key : Hypervisor.Flags.ValueHex Value: 4a10ef 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: 3f7 BUGCHECK_CODE: a BUGCHECK_P1: 2d BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8010b617538 FILE_IN_CAB: 072524-15218-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x808 Kernel Generated Triage Dump READ_ADDRESS: fffff8010c11c4a8: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse 000000000000002d CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: fffffb06d9b5a650 -- (.trap 0xfffffb06d9b5a650) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000004ff rbx=0000000000000000 rcx=ffffda8463602380 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8010b617538 rsp=fffffb06d9b5a7e0 rbp=0000000000000001 r8=00000000ffffffff r9=0000000000000001 r10=0000000000000001 r11=ffffda846f2e8038 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!RtlpHpLfhSubsegmentDecommitPages+0xc8: fffff8010b617538 410fb6472d movzx eax,byte ptr [r15+2Dh] ds:000000000000002d=?? Resetting default scope STACK_TEXT: fffffb06d9b5a508 fffff8010b82bd29 : 000000000000000a 000000000000002d 0000000000000002 0000000000000000 : nt!KeBugCheckEx fffffb06d9b5a510 fffff8010b827189 : 0000000000000000 0000000000000000 0000000000000000 ffffda8463d40040 : nt!KiBugCheckDispatch+0x69 fffffb06d9b5a650 fffff8010b617538 : 0000000000000002 fffff8010b616b48 ffffda8463604990 ffffda8463604998 : nt!KiPageFault+0x489 fffffb06d9b5a7e0 fffff8010b616b32 : ffffda84636047d0 ffffda84636047d8 ffffda84636023ff ffffda8463602380 : nt!RtlpHpLfhSubsegmentDecommitPages+0xc8 fffffb06d9b5a850 fffff8010b615fa8 : ffffda84636024e8 0000000000000000 0000000000000000 ffffda8463602200 : nt!RtlpHpLfhOwnerCompact+0x6e fffffb06d9b5a8b0 fffff8010b6197f2 : 0000000000000000 fffffb06d9b5aac0 fffff8010c075600 0000000000000000 : nt!RtlpHpLfhContextCompact+0xb0 fffffb06d9b5a900 fffff8010b619cb5 : 0000000000000001 0000000000000000 0000000000000000 ffffda8480000000 : nt!RtlpHpHeapCompact+0x66 fffffb06d9b5a930 fffff8010b7064f5 : 0000000000000001 ffffda840000003f fffffb0600000001 ffffda8400000000 : nt!ExpHpCompactionRoutine+0x205 fffffb06d9b5a9c0 fffff8010b679ca7 : ffffda8463d40040 00000000000002f7 ffffda8463d40040 fffff8010b7063a0 : nt!ExpWorkerThread+0x155 fffffb06d9b5abb0 fffff8010b81af64 : ffff920046a51180 ffffda8463d40040 fffff8010b679c50 0000000000000000 : nt!PspSystemThreadStartup+0x57 fffffb06d9b5ac00 0000000000000000 : fffffb06d9b5b000 fffffb06d9b54000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!RtlpHpLfhSubsegmentDecommitPages+c8 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.3880 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: c8 FAILURE_BUCKET_ID: AV_nt!RtlpHpLfhSubsegmentDecommitPages OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {3ea916f4-98f1-2e2d-978b-851f95bd1f17} Followup: MachineOwner"

These are the things that I did to try and fix the issue.

  1. I tried to have a clean installation of my graphics drivers
  2. I cleaned up all my ssd and hdd.
  3. I ran the windows memory diagnostics and it came back with no error.

I really want to play VR games but with this error it makes it very annoying and irritating to do so. Please help me solve this. Thank you.

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2024-07-27T12:29:03+00:00

    Hey Dave, sorry for the late reply as I was testing it multiple times to ensure that the issue was fixed. Good news is that I am no longer facing blue screen issues when playing VR. Thank you very much for your fast responses and direct answers. I really appreciated it. Thank you.

    Was this answer helpful?

    0 comments No comments
  2. DaveM121 891.1K Reputation points Independent Advisor
    2024-07-25T06:07:59+00:00

    Your minidump files indicate the Nvidia graphics drivers and also some USB drivers caused the system crashes.

    1

    Completely remove the current Nvidia device driver using the widely available free DDU utility, then restart your PC and go to the Nvidia website to download and install a slightly older version of the Nvidia device driver.

    A slightly older version of that driver is more stable than the latest version.

    2

    Go to the support page for your PC or Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, if you do not have your drive encrypted with Bitlocker, check for any BIOS update that may need to be installed

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-07-25T04:16:05+00:00

    Hello Dave, Thank you very much for the quick respones. Here are all the dumpfiles I have: MinDumps.zip

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. DaveM121 891.1K Reputation points Independent Advisor
    2024-07-24T17:27:54+00:00

    Hi, I am Dave, I will help you with this.

    Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    Was this answer helpful?

    0 comments No comments