|
FL Studio Error
|
View this Thread in Original format
| echosystm |
So, I've got a new computer now - Core 2 Duo
I open up FL, and i get this error message about my CPU and a string of jibberish! "Ok then...". Reopen fl studio, and I get a different error, this time some "error protection: 552132" or something.
I don't get anymore errors now (I havent changed anything at all). What the hell was that all about? Something to do with the crap dual core support or what? |
|
|
| echosystm |
Just reinstalled it to see if it would do it again. It did.
| quote: | OS: Windows XP Professional, SP2
CPU: GenuineIntel, Intel P6 (Model 15), MMX @ 1200 MHz
Module name: C:\Program Files\Image-Line\FL Studio 7\FL.exe
Application data:
VmVyc2lvbjogV2tkT0lsQjNjV0JzYWxzcUoxdy9KamxVSmlvR0FWYzl
JejQ3TG0xNmVYeDFNU0lrUFNFaU5FZHdlbk4yWkgxRk5UbEJVM1o2ZT
Nrd1VYZHdlajl6VDBkVlZVTlJSbmtLDQpJbWFnZUJhc2U6IDAwQkMwM
DAwDQotMQ0KQ29kZSA9IFsxMTRdDQotIDIyMQ0KLSA3Mg0KLSAyMTcN
Ci0gMA0KLSBbXQ0KPiBDOlxQcm9ncmFtIEZpbGVzXEltYWdlLUxpbmV
cRkwgU3R1ZGlvIDdcRkwuZXhlDQoNCkltYWdlLUxpbmUNCkZMIFN0dW
RpbyBlbmdpbmUgbGF1bmNoZXINCjAuMC4wLjANCkZMIFN0dWRpbw0KS
W1hZ2UtTGluZQ0KMC4wLjAuMA0KRkwgU3R1ZGlvDQoNCj4gQzpcV0lO
RE9XU1xzeXN0ZW0zMlxudGRsbC5kbGwNCj4gQzpcV0lORE9XU1xzeXN
0ZW0zMlxrZXJuZWwzMi5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMl
xvbGVhdXQzMi5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxtc3Zjc
nQuZGxsDQo+IEM6XFdJTkRPV1Ncc3lzdGVtMzJcVVNFUjMyLmRsbA0K
PiBDOlxXSU5ET1dTXHN5c3RlbTMyXEdESTMyLmRsbA0KPiBDOlxXSU5
ET1dTXHN5c3RlbTMyXEFEVkFQSTMyLmRsbA0KPiBDOlxXSU5ET1dTXH
N5c3RlbTMyXFJQQ1JUNC5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zM
lxvbGUzMi5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxjb21jdGwz
Mi5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxTSExXQVBJLmRsbA0
KPiBDOlxXSU5ET1dTXFdpblN4U1x4ODZfTWljcm9zb2Z0LldpbmRvd3
MuQ29tbW9uLUNvbnRyb2xzXzY1OTViNjQxNDRjY2YxZGZfNi4wLjI2M
DAuMjk4Ml94LXd3X2FjM2Y5YzAzXGNvbWN0bDMyLmRsbA0KPiBDOlxQ
cm9ncmFtIEZpbGVzXEltYWdlLUxpbmVcRkwgU3R1ZGlvIDdcRkxFbmd
pbmUuZGxsDQoNCkltYWdlLUxpbmUNCkZMIFN0dWRpbyBlbmdpbmUNCj
cuMC4wLjANCkZMIFN0dWRpbw0KSW1hZ2UtTGluZQ0KMS4wLjAuMA0KR
kwgU3R1ZGlvDQoNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxtc2ltZzMy
LmRsbA0KPiBDOlxXSU5ET1dTXHN5c3RlbTMyXHZlcnNpb24uZGxsDQo
+IEM6XFdJTkRPV1Ncc3lzdGVtMzJcbXByLmRsbA0KPiBDOlxXSU5ET1
dTXHN5c3RlbTMyXHdpbnNwb29sLmRydg0KPiBDOlxXSU5ET1dTXHN5c
3RlbTMyXHNoZWxsMzIuZGxsDQo+IEM6XFdJTkRPV1Ncc3lzdGVtMzJc
Y29tZGxnMzIuZGxsDQo+IEM6XFdJTkRPV1Ncc3lzdGVtMzJcd2lubW0
uZGxsDQo+IEM6XFdJTkRPV1Ncc3lzdGVtMzJcbXNhY20zMi5kbGwNCj
4gQzpcV0lORE9XU1xzeXN0ZW0zMlxoaGN0cmwub2N4DQo+IEM6XFdJT
kRPV1Ncc3lzdGVtMzJcd3NvY2szMi5kbGwNCj4gQzpcV0lORE9XU1xz
eXN0ZW0zMlxXUzJfMzIuZGxsDQo+IEM6XFdJTkRPV1Ncc3lzdGVtMzJ
cV1MySEVMUC5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxEU291bm
QuZGxsDQo+IEM6XFByb2dyYW0gRmlsZXNcSW1hZ2UtTGluZVxGTCBTd
HVkaW8gN1xPcGVuQXNpby5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0z
MlxvbGVwcm8zMi5kbGwNCj4gQzpcUHJvZ3JhbSBGaWxlc1xJbWFnZS1
MaW5lXEZMIFN0dWRpbyA3XERTUF9JUFAuZGxsDQo+IEM6XFdJTkRPV1
Ncc3lzdGVtMzJcdXh0aGVtZS5kbGwNCj4gQzpcV0lORE9XU1xzeXN0Z
W0zMlxXSU5UUlVTVC5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxD
UllQVDMyLmRsbA0KPiBDOlxXSU5ET1dTXHN5c3RlbTMyXE1TQVNOMS5
kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxJTUFHRUhMUC5kbGwNCj
4gQzpcV0lORE9XU1xzeXN0ZW0zMlx3ZG1hdWQuZHJ2DQo+IEM6XFdJT
kRPV1Ncc3lzdGVtMzJcbXNhY20zMi5kcnYNCj4gQzpcV0lORE9XU1xz
eXN0ZW0zMlxtaWRpbWFwLmRsbA0KPiBDOlxXSU5ET1dTXHN5c3RlbTM
yXEtzVXNlci5kbGwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxSSUNIRU
QzMi5ETEwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlxSSUNIRUQyMC5kb
GwNCj4gQzpcV0lORE9XU1xzeXN0ZW0zMlx2b3JiaXMuYWNtDQpUaGlz
IHNvZnR3YXJlIGlzIGJhc2VkIG9uIGEgY29kZSBvZiAnbGliVm9yYml
zJy4NClhpcGhvcGhvcnVzIGxpYlZvcmJpcyBJIDIwMDExMjMxDQpDb3
B5cmlnaHQgKEMpMjAwMSBYaXBob3Bob3J1cw0KSE1TIGh0dHA6Ly9oc
C52ZWN0b3IuY28uanAvYXV0aG9ycy9WQTAxMjg5Ny8NCk9nZyBWb3Ji
aXMgQ09ERUMgZm9yIE1TQUNNDQowLCAwLCAzLCA2DQp2b3JiaXMNCkN
vcHlyaWdodCAoQykyMDAxIEguTXV0c3VraQ0Kdm9yYmlzLmFjbQ0KMC
wgMCwgMywgNg0KT2dnIFZvcmJpcyBBdWRpbyBjb2RlYyBmb3IgTVNBQ
00NCjIwMDIvMDcvMDggcHVibGljIGJldGENCg==
|
And then
| quote: | Protection Error
Error: 157 |
And then
| quote: |
---------------------------
FL.exe - Application Error
---------------------------
The exception unknown software exception (0x0eedfade) occurred in the application at location 0x7c812a5b.
---------------------------
OK
---------------------------
|
Followed by 3 other errors or so, eventually terminating the program. Then I reopen it and it works completely fine. lol? |
|
|
| echosystm |
| Also, this is not cracked, just incase any of you wise asses were gonna jump on me ;) |
|
|
| echosystm |
| Seems to not crash when I have an ASIO driver selected. :conf: |
|
|
| SMC |
| Have you reported this at the FL tech forum? |
|
|
| echosystm |
| quote: | Originally posted by SMC
Have you reported this at the FL tech forum? |
Nein, this is just the demo copy (i'm not registered) |
|
|
| SMC |
| quote: | Originally posted by echosystm
Nein, this is just the demo copy (i'm not registered) |
I see. |
|
|
| thoughtlessjex |
There are people in this world that can tell you what a core dump means. They have spent endless hours memorizing hex values, along with their meanings in context and their alphanumeric equivalents. I am constantly awed that people like this exist.
Unfortunately, I don't think any of them frequent this board. As such, asking us about a problem and dropping a core dump on us won't get you very far. :p
As far as the error itself, I've never encountered it. I think, demo or no, you should ask the FL tech folks about it, and if they can't help, then find some grungy, nerdy tech talk forum where the above people I've mentioned congregate and talk in hex. If you can communicate effectively with them (not an easy task), they might be able to at least tell you what happened.
Quite likely, though, the guys at FL tech will know what's happening. |
|
|
| Lindo |
We're not grungy and nerdy! lol
Well I believe I can help you out. The program is having errors with the instruction pointer (points to where the program should jump next and start new operations). It then crashes because it doesn't know where to go to next because the instruction pointer is pointing to some random place in memory "0x7c812a5b." This has happened to a few people before and I believe it is contributed to having an error with your memory. The best program to test your memory is memtest86. Run it on the highest setting overnight and see if you get any errors in the morning. If you have generic ram, then it is probably your memory's fault. Good luck!
Edit: Do you have an ATI video card? |
|
|
| DJ Shibby |
| quote: | Originally posted by thoughtlessjex
There are people in this world that can tell you what a core dump means. They have spent endless hours memorizing hex values, along with their meanings in context and their alphanumeric equivalents. I am constantly awed that people like this exist. |
Nah man, it's simpler than it seems... it's just location markers, and the equivalent data that caused the crash... useless to everyone really except a programmer.
I have a core2 duo with FL7 installed and it works beautifully on XP SP2. So let's do some trouble shooting...
1. Do you have any VST/VSTis installed when FL crashes, or is it the FL core engine itself that is crashing?
2. Updated to XP service pack 2, or are you running Vista?
3. What other stuff you got running? Try closing all your other apps to make sure there's not a conflict
4. What graphics card?
With the info we have so far, my guess is that it's probably a device driver error with your soundcard... but you might have Vista, in which case I have no idea. I get similar errors sometimes, usually at the most frustrating times when I haven't saved in a while. :)
peace |
|
|
| echosystm |
yeah seems to be my soundcard driver (only get that error on direct sound). Windows XP sp2 w/ audiophile 24/96.
RAM is fine, I ran a 24 hour burn in when i built it, its corsair too.
Problem solvered kiddos! Thanks, |
|
|
| Aesthetic |
| On a side note echo.. just how much has the new cpu improved performance? I have an old 3ghz chip and some of my projects are maxed.. any advice would be great :cool: |
|
|
|
|
