Wow crashing. not enough memory resources are available to process this command

Support Technical Support
1

This application has encountered a critical error:

Not enough memory resources are available to process this command.

Program: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe
ProcessID: 10448
ThreadID: 13924
File: D:\BuildServer\A\work-git\wow\Engine\Source\ObjectAlloc\ObjectAlloc.cpp
Line: 392

Requested 11185008 bytes of memory

<Exception.IssueType> Exception
Out of Memory
Exception.Summary:
Not enough memory resources are available to process this command.
Requested 11185008 bytes of memory at D:\BuildServer\A\work-git\wow\Engine\Source\ObjectAlloc\ObjectAlloc.cpp(392)
<:Exception.Summary>
Exception.Assertion:
DBG-ADDR<00007ff6933344ed>(“Wow.exe”)
DBG-ADDR<00007ff693334d53>(“Wow.exe”)
DBG-ADDR<00007ff694a44a5d>(“Wow.exe”)
DBG-ADDR<00007ff694a45057>(“Wow.exe”)
DBG-ADDR<00007ff694a45c30>(“Wow.exe”)
DBG-ADDR<00007ff693409222>(“Wow.exe”)
DBG-ADDR<00007ff6934077ce>(“Wow.exe”)
DBG-ADDR<00007ff693401241>(“Wow.exe”)
DBG-ADDR<00007ff693409d23>(“Wow.exe”)
DBG-ADDR<00007ff69340a1c3>(“Wow.exe”)
DBG-ADDR<00007ff69340b4a8>(“Wow.exe”)
DBG-ADDR<00007ff6933f5e27>(“Wow.exe”)
DBG-ADDR<00007ff695e76e3f>(“Wow.exe”)
DBG-ADDR<00007ff695e7722c>(“Wow.exe”)
DBG-ADDR<00007ff693325f1b>(“Wow.exe”)
DBG-ADDR<00007ff693346f0e>(“Wow.exe”)
<:Exception.Assertion>
Exception.HashBlock:
DBG-OPTIONS
ERROR #8
DBG-ADDR<00007ff6933344ed>(“Wow.exe”)
DBG-ADDR<00007ff693334d53>(“Wow.exe”)
DBG-ADDR<00007ff694a44a5d>(“Wow.exe”)
DBG-ADDR<00007ff694a45057>(“Wow.exe”)
DBG-ADDR<00007ff694a45c30>(“Wow.exe”)
DBG-ADDR<00007ff693409222>(“Wow.exe”)
DBG-OPTIONS<>
<:Exception.HashBlock>
Requested 11185008 bytes of memory
No

