• The forum software that supports hummy.tv will be upgraded to XenForo 2.3 on Wednesday the 20th of November 2024 starting at 7pm

    There will be some periods where the forum is unavailable, please bear with us. More details can be found in the upgrade thread.

Strange regular crashes

beastman

New Member
This may not be directed related to the custom firmware but I thought I'd try here first as I've run the obvious diagnostics with nothing pointing to the problem. The only thing I can see that might be, clutching at straws. is the fact that I have a very poor signal that does cause some occasional reception issues/glitches, although when the box does random reboots its not when there's an obvious break up of the picture. Can a poor signal cause rebooting/crashes? I do have a 2.5inch 1TB drive in there but its a recommended AV drive, WDC WD10JUCT and the disk test is fine.

I would be grateful for any ideas as to what this could be. Thanks.

System Information Web interface version: 1.3.1-1
Custom firmware version: 3.10 (build 2734)
Humax Version: 1.03.12 (kernel HDR_CFW_3.10)
Loader Version: a7.30
System ID: 80bc.7e00
Serial Number: 63 7104952 00091
Last Boot Reason: Unknown (4)
Code:
Crash log:

Text Log last modified: Wed Aug 10 03:26:35 2016

21 Humax crashed at Thu Aug 18 09:20:31 UTC 2016 - Uptime: 245
20 Humax crashed at Tue Aug 16 23:53:49 UTC 2016 - Uptime: 67
19 Humax crashed at Tue Aug 16 23:52:19 UTC 2016 - Uptime: 4321
18 Humax crashed at Tue Aug 16 22:39:54 UTC 2016 - Uptime: 67
17 Humax crashed at Tue Aug 16 22:38:24 UTC 2016 - Uptime: 611
16 Humax crashed at Tue Aug 16 22:27:49 UTC 2016 - Uptime: 66
15 Humax crashed at Tue Aug 16 22:26:20 UTC 2016 - Uptime: 432
14 Humax crashed at Tue Aug 16 22:18:45 UTC 2016 - Uptime: 67
13 Humax crashed at Tue Aug 16 22:17:14 UTC 2016 - Uptime: 435
12 Humax crashed at Tue Aug 16 22:09:35 UTC 2016 - Uptime: 67
11 Humax crashed at Tue Aug 16 22:08:06 UTC 2016 - Uptime: 432
10 Humax crashed at Tue Aug 16 22:00:29 UTC 2016 - Uptime: 67
9 Humax crashed at Tue Aug 16 21:59:00 UTC 2016 - Uptime: 524
8 Humax crashed at Tue Aug 16 21:49:53 UTC 2016 - Uptime: 433
7 Humax crashed at Tue Aug 16 21:42:17 UTC 2016 - Uptime: 67
6 Humax crashed at Tue Aug 16 21:40:45 UTC 2016 - Uptime: 36167
5 Humax crashed at Tue Aug 16 11:37:35 UTC 2016 - Uptime: 66
4 Humax crashed at Tue Aug 16 11:36:04 UTC 2016 - Uptime: 8800
3 Humax crashed at Tue Aug 16 09:09:01 UTC 2016 - Uptime: 67
2 Humax crashed at Thu Aug 11 12:27:54 UTC 2016 - Uptime: 865
1 Humax crashed at Thu Aug 11 12:13:06 UTC 2016 - Uptime: 67

A PREVIOUS LOG HERE:

98
Humax crashed at Wed Aug 10 02:25:49 UTC 2016 - Uptime: 68

97
Humax crashed at Wed Aug 10 02:24:18 UTC 2016 - Uptime: 428

96
Humax crashed at Wed Aug 10 02:16:46 UTC 2016 - Uptime: 67

95
Humax crashed at Wed Aug 10 02:15:16 UTC 2016 - Uptime: 534

94
Humax crashed at Wed Aug 10 02:05:59 UTC 2016 - Uptime: 444

93
Humax crashed at Wed Aug 10 01:58:11 UTC 2016 - Uptime: 67

92
Humax crashed at Wed Aug 10 01:56:41 UTC 2016 - Uptime: 525

91
Humax crashed at Wed Aug 10 01:47:33 UTC 2016 - Uptime: 436

90
Humax crashed at Wed Aug 10 01:39:53 UTC 2016 - Uptime: 68

89
Humax crashed at Wed Aug 10 01:38:23 UTC 2016 - Uptime: 551

88
Humax crashed at Wed Aug 10 01:28:49 UTC 2016 - Uptime: 440

87
Humax crashed at Wed Aug 10 01:21:04 UTC 2016 - Uptime: 67

86
Humax crashed at Wed Aug 10 01:19:34 UTC 2016 - Uptime: 447

85
Humax crashed at Wed Aug 10 01:11:43 UTC 2016 - Uptime: 67

84
Humax crashed at Wed Aug 10 01:10:13 UTC 2016 - Uptime: 521

