Reason (11) crashes while loading, reinstalled, still the same, halp?

[whyisitalwaysme]

Hey guys, I have a serious problem...
I am currently using Reason 11 (1139), and it crashes right before it would start (plugin scan is completed). There is no error message.
I think I tried to install the Early-Access version of Reason 12 just before that, and it failed since I am still using Windows 7. So mabe it has something to do with that...?

I tried deinstalling and reinstalling Reason 11, but the problem stays: Everytime after the plugin scan instead of opening the DAW, the whole proccess just disappears without any error message. Anyone knows what I can do?

I'd really like to keep my presets and folders etc. - but at this point I just wish to start the freaking program at all lol.

Sorry if this is a known bug, I couldn't find anything on Google.

[jam-s]

You could try to go to the Reason preferences folder and (after making backups) try to delete/rename some of the preferences files and try if this fixes the problem. also there might be some kind of crash log that might give some further hints on what exactly is failing. Also it might be an idea to contact RS support.

[whyisitalwaysme]

Hey and thanks for your comment, I was thinking there had to be some crash-logs, too. All I could find is the "logs" folder in appdata->roaming->propellerhead sw -> reason. But my last log is from over a month ago, but the problem started happening only a few days ago.

Which preferences folder do you mean, though, could you tell me where it's located?

I tried reinstalling reason in all way I could imagine, but the problem is still there. I changed nothing on my PC exept for trying to install Reason 12, but I'm pretty sure it didn't even let me install since I use Win 7. I checked the registry for any Reason 12 related entries, but there are none... I'm really lost at this point.

For whatever reason, the rack plugin works in other DAWs. I never even used it till today, and it really seems to be just the rack with reasons built in plugins, so that doesn't really help me since I use Reason for everything: recording, producing, arranging.

If anyone knows there these logs could be at, feel free to tell me. I just don't want to accept that the program just stops working from one day to the next...

[Loque]

Do you use VSTs in Reason? Disable the VST scanning or just start it often enough and hope all crashing plugins are disabled.

[jam-s]

Hey and thanks for your comment, I was thinking there had to be some crash-logs, too. All I could find is the "logs" folder in appdata->roaming->propellerhead sw -> reason. But my last log is from over a month ago, but the problem started happening only a few days ago.

Which preferences folder do you mean, though, could you tell me where it's located?

