In the past week my Receptor has started freezing and/or resetting at random times. Sometimes it will be running for an hour w/o a problem and tonight i had it freeze twice during the first two songs of our set and it did not freeze again till the last song - maybe 30 mins later. I generally use a multi for every song. Kontact 2 it in every multi among other things. I haven't added or installed anything recently. I do gig a lot and have it in a shock mount rack but it's in and out of the trailer everyday.
I've uploaded the sys log. If someone who knows that sort of thing can take a look??? please. it's posted here: http://afteredmund.com/YatesSystemLog.txt
I've got a TV taping on Tue, so if there's any ideas please don't hold back.
thanks a ton,
Yates
HELP! Freezing and restarting at random
-
- KVRer
- 10 posts since 12 Feb, 2007
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Yates,
I took a quicklook thru your log (great idea posting the log, by the way. That was helpful).
A couple of things come to mind:
a.) at the end of the log, I see a whole bunch of DHCP logged entries. I'm wondering if something in your system is confusing DHCP. If you haven't already, perhaps you should turn DHCP off, and use a fixed IP address (I would just choose the previous IP address that DHCP last assigned to you).
b.) I also noticed a USB error: " Ignoring m_usbMidi error 'No such device'". You should check your USB connections. Possibly move any Midi or iloK thingy's hanging from your USB ports to other ports.
These are just stabs, but I hope something helps.
Best Regards,
Kevin L
I took a quicklook thru your log (great idea posting the log, by the way. That was helpful).
A couple of things come to mind:
a.) at the end of the log, I see a whole bunch of DHCP logged entries. I'm wondering if something in your system is confusing DHCP. If you haven't already, perhaps you should turn DHCP off, and use a fixed IP address (I would just choose the previous IP address that DHCP last assigned to you).
b.) I also noticed a USB error: " Ignoring m_usbMidi error 'No such device'". You should check your USB connections. Possibly move any Midi or iloK thingy's hanging from your USB ports to other ports.
These are just stabs, but I hope something helps.
Best Regards,
Kevin L
-
- KVRer
- Topic Starter
- 10 posts since 12 Feb, 2007
thanks for the suggestions. I'll go static for sure. - the loge might be from where i borrowed a bandmates computer to pull the log... i'll give it a try anyway.
Yea, my iLok stopped working a while back and my solution was to just stop using plugs that needed it. - I mostly just use a freak load of samples via Kontakt 2 and some random freeware synths and fx.
A software engineer friend of mine suggested that it might be overheating. Is that a possibility?
here's the last few lines of the log before the machine freezes:
Jan 19 07:18:35 Receptor-1 rm-host: HostApp.cpp::Start[365]: Ignoring m_usbMidi error 'No such device'
Jan 19 07:18:35 Receptor-1 rm-host: source/VstPlugin.cpp::VstPlugin[165]: Float limit: 50.0
Jan 19 07:18:36 Receptor-1 rm-host: source/VstPlugin.cpp::SetSamples[838]: assertion failed
Jan 19 07:18:48 Receptor-1 modprobe: modprobe: Can't locate module snd-seq-client-62
Jan 19 07:18:48 Receptor-1 modprobe: modprobe: Can't locate module sound-service-1-0
Jan 19 07:18:48 Receptor-1 modprobe: modprobe: Can't locate module sound-service-2-0
Jan 19 07:18:48 Receptor-1 modprobe: modprobe: Can't locate module sound-service-3-0
Jan 19 07:18:49 Receptor-1 rm-host: source/VstPlugin.cpp::VstSetTo[2319]: '/c/Program Files/VST Plugins/Unsupported Plugins/URS/URS A Series EQ.dll' reports unsupported version 2400; using 2300
Jan 19 07:18:49 Receptor-1 rm-host: source/VstPlugin.cpp::SetSamples[838]: assertion failed
Jan 19 07:18:49 Receptor-1 last message repeated 2 times
Jan 19 07:18:50 Receptor-1 rm-host: HostApp.cpp::HandleEvent[903]: rm-host ready
thanks! i'm still open to more suggestions.
Yates
Yea, my iLok stopped working a while back and my solution was to just stop using plugs that needed it. - I mostly just use a freak load of samples via Kontakt 2 and some random freeware synths and fx.
A software engineer friend of mine suggested that it might be overheating. Is that a possibility?
here's the last few lines of the log before the machine freezes:
Jan 19 07:18:35 Receptor-1 rm-host: HostApp.cpp::Start[365]: Ignoring m_usbMidi error 'No such device'
Jan 19 07:18:35 Receptor-1 rm-host: source/VstPlugin.cpp::VstPlugin[165]: Float limit: 50.0
Jan 19 07:18:36 Receptor-1 rm-host: source/VstPlugin.cpp::SetSamples[838]: assertion failed
Jan 19 07:18:48 Receptor-1 modprobe: modprobe: Can't locate module snd-seq-client-62
Jan 19 07:18:48 Receptor-1 modprobe: modprobe: Can't locate module sound-service-1-0
Jan 19 07:18:48 Receptor-1 modprobe: modprobe: Can't locate module sound-service-2-0
Jan 19 07:18:48 Receptor-1 modprobe: modprobe: Can't locate module sound-service-3-0
Jan 19 07:18:49 Receptor-1 rm-host: source/VstPlugin.cpp::VstSetTo[2319]: '/c/Program Files/VST Plugins/Unsupported Plugins/URS/URS A Series EQ.dll' reports unsupported version 2400; using 2300
Jan 19 07:18:49 Receptor-1 rm-host: source/VstPlugin.cpp::SetSamples[838]: assertion failed
Jan 19 07:18:49 Receptor-1 last message repeated 2 times
Jan 19 07:18:50 Receptor-1 rm-host: HostApp.cpp::HandleEvent[903]: rm-host ready
thanks! i'm still open to more suggestions.
Yates
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi again Yates
I'm not sure about the overheating. If you think that is a possibility, you could try removing Receptor from it's rack and seeing if problems persist. I think your log showed that you have a C or Pro unit, so overheating is less of a risk. I'm guessing this isn't the case.
The 3-8 messages in the log (from your post above) interest me. They look like messages from a plug that can't resolve some .dll or other type of service. I'm not sure how to attribute these to a given plug - if you have been adding 'free plugins' lately, you might wish to remove some backwards and then check the logs to see if problems go away. This is a long trial-and error process though. If you mostly depend on Kontakt however, cutting back on other things to get back to a stable state might be wise.
Have you emailed your log to muse? If you do this, then give them a call, you might get some 'more informed' detective work.
Hope this helps,
Kevin L
I'm not sure about the overheating. If you think that is a possibility, you could try removing Receptor from it's rack and seeing if problems persist. I think your log showed that you have a C or Pro unit, so overheating is less of a risk. I'm guessing this isn't the case.
The 3-8 messages in the log (from your post above) interest me. They look like messages from a plug that can't resolve some .dll or other type of service. I'm not sure how to attribute these to a given plug - if you have been adding 'free plugins' lately, you might wish to remove some backwards and then check the logs to see if problems go away. This is a long trial-and error process though. If you mostly depend on Kontakt however, cutting back on other things to get back to a stable state might be wise.
Have you emailed your log to muse? If you do this, then give them a call, you might get some 'more informed' detective work.
Hope this helps,
Kevin L