Godot crashing to the point where it's unusable

chompsie · December 8, 2025, 10:23pm

Godot Version

I have Godot 4.5.1

Issue

So recently, I’ve tried out Godot for my first time to make my 1st 3D game. And I’ve really enjoyed it! adding things is really easy, gdscript is a really nice and easy programming language, etc. I was really enjoying this engine until 2 days ago, when I started working on a title screen for my game. it just started randomly crashing, to the point where it is unusable I have no idea how it happened, I did ask the Godot discord server how to do this and to not much avail. Keep in mind, I have been working on my game for about a month. And I have a prototype of the game almost ready to send to a friend. I do have one window mode enabled, and I have been trying to get this working, and it just hasn’t. I am considering on just using a different game engine and I really don’t want to do that, since I had been really enjoying this engine. Is there any method to fix this?

FencerDevLog · December 9, 2025, 5:21am

Anything in your Godot log? System log? Any other log? What platform are you working on? What is your GPU? Have you updated your drivers recently?

Please provide as many details as possible.

Toxe · December 9, 2025, 2:07pm

What crashes? The editor or your game?
Try running it from the console with verbose output to see if there are any interesting messages.
Can you compile the source and run it in a debugger?

chompsie · December 9, 2025, 9:51pm

I haven’t updated my drivers in awhile, The godot logs haven’t been much use to me so far, I am working on windows, and I have 12 gigabytes of ram on my gpu.

marcythejinx · December 9, 2025, 10:48pm

This isn’t very informative, you should post your full log and system info, all the details are important. Also, keep your drivers and OS up-to-date, when you say you haven’t updated your drivers in a while you could be experiencing a driver related issue that was already solved. But I think if that doesn’t help you’re be better off opening an issue here anyway.

chompsie · December 13, 2025, 5:44pm

The editor keeps crashing.

chompsie · December 13, 2025, 6:01pm

If anyone has ever experienced this, and fixed this issue, please let me know! Every online forum I’ve seen showcasing this issue hasn’t been able to fix it. This is like the Xbox 360 red ring of death, but with the Godot engine.

CodeSmile · December 14, 2025, 3:21pm

Because “this issue” does not exist. There is no such issue as “Godot crashes” because the reasons for a crash are manifold.

It could be because of a bug in the software, but more commonly it’s because of the data thrown at it (your assets and scenes and scripts), or the machine it runs on (buggy drivers, failing hardware).

If you want a solution you need to provide the details as mentioned above! The logs specifically but also the actual behaviour that you observe since there is no uniform definition of “crash”.

You have the "plop and its gone” crash to desktop, you have various messages telling you the software has crashed (those details matter), you have the situation where the app is no longer responsive (frozen - could be a script of yours in an infinite loop), and of course you have the “entire OS is frozen” as well as “computer reboots”. The latter two are most commonly a system issue.

blazeblue32 · December 18, 2025, 11:29am

Never mind, it has started crashing again. Hard editor crash, including the console, so not dice there. Drivers and OS are up to date, running windows 11 with 32Gb ram, i7 13700k, RTX 5080, and not other applications are crashing like this. It just randomly crashes, not repeatable, but every few minutes, could be doing anything and it will just CTD.

I have an EV log, please let me know where I can find other logs that might be needed.

