GPF in __fget_light

So 11 seconds before the GPF, I get this weird curl error from my DDNS script. Thing they are related?   I know it's an old box, but replaced the memory 6 months ago and upgraded it to 4G.   Recently added a docker instance running storj but not seeing that in the stack.    Any thoughts?

Apr 22 03:16:01 medianas2 CRON[20470]: (root) CMD (/root/work/ddns/update-ddns.sh >> /var/log/autonet.log 2>&1)
Apr 22 03:16:01 medianas2 CRON[20471]: (root) CMD (/root/work/autonet/network_check.sh >> /var/log/autonet.log 2>&1)
Apr 22 03:16:21 medianas2 CRON[20468]: pam_unix(cron:session): session closed for user root
Apr 22 03:16:35 medianas2 ng-csd[3437]: Curl returned error code 56. Failure when receiving data from the peer
Apr 22 03:16:35 medianas2 ng-csd[3437]: E0422 03:16:35.763751 3437 CurlHttpClient.cpp:427] Curl returned error code 56. Failure when receiving data from the peer
Apr 22 03:16:46 medianas2 kernel: general protection fault: 0000 [#1] SMP 
Apr 22 03:16:46 medianas2 kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc nv6lcd(O) vpd(PO)
Apr 22 03:16:46 medianas2 kernel: CPU: 0 PID: 20483 Comm: ping Tainted: P           O    4.4.190.x86_64.1 #1
Apr 22 03:16:46 medianas2 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014  07/26/2010
Apr 22 03:16:46 medianas2 kernel: task: ffff880131fd0000 ti: ffff880144e20000 task.ti: ffff880144e20000
Apr 22 03:16:46 medianas2 kernel: RIP: 0010:[<ffffffff881347dd>]  [<ffffffff881347dd>] __fget_light+0x42/0x59
Apr 22 03:16:46 medianas2 kernel: RSP: 0018:ffff880144e23ee0  EFLAGS: 00010286
Apr 22 03:16:46 medianas2 kernel: RAX: a1a8ffffffffffff RBX: 0000000000000092 RCX: 0000000000000001
Apr 22 03:16:46 medianas2 kernel: RDX: ffff8800a89c4300 RSI: 0000000000004000 RDI: 0000000000000001
Apr 22 03:16:46 medianas2 kernel: RBP: ffff880144e23ee0 R08: 00007ffed0ec62d0 R09: 0000000000000004
Apr 22 03:16:46 medianas2 kernel: R10: 00007ffed0ec6100 R11: 0000000000000246 R12: 00007fb5cd0542a0
Apr 22 03:16:46 medianas2 kernel: R13: fffffffffffffff7 R14: 0000000000000000 R15: 0000000000000000
Apr 22 03:16:46 medianas2 kernel: FS:  00007fb5cd26d700(0000) GS:ffff88014fc00000(0000) knlGS:0000000000000000
Apr 22 03:16:46 medianas2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 22 03:16:46 medianas2 kernel: CR2: 00007fc00404447b CR3: 00000001003d2000 CR4: 0000000000040670
Apr 22 03:16:46 medianas2 kernel: Stack:
Apr 22 03:16:46 medianas2 kernel:  ffff880144e23ef0 ffffffff88134802 ffff880144e23f08 ffffffff88135096
Apr 22 03:16:46 medianas2 kernel:  ffffffff8811ed62 ffff880144e23f48 ffffffff8811ed83 00007fb5cd276000
Apr 22 03:16:46 medianas2 kernel:  0000000000000092 00007fb5ccce30e0 0000000000000092 00007fb5cd0542a0
Apr 22 03:16:46 medianas2 kernel: Call Trace:
Apr 22 03:16:46 medianas2 kernel:  [<ffffffff88134802>] __fdget+0xe/0x10
Apr 22 03:16:46 medianas2 kernel:  [<ffffffff88135096>] __fdget_pos+0xa/0x39
Apr 22 03:16:46 medianas2 kernel:  [<ffffffff8811ed62>] ? SyS_read+0x92/0x92
Apr 22 03:16:46 medianas2 kernel:  [<ffffffff8811ed83>] SyS_write+0x21/0x92
Apr 22 03:16:46 medianas2 kernel:  [<ffffffff888e664a>] entry_SYSCALL_64_fastpath+0x1e/0x8e
Apr 22 03:16:46 medianas2 kernel: Code: ca 75 2f 48 8b 50 20 8b 02 39 c7 72 04 31 c0 eb 2f 89 f9 48 39 c1 48 19 c0 21 c7 48 8b 42 08 48 8d 04 f8 48 8b 00 48 85 c0 74 e2 <85> 70 44 74 10 eb db e8 40 fc ff ff 48 85 c0 74 d1 48 83 c8 01 
Apr 22 03:16:46 medianas2 kernel: RIP  [<ffffffff881347dd>] __fget_light+0x42/0x59
Apr 22 03:16:46 medianas2 kernel:  RSP <ffff880144e23ee0>
Apr 22 03:16:46 medianas2 kernel: ---[ end trace f1b487395c689158 ]---