• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Very weird cable modem problem

DT4K

Diamond Member
I recently moved and about 2 weeks ago, I had my cable internet hooked up. Ever since then, I'm getting a "Windows has recovered from a serious error" message box every time I boot up. After clearing the message box, the system runs fine. No problems at all. If I unplug my ethernet cable from the cable modem and reboot, I don't get the error message. Everything about my system, except the cable modem, is the same as I had at my previous house with a different isp. So it has to be something weird going on with my cable modem. I keep getting these 3 event log entries.

1. Information - Tcpip - The system has detected that network adapter(...) was connected to the network and has initiated normal operation over the network adapter.

2. Information - Save Dump - The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a(0x00100456, 0x000000ff, 0x00000001, 0x804d79ab). A dump was saved in: C:\Windows\Minidump\mini121302-06.dmp.

3. Error - System Error - Error code 0000000a, parameter1 00100456, parameter2 000000ff, parameter3 00000001, parameter4 804d79ab.

Anyone have any ideas ?

Thanks
 
Perhaps you should uninstall your ethernet adapter and install it again. That will force Windows to reload various software necessary for networking. It's worth a shot...
 
OK, this is very strange. But this problem just disappeared. I haven't seen it now in the last 3 or 4 days.
Because I didn't get it when I unplugged my ethernet from my cable modem, I'm sure it was something going on with the modem or my ISP.
Maybe they had something screwed up with the modem configuration and they just fixed it. I don't know, it just seems weird that something like that would have caused me to get a dump and error messages every time I booted.
 
Back
Top