10.2.0.52649
Retail
<Jira.JiraProjectId> 11503
<Jira.JiraProjectKey> WOW10
<Exception.ProjectId> 10
<Exception.BuildNumber> 52649
<Exception.Branch> 10.2.0
Mainline
World of Warcraft
Client
Type: WoW
Wow.exe
Executable UUID: 1E079D9E-445D-42FD-8764-C257640D9453
<Wow.Platform> X64
<Exception.Platform> Win 11 (x86 64-bit)
User: tcati
Computer: TCATIZONE-PC
Virtual Memory: 0.00 MB
Free Disk Space: 654.42 GB
Exe Built: Dec 19 2023 16:27:12
0000007F 00001FFF 00000400
App Up Time: 0 days, 0 hours, 27 minutes, 0 seconds
System Up Time: 1 days, 7 hours, 18 minutes, 40 seconds
QueryPerformanceCounter
Current Frame: 142081
Current Time: 112719769
Current Tick: 16
0
1
Number of thread pool threads: 6/6/6 (High/Mid/Low)
Battle.net.exe
<Locale.Text> enUS
<Locale.Audio> enUS
Session Time(hh:mm:ss): 00:26:55
<SessionTime.Grouping> 00:15:00 - 00:29:59
Time in World(hh:mm:ss): 00:26:42
<TimeInWorld.Grouping> 00:15:00 - 00:29:59
Total Time in World(hh:mm:ss): 00:26:42
<TotalTimeInWorld.Grouping> 00:15:00 - 00:29:59
<Set.Addons.All.Loaded> DBM-Core 8a2800a
<Set.Addons.All.Loaded> DBM-StatusBarTimers 8a2800a
<Set.Addons.All.Loaded> DBM-VPVEM 4a6af0c
<Set.Addons.All.Loaded> DBM-Affixes
<Set.Addons.All.Loaded> AstralKeys 3.98
<Set.Addons.All.Loaded> Auctionator 10.2.9
<Set.Addons.All.Loaded> BigWigs v309.1
<Set.Addons.All.Loaded> BigWigs_Core v309.1
<Set.Addons.All.Loaded> BigWigs_Plugins v309.1
<Set.Addons.All.Loaded> Decursive 2.7.14
<Set.Addons.All.Loaded> Details #Details.20231219.12111.155
<Set.Addons.All.Loaded> Details_Compare2
<Set.Addons.All.Loaded> Details_EncounterDetails
<Set.Addons.All.Loaded> Details_RaidCheck
<Set.Addons.All.Loaded> Details_Streamer
<Set.Addons.All.Loaded> Details_TinyThreat
<Set.Addons.All.Loaded> Details_Vanguard
<Set.Addons.All.Loaded> GTFO 5.6.1
<Set.Addons.All.Loaded> Hekili v10.2.0-1.0.19a
<Set.Addons.All.Loaded> LittleWigs_BattleForAzeroth
<Set.Addons.All.Loaded> Plater Plater-v571-Retail
<Set.Addons.All.Loaded> RaiderIO_DB_US_M
<Set.Addons.All.Loaded> RaiderIO 10.2.0 (v202312210600)
<Set.Addons.All.Loaded> RaiderIO_DB_US_R
<Set.Addons.All.Loaded> RaiderIO_DB_US_F
<Set.Addons.All.Loaded> Simulationcraft 10.2.0-01
<Set.Addons.All.Loaded> WeakAuras 5.8.7
<Set.Addons.All.Unloaded> DBM-Core
<Set.Addons.All.Unloaded> DBM-GUI
<Set.Addons.All.Unloaded> DBM-StatusBarTimers
<Set.Addons.All.Unloaded> DBM-VPVEM
<Set.Addons.All.Unloaded> DBM-Brawlers
<Set.Addons.All.Unloaded> DBM-Affixes
<Set.Addons.All.Unloaded> DBM-Raids-Cata
<Set.Addons.All.Unloaded> DBM-Raids-Dragonflight
<Set.Addons.All.Unloaded> DBM-DragonIsles
<Set.Addons.All.Unloaded> DBM-WorldEvents
<Set.Addons.All.Unloaded> AstralKeys
<Set.Addons.All.Unloaded> Auctionator
<Set.Addons.All.Unloaded> BigWigs
<Set.Addons.All.Unloaded> BigWigs_Aberrus
<Set.Addons.All.Unloaded> BigWigs_Amirdrassil
<Set.Addons.All.Unloaded> BigWigs_BurningCrusade
<Set.Addons.All.Unloaded> BigWigs_Cataclysm
<Set.Addons.All.Unloaded> BigWigs_Classic
<Set.Addons.All.Unloaded> BigWigs_Core
<Set.Addons.All.Unloaded> BigWigs_DragonIsles
<Set.Addons.All.Unloaded> BigWigs_Legion
<Set.Addons.All.Unloaded> BigWigs_Options
<Set.Addons.All.Unloaded> BigWigs_Plugins
<Set.Addons.All.Unloaded> BigWigs_VaultOfTheIncarnates
<Set.Addons.All.Unloaded> BigWigs_WarlordsOfDraenor
<Set.Addons.All.Unloaded> BigWigs_WrathOfTheLichKing
<Set.Addons.All.Unloaded> Decursive
<Set.Addons.All.Unloaded> Details
<Set.Addons.All.Unloaded> Details_Compare2
<Set.Addons.All.Unloaded> Details_EncounterDetails
<Set.Addons.All.Unloaded> Details_RaidCheck
<Set.Addons.All.Unloaded> Details_DataStorage
<Set.Addons.All.Unloaded> Details_Streamer
<Set.Addons.All.Unloaded> Details_TinyThreat
<Set.Addons.All.Unloaded> Details_Vanguard
<Set.Addons.All.Unloaded> GTFO
<Set.Addons.All.Unloaded> Hekili
<Set.Addons.All.Unloaded> LittleWigs
<Set.Addons.All.Unloaded> LittleWigs_BattleForAzeroth
<Set.Addons.All.Unloaded> LittleWigs_BurningCrusade
<Set.Addons.All.Unloaded> LittleWigs_Cataclysm
<Set.Addons.All.Unloaded> LittleWigs_Classic
<Set.Addons.All.Unloaded> LittleWigs_Legion
<Set.Addons.All.Unloaded> LittleWigs_MistsOfPandaria
<Set.Addons.All.Unloaded> LittleWigs_Shadowlands
<Set.Addons.All.Unloaded> LittleWigs_WarlordsOfDraenor
<Set.Addons.All.Unloaded> LittleWigs_WrathOfTheLichKing
<Set.Addons.All.Unloaded> Plater
<Set.Addons.All.Unloaded> RaiderIO_DB_US_M
<Set.Addons.All.Unloaded> RaiderIO_DB_EU_M
<Set.Addons.All.Unloaded> RaiderIO_DB_KR_M
<Set.Addons.All.Unloaded> RaiderIO_DB_TW_M
<Set.Addons.All.Unloaded> RaiderIO
<Set.Addons.All.Unloaded> RaiderIO_DB_US_R
<Set.Addons.All.Unloaded> RaiderIO_DB_EU_R
<Set.Addons.All.Unloaded> RaiderIO_DB_KR_R
<Set.Addons.All.Unloaded> RaiderIO_DB_TW_R
<Set.Addons.All.Unloaded> RaiderIO_DB_US_F
<Set.Addons.All.Unloaded> RaiderIO_DB_EU_F
<Set.Addons.All.Unloaded> RaiderIO_DB_KR_F
<Set.Addons.All.Unloaded> RaiderIO_DB_TW_F
<Set.Addons.All.Unloaded> RareScanner
<Set.Addons.All.Unloaded> Simulationcraft
<Set.Addons.All.Unloaded> WeakAuras
<Set.Addons.All.Unloaded> WeakAurasArchive
<Set.Addons.All.Unloaded> WeakAurasModelPaths
<Set.Addons.All.Unloaded> WeakAurasOptions
<Set.Addons.All.Unloaded> WeakAurasTemplates
<Addons.HasAny.Loading> No
<Addons.HasAny.Loaded> Yes
0
0
No
<IME.Current> “”, {00000000-0000-0000-0000000000000000}, inactive
<SoundSystem.Restarts> 0
<LoadingScreen.Enabled> No
<CombatLogEntry.Current> CombatLogEntry::PushEvent(casterGuidType, targetGuidType): 2, 2
Number of successful WoWConnections: 17
<Realm.Name> Stormrage
<Realm.IP> 66.40.179.235:3724
<Realm.Version> 10.2.0.51825
<Realm.Flags> 0xA0
Battle Tag: catizone#1295
1763
<LocalZone.Name> Atal’Dazar
<LocalZone.AreaID> 9028
Local Player: Osolemnly, Player-60-0F3F9DA4, (1763, -822.752, 2522.31, 731.574)
Current Object Track: Hammurabi, Player-60-0EA28EBE, (1763, -823.79, 2508.88, 730.225)
Locked Target: Yazma, Creature-0-4215-1763-12149-122968-00000773D5, (1763, -821.819, 2503.71, 730.227)
Last Enemy Target: Yazma, Creature-0-4215-1763-12149-122968-00000773D5, (1763, -821.819, 2503.71, 730.227)
Selected Player: Player-60-0F3F9DA4
<Character.Info.Race> Night Elf
<Character.Info.Class> Hunter
<Character.Info.Spec> Beast Mastery

