PC Freezing - Unresponsive

Fresh windows 11 install 24H2 Pro
Everything is up to date
Every hardware tested and in order
Hardware specs in screenshots attached

Freezes occur only when playing eve online. When it happens the screen stop refreshing and show the last frame before the freeze happened. Wireless keyboard and mouse disconnects but it would be unresponsive in a wired set up as well. Only thing I can see the PC responding to is powering it off with the power button.

Edit: I don’t have a graphics card installed in this PC, the integrated GPU in the 9800x3d can handle eve at potato graphics well enough.
Edit2: The system doesn’t recover. This isn’t connected to the OneDrive issue.
Edit3: I was patient enough to wait for it to get to BSOD screen this time and I didn’t restart it manually. The PC at least restarts on it’s own.
Edit4: I have allocated a fix 8GB of RAM to the integrated GPU. So far so good, game would have crashed many times by now but it has been running in background for most of the time. I am going to try to actually play it now and see if it crashes.
Edit 5: Giving it more memory didn’t solve the issue. Eventually it crashed. BSOD screen had this stop code: VIDEO DXGKRNL FATAL ERROR
Edit 6: Happened on my laptop as well. Today’s game update totaly wrecked the game. My launcher became unstartable after the crash right after start up after the update.






Have you looked at the Windows 11 crash log for information on why?

There is a minidump file that was created now that I let the system go through the bugcheck but I can’t read it. I think only microsoft can?

Edit: I was refering to the volmgr dumb file when I said that probably only microsoft can read it. There was a volmgr dump file created and there was a minidump file created by the bugcheck.

Can always copy/paste it https://pastebin.com/ and then provide link.

Also, did you allocate some Vram to help the onboard graphics?

There’s your first problem

And there’s the second…

1 Like

I will do drop it to pastebin.com, here is the link: ************* Preparing the environment for Debugger Extensions Gallery reposito - Pastebin.com (never done this before so I don’t know if I did it right. I basically copied what WinDbg shows after opening the minidump file)
So for what the WinDbg writes after analyse:

************* Path validation summary **************
Response Time (ms) Location
Deferred srvC:\SymbolsSymbol information
2: kd> !analyze -v


  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff802dbfc33b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:




*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: TickPeriods ***



KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 968

Key  : Analysis.Elapsed.mSec
Value: 969

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

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

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

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

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

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

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: 0x133

Key  : Bugcheck.Code.TargetModel
Value: 0x133

Key  : Dump.Attributes.AsUlong
Value: 0x21808

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: 0x133_ISR_dxgmms2!VidSchiInterlockedInsertTailList

Key  : Failure.Hash
Value: {a4196c53-b14d-c9a4-c584-932877bf6407}

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

Key  : Stack.Pointer
Value: ISR

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff802dbfc33b0

BUGCHECK_P4: 0

FILE_IN_CAB: 040725-12515-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffc6050190f080

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: AMDRSServ.exe

