Teardown - Experimental not lauching

[tardy thicket]

Hi, ive followed the steps in #1449430061282496603 message to give you logs

Where can I post my zip?

[trim gazelle]

Try posting it in here

[tardy thicket]

It wont let me

I cant upload files

Do I need image perms the role?

[trim gazelle]

Yes

[tardy thicket]

How do I get that?

[trim gazelle]

You will have to be in the server for a couple days

Couple days - month

[tardy thicket]

Ah okay

Any other way I can get my logs sent over? Looking to play teardown on stream later

[trim gazelle]

If you want you can copy some of it and paste if that’s possible

I don’t know how the logs look like

[tardy thicket]

Okay will see what I can do

[trim gazelle]

Or if a mod comes you can dm them if they accept it

[tardy thicket]

Okay thanks

[tardy thicket]

Anyone of the devs able to help? Still having yhis issue

This*

[late kettle]

Hi, would you be able to send the logs via DMs? 🙂

[tardy thicket]

Sure have sent them over

[late kettle]

Did not find anything that points to a specific issue, seems mostly like access violation and similar. Could be a bad driver, overclock that is unstable, system that is unstable, etc.
I see that you've had bluescreens, that might be the same or similar issue to why the game is crashing.

You could try this:

1. Press Windows+R, this should open a small window in the bottom left corner
2. Type "%localappdata%\Teardown" in the text box, and press ENTER. This will open the file explorer
3. Find the options.xml file and double click it, any text editor should work to open it with (e.g. Notepad)
4. Towards the top, find the line "<gfxapi value="1">", change the 1 to a 0, so it becomes "<gfxapi value="0">"
5. Save the file by pressing CTRL+S on the keyboard and close the file, try to launch Teardown

[tardy thicket]

Blue screens? Haven't had one of them in a while.

Ive tried change it to 0 unfortunately already but that still doesnt work.

[late kettle]

Ok, maybe those entries were a bit old. There's no timestamp on them so it only shows the latest major errors (which maybe weren't that recent) 😅

By the way, did it stop working recently or has experimental branch never worked? And does normal branch still work as usual?

[tardy thicket]

Haven't tried experimental before the multiplayer release to be honest, it loads up perfectly fine in normal mode but the minute I switch to Experimental, I click start and then thats it it doesnt load :/

Ive tried reinstalling, ive tried deleting my app data teardown folder to see if that works but unfortunately nothings helping 😅

[tardy thicket]

Anything else I can try?

[late kettle]

Well, I don't have anything solid that could be tried.
The error is as follows, and that doesn't narrow it down at all 😕

ExceptionAddress: 00007ff7d237be41 (teardown+0x00000000004ebe41)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

"often caused by outdated drivers, corrupted game files, antivirus interference, or overclocking, but can also point to faulty RAM or system issues; fixing it usually involves updating drivers (especially GPU), verifying game files, running as administrator, or disabling background apps like antivirus." - Google AI summary

[tardy thicket]

Im UK based so will have a check of my event viewer tomorrow right after trying to launch it and see what I can see,

Its weird how normal mode works,
Ive even gone to the trouble of deleting all mods/folders to make sure nothing is on the PC ect but will see what the event viewer says tomorrow

[tardy thicket]

This is what i've seen in Event Viewer:

