Windows 10: Event log filled with WPNConnectionFailure

Having some internet issues where connection is lost for 3-4 minutes and the cable modem restarts. The event viewer is filled with the logs below usually before the internet disconnects. I'm wondering if this is the cable modem's fault and Windows just reporting what's happening, or if the computer itself is causing the cable modem to restart.

Code:

Fault bucket , type 0
Event Name: WPNConnectionFailure
Response: Not available
Cab Id: 0


Problem signature:
P1: Data Fast-Reconnect
P2: 8004acb1
P3: WNP
P4: Unknown
P5: Unknown
P6: Unknown
P7: 1
P8: 242
P9: 
P10: 


Attached files:


These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Data Fast-Reconn_948082bbf1a964363bb623d89e8361737c0fd49_00000000_12253bec


Analysis symbol: 
Rechecking for solution: 0
Report ID: d6e0a261-80a9-11e5-bfcc-6245b4e75b75
Report Status: 96

Code:

Version=1EventType=WPNConnectionFailure
EventTime=130908637623185983
Consent=1
UploadTime=130908638701733410
ReportFlags=256
ReportIdentifier=9934434f-80a9-11e5-bfcc-6245b4e75b75
Response.type=4
Sig[0].Name=Scenario
Sig[0].Value=Data Fast-Reconnect
Sig[1].Name=Error Result
Sig[1].Value=8004acb1
Sig[2].Name=Error Source
Sig[2].Value=WNP
Sig[3].Name=Protocol
Sig[3].Value=Unknown
Sig[4].Name=Proxy Type
Sig[4].Value=Unknown
Sig[5].Name=Interface Type
Sig[5].Value=Unknown
Sig[6].Name=Platform Role
Sig[6].Value=1
Sig[7].Name=Geo Id
Sig[7].Value=242
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10240.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
FriendlyEventName=Windows Push Notifications Connectivity Quality of Service Event
ConsentKey=WPNConnectionFailure
AppName=wpnprv.dll
AppPath=C:\WINDOWS\wpnprv.dll
ApplicationIdentity=00000000000000000000000000000000

To give you an idea of how frequent the log entries are (there are lots of them)

Another log in the event viewer mentions this. It usually triggered when a torrent client is running

TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.