Every-time I put on Channel E4 +1 it crashed. I decided to delete the channel then used E4 but now it crashes when that channel is on. Can you help?
I have the same problem, HDR Fox T2 1.03.12/3.03 crashing every two minutes. I've done a factory reset and it didn't fix it, the box now crashes every two minutes without any channels tuned. I went into maintenance mode and ran a disc fix, which found nothing. I also ran an extended disc check and that found no disc faults.
What do I do next? Are there other diagnostics I can run from maintenance mode which have any chance of resolving this? The box isn't that old, it's a Grade A from Humax Direct bought after the model was discontinued. Ironically this one was a hedge against my much older one dying, which has now been pressed back into service.
Unplug the network. Unplug the disk. Check power supply. Fault finding by substitution (and hope you don't break both boxes).
Have you tried turning off content share ?
Diagnostics > DLNA Server > Reset DLNA DatabaseThat appears to fix it, thanks. I assume that means the DLNA database is corrupt. So how do I delete and re-create it please with CFW?
Diagnostics > DLNA Server > Reset DLNA Database
Yes that's fixed it thanks. I was wonderng how the average user would deal with this, but realised a factory reset with hard disc format would fix it. Just with rather drastic side effects.
I spoke too soon. Once content sharing was re-enabled, after some time it crashed and rebooted again. I assume this means there is a recording somewhere on the disc it can't cope with indexing. Unless anyone has a better thought?
I'll turn content sharing off for now and see how it goes, to check there isn't another problem.
Normally down to a DLNA software running on something else. BH will be along with the links to the fixes I hope ? Have you installed Twonky on some other kit recently ?
Is it alway me that has to supply these?BH will be along with the links to the fixes I hope ?
In that case it must be something local. I would start by looking at what's been recorded since it wasn't crashing and move it all off to something external. Then it's just a matter of divide and conquer until you find the errant file(s) (and make sure you keep a copy as it might be useful for investigation).