FLStudio - ACCESS VIOLATION

RecklessGint · Joined: Apr 30, 2007 Posts: 23 Location: Santa Barbara, CA

I'm using FLStudio 7 Producer Edition. Every now and then, I get this error message:

Posted Image, might have been reduced in size. Click Image to view fullscreen.

Posted Image, might have been reduced in size. Click Image to view fullscreen.

It seems to come up at random times, when I'm least expecting it. I lose whatever progress I've made, and if I'm foolish enough (which I'm not anymore) to answer 'yes' to "save changes to (project).flp?" the file gets corrupted.

Anyone else had this problem before? And is there a way to eliminate it?

EdisonRex · Posted: Thu May 31, 2007 12:02 am Post subject:

Are you running any 3rd party VSTs?
Is this Windows XP?
Latest DirectX? (9/10?)

What's your sound system? Does it have latest drivers installed?

RecklessGint · Joined: Apr 30, 2007 Posts: 23 Location: Santa Barbara, CA

1. Yes, but none that I didn't used to use, and they didn't give me problems then.

2. Windows XP Professional

3. DirectX 9

I managed to get through a fairly lengthy update session on one track without any errors. Perhaps there is a particular event the error is linked to, and I just haven't been observant enough to pinpoint it yet.

EDIT: Sound system.. I'm using an M-Audio Delta 66 as my soundcard, with the latest drivers installed.

RecklessGint · Joined: Apr 30, 2007 Posts: 23 Location: Santa Barbara, CA

Well.. I figured out when it's happening.. When I try to delete an SFZ. Bleh.

RecklessGint · Joined: Apr 30, 2007 Posts: 23 Location: Santa Barbara, CA

Except.. it seems to be happening most of the time when I delete a Fruity Soundfont Player channel as well now.. God damnit.

Did I mention this is a fresh install from the FL CD onto a freshly installed copy of Windows XP as of about 3 days ago?
For fuck's sake. head banging monitor

EdisonRex · Posted: Thu May 31, 2007 6:39 am Post subject:

RecklessGint · Joined: Apr 30, 2007 Posts: 23 Location: Santa Barbara, CA

One more detail to that fresh install part: Yes, this is a fresh install of this FL CD, but it's not the first one I've done. During the previous two times I had it installed, I did not get Access Violations.

As far as the arguments in the error messages go... The first number is always the same (00F95D71), the second one is not. (Some examples: 61726370, 00003B33, and the one in the screenshot, 27C20200).

EdisonRex · Posted: Fri Jun 01, 2007 3:30 am Post subject:

The first number is the address of the instruction failing on the access violation. The second one is the address of the data being read, which is causing the access violation. Because FLEngine.dll is the faulting program, you can assume that the place where the instruction fails is always in the same place (it is the same instruction in the same routine). It certainly looks like a software problem; The context of the second argument looks like it should be interpreted as a value, but instead it is being interpreted as a reference. Maybe something's corrupted and you can reinstall this product.

Have you sent this to fruityloops.com technical support? They only open their support forum to registereed users (probably as incentive to get people with cracked versions to buy proper versions).

RecklessGint · Joined: Apr 30, 2007 Posts: 23 Location: Santa Barbara, CA

I upgraded my OS with a special CD of a friend of mine, and there is no problem anymore. =)

EdisonRex · Posted: Sun Jun 03, 2007 6:46 am Post subject:

hmm. Glad it's working then. Cool