CVar Settings:
<CVar.RAIDgroundEffectDist> 160
<CVar.CACHE-WQST-QuestObjectiveHotfixCount> 0
<CVar.Sound_MasterVolume> 0.15000000596046
<CVar.groundEffectDist> 200
<CVar.raidGraphicsTextureResolution> 2
<CVar.terrainLodDist> 500
<CVar.playIntroMovie> 11
<CVar.raidGraphicsProjectedTextures> 1
<CVar.CACHE-WQST-QuestObjectiveXEffectRecordCount> 25291
<CVar.RAIDreflectionMode> 0
<CVar.CACHE-WQST-QuestV2RecordCount> 55933
<CVar.reflectionMode> 0
<CVar.Sound_EnableAmbience> 0
<CVar.RAIDparticleMTDensity> 70
<CVar.graphicsDepthEffects> 3
<CVar.lodObjectCullSize> 18
<CVar.RAIDparticleDensity> 50
<CVar.portal> US
<CVar.raidGraphicsEnvironmentDetail> 4
<CVar.interactKeyWarningTutorial> 1
<CVar.graphicsQuality> 7
<CVar.agentUID> wow
<CVar.Sound_AmbienceVolume> 0.80000001192093
<CVar.KioskLobbyKickSeconds> 30
<CVar.raidGraphicsGroundClutter> 4
<CVar.Sound_DialogVolume> 0.65000003576279
<CVar.RAIDsunShafts> 1
<CVar.graphicsProjectedTextures> 1
<CVar.waterDetail> 2
<CVar.CACHE-WQST-QuestObjectiveRecordCount> 55001
<CVar.Sound_MusicVolume> 0.30000001192093
<CVar.raidGraphicsDepthEffects> 2
<CVar.maxFPS> 0
<CVar.horizonStart> 1900
<CVar.RAIDlodObjectMinSize> 0
<CVar.sunShafts> 2
<CVar.raidGraphicsSpellDensity> 4
<CVar.audioLocale> enUS
<CVar.RAIDgraphicsQuality> 4
<CVar.physicsLevel> 2
<CVar.SSAO> 4
<CVar.raidGraphicsViewDistance> 4
<CVar.shadowTextureSize> 2048
<CVar.graphicsTextureResolution> 2
<CVar.projectedTextures> 1
<CVar.RAIDfarclip> 6000
<CVar.TerrainLodDiv> 512
<CVar.Sound_OutputDriverName> System Default
<CVar.RAIDWaterDetail> 2
<CVar.graphicsGroundClutter> 6
<CVar.farclip> 7000
<CVar.graphicsLiquidDetail> 2
<CVar.textLocale> enUS
<CVar.raidGraphicsComputeEffects> 2
<CVar.graphicsShadowQuality> 4
<CVar.RenderScale> 1
<CVar.RAIDwmoLodDist> 350
<CVar.shadowSoft> 1
<CVar.seenLevelSquishPopup> 1
<CVar.RAIDVolumeFog> 1
<CVar.groundEffectDensity> 80
<CVar.Sound_EnableDialog> 0
<CVar.engineSurveyPatch> 100200
<CVar.raidGraphicsParticleDensity> 3
<CVar.graphicsSpellDensity> 4
<CVar.RAIDhorizonStart> 1400
<CVar.hwDetect> 0
<CVar.videoOptionsVersion> 37
<CVar.raidGraphicsLiquidDetail> 2
<CVar.vsync> 0
<CVar.maxFPSBk> 10
<CVar.graphicsEnvironmentDetail> 6
<CVar.shadowMode> 3
<CVar.gxApi> d3d11
<CVar.graphicsComputeEffects> 3
<CVar.shadowBlendCascades> 1
<CVar.Sound_SFXVolume> 0.80000001192093
<CVar.raidGraphicsOutlineMode> 1
<CVar.SSAOType> 1
<CVar.RAIDentityLodDist> 8
<CVar.Sound_EnableSFX> 0
<CVar.gameTip> 110
<CVar.RAIDgroundEffectDensity> 64
<CVar.expandUpgradePanel> 0
<CVar.RAIDlodObjectFadeScale> 90
<CVar.refraction> 2
<CVar.OutlineEngineMode> 2
<CVar.RAIDrippleDetail> 1
<CVar.useUiScale> 1
<CVar.RAIDTerrainLodDiv> 512
<CVar.CACHE-WQST-QuestObjectiveXEffectHotfixCount> 0
<CVar.raidGraphicsSSAO> 2
<CVar.engineSurvey> 8
<CVar.MSAAQuality> 2
<CVar.RAIDhorizonClip> 6000
<CVar.CACHE-WGOB-GameObjectsRecordCount> 108028
<CVar.targetFPS> 50
<CVar.graphicsParticleDensity> 5
<CVar.RAIDVolumeFogLevel> 1
<CVar.rippleDetail> 1
<CVar.entityShadowFadeScale> 25
<CVar.horizonClip> 7000
<CVar.RAIDshadowMode> 2
<CVar.RAIDlodObjectCullSize> 20
<CVar.graphicsViewDistance> 6
<CVar.RAIDweatherDensity> 1
<CVar.CACHE-WGOB-GameObjectsHotfixCount> 2
<CVar.CACHE-WQST-QuestV2HotfixCount> 1
<CVar.KioskCharacterTemplateSet> 0
<CVar.wmoLodDist> 400
<CVar.weatherDensity> 3
<CVar.RAIDentityShadowFadeScale> 20
<CVar.RAIDrefraction> 1
<CVar.gxMaximize> 1
<CVar.graphicsOutlineMode> 2
<CVar.LowLatencyMode> 2
<CVar.volumeFog> 1
<CVar.raidGraphicsShadowQuality> 2
<CVar.RAIDprojectedTextures> 1
<CVar.uiScale> 0.64999997615814
<CVar.lodObjectMinSize> 0
<CVar.RAIDSSAO> 2
<CVar.graphicsSSAO> 4
<CVar.RAIDOutlineEngineMode> 1
<CVar.cameraFov> 85
<CVar.KioskCanSessionExpire> 1