83
Humax crashed at Wed Aug 10 01:01:09 UTC 2016 - Uptime: 430

82
Humax crashed at Wed Aug 10 00:53:35 UTC 2016 - Uptime: 67

81
Humax crashed at Wed Aug 10 00:52:05 UTC 2016 - Uptime: 429

80
Humax crashed at Wed Aug 10 00:44:32 UTC 2016 - Uptime: 67

79
Humax crashed at Wed Aug 10 00:43:02 UTC 2016 - Uptime: 431

78
Humax crashed at Wed Aug 10 00:35:28 UTC 2016 - Uptime: 67

77
Humax crashed at Wed Aug 10 00:33:57 UTC 2016 - Uptime: 528

76
Humax crashed at Wed Aug 10 00:24:47 UTC 2016 - Uptime: 439

75
Humax crashed at Wed Aug 10 00:17:04 UTC 2016 - Uptime: 67

74
Humax crashed at Wed Aug 10 00:15:34 UTC 2016 - Uptime: 519

73
Humax crashed at Wed Aug 10 00:06:31 UTC 2016 - Uptime: 521

72
Humax crashed at Tue Aug 9 23:57:27 UTC 2016 - Uptime: 448

71
Humax crashed at Tue Aug 9 23:49:35 UTC 2016 - Uptime: 67

70
Humax crashed at Tue Aug 9 23:48:05 UTC 2016 - Uptime: 442

69
Humax crashed at Tue Aug 9 23:40:19 UTC 2016 - Uptime: 67

68
Humax crashed at Tue Aug 9 23:38:49 UTC 2016 - Uptime: 444

67
Humax crashed at Tue Aug 9 23:31:00 UTC 2016 - Uptime: 68

66
Humax crashed at Tue Aug 9 23:29:30 UTC 2016 - Uptime: 426

65
Humax crashed at Tue Aug 9 23:21:59 UTC 2016 - Uptime: 67

64
Humax crashed at Tue Aug 9 23:20:29 UTC 2016 - Uptime: 445

63
Humax crashed at Tue Aug 9 23:12:40 UTC 2016 - Uptime: 67

62
Humax crashed at Tue Aug 9 23:11:10 UTC 2016 - Uptime: 517

61
Humax crashed at Tue Aug 9 23:02:10 UTC 2016 - Uptime: 433

60
Humax crashed at Tue Aug 9 22:54:33 UTC 2016 - Uptime: 68

59
Humax crashed at Tue Aug 9 22:53:02 UTC 2016 - Uptime: 431

58
Humax crashed at Tue Aug 9 22:45:27 UTC 2016 - Uptime: 67

57
Humax crashed at Tue Aug 9 22:43:57 UTC 2016 - Uptime: 446

56
Humax crashed at Tue Aug 9 22:36:06 UTC 2016 - Uptime: 67

55
Humax crashed at Tue Aug 9 22:34:36 UTC 2016 - Uptime: 519

54
Humax crashed at Tue Aug 9 22:25:34 UTC 2016 - Uptime: 520

53
Humax crashed at Tue Aug 9 22:16:31 UTC 2016 - Uptime: 430

52
Humax crashed at Tue Aug 9 22:08:56 UTC 2016 - Uptime: 66

51
Humax crashed at Tue Aug 9 22:07:27 UTC 2016 - Uptime: 457

50
Humax crashed at Tue Aug 9 21:59:26 UTC 2016 - Uptime: 67

49
Humax crashed at Tue Aug 9 21:57:56 UTC 2016 - Uptime: 519

48
Humax crashed at Tue Aug 9 21:48:54 UTC 2016 - Uptime: 427

47
Humax crashed at Tue Aug 9 21:41:22 UTC 2016 - Uptime: 67

46
Humax crashed at Tue Aug 9 21:39:52 UTC 2016 - Uptime: 517

45
Humax crashed at Tue Aug 9 21:30:52 UTC 2016 - Uptime: 428

44
Humax crashed at Tue Aug 9 21:23:21 UTC 2016 - Uptime: 67

43
Humax crashed at Tue Aug 9 21:21:50 UTC 2016 - Uptime: 439

42
Humax crashed at Tue Aug 9 21:14:07 UTC 2016 - Uptime: 67

41
Humax crashed at Tue Aug 9 21:12:36 UTC 2016 - Uptime: 521

40
Humax crashed at Tue Aug 9 21:03:33 UTC 2016 - Uptime: 437

39
Humax crashed at Tue Aug 9 20:55:52 UTC 2016 - Uptime: 67

38
Humax crashed at Tue Aug 9 20:54:21 UTC 2016 - Uptime: 437

37
Humax crashed at Tue Aug 9 20:46:40 UTC 2016 - Uptime: 67

36
Humax crashed at Tue Aug 9 20:45:09 UTC 2016 - Uptime: 536

35
Humax crashed at Tue Aug 9 20:35:50 UTC 2016 - Uptime: 562

