Ableton Crash on Loading VST [v3.0.63 x64]

Windows/Mac DAW guides (VST/AU)
,
1

Hi,

I’ve downloaded the demo version of MG3 for Win10 and I’m trying to use it with Ableton Live Suite 12. However, as soon as I load the VST into any Ableton project (an existing one, or a new blank project), Ableton itself instantly crashes.

The dump from Ableton gives the error as: 0xc0000005 The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

The MG3 VST log gives the following:

Log

MIDI Guitar 3.0.63 - 64-bit
Log started: 20 Jan 2026 11:49:06am

Log file: C:\Users*\AppData\Roaming\JamOrigin\MIDI Guitar Log VST3.txt
Patch dir: C:\Users*\AppData\Roaming\JamOrigin\Patches\MIDI Guitar
MIDI Guitar 3.0.63
Initializing platform
Initializing plugin formats
Offbeat Engine is ready
User Directory: C:\Users*\AppData\Roaming\JamOrigin
Setup Offbeat Engine
Loading Patch Settings and MIDI Control
Preparing to play: 48000/256
Offbeat Engine processing 48000
Releasing resources
Offbeat Engine suspending 48000
Preparing to play: 48000/256
Offbeat Engine processing 48000
Releasing resources
Offbeat Engine suspending 48000
Preparing to play: 48000/256
Offbeat Engine processing 48000
Number of audio channels: 2/2
Downloaded: C:\Users*\AppData\Roaming\JamOrigin\Preferences\serverinfo.txt
Mounting dedicated input TOPPING Pro USB Audio Device
Dedicated input TOPPING Pro USB Audio Device 48000 128 1
Loading Patch: MIDI GUITAR MINI
Loading MIDI MINI patch
Crash:
0: GetPluginFactory + 0x7c725
1: GetPluginFactory + 0x424c92
2: GetPluginFactory + 0x7cb0a
3: UnhandledExceptionFilter + 0x1e7
4: memset + 0x1218
5: _C_specific_handler + 0x96
6: _chkstk + 0x11f
7: RtlRaiseException + 0x484
8: KiUserExceptionDispatcher + 0x2e
9: GetSettingsBlobsAll + 0x22053

This occurs with both VST and VST3 plugins (error log is identical, aside from the addresses).

Side-note: I do normally have Ableton & my interface at 96kHz. I set them to 48kHz (since I see the engine retrying to sync a few times in the log), though it made no difference. The standalone version does also work with my hardware otherwise at 96kHz (unfortunately, even at 48kHz, I can’t get Ableton to take MIDI-input from the standalone version, only audio – at which point, I might as well just use Ableton’s own conversion tools).

2

Regarding MG3 standalone: How can Ableton Live take audio from another application on Windows? MG3’s MIDI out certainly transmits from the standalone app but you must use a virtual MIDI port-generating application, like LoopBeMIDI, for example.

Re: VST2/3 crashes, I hope a Windows pro can chime in.

3

Actually, I’ve got it taking audio from the standalone fine (virtual ASIO bridge). Unfortunately, I evidently failed to twig that I’d need an equivalent of that for MIDI. Mistakenly assumed the “MIDI device” in the standalone would do it (in my defence, I’ve done audio for decades, but this is my first foray into self-creating music-from-home using anything vaguely MIDI-shaped). Cheers for the pointer!

4

one option for a midi equivalent is loopbe:

bome is another option, but is much more complicated/capable.

on your vst crash issue, try a database reset:

https://help.ableton.com/hc/en-us/articles/360000794970-Resetting-Live-s-Database

i don’t think doing this will cause any other problems. if you have a lot of vsts it may take some time though.

5

Thanks for reporting!

I don’t have any clues right now, but there will be an update tomorrow (3.0.67). I’d appreciate if you can try with this one and see if it’s addressed. Otherwise im going to try to reproduce and look deeply into this

1 Like
6

This is what I have installed on my Windows test device. It’s freeware.

7

Hi, I have some more information about this since I’ve recently been troubleshooting plugin crashes on my system.

The actual crash is caused by a new bug in the AMD OpenGL driver starting at around version 25.11.1.

The bug causes the DAW to crash while trying to initialize plugin GUIs that use OpenGL (access violation in atio6axx!GetSettingsBlobsAll), such as those that were made with Juice. It happens in several DAWs including Ableton, Cubase and Reaper and with many different plugins.

Until AMD can fix this bug, you’ll have to downgrade to an older version such as 25.9.1.

2 Likes
8

Thanks for troubleshooting.

When I get better time, I will try to install the faulty driver and reproduce to see if a fix is possible on our side.

1 Like