Installation settings:

UID: wow
Expansion Level: 9
PTR: 0
Beta: 0
ProductCode: ‘WoW’

           GxInfo

D3D11
<Graphics.ShaderModel> dx_5_0
Modified
Yes
<Graphics.UMDVersion> 31.0.0015.4633
<Graphics.DriverDate> 2023-12-06
<Graphics.VendorID> 0x10DE
<Graphics.PCIIdentifier> VID=0x10DE,DID=0x2882,REV=0xA1,SSID=0x00001726
Graphics.DeviceID 0x2882
<Graphics.DeviceName> NVIDIA GeForce RTX 4060
<Graphics.VideoMemory> 7971 MB
0
0
0
0
No
Locally overridden files
-2 : Cache/TitleIcons/09dbf2bd4f836f95123e02392657828a56eb20d6258ce79070eebfb4dbdd510b.png
-11 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\7547106c78f6de3acffcdc69bafada65f68398d870cef88d080d4594456f6b47.png
-10 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\6c490fa8e0cc976778f4141d62fb2d9271c7ba3491d8e1bd5f1d410c27d9f551.png
-8 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\3dc6fb402b907e5e677e039d4c22743b3a7b05f810c60e1b94c3cad369a1656f.png
-13 : Cache/TitleIcons/a72103e6c80f871d614d79237c6796fc75802d3ff8cb2bc687ed3285570b90af.png
-9 : Cache/TitleIcons/6362ed5e723d65a69c79519951fead8e3a408d2fa11dc673acc8a28b4190a1af.png
-20 : C:\Program Files (x86)\World of Warcraft_retail_\Fonts\615960.slugo
-7 : Cache/TitleIcons/31286255cc05f4509c87e09cde02df40e78b870873f3e3354b90a2dd28e15cb0.png
-22 : C:\Program Files (x86)\World of Warcraft_retail_\Fonts\615971.slug
-12 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\a4822f7b29f1375da1c0c05170072e467d939381f973e3e7ad8fa761e804559d.png
-15 : Cache/TitleIcons/c58f2d994a6ee537901c5b6e68f575273d4ef82f7318407f7e7b8d1964dbbf5f.png
-4 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\225231c6bc737ca317db2e94565b1820d8a25a7e6c24f92f0e37fe2fbdb63f54.png
-16 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\TitleIconsIndex.json
-3 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\0d377a123751339d655fde92c3d5bd9753516c8ccf6037f46ba96a2b76752f2b.png
-14 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\be2c0ac361624a41bf18d00fbf4e61c206e9482983150f06b4e557976b0c3fe1.png
-23 : C:\Program Files (x86)\World of Warcraft_retail_\Fonts\615974.slug
-21 : C:\Program Files (x86)\World of Warcraft_retail_\Fonts\615968.slug
-19 : C:\Program Files (x86)\World of Warcraft_retail_\Fonts\615960.slug
-7150 : C:\Program Files (x86)\World of Warcraft_retail_\Screenshots\WoWScrnShot_122223_084326.jpg
-7149 : C:\Program Files (x86)\World of Warcraft_retail_\Screenshots\WoWScrnShot_121323_171404.jpg
-1 : C:\Program Files (x86)\World of Warcraft_retail_.flavor.info
-6 : Cache/TitleIcons/268465f985233f504c8101f946ece79c8d3e518913aabdc09ff94f5aca429b71.png
-5 : C:\Program Files (x86)\World of Warcraft_retail_\Cache\TitleIcons\25b2afa8a57a757e4df933979bd8c5da996e3efb576b3ea942210f12f1e403c0.png

