Ableton Forum

I recently installed W7. Live 8.1.1 is now crashing frequently with this error:
memory corruption error 0x6e

any ideas??

thanks

A.

Hi !
I'm using Live 8.1.1 for 24 hours now on my Windows Vista laptop, and have the same error message (Memory Corruption detected, 0x6e)... I have found no solutions yet
I've been using Live 7 for ages (I updated to be able to use the launchpad) and never had that kind of bug...

May anyone help ?

Thanks for support !

I've been searching over internet and i found a lot of issues talking about memory corruption, with that reference, and others in the same format. for what i understand of what i saw, that bug is not from ableton, the bug is from the pc because i already saw ableton running on windows vista and Windows 7 perfectly with no bugs like that. i'll see if i can find on internet the correction of those bugs, and if so, i will post here, maybe that help

Indeed, I noticed with different configurations that this bug comes often when I have several periphericals connected to my laptop, and when, furthermore, I'm working on a project with lots of effects or Instruments, requiring lots of memory. It seems that more than just memory, the number of devices connected is mainly responsible for this bug.
When I use a firewire soundcard (TC Electronics Konnekt 6), with the launchpad novation and an UC-33 (MIDI control), on a full project, the bug often appears. However, if I disconnect the launchpad or the UC-33, it doesn't happen.
I came to the conclusion that it comes from the number of devices plugged into the laptop AND (probably) power supplied by the laptop (it doesn't change anything if I unplug the soundcard which has its own power upply).

The problem is that this bug is due to the configuration of my workstation, and so the "compatibility" between the laptop, its system, CPU, memory, OS, and the different devices used, and also the software project...
In other words, it may be difficult to find an appropriate issue when this bug happen...

BUT the strange thing is that this bug only appeared when working on LIVE 8... which is also the moment when I began to use a launchpad... So it's difficult to say if the problem is due to the new software architecture (this bug never happened on LIVE 7 and previous), or if it is due to the use of too many devices (the arrival of the launchpad as one more device may be responsible, instead of working on the last version of LIVE). Anyway, I think that using all-in-one devices may be helpful to avoid these kinds of problem in the future.. that's my advice !