|
|
Thread Tools | Display Modes |
04-10-2018, 02:37 PM | #1 |
Human being with feelings
Join Date: Aug 2012
Posts: 10
|
REAPER [5.7X] unusable on Windows 10 - Crashes randomly and very frequently (FIXED)
Hello there,
I have a massive problem with REAPER 5.7X on my Windows 10 (Home 10.0.16299) laptop. The problem is, that it crashes randomly. It just says "REAPER is not responding anymore" and then it's dead. No error messages, nothing. There's also nothign of value in the Windows Error Logs. This is usually triggered by a specific action. Although it's not 100% reproducable - it is known to crash during following actions: - Toggling the Mixer - Deleting Tracks - Accessing the Routing Window - Opening a New Project Tab - Opening a Project - Deleting Media Items - Deleting FX Any of this action can trigger a crash, but it doesn't always do it. If REAPER crashes when I delete certain tracks and I reload the project and delete those same tracks again, it may not crash this time. It's like it has a certain percantage chance of crashing whenever I do one of these actions mentioned above. And that chance is high! Like, seriously, it crashes basically every five or ten minutes while working on a project. It makes REAPER literally unusable on my laptop - which is a shame since it's my main DAW and I need it for my work. I've got REAPER on my Windows 7 Desktop PC at the studio and it's solid like a rock, but on the laptop it just doesn't work. The laptop is very new, it's got an Intel i5, 8GB of RAM and an SSD. It shouldn't be a hardware bottleneck. Oh yeah and the crashes are not dependant on the sound interface I'm using. Happens on RME Fireface, Microsoft DirectSound, ASIO4All and Dante Virtual Soundcard. Thing I've tried to remedy the problem (without effect): - Loading projects in recovery mode - Deleting Custom Scripts - Deleting all VST folders - Deleting Custom Themes - Deleting User preferences - Doing a 100% clean reinstall - Doing a portable install (-> same problems) Now, because I'm literally out of options at this point - I installed an old version of REAPER. Version 5.0. I played around with it for a while and it seems to be stable. It's hard to say of course, because of the randomness of the crashes but on the surface it seems, that old versions don't have these problems. So what can I do now? I absolutely need REAPER to work properly on the laptop. If I can't get it to work I might need to switch to a different DAW alltogether. And I would hate to do that but I've got no other choice at the moment. Can you guys help me? Cheers and thank you Last edited by Megamag; 04-10-2018 at 03:11 PM. |
04-10-2018, 02:52 PM | #2 | |||
Human being with feelings
Join Date: Aug 2012
Posts: 10
|
I've included some logs from the Event Viewer. I don't know if this is helpful.
Quote:
Quote:
Quote:
|
|||
04-10-2018, 05:29 PM | #3 |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 16,117
|
(updated reply below)
Last edited by Justin; 04-10-2018 at 06:26 PM. |
04-10-2018, 06:18 PM | #4 |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 16,117
|
I'm guessing the issue is with Stardock Fences, but I've located the probable bug on our end (thank you for the crash report!).
Can you confirm something? You said 5.0 worked -- can you compare 5.15 and 5.16 from https://www.reaper.fm/download-old.php ? If it's what I think it is, 5.15 will work and 5.16 will crash. The next prerelease in the prerelease forum should fix (assuming that 5.15 works and 5.16 doesn't) -- for now you might want to try disabling Fences. Last edited by Justin; 04-10-2018 at 06:26 PM. |
04-11-2018, 02:18 PM | #5 | |||
Human being with feelings
Join Date: Aug 2012
Posts: 10
|
Quote:
Both 5.15 and5.16 are stable (or at least I couldn't get them to crash). Also I tried out 5.78 again with deinstalled Fences and it crashed again. I got a new log without Stardocks Fences: Quote:
Quote:
https://www.dropbox.com/s/wvka3m2jwk...ortV2.ini?dl=0 I hope we can work this out. Cheers! EDIT: I think I've traced it down by incrementally installing old versions until I could get one to crash. It seems to be the jump between 5.18 and 5.20 that causes the issues. 5.18 is stable, whereas 5.20 crashes just like the newest version does. So maybe that's where the fault lies? Last edited by Megamag; 04-11-2018 at 02:35 PM. |
|||
04-11-2018, 03:53 PM | #6 |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 16,117
|
Can you try 5.79pre12 in the pre-release forum and see if that fixes?
|
04-11-2018, 04:12 PM | #7 | |
Human being with feelings
Join Date: Aug 2012
Posts: 10
|
Quote:
I will keep an eye on it and see if it stays that way. Thank you very much - that might have saved me Cheers |
|
04-11-2018, 04:22 PM | #8 |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 16,117
|
|
04-12-2018, 03:19 AM | #9 |
Banned
Join Date: Dec 2016
Location: England
Posts: 2,432
|
REAPER= tailor made software-lovingly crafted by passionate artists.
where else do you get that 1st hand reasponse ?!? priceless. +thanking cockos for the dedication to perfection. |
04-13-2018, 11:25 PM | #10 |
Human being with feelings
Join Date: Jul 2016
Posts: 36
|
wow, well.. Its interesting to say the least. I have been using reaper 5.78 normally, I sometimes get an error but that is when a dialog comes up asking for the routing confirmation when I insert mostly kontakt on it. But then I review the changelogs and it says a potential accessibility crash.. what part of the accessibility is at stake here? any service or so on? I am asking because I use reaper with a screenReader.
|
Thread Tools | |
Display Modes | |
|
|