That one from above sounds like the right place (if you've got R11 suite, then change it to "Reason Suite" to it).

I'd try to delete "Reason Suite Plugin Folders.prf"/"Reason Plugin Folders.prf" first and then try with other .prf files.

EDIT: I've also seen crashes of Reason related to the GPU. So try to check if the GPU driver is up-to-date.

[whyisitalwaysme]

@loque Thanks, can you disable the VST scanning without opening the program? Could you please tell me how to do so?
Also, yes, I mostly use VSTs, but I haven't installed any new ones before this crash-thing started to happen. I have FL Studio installed, too, and that program runs just fine using the same VSTs. Even the Reason Rack VST works in FL Studio, wierdly. But yeah, please tell me how to deactive that scan, I'd try anything at this point


@jam-s
I deleted that whole folder (made a backup before), and nothing changed. I even found one more folder not under appdata-> roaming but appdata->local that I deleted. Nothing changes the crash. It's always exactly after the plugin check, right when the program would open...
Also checked my gpu drivers, they are up to date.

I wrote the official support, too, if they can tell me what's wrong I'll post it here in case others might encounter the sameproblem. But that will probably take some time.

[arnigretar]

Hey mate, this thing happened with me as well on my windows 7 machine. It crashed for 3-4 days and finally - after contacting support - it just opened. Don't know why or how. But I tried re-installing couple of times and deleting all Reason files. But nothing. But just one try - few days later - it just opened. At least you know more people have had this problem. Hope yours get solved.

[whyisitalwaysme]

@arnigretar

Thanks so much for that answer It is actually comforting to know I'm now the only human on this planet with this wierd problem. I really hope that happens to me, too ,since with all my Windows experience it just doesn't make sense that a software stops working without me changing anything. It just seems logical that the problem is gonna be solved the way it appeared, by me not changing anything I'll keep you updated, all of the greets to Iceland bro

[Loque]

...

You can try the preferences files.
viewtopic.php?f=4&t=7514631

[whyisitalwaysme]

Short Update: I tried deleting all files and reinstalling, everything i could find in roaming and even "local". Nothing changed. I googled and can't seem to find a single person with the same problem. One guy also couldn't start reason, but he had the setting that opens his last worked-on song, and that song had a faulty vst. He could open a demo song and changed that setting. I can't even do that.

Literarlly all I can find is my own thread when I try to google my issue. And as to @arnigretar , while I do still have hope, apparently Reason can crash when loading bad VSTs, but skips those the next time it loads. Maybe that's why it worked for you at some point, because all the VSTs Reason couldn't handle were skipped...

I don't know anymore, other DAWs work fine, I didn't change any VSTs when this problem started appearing. I'll post the support peoples message as soon as they get to me. What a shitshow...

[Loque]

Short Update: I tried deleting all files and reinstalling, everything i could find in roaming and even "local". Nothing changed. I googled and can't seem to find a single person with the same problem. One guy also couldn't start reason, but he had the setting that opens his last worked-on song, and that song had a faulty vst. He could open a demo song and changed that setting. I can't even do that.

Literarlly all I can find is my own thread when I try to google my issue. And as to @arnigretar , while I do still have hope, apparently Reason can crash when loading bad VSTs, but skips those the next time it loads. Maybe that's why it worked for you at some point, because all the VSTs Reason couldn't handle were skipped...

I don't know anymore, other DAWs work fine, I didn't change any VSTs when this problem started appearing. I'll post the support peoples message as soon as they get to me. What a shitshow...

Well, i did a reinstall a short time back and was surprised how many bad coded VSTs i still had installed. A few crashed, did not responded, wanted stupid serial input boxes hidden behind some windows, presented error boxes because they couldnt write to protected locations and so on and so forth...

The worst commercial plugins i had were from Waves, which crashed regularly, so removed them all. TG, i didnt had paid for them and got them for free.

Once i got through the VST crap, Reason just rans fine. Again, i can only recommend to disable VST folders to check if that is the problem. If so, get rid of all that VST crap you will never use anyway and you do not need...

[Arrant]

Have you tried turning it on and off again?

Seriously, in this case I would suspect a faulty VST. Maybe try to temporarily rename your VST folder and see if that helps? Making sure no plugins are actually loaded at startup.

[whyisitalwaysme]

Thanks guys, I too thought that VSTs could be a problem for whatever reason. Again, I HAVEN'T CHANGED ANYTHING when this problem started happening, no new VSTs, but this wouldn't be the first time I had PC problems without changing anything.

I did as you said and renamed my VST folders, which was successful in the way that there was no vst-check when launching, but the problem is the same... I see the reason boot screen, and just when the glorious sequencer and the less glorious companion would open, it crashes.

The wierdest thing is that noone in the internet world seems to have this problem... Well, I'll keep trying stuff and keep this updated in case I'm not the only one. Thanks again for your help, guys.

[whyisitalwaysme]

The only thing I did do before this happened was trying to install Reason 12. I just tried it again, and it doesn't even start installing since I still run Windows 7. I thought maybe that could have screwed up something in the registry, but unfortunately that's a dead end, too, since Reason 12 doesn't even start installing if you have Windows 7. Also, I did check the registry and all the places I know, and there are no entries for Reason 12.

[Arrant]

Running out of ideas.. Maybe a permission problem? Some UAC settings or something playing tricks with you?

Make sure you are properly admin while uninstalling / reinstalling.

[jam-s]

I think Reason Studios support might have some setting for you to enable debug logging so they can diagnose the problem. Also you might be able to dig deep into the crash using https://docs.microsoft.com/en-us/sysint ... ds/procmon

[Loque]

Thanks guys, I too thought that VSTs could be a problem for whatever reason. Again, I HAVEN'T CHANGED ANYTHING when this problem started happening, no new VSTs, but this wouldn't be the first time I had PC problems without changing anything.

I did as you said and renamed my VST folders, which was successful in the way that there was no vst-check when launching, but the problem is the same... I see the reason boot screen, and just when the glorious sequencer and the less glorious companion would open, it crashes.

The wierdest thing is that noone in the internet world seems to have this problem... Well, I'll keep trying stuff and keep this updated in case I'm not the only one. Thanks again for your help, guys.

It could be the audio driver. Try to update or change Reason to use a different one or temporary disable them all.

[whyisitalwaysme]

@Loque Thanks again, that's also something I thought. I do use the ASIO4ALL driver sometimes to record my guitar over a Fender Mustang Amp (works through USB). It could be the case that I left Reason with that driver set as default, not my normal one. But how can I change that if I can't enter reason?

Also, I did delete all preference folders and reinstalled Reason without them. Shouldn't Reason use my default Windows driver if it can't find any preferences? When I tried, the same error happened. With all the things I tried, the same error happened, to be frank. Reason loads, just before the program would open, the reason boot screen disappears and nothing happens.No error code, nothing...

[khan-flo-mah]

I FIXED THIS ISSUE:
SAME THING HAPPENED TO ME. and YES I use a LOT of vsts. And YES I changed nothing (or did I?)
the answer was, the Focusrite wasnt plugged in. And the last time reason was opened , it used that focusrite external audio. well it wasnt plugged in with the usb, and CRASH. Right at the windows page. I plugged it in? Boom ...opened.
So one person said "it could be the audio"
another said "it just started working after a few days"
Likely the audio driver. Or he rebooted after an automatic update that he was not aware of.


in my case, it wasnt on at all.