Samsung Galaxy S3 Reboot Issue (ROOTED)

[BluesKing689]

I'm suffering from this problem for MONTHS, but I recently get my account , so I can now finally ask :
My S3 always reboots when I GO ONLINE (offline or boot in safe mode is fine, this issue only occurs when I connected to any Wi-Fi) (Sometimes it's fine , and IDK why , like when I'm writing this topic)
Before, I googled many crap times , and here's the solutions that I've tried:
- Wipe cache - FAILED
-Use CPU Tuner to adjust the CPU Frequency - Helped 50%, but still FAILED
-Use FXR Wifi Fix & Rescue - FAILED
-Give up using TouchWiz but use LINE Launcher - FAILED OF COURSE
GUYS, IF YOU'VE SOLVED THIS PROBLEM, PLS LET ME KNOW SOON! Cuz this problem interrupted my online experience such as watching YouTube or gaming! :]

 

[Claude Speed]

I'm suffering from this problem for MONTHS, but I recently get my account , so I can now finally ask :
My S3 always reboots when I GO ONLINE (offline or boot in safe mode is fine, this issue only occurs when I connected to any Wi-Fi) (Sometimes it's fine , and IDK why , like when I'm writing this topic)
Before, I googled many crap times , and here's the solutions that I've tried:
- Wipe cache - FAILED
-Use CPU Tuner to adjust the CPU Frequency - Helped 50%, but still FAILED
-Use FXR Wifi Fix & Rescue - FAILED
-Give up using TouchWiz but use LINE Launcher - FAILED OF COURSE
GUYS, IF YOU'VE SOLVED THIS PROBLEM, PLS LET ME KNOW SOON! Cuz this problem interrupted my online experience such as watching YouTube or gaming! :]

You could reflash your stock ROM and re-root

 

[BluesKing689]

That means I have to backup my data and reflash the stock ROM using Odin right?
P. S. The problem occurs when this message appears : "Connected to WiFi network [WiFi name]"

 

[BluesKing689]

Anymore solutions besides reflashing my stock ROM?
The issue is getting serious now and even I'm offline, it still reboots! (rare)
Also, once my phone crashes and reboots, I wanna open the AC Forum but somehow it instantly reboots!

 

[BluesKing689]

Now the problem doesn't exist anymore
Maybe because I rerooted with KingRoot instead