34
Humax crashed at Tue Aug 9 20:26:05 UTC 2016 - Uptime: 432

33
Humax crashed at Tue Aug 9 20:18:29 UTC 2016 - Uptime: 68

32
Humax crashed at Tue Aug 9 20:16:58 UTC 2016 - Uptime: 524

31
Humax crashed at Tue Aug 9 20:07:51 UTC 2016 - Uptime: 429

30
Humax crashed at Tue Aug 9 20:00:18 UTC 2016 - Uptime: 68

29
Humax crashed at Tue Aug 9 19:58:47 UTC 2016 - Uptime: 532

28
Humax crashed at Tue Aug 9 19:49:32 UTC 2016 - Uptime: 454

27
Humax crashed at Tue Aug 9 19:41:35 UTC 2016 - Uptime: 67

26
Humax crashed at Tue Aug 9 19:40:05 UTC 2016 - Uptime: 439

25
Humax crashed at Tue Aug 9 19:32:21 UTC 2016 - Uptime: 67

24
Humax crashed at Tue Aug 9 19:30:51 UTC 2016 - Uptime: 449

23
Humax crashed at Tue Aug 9 19:22:59 UTC 2016 - Uptime: 67

22
Humax crashed at Tue Aug 9 19:21:28 UTC 2016 - Uptime: 519

21
Humax crashed at Tue Aug 9 19:12:27 UTC 2016 - Uptime: 425

20
Humax crashed at Tue Aug 9 19:04:58 UTC 2016 - Uptime: 67

19
Humax crashed at Tue Aug 9 19:03:27 UTC 2016 - Uptime: 450

18
Humax crashed at Tue Aug 9 18:55:33 UTC 2016 - Uptime: 68

17
Humax crashed at Tue Aug 9 18:54:02 UTC 2016 - Uptime: 426

16
Humax crashed at Tue Aug 9 18:46:33 UTC 2016 - Uptime: 67

15
Humax crashed at Tue Aug 9 18:45:02 UTC 2016 - Uptime: 547

14
Humax crashed at Tue Aug 9 18:35:32 UTC 2016 - Uptime: 425

13
Humax crashed at Tue Aug 9 18:28:02 UTC 2016 - Uptime: 68

12
Humax crashed at Tue Aug 9 18:26:31 UTC 2016 - Uptime: 426

11
Humax crashed at Tue Aug 9 18:19:01 UTC 2016 - Uptime: 68

10
Humax crashed at Tue Aug 9 18:17:30 UTC 2016 - Uptime: 427

9
Humax crashed at Tue Aug 9 18:10:00 UTC 2016 - Uptime: 67

8
Humax crashed at Tue Aug 9 18:08:29 UTC 2016 - Uptime: 570

7
Humax crashed at Tue Aug 9 17:58:36 UTC 2016 - Uptime: 432

6
Humax crashed at Tue Aug 9 17:51:00 UTC 2016 - Uptime: 67

5
Humax crashed at Tue Aug 9 17:49:15 UTC 2016 - Uptime: 437727

4
Humax crashed at Thu Aug 4 16:13:24 UTC 2016 - Uptime: 67

3
Humax crashed at Sat Jul 30 11:09:37 UTC 2016 - Uptime: 2414

2
Humax crashed at Sat Jul 30 10:28:48 UTC 2016 - Uptime: 147580

1
Humax crashed at Thu Jul 28 17:29:33 UTC 2016 - Uptime: 161928
 
Last edited:
I'd say it was network or DLNA related, or perhaps there's a bad recording somewhere on your disk.
Unplug the network and see if it still crashes.
Reset the DLNA database on the WebIf Diag. page.
 
The "normal protocol for posting terminal dumps" is not normal protocol for newbies BH. And they likely have not come across your previous sighs on the subject either and the chances of the next newbie reading your last post, I suspect, might also be slim.;)
 
In addition to following the steps that Black Hole has pointed you to, install the crashdiag package and when it crashes again run the crashdiag diagnostic and post the output.
 
Thanks for the comments. I've reset the DNLA database but I had to do this twice as the first time I did it it, when switching Content Share back on, the box crashed and rebooted. The second attempt worked fine.
af123 - you advised to install crashdiag - is it not already installed or is that a key bit I need to do? I ran the command and got this:

Code:
>>> Beginning diagnostic crashdiag

Running: crashdiag
No core directory.

>>> Ending diagnostic crashdiag

Completed.

No core directory - sounds iffy?

I will leave the LAN connected for now and see how it goes for a few days and it it still crashes I will leave it disconnected - I have MyCloud NAS that uses Twonky so maybe that's key issue.
 
He said to install the crashdiag package, then run the crashdiag diagnostic after a crash. They are two different things (go to WebIF >> Package Management).

Before that, you need to go through the diagnostic steps in my guide. Twonky is a likely candidate, but it can be guarded against if it is.
 
Last edited:
Back
Top