Percent memory used: 47
Total physical memory: 34057973760 (31.72G)
Free physical memory: 17799548928 (16.58G)
Total Page file: 84389621760 (78.59G)
Free Page file: 215040000 (205.08M)
Total virtual memory: 140737488224256 (128.00T)
Free virtual memory: 140719388487680 (127.98T)
<Memory.HighLoad> No
<Memory.LowPageFile> Yes

Working Set Size: 5994070016 (5.58G)
Peak Working Set Size: 6543835136 (6.09G)
Pagefile Usage: 8270065664 (7.70G)
Peak Pagefile Usage: 10594201600 (9.87G)
Page Fault Count: 8037731
Quota Paged Pool Usage: 1523968 (1.45M)
Quota Peak Paged Pool Usage: 2070712 (1.97M)
Quota Non-Paged Pool Usage: 479760 (468.52K)
Quota Peak Non-Paged Pool Usage: 519848 (507.66K)

Loaded Module Total: 341.27M
Debug Tracking Total: 0.00B

List of running Wow.exe processes

Process: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe; pid: 10448

List of running Agent.exe processes

Process: C:\ProgramData\Battle.net\Agent\Agent.8445\Agent.exe; pid: 19300

Dump file written with return: (0) The operation completed successfully.

2 Likes
2

