Asus RT-AC3200 randomly rebooting constantly

[Lucky225]

Hi all, hope this is the right place to be asking this.

I have an ASUS RT-AC3200 that after I upgraded to latest stock firmware (3.0.0.4.382_51640) has been randomly rebooting with null pointer errors from a kernal panic in the reboot message on the system log (see below). I tried factory resetting it with the initialize option to clear NVRAM but still get the same issue. I would run Merlin but for some reason the wifi settings just don't jive with all the iot crap I have in my house (about 15 light bulbs, 3 alexa devices, some power switches, wyze cameras etc.), everytime I flash to a new firmware or factory reset etc I have to go through and manually change the wifi SSIDs (one for the 2.4ghz iot crap, 5ghz needs a different SSID or half the iot crap fails) so it's pretty frustrating to try this or try that, if it involves yet another factory reset and firmware flash as I've found even with the same exact settings on one firmware vs another the iot crap will fail to renegotiate after a fresh flash. So I have all that crap working on the stock newest firmware currently, but I keep getting random reboots with the null pointer error, this didn't happen until the latest firmware upgrade from ASUS but has become very troubling as it tends to happen at least once a day and sometimes more. I've noticed the logs also show 'May 4th' indicating the date/time is lost when this happens. Below is the log:

May 4 23:05:00 kernel: _ Reboot message ... _______________________________________________________
May 4 23:05:00 kernel: <1>Unable to handle kernel NULL pointer derefere�U�at virtual address 00000000
May 4 23:05:00 kernel: <1>pgd = 80004000
May 4 23:05:00 kernel: <1>[00000000] *pgd=00000000
May 4 23:05:00 kernel: <0>Internal error: Oops: 817 [#1] PREEMPT SMP
May 4 23:05:00 kernel: <0>last sysfs file: /sys/class/net/eth0/speed
May 4 23:05:00 kernel: <4>module: nf_nat_sip 7f3df000 5031
May 4 23:05:00 kernel: <4>module: nf_conntrack_sip 7f3d6000 15713
May 4 23:05:00 kernel: <4>module: nf_nat_h323 7f3cf000 4761
May 4 23:05:00 kernel: <4>module: nf_conntrack_h323 7f3c1000 33807
May 4 23:05:00 kernel: <4>module: nf_nat_rtsp 7f3bb000 3202
May 4 23:05:00 kernel: <4>module: nf_conntrack_rtsp 7f3b5000 4067
May 4 23:05:00 kernel: <4>module: nf_nat_ftp nntrack_ftp 7f3a8000 4909
May 4 23:05:00 kernel: <4>m0 934
May 4 23:05:00 kernel: <4>module: usblp 7f39a07f37d000 85357
May 4 23:05:00 kernel: <4>module: tntfs 7f2fd000 468922
May 4 23:05:00 kernel: <4>module: tfat 7f2c4000 191259
May 4 23:05:00 kernel: <4>module: ext2 7f2af000 53788
May 4 23:05:00 kernel: <4>module: ext4 7f26e000 222306
May 4 23:05:00 kernel: <4>m>module: crc16 7f254000 1007
May 4 23:05:00 kernel: <4>module: ext3 7f231000 106589
May 4 23:05:00 kernel: <4>module: jbd 7f220000 42799
May 4 23:05:00 kernel: <4>module: mbcache 7f219000 4599
May 4 23:05:00 kernel: <4>module: usb_storage 7f20a000 34230
May 4 23:05:00 kernel: <4>module: sg 7f1ff000 20039
May 4 23:05:00 kernel: <4>module: sd_4>module: scsi_mod 7f1c8000 108826
May 4 23:05:00 kernel: <4>module: cdc_mbim 7f1c2000 3137
May 4 23:05:00 kernel: <4>module: qmi_wwan wdm 7f1b4000 7252
May 4 23:05:00 kernel: <4>module: e: rndis_host 7f1a5000 5256
May 4 23:05:00 kernel: <7f186000 11844
May 4 23:05:00 kernel: <4>module: mii _LOG 7f179000 4494
May 4 23:05:00 kernel: <4>module: fs2 7f119000 91538
May 4 23:05:00 kernel: <4>module: zlib_deflate 7f10f000 19489
May 4 23:05:00 kernel: <4>module: dhd 7f02e000 242573
May 4 23:05:00 kernel: <4>module: et 7f01b000 49073
May 4 23:05:00 kernel: <4>module: igs 7f013000 11927
May 4 23:05:00 kernel: <4>module: emf 7f00a000 153647
May 4 23:05:00 kernel: <4>Modules linked in: nf_nat_sip nf_conntrack_sip nf_nat_h323 nf_conntrack_h323 nf_nat_rtsp nf_conntrack_rtsp nf_nat_ftp nf_blp thfsplus tntfs(P) tfat(P) ext2 ext4 jbd2 crc16 ext3 jbd mbcache usb_storage sg sd_mod scsi_wwan cdc_wdm cdc_ncm rndis_host cdc_ether asix cdc_acm usbnet miicd ehci_hcd usbcore jffs2 zlib_deflate dhd et(P) igs(P) emf(P) ctf(P) [last unloaded: nf_conntra
May 4 23:05:00 kernel: _mailbox_intr+0x164/0x1f0 [dhd]
May 4 23:05:00 kernel: <4>LR is at dhdpcie_bus_process_mailbox_intr+0x14c/0x1f0 [dhd]
May 4 23:05:00 kernel: <00000000
May 4 23:05:00 kernel: <4>r10: 8004d1d4 r9 : 807f05dae0 r6 : 00000000 r5 : 000000 r0 : 00000834
May 4 23:05:00 kernel: <4>Flags: nZ2 ISA ARM Segment kernel
May 4 23:05:00 kernel: <4>Coer (pid: 0, stack limit = 0x8f83 00000000 8f80e000 00000000 10000000
May 4 23:05:00 kernel: <0>d00000000 8f83c000 7f0529bc 00000100 8040f21c
May 4 23:05:00 kernel: <0>df00: 8ee38000 8ee3b8cc 00000000 7f033490 8ee3b8c8 8007a428 8007a31c 00000001
May 4 23:05:00 kernel: <000001 803c4d70
May 4 23:05:00 kernel: <0>df40: 90810000 80068b34 00000006 0000000a 0000000 0000001f 00000000 8007abcc 0ff b0100100 000000a3 00000002 000
May 4 23:05:00 kernel: <0>dfa0: 8f83dfe0 00000000 8f848 becef5ea b82d97ad
May 4 23:05:00 kernel: <4>[<7f0418ss_mailbox_intr+0x164/0x1f0 [dhd])
May 4 23:05:00 kernel: <4>[<7f041870>] (dhdpcie_bus_ [dhd]) from [<7f0529bc>] (dhd_bus_dpc+0xc8/0x150 [dhd])
May 4 23:05:00 kernel: <4>unwind: Index not found 7f0529bc
May 4 23:05:00 kernel: <0>d trace 73e868c3d8f8c871 ]---
May 4 23:05:00 kernel: <0>Kernel panic - not syncing: Fatx7c/0x1a8)
May 4 23:05:01 kernel: <4>[<80302594>] (pani(die+0x1ac/0x1dc)
May 4 23:05:01 kernel: <4>[<800536f8>00000 7f0553ec 8f83ded0
May 4 23:05:01 kernel: <4>dec0: ^C+0x4c/0x60) from [<7f041870>] (d
May 4 23:05:01 kernel: ____________________________________________________________________________

 

[devnulldump]

@Lucky225
I have the same identical issue, just wondering if you had any luck in finding the root-cause?

 

[Kiddco]

@Lucky225 @devnulldump
I have been plauge with this ramdom rebooting ever since last year. Have you guys find any solution to this problem? My log says the same error code and i have tried many things to try to resolve this issue. I thought i figured it out when i replace the power supply and add cooling to the router but i think it only lasted for 12 days and it reset itself.

 

[L&LD]

If a full reset doesn't work, then it most likely is a hardware issue.

See the link in my signature below for the M&M Config and also the Nuclear Reset guides for help to get your router back to a good/known state.

 

[Kiddco]

Thanks L&LD for the reply. I just flashed fresh tomato onto the router and had followed your nuke guide. Hopefully this will remedy the random rebooting I had.