NIC GSOD

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I just registered here because I wanted to let everyone know that if you get GSODs or shutdowns and the problem always points to the NIC, try turning off Cool N Quiet.

No matter what NIC I used, internal, external, USB, WhoCrashed always pointed to the NIC.

Hope this saves someone some trouble.

(AB350M Pro4 w/Ryzen 1200)

chamber32

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
chamber32 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 14 Jun 2018 Location: Bridge Creek, O Status: Offline Points: 5	Post Options Post Reply Quote chamber32 Report Post Thanks(0) Quote Reply Topic: NIC GSOD Posted: 14 Jun 2018 at 7:19pm
	I just registered here because I wanted to let everyone know that if you get GSODs or shutdowns and the problem always points to the NIC, try turning off Cool N Quiet. No matter what NIC I used, internal, external, USB, WhoCrashed always pointed to the NIC. Hope this saves someone some trouble. (AB350M Pro4 w/Ryzen 1200) chamber32

chamber32 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 14 Jun 2018 Location: Bridge Creek, O Status: Offline Points: 5	Post Options Post Reply Quote chamber32 Report Post Thanks(0) Quote Reply Posted: 15 Jun 2018 at 8:38pm
	Well, I thought that was it, but now the problem has returned after Win10 Insider update.

chamber32 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 14 Jun 2018 Location: Bridge Creek, O Status: Offline Points: 5	Post Options Post Reply Quote chamber32 Report Post Thanks(0) Quote Reply Posted: 18 Jun 2018 at 9:07pm
	UPDATE: It suddenly dawned on me that the one common thing to all NICs was that I was pointing to a Linux proxy, removed proxy setting, all good! I don't understand why this would happen, but glad I got it resolved.