How full are your hard drives? Most SSDs require 15–20% free space to operate optimally.

If that space is available, then you may have some process running in the background eating up the available pagefile space.

3

my hard drives are about 50% i still have 500gb to use

so im running wow and when i join a group my disk usage shoots up quite a bit but settles back down
 im trying to google it but get nothing. i have 450GB free on my 1tb SSD and 300gb free on my back up one

4

Definitely seems like some app in the background is eating up the pagefile. Anything suspicious in the task manager?

Some of the tech users on the Microsoft forum will read the dump file for you, but that’s not something I handle in these forums.

1 Like
6

Interesting
 I had similar earlier today as well, seemingly out of nowhere, but it threw the exception from a different file, happened right after I hearthed from Emerald Dream back to Valdrakken.

Not enough memory resources are available to process this command. Requested 14210864 bytes of memory at D:\BuildServer\A\work-git\wow\Engine\Source\Model2\M2Shared.cpp(1163)

And similar pagefile madness where it had hugely inflated the size of what is normally an unused pagefile to 86GB even though I also had free physical memory available. Error and crash happened when the pagefile outgrew the free space of the drive it was on seemingly.

Percent memory used:    81
Total physical memory:  34264268800 (31.91G)
Free physical memory:   6349959168 (5.91G)
Total Page file:        92616593408 (86.26G)
Free Page file:         500822016 (477.62M)
Total virtual memory:   140737488224256 (128.00T)
Free virtual memory:    140665584558080 (127.93T)
<Memory.HighLoad> No
<Memory.LowPageFile> Yes
------------------------------------------------------------------------------
Working Set Size:       6256492544 (5.83G)
Peak Working Set Size:  8687398912 (8.09G)
Pagefile Usage:         14752587776 (13.74G)
Peak Pagefile Usage:    14967136256 (13.94G)
Page Fault Count:       10531498
Quota Paged Pool Usage:           1812144 (1.73M)
Quota Peak Paged Pool Usage:      2796848 (2.67M)
Quota Non-Paged Pool Usage:       410624 (401.00K)
Quota Peak Non-Paged Pool Usage:  624160 (609.53K)

Have never observed this as an issue before today. After WoW crashed, everything but Chrome was fine, but had to kill Chrome as well. Rebooted for a clean start though, did a couple Windows Updates (Windows 10), and moved pagefile to another drive with more free space, but also limited in size with custom min 5G, max 15G in case it ran amok again.