Log Name:      Application
Source:        Application Error
Date:          18/12/2025 9:25:37 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      
User:          
Computer:      
Description:
Faulting application name: Godot_v4.5.1-stable_win64.exe, version: 4.5.1.0, time stamp: 0x68ed4f8e
Faulting module name: nvoglv64.dll, version: 32.0.15.9144, time stamp: 0x692ea4f0
Exception code: 0xc0000005
Fault offset: 0x0000000000df4301
Faulting process id: 0x570C
Faulting application start time: 0x1DC7004554566B5
Faulting application path: C:\Godot\Godot_v4.5.1-stable_win64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_6d8eaa80a18aada4\nvoglv64.dll
Report Id: dd752363-e756-4e40-90fb-08f0ebf83b4c
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2025-12-18T10:25:37.1246729Z" />
    <EventRecordID>46159</EventRecordID>
    <Correlation />
    <Execution ProcessID="29580" ThreadID="24200" />
    <Channel>Application</Channel>
    <Computer>Blaze-PC</Computer>
    <Security UserID="" />
  </System>
  <EventData>
    <Data Name="AppName">Godot_v4.5.1-stable_win64.exe</Data>
    <Data Name="AppVersion">4.5.1.0</Data>
    <Data Name="AppTimeStamp">68ed4f8e</Data>
    <Data Name="ModuleName">nvoglv64.dll</Data>
    <Data Name="ModuleVersion">32.0.15.9144</Data>
    <Data Name="ModuleTimeStamp">692ea4f0</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">0000000000df4301</Data>
    <Data Name="ProcessId">0x570c</Data>
    <Data Name="ProcessCreationTime">0x1dc7004554566b5</Data>
    <Data Name="AppPath">C:\Godot\Godot_v4.5.1-stable_win64.exe</Data>
    <Data Name="ModulePath">C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_6d8eaa80a18aada4\nvoglv64.dll</Data>
    <Data Name="IntegratorReportId">dd752363-e756-4e40-90fb-08f0ebf83b4c</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

blazeblue32 · December 18, 2025, 11:29am

Hey mate, hope you’ve sorted it out, but if not, I was having the same issue as you, editor kept crashing, and I couldn’t find any logs to explain why. I was using the steam version, which doesn’t come with the console .exe that is needed to get the editors logs (afaik), so I downloaded Godot 4.5.1 from the Godot site instead, hoping to use the console version to find the issue, but turns out it doesn’t crash anymore, so perhaps is an issue with the steam version for some reason. Hope this helps, if not, at least using the console version of the exe will give you a better idea what is going wrong. I case you don’t already know the console version of the exe is included in all godot downloads from the site, the zip contains two .exe’s, the normal version, and the console version. I’m just getting into godot myself and it seems great compared to GMS, I’d be a shame if you had to loose all that work switching to another engine due to issue with steams version.

OleNic · December 19, 2025, 12:40pm

Looks like it’s crashing on Nvidia’s OpenGL driver.

davidicus · January 11, 2026, 4:22am

Godot editor seems to crash after ~two minutes of use here. Just closes, doesn’t seem to matter what I’m editing. I was using Steam’s 4.5.1 stable, so tried editing in recovery mode. No help.

I downloaded 4.5.1 stable separately to try it (same issue). I tried the console version, but the console crashed with it (is that expected?).

My project is the problem. Something went bad. I created a fresh empty project and couldn’t repro the issue. I seem to remember deleting a script (from Godot) soon before the trouble started, then tried adding a script to a Timer node (I think it died there)–might be related?

Short of starting from scratch, what’s the best way forward?

davidicus · January 11, 2026, 4:36am

That was quick. I deleted the project’s .godot folder. Seems to have ironed things out.

trizZzle · January 11, 2026, 4:44am

As the OPs problem seemed to be Nvidias OpenGL driver I just wanted to add that from Godot 4.6 on the default renderer is Direct3D 12 and not OpenGL anymore. Apparently there were too many problems with it. Maybe switching to Direct3D12 helps with 4.5.1 too. I’m not sure how much of a difference there is between 4.5.1 and 4.6. But the source might have more information on that.

Source:

github.com/godotengine/godot

Windows: Make Direct3D 12 the default RD driver for new projects

master ← akien-mga:windows-d3d12-default

opened 09:46PM - 26 Nov 25 UTC

akien-mga

+6 -2