Faulting application name: teardown.exe, version: 1.0.0.1, time stamp: 0x696753eb
Faulting module name: ntdll.dll, version: 10.0.26100.7623, time stamp: 0x5b6dddee
Exception code: 0xc0000005
Fault offset: 0x000000000001daa4
Faulting process id: 0x275D4
Faulting application start time: 0x1DC8C5EACC4BA48
Faulting application path: E:\SteamLibrary\steamapps\common\Teardown\teardown.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 010b6355-4a92-4a82-9684-97b155dfda68
Faulting package full name: 
Faulting package-relative application ID: ```


I've verified the game, done a clean GPU Driver install, repaired Windows system files, reset my RAM, and tried turning XMP off, till having the issue,

Whens the next experimental update coming out do you know?

[late kettle]

I now see that the game is located on another drive, have you tried moving it to the C: drive?
P.s., try this repair tool as well (after having tried moving the game)
https://aka.ms/vc14/vc_redist.x64.exe

[tardy thicket]

Okay have moved it to my C: drive and still no luck,
Ive tried repairing vc-redist-x64, uninstalling and reinstalling but something on my machine doesnt like it

Also checked Windows Security to see if anything from there is causing an issue and im not seeing anything obvious

[late kettle]

Weird.

A quite simple test you can try to narrow down the issue a lot is to make a new Windows user and just install Steam on that account. That will rule out any user account issues at least 🤔

[tardy thicket]

Okay I'll give that a go tomorrow

[tardy thicket]

Okay created a brand new user profile locally and still getting the same issue 🙁

[late kettle]

Ouch, well that rules out a lot of things but doesn't solve the problem...
It's very likely that this is a driver/hardware issue in this case since everything else failed, I'm unfortunately out of options but to recommend doing a Windows reinstall or a memory test https://memtest86.com/

If you already did a full DDU and Windows repair and that didn't work, then next in line is the RAM. But if RAM is the issue, you should be seeing this issue on more games than just Teardown 😕

[tardy thicket]

Okay done a memory test, everything passed so the error you was seeing must of been old

So not sure what else to try and apparently the RAM isnt the issue

[late kettle]

The error logs are from 2026-01-16, was that when the crash last happened?

1. Did you use the DDU tool for a clean GPU Driver install?
   https://www.reddit.com/r/pcmasterrace/comments/1ccssm0/complete_ddu_guide/

2. Did you try both of these when repairing Windows?
   a. "sfc /scannow"
   b. "dism /online /cleanup-image /restorehealth"

You also don't happen to be overclocking the CPU or similar?
And for the DDU, maybe try reinstalling another older driver version. Sometimes the latest one might not be the best.

If you've tried both of the commands I sent and did the display driver uninstall with the tool in the guide and it is still not working I'm unfortunately also out of ideas.
That's all the hardware that I could think of that may be causing these issues.

If you have any more up to date logs then feel free to send them over, maybe they have a different error that is more descriptive. Other then that, the only option would be a fresh Windows install (but that should be the really last option since it may not end up working if it's a hardware problem).

[tardy thicket]

Nope haven't overclocked my CPU or GPU,
Ive run ProcMon, and can see its failing to create d3d8.dll in Syste,32:

[tardy thicket]

Also getting the same for d3d.dll

[late kettle]

Could you save the output of the ProcMon log when you're trying to open the game and send over the result? 🙂

I don't think this issue has to do with the d3d8.dll opening (since that is likely just testing what dlls you have), but maybe something else in those logs could give a lead.

[tardy thicket]

Sure here is the PML file, let me know if you need it in XML or CSV

[late kettle]

Okay, this might be a stretch but I know OneDrive have caused various issues before so why not blame it for causing this one. If you aren't using OneDrive, https://youtu.be/eGxtK5WxiLA?si=Hpeayj_UWbz_46t7&t=6

[tardy thicket]

So I am using OneDrive, what is it you need me to set to local?

[late kettle]

Well, if you're using OneDrive I don't think you should try the solution I proposed (since it gets rid of it). I guess some more investigation has to be done into this issue since I see some other people have it as well 🤔

[tardy thicket]

Oh interesting, I wonder what hardware they have that matches mine
Are you seeing it mainly with AMD or Intel machines?

[late kettle]

Windows 11
Intel Core i7 930 2.80GHz
Radeon RX 470

As an example of someone else with the same problem 😕

[tardy thicket]

Yeah totally different,
Unless its something to do with the AMD overlay program is all that comes to mind right now, I can test tomorrow but disabling that unless you can confirm that user hasnt got that program running

[late kettle]

Try disabling that if you have it.

Any overlays in general might cause issues, so quite a long list 😅

[tardy thicket]

Ive gone through all of the overlay apps and disabled them, its still not working...this is stumping me big time!

Assuming you didnt see anything in the PML file?

[tardy thicket]

I need to test it but have just been given this "workaround"

verify integrity of game files, optionally set it as private in your steam library, spam the hell out of play for about 20-40 minutes and it will open