STACK_TEXT:
ffffda014646db48 fffff802db32eeb9 : 0000000000000133 0000000000000001 0000000000001e00 fffff802dbfc33b0 : nt!KeBugCheckEx
ffffda014646db50 fffff802db3a4491 : 0000000000000000 0000000000000002 0000000000000000 000000000038245d : nt!KeAccumulateTicks+0x589
ffffda014646dbc0 fffff802db3a4055 : 0000000000217699 0000000000000000 00000085da64d044 000000000000000d : nt!KiUpdateRunTime+0xc9
ffffda014646dc40 fffff802db28573e : 000000000000000d 0000000000000000 ffffda014645a9c8 fffff802dbf20748 : nt!KiUpdateTime+0x2b5
ffffda014646ddd0 fffff802db2870ed : ffffc604ca602fc0 0000000000000000 ffffc604ca603070 fffff802dbf8e140 : nt!KeClockInterruptNotify+0x66e
ffffda014646df50 fffff802db67d96e : ffffd78c85856f02 ffffc604ca602fc0 ffffd78c85856d10 00000085dacb5e25 : nt!KiCallInterruptServiceRoutine+0x2ed
ffffda014646dfb0 fffff802db67e17c : 00000085dacb4a91 ffffd78c85856d90 00000085dacb4a9e 0000f547391da152 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffd78c85856d10 fffff802db2e0c72 : ffff930800000000 0000000000000001 ffff9308d95e7d60 fffff8026f976fc6 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffd78c85856ea0 fffff802db2e0bd8 : ffffd78c85856f50 0000000000000000 ffffc604e06987c0 ffff9308b96c75a0 : nt!KxWaitForLockOwnerShip+0x62
ffffd78c85856f00 fffff8026f8c0e88 : ffffc60502903078 ffffc604e0698160 0000000000000000 0000000000000000 : nt!KeAcquireInStackQueuedSpinLock+0x68
ffffd78c85856f30 fffff8026f976c82 : ffffc60502903010 ffff9308b96c7770 ffff930800000000 0000000033616956 : dxgmms2!VidSchiInterlockedInsertTailList+0x38
ffffd78c85856f80 fffff8026f977938 : ffff9308b96c75a0 ffffd78c85857129 ffff9308b96c7770 0000000000000000 : dxgmms2!VidSchiCreateDeviceInternal+0x14e
ffffd78c85857040 fffff8026d162126 : ffff9308b96c75a0 ffffd78c85857129 ffff9308b96c75a0 0000000000000000 : dxgmms2!VidSchCreateDevice+0x28
ffffd78c858570a0 fffff8026d16161b : ffff9308b96c75a0 ffffc604e0696000 ffffc604df3ea7a0 fffff8026d0af1a5 : dxgkrnl!DXGDEVICE::Initialize+0x33e
ffffd78c85857190 fffff8026d160c93 : ffffc604e0696000 ffffd78c858574e0 00000017829dd040 0000000000000000 : dxgkrnl!ADAPTER_RENDER::CreateDevice+0x253
ffffd78c85857210 fffff8026d160801 : ffffc6050190f080 ffffc6050190f080 00000017829dd040 ffffc6050190f080 : dxgkrnl!DxgkCreateDeviceImpl+0x483
ffffd78c85857430 fffff802db68ee58 : ffffc60501900000 0000012f7b1fd1d0 ffffc6050190f080 00000017829dd040 : dxgkrnl!DxgkCreateDevice+0x11
ffffd78c85857460 00007ff86fe94b14 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
00000017829dcca8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`6fe94b14

SYMBOL_NAME: dxgmms2!VidSchiInterlockedInsertTailList+38

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.26100.3624

STACK_COMMAND: .process /r /p 0xffffc604ff8bd080; .thread 0xffffc6050190f080 ; kb

BUCKET_ID_FUNC_OFFSET: 38

FAILURE_BUCKET_ID: 0x133_ISR_dxgmms2!VidSchiInterlockedInsertTailList

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a4196c53-b14d-c9a4-c584-932877bf6407}

Followup: MachineOwner

I run wow on it perfectly fine. Could you please be a bit more elaborate? :slight_smile:

I didn’t alocate Vram to the onboard graphics as I don’t know how to do it or that I needed to do this in the first place however when I checked in task manager my exefile.exe was using somewhere around 4.5GB of the memory at lowest graph so I imagine it is using it.

2nd answer on this: the AMD Software: Adrenaline Edition only sees 512 MB of VRAM from DDR5 3000 MHz. So I assume no, it doesn’t allocate enough memory for itself or maybe it changes while opening tasks that it would require it to allocate more. Where could I see if I need to allocate more memory to it?

This seems to have worked. I had hours of freeze free gaming after allocating the GPU fixed amount of 8GB of RAM to us it as memory. Now that I have done it eve’s exefile itself doesn’t use as much RAM as reported by the task manager as previously when the GPU had 512 MB of RAM allocated to it that could have been change automatically based on system needs.

I am assuming and might be wrongfully that if a the GPU runs out of it’s allocated VRAM it will start to use RAM as memory and when that happens the issue comes up. Not sure what conflicts there but it make sense that some ppl would have the crash on totally different systems running X amount of account on very different graphic settings. One of my friend sorted out his issue via changing from Dx 12 to Dx 11 on all of his machines. I guess that could also reduce memory load. What I have gathered is that the issue seems to came with windows 24H2 update for everyone who is involved in this.

Sorry, RL life got in the way and had to go to work.

But good you figured it out. I was seeing the 512mb of ram and seen online that would work if there was at least 1024mb of Vram. You kicked it up to 8gb of Vram should more than cover game needs.

I am using the same OS, and Im also getting random PC freezes and I have a good graphics card and a huge amount of RAM. The one thing im seeing is spiking CPU. I am running multiple clients though.

It must be related to the OS.

For minimum VRAM amount reference:

https://support.eveonline.com/hc/en-us/articles/5885219196828-System-Requirements

I have tried everything I read about that could work with the exception of windows 10 install or older windows 11 patch install (don’t install windows 10) and nothing works. Some guide or input from a CCP dev would actually be great.

Or, even better, they could focus on FIXING this crap instead of focusing on the dumbass Capsuleer Day garbage. Hell, they even ■■■■■■ THAT up this year… Daily free ■■■■ is complete trash. Unless you like to make skins, but even then, not very damn good :stuck_out_tongue:

Found a triger to this. Almost always today only for whatever reason?? Opening the character page where the 3D animated character would load crashes my system almost immediately. Previously I was using the clone junp page a lot and I think that page also loads the 3D animated character so I dunno what is all the sudden change about why it is crash but for the love of Amarr be so kind CCP and give us an answer already because this crash is literally only happe ing with rning eve online. Thanks.

I might have found a fix.. but I have no idea if it is an actual fix or the crashes just not happening now for whatever reason. In windows settings under system>display>graphics I have changed eve exefile’s setting from having optimisation for windowed mode turned on to off and also changed system decides what power usage it want to give to eve to forcing high performancd.

I have also turned on performance mode in AMD software but I doubt it would do much there as I have turned off all of the software based tuning such as AMD reflex and what not…

These changes I have done on the laptop. Compared to yesterday’s crashing every time I tried to alt tab on it now it never happened today, not even once.

I will end up trying these changes on the pc too to see if it would fix the problem there too.