non sequitur, minimum requirement for war3 includes win7, your comment is a waste of bandwidth.
1 Like
Warcraft III
<Exception.ProjectId>264
<Exception.JiraProjectId>19202
<Exception.JiraProjectKey>WAR3
<Exception.BuildNumber>22370
<Exception.Platform>Windows
<Exception.DesktopOS>Win
<BlizzardError.AffectsVersions>War III 2.0.0
<BlizzardError.FixVersions>War III 2.0.X
<BlizzardError.Source>Blizzard Error Report
<BlizzardError.Language>English
<Exception.IssueType>Exception
<Exception.Priority>1
<Process.Name>\Device\HarddiskVolume3\Program Files (x86)\Warcraft III_retail_\x86_64\Warcraft III.exe
<Process.Parent.Name>\Device\HarddiskVolume3\Program Files (x86)\Battle.net\Battle.net.exe
<Process.CommandLine>“C:\Program Files (x86)\Warcraft III_retail_\x86_64\Warcraft III.exe” -launch -uid w3
<Mem.PhysicalUsed>168 MB
<Mem.VirtualUsed>568 MB
<Mem.Committed>124 MB
<Mem.PhysicalAvailable>56924 MB
<Mem.VirtualAvailable>8388040 MB
<Mem.PageAvailable>119820 MB
Exception.Summary:
ACCESS_VIOLATION (Failed to write address 0x0000000000000000 at instruction 0x00000001414CF988) DBG-OPTIONS DBG-ADDR<00000001414CF988>(“”) ← DBG-ADDR<000000013FAEC0AB>(“”) ← DBG-ADDR<000000013F9EBE4D>(“”) DBG-OPTIONS<>
<:Exception.Summary>
I have just the same error report. Bad instructions are the same: “0x00000001414CF988”.
Warcraft III
<Exception.ProjectId>264
<Exception.JiraProjectId>19202
<Exception.JiraProjectKey>WAR3
<Exception.BuildNumber>22370
<Exception.Platform>Windows
<Exception.DesktopOS>Win
<BlizzardError.AffectsVersions>War III 2.0.0
<BlizzardError.FixVersions>War III 2.0.X
<BlizzardError.Source>Blizzard Error Report
<BlizzardError.Language>English
<Exception.IssueType>Exception
<Exception.Priority>1
<Process.Name>\Device\HarddiskVolume7\Games\Warcraft III_retail_\x86_64\Warcraft III.exe
<Process.Parent.Name>\Device\HarddiskVolume7\Programs\Battle.net\Battle.net.exe
<Process.CommandLine>“X:\Games\Warcraft III_retail_\x86_64\Warcraft III.exe” -launch -uid w3
<Mem.PhysicalUsed>297 MB
<Mem.VirtualUsed>705 MB
<Mem.Committed>303 MB
<Mem.PhysicalAvailable>12401 MB
<Mem.VirtualAvailable>8387903 MB
<Mem.PageAvailable>12464 MB
Exception.Summary:
ACCESS_VIOLATION (Failed to write address 0x0000000000000000 at instruction 0x0000000141B1F988) DBG-OPTIONS DBG-ADDR<0000000141B1F988>(“”) ← DBG-ADDR<000000014013C0AB>(“”) ← DBG-ADDR<000000014003BE4D>(“”) DBG-OPTIONS<>
<:Exception.Summary>
Info from test based on Windows 11. It seems that the problem is related to nullptr (null pointer), because of “Failed to write address 0x0000000000000000”.
Warcraft III
<Exception.ProjectId>264
<Exception.JiraProjectId>19202
<Exception.JiraProjectKey>WAR3
<Exception.BuildNumber>22385
<Exception.Platform>Windows
<Exception.DesktopOS>Win
<BlizzardError.AffectsVersions>War III 2.0.0
<BlizzardError.FixVersions>War III 2.0.X
<BlizzardError.Source>Blizzard Error Report
<BlizzardError.Language>English
<Exception.IssueType>Exception
<Exception.Priority>1
<Process.Name>\Device\HarddiskVolume5\Warcraft III_retail_\x86_64\Warcraft III.exe
<Process.Parent.Name>\Device\HarddiskVolume3\Program Files (x86)\Battle.net\Battle.net.exe
<Process.CommandLine>“E:\Warcraft III_retail_\x86_64\Warcraft III.exe” -launch -uid w3
<Mem.PhysicalUsed>286 MB
<Mem.VirtualUsed>4591 MB
<Mem.Committed>62 MB
<Mem.PhysicalAvailable>1625 MB
<Mem.VirtualAvailable>134213137 MB
<Mem.PageAvailable>3189 MB
Exception.Summary:
ACCESS_VIOLATION (Failed to write address 0x0000000000000000 at instruction 0x00007FF64D12E578) DBG-OPTIONS DBG-ADDR<00007FF64D12E578>(“Warcraft III.exe”) ← DBG-ADDR<00007FF64B71FC8B>(“Warcraft III.exe”) ← DBG-OPTIONS<>
<:Exception.Summary>
scroll all the way down, and look for vRam and see if it is being initialized.
it should be vRam = ??
Yes, it was initialized (in my case). I got this row in Windows 7:
<GPU.vram>5983 MB
1 Like
I don’t think there is a simple fix or workaround to be found by studying the error logs… let’s hope this gets some moderator/developer attention now after the successful mac hotfix
1 Like
how do you think devs debug applications ?
Not really with generic error logs that look the same since wc3 was first released decades ago. This requires a global fix or at least a statement that there is and will be no more win7 support for the game from now on
Errors are the same because code is still the same. Those exceptions point to something specific that’s broken.
Like in this case ::: ACCESS_VIOLATION (Failed to write address 0x0000000000000000 at instruction 0x00000001416AE578) ::: is a null pointer pointing to address that hasn’t been created yet. This a GPU issue. Possibly has to do with directX12
Reforged has various toggles for different audio/visual settings, I am guessing default settings aren’t compatible with legacy hardware.
This isn’t to do with windows 7 per se, more so to do with GPUs not supporting Dx12,
can you try running warcraft 3 with these commandline parameters battle.net > warcraft 3 > options > game settings> additional command-line arguments -graphicsapi Direct3D9
if it’s the gpu, it should say something about the GPU or the operating system.
3 Likes
Seems you are correct, Tenrai. The game launches with -graphicsapi Direct3D9
1 Like
Thank you Tenrai!; After adding the additional command line works perfectly on my windows 7 machine.
Edit: Although the game launches, once you reach the title screen the game mouse is invisible.
I created a single player custom game and there are all ton of graphical glitches so much so I can not play the game.
3 Likes
Same problem here. The mouse is invisible but the game start with that command line.
The game editor (world editor) still crash instantly. Each map has massive graphical glitches and is umplayeable.
Same for me. So wc3 glitches with direct3d9 and the default (which is directx11 atm?) doesn’t launch on win7 it seems
can you guys check options? try toggling different graphical settings.
The invis cursor and glitches ingame seem to be a known thing → No cursor and games don't load properly - Technical Support - Warcraft III: Reforged Forums
Doesn’t really work for me. The game only takes me to a black screen now instead of terminating with an error.
I’m surprised the game even launched under DX9 considering they disabled it at some point after Reforged was released along with OpenGL.
OpenGL2 command doesn’t work though.
-graphicsapi OpenGL2
-graphicsapi OpenGL3
-graphicsapi OpenGLCore
-graphicsapi OpenGL4
-graphicsapi Vulkan
-graphicsapi Direct3D11
Try it, maybe some of this will help