Started up WoW this evening, and an hour or so into playing, pagefile was seemingly still at the recommended 5GB I had set previously as the custom minimum. Another two hours later, it had inflated it from 5G to 11G and growing, the WoW process had caused 60 million page faults (more than twice as many as anything else running), was using 6G physical still, but commit size was up to 16GB which is in line with the pagefile inflation. Closed it
 commit size dropped way back down, system sittting at 14GB used physical mem out of 32GB after closing WoW.

Unclear why it seems to be ignoring available physical memory and paging out so much, or why it just started doing it today. Going to do more testing tomorrow with wiped out AddOns/Cache/WTF/etc and then also rolling back any addons that updated in the last two days to see if maybe it’s one of those. Both AllTheThings and Oribos Exchange updated are are large data addons, so maybe related to one of them.

1 Like
7

I have had the exact same problem for over a week now. Out of nowhere last week I was mid-dungeon and got this crash, and RIGHT after the crash, when I reloaded, the Battle.net client did an ~400MB patch ( not on a patch day ).

Ever since, it crashes at least 3-4 times per day - doesn’t matter what I’m doing. I’ve just been sitting on Valdrakken, I’ve been mid-dungeon, mid-raid, it can happen anywhere, any time.

Like you, I have almost 500GB free on my SSD, I’ve run task manager and there’s literally 0 spikes of any kind in either memory, HDD, CPU, or network for that matter. When it happens my RAM is typically only 20% in use, plenty of room.

I’ve done a scan and repair of the WoW files via the battle.net client, I’ve run a chkdsk/scandisk and no errors/issues/repairs needed. I’ve checked if the drive needs to be optimized, and it’s fine/current. I’ve tried disabling all add-ons, I’ve tried setting the graphics to low ( looks like minecraft ), I’ve tried rolling back graphic driver versions. I’ve tried paring down my start-up and running applications such that literally, WoW is the only application running, and it still happens.

IMO, this is a problem on WoW’s end that needs to be patched or something, because I never had ANY problems, ever - literally 0 crashes - for YEARS, and all of a sudden now it happens?

It’s so frustrating too because it’s unpredictable, so I just have to warn people I might crash but I’ll be back asap, and then I live my gaming life in fear of it happening at the worst moment. I typically main healer so I’ve had to only do DPS which I don’t like, just because it’s less impactful if I d/c for the group/raid.

4 Likes
8

Tonight has been the worst it’s ever been - literally can’t go longer than 2-3 minutes without a crash. Can we get some dev eyes on this or something please?

2 Likes
9

you want to rename the following folders interface, cache and wtf then test. add .bak to each folder

10

I’, getting the same thing. The only thing new I’ve started using on this computer is microsoft edge. It’s uses the most resources net to battlenet on mine.

1 Like
11

FWIW - I have literally never even opened Edge on my computer. So we can rule that out. It’s got to be something with the most recent patch IMO - too coincidental to be otherwise.

1 Like
12

I ended up trying a number of things to resolve this, and it has since stopped happening.

After having this happen multiple times in WoW, I also had it happen while playing Destiny 2. Then while testing, I found I could also cause runaway memory issues just loading videos in tabs in Chrome and Firefox both. Started to suspect the latest nvidia driver 546.33, as they added in an option in the settings for “CUDA - Sysmem Fallback Policy” for falling back to system memory
 though it sounds like it’s been able to do that functionality for some time for Stable Diffusion, the option to configure it is new. That seemed like a possible cause though since system memory was running wild and paging
 but turning it off seemed to make no difference. And further, I had had that version installed since Dec 13th, and didn’t have any issues until the 27th despite being on vacation for the holidays and playing games constantly. But many many tests after adjusting options and reboots later, it was still happening
 usually just took some time. Also found an nvidia developer thread about a possible memory leak in cudaGraphicsMapResources from October that made me think it could be driver related still despite it not being recently installed.

Got tired of trying to figure out exactly what it was though, and eventually just DDU removed 546.33 and reverted nvidia drivers back all the way to 537.58, even though I hadn’t been having any issues in 545.92, 546.01, or 546.08, etc either. Since reverting to 537.58 though, I have had ZERO issues. Not in WoW, not in D2, not with browser tabs loading videos.

