Computer randomly freezing after switching to Ethernet.

[Ketchup]

Alright, so since the night of yesterday(17th Aug) the problem seems to have stopped. This is really weird, it has abruptly stopped with no solid reason behind it....

I have a love/hate relationship with stuff like this. While I am glad "insert problem here" is gone, I am almost ticked that I never got to figure out what it was.

 

[tweakboy]

Its your OC that is the problem here.

 

[tweakboy]

Hey ketchup79 nice rig.

 

[inf1nity]

ambient room temperatures change?

Well, now that you mention it, it's been raining here since the evening of the 17th, and temperatures have indeed, come down quite a bit.

However, I have never experienced overheating problems on my PC ever before this. Even before the rains, the computer worked normally when i unplugged the ethernet cable..

 

[inf1nity]

I have a love/hate relationship with stuff like this. While I am glad "insert problem here" is gone, I am almost ticked that I never got to figure out what it was.

Yup, same here.. :thumbsdown:

 

[tortillasoup]

Well, now that you mention it, it's been raining here since the evening of the 17th, and temperatures have indeed, come down quite a bit.

However, I have never experienced overheating problems on my PC ever before this. Even before the rains, the computer worked normally when i unplugged the ethernet cable..

The Northbridge/southbridge whatever may be overheating from the heat load of the ethernet setup and or experiencing a voltage sag when things get too hot. Electronics can be finicky with excessive temperatures or too low of temperatures as well.

 

[Puffnstuff]

Alright, so since the night of yesterday(17th Aug) the problem seems to have stopped. This is really weird, it has abruptly stopped with no solid reason behind it.

I haven't done anything special. Disabled IPv6, .

Now I'm thinking that is part of your problem. You should be able to use ipv6 without issue unless you have a conflict with your system. I run with 4 & 6 enabled and my pc's all connect with both enabled in their connection properties.

 

[tweakboy]

I could be the PSU .... hmmm gl

 

[inf1nity]

UPDATE: I definitely think it has something to do with temperatures, because when the ambient temperatures go down after a slight drizzle, it stops happening.

However, I have set the PC to shutdown when the CPU hits 70 celsius. When the CPU hits 70 degrees, the PC turns off automatically. It doesn't freeze, it doesn't hang, it just powers off.

Once again, the PC turns off when the CPU hits 70C. It doesn't freeze and stop responding.

This freezing problem is unique and definitely has something to do with the ethernet, because it started happening only after I switched to ethernet, and doesn't happen when the internet is turned off.

It also doesn't happen when ambient temperatures are low.

I'm completely at my wits end trying to diagnose this issue. Google isn't much help either...

 

[JimKiler]

Time to try a different NIC.

 

[sdifox]

try this
open command prompt as administrator

type in this

netsh int ip reset

 

[tortillasoup]

UPDATE: I definitely think it has something to do with temperatures, because when the ambient temperatures go down after a slight drizzle, it stops happening.

However, I have set the PC to shutdown when the CPU hits 70 celsius. When the CPU hits 70 degrees, the PC turns off automatically. It doesn't freeze, it doesn't hang, it just powers off.

Once again, the PC turns off when the CPU hits 70C. It doesn't freeze and stop responding.

This freezing problem is unique and definitely has something to do with the ethernet, because it started happening only after I switched to ethernet, and doesn't happen when the internet is turned off.

It also doesn't happen when ambient temperatures are low.

I'm completely at my wits end trying to diagnose this issue. Google isn't much help either...

CPU temperatures and southbridge temperatures are different. One can rise independently or in conjunction with another.

 

[inf1nity]

Alright September 9th update.: Formatted C: and reinstalled Windows the day before yesterday. Installed all the drivers. Took care to install them in the correct order(the INF file for the chipset first, then the ethernet driver and then the other drivers.

Been 3 days today. Working fine so far. And the temperatures aren't too low either, the weather is still pretty warm.

Guess it wasn't about the ambient temperatures afterall...

 

[inf1nity]

Alright, it just happened twice in a row again. W.T.F

It seems to have started happening after i updated Windows. However, now its not as frequent as it was before.

 

[sdifox]

Have you been monitoring system temps?

 

[inf1nity]

Yes I have, they're fine. Fan activity is normal, and I have cleaned out the entire PC, cleaned the cooler and applied fresh thermal paste last week.

 

[sdifox]

Yes I have, they're fine. Fan activity is normal, and I have cleaned out the entire PC, cleaned the cooler and applied fresh thermal paste last week.

On the south bridge as well?

Got a spare Nic you can stick in?

 

[inf1nity]

On the south bridge as well?

Got a spare Nic you can stick in?

No, didn't apply paste on the SB, but I've had dust buildups in the past and this particular issue has never happened. I've got CPU protection enabled and it powers off the computer if the CPU temp hits 70 C.

No spare NIC unfortunately.

 

[sdifox]

No, didn't apply paste on the SB, but I've had dust buildups in the past and this particular issue has never happened. I've got CPU protection enabled and it powers off the computer if the CPU temp hits 70 C.

No spare NIC unfortunately.

The south bridge is usually where the onboard nic is.

 

[inf1nity]

So i finally downgraded to Windows 7 and this issue has stopped occurring.

Not exactly a solution, tbh, but better than the multiple issues i was having with Windows 8.