PS4 Freezing in Dungeons again.

[vigioX-Sun]

ok. so I do ping, and it just keeps going and going and going. isn't it supposed to stop at some point?

I did to a traceroute on the server you gave me.

tracepath 184.107.107.176
1: 192.168.0.101 0.193ms pmtu 1500
1: 192.168.0.1 76.790ms
1: 192.168.0.1 3.995ms
2: no reply
3: 173-219-252-170.suddenlink.net 40.336ms
4: 173-219-232-135.suddenlink.net 41.966ms
5: ae0-111.cr2-chi1.ip4.gtt.net 49.794ms asymm 6
6: ae0-111.cr2-chi1.ip4.gtt.net 32.112ms
7: iweb-gw.ip4.gtt.net 56.439ms asymm 14
8: ae0.cr5.mtl.iweb.com 53.819ms asymm 15
9: te7-4.dr9.mtl.iweb.com 72.908ms asymm 16
10: te7-3.dr9.mtl.iweb.com 103.258ms asymm 16
11: 174.142.115.218 61.915ms asymm 17
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500

ok thats a lot of hops your ISP uses to get to the server.
first the 2 first hops is from your Ethernet to the modem an there is a problem there since you suppose to be next to it it should only take a few MS( 5-15ms) to get the signal there but look at those numbers:
tracepath 184.107.107.176
1: 192.168.0.101 0.193ms pmtu 1500
1: 192.168.0.1 76.790ms
1: 192.168.0.1 3.995ms
just bcuz of that you should start to feel lagg on the game.
---make sure your ethernet card drivers are update an your ethernet cord is not broken or any dmg(wifi? maybe you got a microwave close or too many walls) if posible put another one an run the test again to see of that goes away.
moving on
the "no reply" hops could be duo to package lost on the network
now it gets worse from here:
6: ae0-111.cr2-chi1.ip4.gtt.net 32.112ms
7: iweb-gw.ip4.gtt.net 56.439ms asymm 14
8: ae0.cr5.mtl.iweb.com 53.819ms asymm 15
9: te7-4.dr9.mtl.iweb.com 72.908ms asymm 16
10: te7-3.dr9.mtl.iweb.com 103.258ms asymm 16
11: 174.142.115.218 61.915ms asymm 17

way too high MS im surprise you could even play the game like this, like if you play titan you should have like no time to dodge the push attack with such high ms since its taking to long to get from your router to the server, i wish i could explain better but English is not my main language
but just to give you an example this is how more or less it should look:
:\Users\vigioX>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 3 ms 2 ms 5 ms 10.1.10.1
2 16 ms 10 ms 9 ms 96.120.37.181
3 26 ms 30 ms 19 ms xe-3-0-2-sur05.northdade.fl.pompano.comcast.net
[96.108.135.221]
4 12 ms 15 ms 29 ms te-0-4-0-9-ar01.northdade.fl.pompano.comcast.net
[69.139.180.209]
5 22 ms 19 ms 29 ms be-20214-cr02.miami.fl.ibone.comcast.net [68.86.
90.205]
6 20 ms 26 ms 19 ms hu-0-12-0-1-pe03.nota.fl.ibone.comcast.net [68.8
6.82.250]
7 13 ms 13 ms 18 ms ix-xe-0-1-2-0.tcore1.MLN-Miami.as6453.net [66.11
0.9.101]
8 79 ms 99 ms 87 ms if-ae-1-2.tcore2.MLN-Miami.as6453.net [63.243.15
2.62]
9 76 ms 77 ms 81 ms if-ae-3-2.tcore2.DT8-Dallas.as6453.net [66.110.7
2.6]
10 71 ms 79 ms 80 ms if-ae-2-2.tcore1.DT8-Dallas.as6453.net [66.110.5
6.5]
11 89 ms 81 ms 78 ms if-ae-23-2.tcore2.CT8-Chicago.as6453.net [64.86.
79.120]
12 80 ms 89 ms 80 ms if-ae-3-2.tcore1.W6C-Montreal.as6453.net [66.198
.96.45]
13 75 ms 79 ms 80 ms 66.198.96.58
14 70 ms 73 ms 75 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
15 78 ms 85 ms 99 ms 174.142.115.218
16 78 ms 79 ms 79 ms 184.107.107.176

Trace complete.
now notice the first 2 hops how low they are thats why i say something is wrong there, if you using wifi maybe there are too many walls from your divice to the router try to shorter that or use a ethernet, if using ethernet you need to chck ethernet card/cable/modem.
now look at the route it only take 16 jumps to get to SE server an look at the MS. "miliseconds" 1000ms=1sec now you got an idea.
there is not much you can do about this since is the route that you ISP uses to get to the servers,sure some games dont suffer the same problem but that always depends on the route your modem use,most you can to is to use 3rd party programs or contact your ISP to see if something can be done about this, but there is a problem in your device too so try to fix that.
that was a traceroute now try to do a PING instead type it like this
PING -n 25 184.107.107.176
thats gonna send 25 echo to the server an is gonna give you 25 reply, with that you can see how many packages you are losing.

now you say that everything stops an it moves fast,like time stop an move foward an you see everything that happens in just 2secs or so thats mostly duo to package lost an you getting them back later on, the ping test will tell us that an prove it.