Static IP fixed my hosting problem, but now my PC REBOOTS! Minidump too.

from Sins Forums

Up until tonight I was never able to host a multiplayer game.  Absolutely everything I changed in my router made no difference. If I would host, my friends could not join.  I could easily join their games and play for a good bit, maybe 2 hours tops.  Unfortunately, on a side note, the dreaded minidump errors would come after a good hour or two for me.

In an attempt to fix my hosting issues and possibly see if I could, by some miracle, fix the damning minidump crashes, I had the strange thought to simply turn off DHCP within my router and assign static IP addresses to everything. 

Wala...hosting problem solved!!!  I could instantly host games now and my friends could join!  Maybe this will get rid of the minidumps too!

But...but...the INSTANT I start a game I am hosting or usually withing 10 minutes of the game I host, my PC literally reboots.  CLICK, black screen, reboot. 

I cannot begin to tell you how frustrating this is and I am extremely disappointed.   This is exactly the type of thing driving me towards buying a console. 

If I go back to my friend's games, the rebooting problem goes away, but within an hour or two...MINIDUMP.  If I try hosting again, once I click start game...CLICK, BLACK SCREEN REBOOT.

So I'm stuck with MINIDUMPS or REBOOTS.

Please tell me these two issues are related and PLEASE tell me these problems are going to be addressed in the next patch?

technical
3,002 views 4 replies
Reply #1 from Sins Forums Top
Your PC re-booting has nothing to do with setting your IP to static.


PC's spontaneously re-booting always have something to do with flaky powersupplies, hardware overheating/going bad, corrupt software (not necessarily in that order :) ) not setting IP's to static instead of using DHCP.
Reply #2 from Sins Forums Top
I agree with you that it's not the static IP causing the reboots, but I have a hard time believing it's the powersupply. UNLESS, by hosting a game, I'm draining more juice than when I join one? Doesn't make much sense to me. Also, when the machine comes back up, it says the system has recovered from the ever infamous 'serious error'.

When I click to see the details, I get the standard Windows message stating that a driver is the problem. Driver??? I have everything updated and I actually am running a Windows XP install that's less than a month old.

I'm leaning on corrupt software, specifically SINS and this latest patch. The rebooting only occurs when I attempt to host a SINS match. If the PS was flaky, why am I not having problems with any of my other software or windows in general? Why can I play single player skirmish matches with no problems? I can play 4 hour single player matches with NO issues, no minidumps, NOTHING. Day after day. Flawless.

As soon as I attempt multiplayer, everything goes to hell.

I believe there is a major flaw in the code somewhere, primarily when trying to network a game. Something causing a wicked memory leak spike or possibly even a regular GPF.
Elemental: Reforged
Reply #3 from Sins Forums Top
Figured I'd throw this into the mix: I turned off the 'automatic reboot' option in Windows for any crashes to see if I could get some more info on this rebooting issue. Now when I have the problem, I get a BSOD with 'KMIXER.SYS' as the problem file.

Again, this ONLY happens when I HOST a game. It'll happen immediately or within 5 minutes of starting the match. If I join a game, I still have the horrid minidumps, but no rebooting problems.

I've updated and downgraded sound drivers, ethernet drivers, and video drivers. Nothing matters. Minidumps stay and rebooting persists for any game I try to host. Single player poses no problems, it's strictly MP.
Reply #4 from Sins Forums Top
Figured I'd throw this into the mix: I turned off the 'automatic reboot' option in Windows for any crashes to see if I could get some more info on this rebooting issue. Now when I have the problem, I get a BSOD with 'KMIXER.SYS' as the problem file.Again, this ONLY happens when I HOST a game. It'll happen immediately or within 5 minutes of starting the match. If I join a game, I still have the horrid minidumps, but no rebooting problems.I've updated and downgraded sound drivers, ethernet drivers, and video drivers. Nothing matters. Minidumps stay and rebooting persists for any game I try to host. Single player poses no problems, it's strictly MP.
End of quote


did you email any of these minidumps in to stardock? they do after all contain the information about what is happening when the machine crashes..