Share via

My Pc keeps hard reseting and freezes only playing star citizen for over 30 mins. I can play any other game all day but star citizen keeps hard restarting.

Anonymous
2024-12-22T14:55:11+00:00

I have tried Windows Memory Diagnostic test and memtest86. I only tried memtest86 with all ram slots in with no errors. I haven't tried them, yet individually.

Here is my dump files to take a look at. Can someone help me out.. can it be my power is not enough in my home?

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 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: 42

Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\122224-13468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`7dc00000 PsLoadedModuleList = 0xfffff806`7eaf4850
Debug session time: Sun Dec 22 09:14:40.689 2024 (UTC - 5:00)
System Uptime: 1 days 11:19:32.856
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.................
Loading User Symbols

Loading unloaded module list
....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`7e0b85d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd500`14fe2a60=000000000000001a
9: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the BugCheck.
Arg2: ffff9ecf67b3df80
Arg3: 0000000000000009
Arg4: ffffd50014fe2bd0

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1156

    Key  : Analysis.Elapsed.mSec
    Value: 4333

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1a

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    Key  : Failure.Hash
    Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7497cf94

    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: 24a10ef

    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

    Key  : Stack.Pointer
    Value: ISR

BUGCHECK_CODE:  1a

BUGCHECK_P1: 61941

BUGCHECK_P2: ffff9ecf67b3df80

BUGCHECK_P3: 9

BUGCHECK_P4: ffffd50014fe2bd0

FILE_IN_CAB:  122224-13468-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc3887b98e280

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffd500`14fe2a58 fffff806`7de7a72c     : 00000000`0000001a 00000000`00061941 ffff9ecf`67b3df80 00000000`00000009 : nt!KeBugCheckEx
ffffd500`14fe2a60 fffff806`7e288ecb     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x50c
ffffd500`14fe2bd0 fffff806`7de32c18     : 00007fff`ffff0000 fffff806`7de2f556 fffff806`7dc00000 fffff806`7e27c6ac : nt!KiPageFault+0x38b
ffffd500`14fe2d60 fffff806`7de2f3e0     : ffffd500`14fe3470 00000000`00000000 ffffd500`14fe3390 ffffd500`14fe3478 : nt!RtlpxLookupFunctionTable+0x348
ffffd500`14fe2dd0 fffff806`7de2e1a1     : ffffd500`14fe3cd8 ffffd500`14fe3470 00000000`00000000 ffffd500`14fe3360 : nt!RtlpLookupFunctionEntryForStackWalks+0x200
ffffd500`14fe2e30 fffff806`7de6b664     : 00000000`00000000 00000000`00000001 00000000`00000002 ffffd500`14fdd000 : nt!RtlpWalkFrameChain+0x311
ffffd500`14fe3520 fffff806`7de6d360     : 00000000`00000001 ffffd500`14fe3670 00000000`02108a02 ffffd500`14fdd000 : nt!RtlWalkFrameChain+0x94
ffffd500`14fe3570 fffff806`7de6ce44     : ffffc388`be1ea040 ffffd500`14fe37a9 00000000`02108a02 00000000`00000000 : nt!EtwpTraceStackWalk+0x150
ffffd500`14fe36c0 fffff806`7de2d057     : ffffc388`7bbc6000 00000000`02109a02 00000000`00000000 ffffd500`14fe37f9 : nt!EtwpStackTraceDispatcher+0x144
ffffd500`14fe3730 fffff806`7df82f42     : ffffd500`14fe3af0 fffff806`7e212966 00000000`00000000 00000000`00000000 : nt!EtwpLogKernelEvent+0x587
ffffd500`14fe3850 fffff806`7e21295a     : ffffe891`00000000 00000000`00000000 00000000`00000001 ffffd500`14fe3910 : nt!EtwTraceSiloKernelEvent+0xa2
ffffd500`14fe38b0 fffff806`7e0670c4     : fffff806`7eafe448 fffff806`7e1299fb fffff7c6`8001c900 00000000`00530076 : nt!EtwpProfileInterrupt+0x11a
ffffd500`14fe3920 fffff806`7e067039     : 00000000`00000000 fffff7c6`8001b560 00000000`c0010201 ffffd500`14fe3b40 : nt!KiProcessProfileList+0x78
ffffd500`14fe3950 fffff806`7e129784     : fffff7c6`8001c900 00000000`00000001 ffffd500`14fc7180 0001ba1d`9e603ae1 : nt!KeProfileInterruptWithSource+0x39
ffffd500`14fe3980 fffff806`7e1295a4     : ffffe891`14fe3b00 fffff806`c0010201 ffffd500`14fe3b40 fffff806`c0010200 : nt!Amd64OverflowHandlerInternal+0x1d4
ffffd500`14fe3a20 fffff806`7e0a7c83     : 00000000`00000016 ffffc388`c113b080 00000000`0000007c 00000000`00000184 : nt!Amd64OverflowHandler+0x14
ffffd500`14fe3a50 fffff806`7de7047f     : ffffc388`7b7d3b20 fffff806`7e27be9e 00000000`00000000 fffff806`7e275250 : nt!HalpPerfInterrupt+0x153
ffffd500`14fe3a90 fffff806`7e27be9e     : fffff806`619e8ad3 ffffc388`7b7d3b20 00000000`c0000001 ffffc388`a1f4fe30 : nt!KiCallInterruptServiceRoutine+0x4bf
ffffd500`14fe3af0 fffff806`7e27c6ac     : 00000000`00001000 00000000`00000001 ffffd500`14fc7180 ffffc388`7bbc6000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffd500`14fe3b40 fffff806`619e8ad7     : fca4f9b0`fa65352a ffffffff`e0493f36 f59b2cac`f6e3ee81 f68f5502`ff6ff845 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffd500`14fe3cd8 fca4f9b0`fa65352a     : ffffffff`e0493f36 f59b2cac`f6e3ee81 f68f5502`ff6ff845 f1ec0438`f82edb1f : EasyAntiCheat_EOS+0xde8ad7
ffffd500`14fe3ce0 ffffffff`e0493f36     : f59b2cac`f6e3ee81 f68f5502`ff6ff845 f1ec0438`f82edb1f ffffffff`cd1f5028 : 0xfca4f9b0`fa65352a
ffffd500`14fe3ce8 f59b2cac`f6e3ee81     : f68f5502`ff6ff845 f1ec0438`f82edb1f ffffffff`cd1f5028 00000128`1a80c254 : 0xffffffff`e0493f36
ffffd500`14fe3cf0 f68f5502`ff6ff845     : f1ec0438`f82edb1f ffffffff`cd1f5028 00000128`1a80c254 00000000`00000000 : 0xf59b2cac`f6e3ee81
ffffd500`14fe3cf8 f1ec0438`f82edb1f     : ffffffff`cd1f5028 00000128`1a80c254 00000000`00000000 00000000`00000000 : 0xf68f5502`ff6ff845
ffffd500`14fe3d00 ffffffff`cd1f5028     : 00000128`1a80c254 00000000`00000000 00000000`00000000 00000000`00000004 : 0xf1ec0438`f82edb1f
ffffd500`14fe3d08 00000128`1a80c254     : 00000000`00000000 00000000`00000000 00000000`00000004 00000000`00000000 : 0xffffffff`cd1f5028
ffffd500`14fe3d10 00000000`00000000     : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`00000000 : 0x00000128`1a80c254

MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

STACK_COMMAND:  .process /r /p 0xfffff8067ebcdf80; .thread 0xffffc3887b98e280 ; kb

FAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

Followup:     MachineOwner
---------
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

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-12-23T06:59:34+00:00

    Hello, Tyree Hill

    Welcome to the Microsoft Community.

    Thank you very much for your feedback. I have carefully read the information and problem description you provided. You mentioned that your computer will have a blue screen error when playing Star Citizen, but everything is normal when playing other games.

    I understand the trouble caused by this problem. I analyzed the DMP file you provided. According to the information provided by the DMP file, the system has a

    MEMORY_MANAGEMENT (1a) error, which indicates a memory management problem.

    The process that caused the error is MsMpEng.exe, which is usually related to Windows Defender or Microsoft Security Essentials.

    Fault module name: hardware

    Fault module IMAGE_NAME is hardware_ram

    Fault bucket ID is 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    From the analysis information, the blue screen error is caused by the reserved bit in the page table being set, which is a typical hardware-level memory problem. The error is mainly concentrated in memory management and page table management. But according to your description, if there is a memory hardware error, you should have an error when playing all games, so this is a contradictory fact, which is indeed very strange.

    In order to narrow the scope of the problem, I will give some methods I know, which may help you.

    Method 1. First, I suggest you still check the memory. Please turn off XMP in the BIOS settings. XMP can automatically overclock the memory frequency to increase the frame rate of the game, but in order to find out the cause of the problem, I suggest you temporarily turn off this option.

    Method 2. Please go to your device manufacturer's website to make sure that the device drivers (especially graphics card and storage drivers) are up to date.

    At the same time, I suggest you upgrade your computer's BIOS to the latest version to ensure compatibility and stability with the hardware. Run Windows Update to ensure that system patches and security updates have been applied.

    Method 3. The error log involves EasyAntiCheat_EOS, which is an anti-cheat driver commonly used in games. Please make sure that there is no problem with the software and try to update or reinstall the relevant games and their anti-cheat software.

    Merry Christmas in advance, my friend!

    Best regards

    Brian - Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments No comments