Would be curious if other people running into it were also on 546.33 nvidia GRD driver. Looks like OP was, but two people doesn’t really say much. I have yet to try and re-upgrade to newer versions incrementally to verify it doesn’t happen with them, and also haven’t tried to see if going all the way back up to 546.33 again causes it to start happening again either. Will update if I do, but hoping they just get a new driver out for the new year shortly with a known issue/resolved issue for it, to avoid dealing with it further myself.

1 Like
13

I’ve been on the Nvidia 546.33 this entire time as well, and as with you had tried rollback with no success.

I have noticed the crashing much less lately though - the only thing I did was since another person had mentioned pagefile, I checked and I run WoW out of my secondary drive, which by default doesn’t have a pagefile. So I manually set a pagefile on it, system managed just because why not. It still crashed a few times immediately after but now it has gone from 5-10 times a play session ( at random times throughout ), to maybe 2-3 times a week.

I don’t know if the pagefile change actually did anything though. This was all happening while the Xmas-theme stuff was going on, I wonder if it’s somehow related? I can’t imagine why Tyr wearing a santa hat would cause crashes but
it’s all I’ve got at this point.

14

Rolling back to 537.58 DID work for me, I haven’t had a single issue or crash since using DDU to fully remove 546.33 in safe mode and installing 537.58 normally after that.

Have been leaving Process Explorer’s memory graph open for the last couple weeks to watch for it to runaway again, but it hasn’t happened even once since the rollback. To note, I don’t normally shut off or reboot my system except for when doing monthly updates, so it has been up for almost 17 days straight currently, gaming every day.

And for reference, only went with 537.58 because the nvidia subreddit threads for every new version of the geforce driver lately all seem to indicate that that was the last really stable/well-perfoming version for a lot of people, so figured it was the best choice to go back to for now, despite some of the newer versions seemingly having been fine previously as well.

15

Currently having the same issues. 546.65 and crashed today after install
 fill me in where im dumb, I only have 1 drive on my machine C:\ , why is this calling "D:" ?
D:\BuildServer\A\work-git\wow\Engine\Source\ObjectAlloc\ObjectAlloc.cpp

I left wow for years
came back played my 30days free, subbed then all hell breaks loose with these crashes? I have zero intention of keeping my 12mo sub if this is a constant issue


16

That path was the path of the source file in the file system on the build system at Blizzard when the WoW client was built, not a path on your local machine.

I saw 546.65 was out, and was debating installing them tomorrow when I have a full day to mess around with updating and reverting and rebooting a bunch of times, but didn’t see anything in the release notes to indicate anything had changed that seemed relevant, so based on your comment, sounds like I may not bother.

537.58 drivers are still happy for me, system has been up 22 days, not a single crash of WoW or Destiny 2 still since, no out of memory errors with anything at all, with physical memory use capping out around 23 GB / 32GB used while gaming, never going higher, never dipping into the pagefile to grossly inflate it until crash. For anyone else’s reference/comparison, my overall system is a Ryzen 7 5800X, ASUS B550-TUF, 32GB Corsair DDR4, WoW and Destiny 2 running off NVME drive
 with an EVGA RTX 3050 8GB card.

17

You’re probably right about the Nvidia drivers, but this right here - does this not seem like a huge bug? WoW doesn’t even sanitize bug pops to NOT include the build system in-house???

Regardless seems like WoW itself is also part of the problem here surely?

18

OK few things took place as i was attempting fixes –
Still on - 546.65
system for reference - R7 7800x3d, 32g ddr5, tuf mobo.
reviewed NZXT Cam for mem leaks all good
reviewed Armoury crate for mem leaks - attempted uninstall but not sure i got it all as their uninstaller failed - most things are gone.
spun up wow after these things - and there was a small download prolly a hotfix of some sort - unknown reason for download – few days so far zero issue – however i also noticed that my committed ram and cached drop now after shutting down wow – where this was not happening, its like it was holding on to resources and not releasing it.

19

I’m probably going to jinx it but I haven’t crashed in over a week now. I haven’t changed anything whatsoever from my previous post, I feel like there may have been a WoW patch maybe? Hard to say, but no issues at all

20

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.