You're my last hope!

I have attempted to fix this issue on my own and have decided I definitely need help. I have a sb 6120 modem and a wireless router that have been randomly dropping and resetting. I thought it was happening with increased bandwidth usage, but it doesn't appear to be linked to when I'm downloading or gaming. I have swapped out wireless routers and directly connected to my modem and it still happens. I have spoken with my ISP and they can't see that I have lost connection even while I am currently disconnected. My stats look good with my downstream power stable around 4 or 5 and up around 38. Also, I have pinged my modem and each computer connected wirelessly and show no packet loss. The only correlation I've noticed is when my girlfriend watches things on Hulu or I'm connected to the GUI for the modem it drops more, sometimes... I'm pretty much out of ideas here and I have scheduled an appointment for a tech to come out but I don't want to burn the money if I'm just going to have to replace my modem anyway. Any ideas on ways to test/fix what's going on? I've posted some logs below. Oh, also, I reset factory defaults thinking that might do something, but it didn't. Thanks in advance!

5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

 

Just as an update... the tech came out today and said it sounded like the bandwidth on our node was maxed. He said that during peak hours if there wasn't enough bandwidth we'd get randomly kicked. Likewise, if it wasn't peak hours and someone was using a ton of bandwidth (or several someones), then we could just as easily get disconnected. He said he was going to speak with his lead tech and work on it. Does this sound feasible?