- Implements and closes https://github.com/godotengine/godot-proposals/issues/12…234 Direct3D 12 support was added for the Windows platform in Godot 4.3 by @RandomShaper and further refined in later releases by @DarioSamo (both sponsored by W4 Games, so I'll obama-medal-meme my company a bit). In the 4.6 release cycle, @blueskythlikesclouds focused on fixing known issues with Direct3D 12, with the aim of making it the default RenderingDevice driver for Windows (this time sponsored by the Godot Foundation :1st_place_medal:). Why? Mainly because Vulkan support on Windows is giving us a lot of headache, with GPU drivers often being poorly maintained compared to their Direct3D 12 counterparts. We've seen many regressions in Nvidia and AMD drivers that would outright break Godot and games released with it (e.g. #109378 still ongoing). There are other issues such as Vulkan implicit layers which force us to use [hacks](https://github.com/godotengine/godot/blob/9dd6c4dbac70b28e8156255c3a2b78722772b036/main/main.cpp#L2081-L2097) to work around their harmful impact on Godot. It's understandable, most Windows games use modern APIs target Direct3D 12 on Windows, and thus these are the drivers GPU vendors put most work and testing into. So now that Direct3D 12 in Godot has more or less feature parity with Vulkan (see below), we want to try using it as the default option. See https://github.com/godotengine/godot-proposals/issues/12234 for more arguments in favor of defaulting to Direct3D 12. Some important aspects: - *Edit:* This only impacts **new projects** created in 4.6 or later. To use this new default in pre-existing Godot 4.5 projects, you should set the `rendering/rendering_device/driver.windows` project setting to `d3d12` manually. - Vulkan is still available and can be selected via the `rendering/rendering_device/driver.windows` project setting, or `--rendering-driver vulkan` on the command line. - ~This PR attempts to preserve the behavior of pre-existing projects by explicitly setting the driver to `vulkan` if it was unconfigured (default) prior to upgrading to 4.6. (Uses the approach added by @KoBeWi in #112607.) So by default, only new projects should default to `d3d12`.~ * *Edit:* Took a different approach in the end with similar results. Now `vulkan` stays the default for this setting, but `d3d12` is configured automatically for new projects created in 4.6. * When upgrading from 4.5, you should therefore change `rendering/rendering_device/driver.windows` to `d3d12` if you want to use the new default (recommended). - Compiling from source for Windows will now require downloading the dependencies needed by Direct3D 12. You can do it by running the `misc/scripts/install_d3d12_sdk_windows.py` script. Alternatively, you can compile with `d3d12=no` if you don't need it for your development work. - For PCVR users, we're aware that the Direct3D 12 backend doesn't have full parity with Vulkan yet (missing VRS and foveated rendering IIUC). So if that's a problem for your needs, you can switch back to Vulkan with the aforementioned project setting. - When using Wine to run Windows games on Linux/macOS, note that the system versions of Wine don't support Direct3D 12 by default. Godot should fallback gracefully to Vulkan in that case. On Steam/Proton, it should use Direct3D 12 by default through vkd3d-proton.

davidicus · January 11, 2026, 5:01am

Good to know, since I was wrong, and I’m crashing after all. I don’t think that was Chompsie’s Nvidia issue, but I’d love to know how to get a log like that to inform me about this

UPDATE

I ran Godot from PowerShell and found this, although it doesn’t appear every time. Ugh. C’mon Godot. This is a minimal project right now, just a theme with a font and some UI that displays the time.

WARNING: Failed to load cached shader, recompiling.
at: _load_from_cache (drivers/gles3/shader_gles3.cpp:612)
OpenGL API 3.3.0 Core Profile Context 25.12.1.251128 - Compatibility - Using Device: ATI Technologies Inc. - AMD Radeon RX 6700S

ANOTHER UPDATE

I bit the bullet and started recreating the project. It went fine until I created the theme resource and Godot crashed. “Aha” I thought, but no. I deleted the resource. Another crash when I moved a font and icon into the directory. Why is Godot so unstable suddenly? I can’t remember if it had ever crashed before this.