Home Network Community >
DSL Modem Routers >
TD-W9980 crashing: TP-Link need to fix this issue ASAP!
TD-W9980 crashing: TP-Link need to fix this issue ASAP!
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TD-W9980 crashing: TP-Link need to fix this issue ASAP!
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2015-01-31
2015-02-03 05:34:32
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2015-01-31
TD-W9980 crashing: TP-Link need to fix this issue ASAP!
2015-02-03 05:34:32
Tags:
Region : Ireland
Model : TD-W9980
Hardware Version : V1
Current Firmware Version : 0.6.0 1.8 v0021.0 Build 140925 Rel.32089n
Latest Firmware tested: TD-W9980_V1_141215
ISP : Eircom eFibre VDSL2 (no vectoring so far)
Recently bought a TD-W9980 and quickly began to notice these modem routers have a flaw that has been carried through several generations of TP-link devices. For some odd reason the router doesn't play nice with networked devices pushing high bandwidth up and down and around the WAN/LAN, so much so that it crashes randomly at least twice, maybe three times a day. You can't access the network wirelessly, any new devices attempting to connect will not be assigned an IP by DHCP as it seems to be borked, the modem's firmware settings are inaccessible but you can connect to the internet on a wired connection strangely enough (if the client device has been already assigned an IP before the crash). Syslogs are wiped on restart every time so today I decided to use my NAS as a syslog server so it could feed error messages to it. Nothing/no crash so far.
Similar issues can be seen on the TD-W8980, W8970 and the W8968. I believe it is a flaw in the firmware that leads the router to do intensive CPU work and then overheat (see heatsink replacement link). Some say it might be the NAT table being overloaded (out of bounds or poor memory allocation). Pretty much all these routers are passively cooled and rated with a ideal max temp of 40 degrees Celsius. I can tell you that by placing my hand over the case, it certainly feels like its hitting that threshold quite quickly.
W9980: TP-Link Forum - TD-W9980 multiple issues
W8980: Whirlpool Forum - TD-W8980 error
W8970: http://forum.tp-link.com/showthread.php?3102-TD-W8970-freezing&highlight=NAT+crash TP-Link Forum - TD-W8970 freezing and NAT crash
W8968: TP-Link Forum - My W8968 has begun to freeze up...
Heatsink replacement: ADSL Zone - TD-W8970
Prime culprit seems to be related to torrents and a PLEX media laptop server setup I have going on with a QNAP NAS. I want to like this router. I really do. The menus are a breeze and when it works, its so snappy. My ISP (Eircom) modem router which is a rebranded Zyxel VMG8324-B10A is a load of muck and dies due to unstable firmware as well so I've no other option. I've posted a review on Amazon detailing this and will update it as soon as you release a definitive fix for the issue. Also something to note is the TD-W9980 is not in the list of selectable devices when posting on the forums so I had to edit the HTML combo box on the new thread page to cater for this. I am willing to try beta firmware (as long as patch notes are issued with them detailing whats changed).
Also, another issue that seems to occur in multiple TP-Link devices is that diagnostic tools will always seem to fail when testing DNS root for "Internet surfing" even though I can browse perfectly fine (until of course the modem router crashes!). This error occurs in every firmware available for the TD-W9980 for me.
Test DNS Root: TP-Link Forum - W8980 Test DNS Root
Model : TD-W9980
Hardware Version : V1
Current Firmware Version : 0.6.0 1.8 v0021.0 Build 140925 Rel.32089n
Latest Firmware tested: TD-W9980_V1_141215
ISP : Eircom eFibre VDSL2 (no vectoring so far)
Recently bought a TD-W9980 and quickly began to notice these modem routers have a flaw that has been carried through several generations of TP-link devices. For some odd reason the router doesn't play nice with networked devices pushing high bandwidth up and down and around the WAN/LAN, so much so that it crashes randomly at least twice, maybe three times a day. You can't access the network wirelessly, any new devices attempting to connect will not be assigned an IP by DHCP as it seems to be borked, the modem's firmware settings are inaccessible but you can connect to the internet on a wired connection strangely enough (if the client device has been already assigned an IP before the crash). Syslogs are wiped on restart every time so today I decided to use my NAS as a syslog server so it could feed error messages to it. Nothing/no crash so far.
Similar issues can be seen on the TD-W8980, W8970 and the W8968. I believe it is a flaw in the firmware that leads the router to do intensive CPU work and then overheat (see heatsink replacement link). Some say it might be the NAT table being overloaded (out of bounds or poor memory allocation). Pretty much all these routers are passively cooled and rated with a ideal max temp of 40 degrees Celsius. I can tell you that by placing my hand over the case, it certainly feels like its hitting that threshold quite quickly.
W9980: TP-Link Forum - TD-W9980 multiple issues
W8980: Whirlpool Forum - TD-W8980 error
W8970: http://forum.tp-link.com/showthread.php?3102-TD-W8970-freezing&highlight=NAT+crash TP-Link Forum - TD-W8970 freezing and NAT crash
W8968: TP-Link Forum - My W8968 has begun to freeze up...
Heatsink replacement: ADSL Zone - TD-W8970
Prime culprit seems to be related to torrents and a PLEX media laptop server setup I have going on with a QNAP NAS. I want to like this router. I really do. The menus are a breeze and when it works, its so snappy. My ISP (Eircom) modem router which is a rebranded Zyxel VMG8324-B10A is a load of muck and dies due to unstable firmware as well so I've no other option. I've posted a review on Amazon detailing this and will update it as soon as you release a definitive fix for the issue. Also something to note is the TD-W9980 is not in the list of selectable devices when posting on the forums so I had to edit the HTML combo box on the new thread page to cater for this. I am willing to try beta firmware (as long as patch notes are issued with them detailing whats changed).
Also, another issue that seems to occur in multiple TP-Link devices is that diagnostic tools will always seem to fail when testing DNS root for "Internet surfing" even though I can browse perfectly fine (until of course the modem router crashes!). This error occurs in every firmware available for the TD-W9980 for me.
Test DNS Root: TP-Link Forum - W8980 Test DNS Root
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
Announcement Manage
26 Reply
Posts: 5
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2015-10-20
Re:TD-W9980 crashing: TP-Link need to fix this issue ASAP!
2016-07-05 01:48:07
Hi all - was there ever a solution to this issue? Our 9980 seems to be doing something similar!
The unit is just 10 months old and seems to be experiencing random restarts - the last two being in the middle of the night, or during the day when traffic is either very slow or non-existent. Again the wireless disappears meaning I can't get to the router, the wired system seems absolutely fine..!? It corrects itself in a random timeframe from a few seconds to hours...
I've tried cycling the wi-fi on/off button, which almost acts like a reset - weirdly this also cuts the wired connection as well, should it? When I lose the wireless, devices still say they are connected, all lights on the unit are normal.
I bit the bullet yesterday and went for the pin-hole reset, all appeared to be fixed, but the router has since rebooted itself twice. The router log is next to useless, as it loses the time index, but you can roughly work out when it fell over.
Stuck for options now, not particularly tech minded but giving the Apple Airport serious consideration, just for some fuss-free connectivity...
Here's an example of the log if anyone can shed any light?
The unit is just 10 months old and seems to be experiencing random restarts - the last two being in the middle of the night, or during the day when traffic is either very slow or non-existent. Again the wireless disappears meaning I can't get to the router, the wired system seems absolutely fine..!? It corrects itself in a random timeframe from a few seconds to hours...
I've tried cycling the wi-fi on/off button, which almost acts like a reset - weirdly this also cuts the wired connection as well, should it? When I lose the wireless, devices still say they are connected, all lights on the unit are normal.
I bit the bullet yesterday and went for the pin-hole reset, all appeared to be fixed, but the router has since rebooted itself twice. The router log is next to useless, as it loses the time index, but you can roughly work out when it fell over.
Stuck for options now, not particularly tech minded but giving the Apple Airport serious consideration, just for some fuss-free connectivity...
Here's an example of the log if anyone can shed any light?
33 | 2016-07-04 15:28:08 | DHCPD | Notice | Send ACK to 192.168.1.112 |
34 | 2016-07-04 15:28:08 | DHCPD | Notice | Recv REQUEST from 90:B2:1F:BE:7C:EB |
35 | 2016-07-04 15:28:07 | DHCPD | Notice | Send ACK to 192.168.1.112 |
36 | 2016-07-04 15:28:07 | DHCPD | Notice | Recv REQUEST from 90:B2:1F:BE:7C:EB |
37 | 2016-07-04 15:28:06 | DHCPD | Notice | Send OFFER with ip 192.168.1.112 |
38 | 2016-07-04 15:28:06 | DHCPD | Notice | Recv DISCOVER from 90:B2:1F:BE:7C:EB |
39 | 2016-07-04 15:04:03 | DHCPD | Notice | Send ACK to 192.168.1.116 |
40 | 2016-07-04 15:04:02 | DHCPD | Notice | Recv REQUEST from 28:E7:CF:E8:6E:70 |
41 | 2016-07-04 14:39:42 | DHCPD | Notice | Send ACK to 192.168.1.111 |
42 | 2016-07-04 14:39:42 | DHCPD | Notice | Recv REQUEST from C8:BC:C8:7D:83:D1 |
43 | 2016-07-04 14:39:04 | PPP | Information | ppp0 sent [LCP ProtRej id=0x4 80 57 05 58 00 04] |
44 | 2016-07-04 14:39:04 | PPP | Information | ppp0 rcvd [IPV6CP TermReq id=0x58] |
45 | 2016-07-04 14:39:03 | DHCPD | Notice | Send ACK to 192.168.1.100 |
46 | 2016-07-04 14:39:03 | DHCPD | Notice | Recv REQUEST from 6C:AD:F8:C1:AC:E9 |
47 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [IPCP ConfAck id=0x2 |
48 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [LCP ProtRej id=0x3 80 57 05 57 00 04] |
49 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [IPV6CP TermReq id=0x57] |
50 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [IPCP ConfReq id=0x2 |
51 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [IPCP ConfNak id=0x1 |
52 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [IPCP ConfAck id=0x29 ] |
53 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [IPCP ConfReq id=0x29 ] |
54 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [LCP ProtRej id=0x2 80 57 01 56 00 0e 01 0a 02 21 05 ff fe 7e 44 34] |
55 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [IPV6CP ConfReq id=0x56 ] |
56 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [IPCP ConfReq id=0x1 ] |
57 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [CHAP Success id=0x1 "CHAP authentication success"] |
58 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [LCP EchoRep id=0x0 magic=0x65fa8aeb] |
59 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [CHAP Response id=0x1 <998d81866548116931b9a2dd18323108>, name = "bthomehub@btbroadban |
60 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [CHAP Challenge id=0x1 <65a29cde71b688f1f5a1a42e99a5c90a7b6e5e27d3168134a3e675e86b9fe6 |
61 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [LCP EchoReq id=0x0 magic=0xf66b9847] |
62 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [LCP ConfAck id=0x1 ] |
63 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [LCP ConfAck id=0x4d ] |
64 | 1970-01-01 00:01:59 | PPP | Information | ppp0 rcvd [LCP ConfReq id=0x4d ] |
65 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [LCP ConfReq id=0x1 ] |
66 | 1970-01-01 00:01:59 | PPP | Information | ppp0 sent [PADI Host-Uniq(0x00000a11)] |
67 | 1970-01-01 00:01:57 | PPP | Error | ppp0 |
68 | 1970-01-01 00:01:57 | PPP | Error | ppp0 Timeout waiting for PADO packets |
69 | 1970-01-01 00:01:37 | PPP | Information | ppp0 sent [PADI Host-Uniq(0x0000098f)] |
70 | 1970-01-01 00:01:27 | PPP | Information | ppp0 sent [PADI Host-Uniq(0x0000098f)] |
71 | 1970-01-01 00:01:23 | PPP | Information | ppp0 sent [PADI Host-Uniq(0x0000098f)] |
72 | 1970-01-01 00:01:21 | DSL | Notice | xDSL Enter Showtime!! |
73 | 1970-01-01 00:01:18 | DHCPD | Notice | Send ACK to 192.168.1.105 |
74 | 1970-01-01 00:01:18 | DHCPD | Notice | Recv REQUEST from 20:C6:EB:AF:CF:16 |
75 | 1970-01-01 00:01:18 | DHCPD | Notice | Send OFFER with ip 192.168.1.105 |
76 | 1970-01-01 00:01:18 | DHCPD | Notice | Recv DISCOVER from 20:C6:EB:AF:CF:16 |
77 | 1970-01-01 00:01:18 | DHCPD | Notice | Recv RELEASE from 20:C6:EB:AF:CF:16 |
78 | 1970-01-01 00:01:07 | DHCPD | Notice | Send ACK to 192.168.1.109 |
79 | 1970-01-01 00:01:07 | DHCPD | Notice | Recv REQUEST from 00:0E:58:8A:AE:52 |
80 | 1970-01-01 00:01:06 | DHCPD | Notice | Send ACK to 192.168.1.111 |
81 | 1970-01-01 00:01:05 | DHCPD | Notice | Recv REQUEST from C8:BC:C8:7D:83:D1 |
82 | 1970-01-01 00:01:04 | DHCPD | Notice | Send OFFER with ip 192.168.1.111 |
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#22
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 19
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-06-10
Re:TD-W9980 crashing: TP-Link need to fix this issue ASAP!
2016-07-25 23:17:12
I too am having problems with my WD9980
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#23
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 5
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2015-10-20
Re:TD-W9980 crashing: TP-Link need to fix this issue ASAP!
2016-07-26 16:54:53
Just to add; after contacting support and receiving some suggestions, disabling the uPnP seems to have done the trick - 20 days uptime and no restarts as yet. (I have no idea why this would work!)
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#24
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 5
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-04-08
Re:TD-W9980 crashing: TP-Link need to fix this issue ASAP!
2016-10-10 20:15:11
KB350 wrote
Just to add; after contacting support and receiving some suggestions, disabling the uPnP seems to have done the trick - 20 days uptime and no restarts as yet. (I have no idea why this would work!)
Glad it seems to have fixed the issue for you, is it still presenting as resolved as far as your setup is concerned?
I worry about this being a valid fix though, as;
Universal Plug and Play (UPnP) is a standard that uses Internet and Web protocol s to enable devices such as PCs, peripherals, intelligent appliances, and wireless devices to be plugged into a network and automatically know about each other.
I'm using the latest firmware, which was released in January 2016;
Firmware version:0.6.0 1.13 v0021.0 Build 160125 Rel.52064n
Hardware version:TD-W9980 v1 00000001
I have various devices linked to one another, both internally and externally through the internet, therefore I simply cannot disable uPnP; it is simply impossible and to keep up with my current required setup.
Hmmm not looking good if this is the case.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#25
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 5
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-04-08
Re:TD-W9980 crashing: TP-Link need to fix this issue ASAP!
2016-10-10 20:16:21
neilmch wrote
Hi
I have been experiencing 5ghz dropouts and router crashes. I decided to buy a laptop cooler tray from poundland as it was the perfect size and now the router is working ok and keeping cool. I think the router is overheating and this is causing the problems. It could do with more vents in it. I updated to the latest firmware and it is working ok now with the fan attached
I'm intrigued, did you plug this in to the routers usb port for the cooler tray to be powered, or a wall power socket kind of power connection?
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#26
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 5
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2015-10-20
Re:TD-W9980 crashing: TP-Link need to fix this issue ASAP!
2016-10-11 14:31:23
PhoenixUK wrote
Glad it seems to have fixed the issue for you, is it still presenting as resolved as far as your setup is concerned?
I worry about this being a valid fix though, as;
I'm using the latest firmware, which was released in January 2016;
Firmware version:0.6.0 1.13 v0021.0 Build 160125 Rel.52064n
Hardware version:TD-W9980 v1 00000001
I have various devices linked to one another, both internally and externally through the internet, therefore I simply cannot disable uPnP; it is simply impossible and to keep up with my current required setup.
Hmmm not looking good if this is the case.
Hi, up to a couple of weeks ago it was completely rock-solid, untouched frafew months. But, I recently have seen two of the old school dropouts, i.e. all wired connections perfect, wireless non-existent until a restart occurs. I'm using a fairly simple setup so I'm not sure the uPnP makes much difference to me. I'm also using theJan16 firmware.
Not sure if this makes a difference but; when it had the wireless loss I plugged in an old laptop to look at the log whilst the wireless was out - the log revealed nothing whatsoever out of the ordinary... it seemed to be functioning perfectly - aside of course from every wireless device in the house was out :) Weird
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#27
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2015-01-31
2015-02-03 05:34:32
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2015-01-31
Information
Helpful: 0
Views: 5760
Replies: 26
Voters 0
No one has voted for it yet.
Tags
Related Articles
TD-W9980 firewall issue
584
0
Report Inappropriate Content
Transfer Module
New message