![]() |
NIC GSOD |
Post Reply ![]() |
Author | |
chamber32 ![]() Newbie ![]() ![]() Joined: 14 Jun 2018 Location: Bridge Creek, O Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() 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. |
|
![]() |
|
chamber32 ![]() Newbie ![]() ![]() Joined: 14 Jun 2018 Location: Bridge Creek, O Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
Well, I thought that was it, but now the problem has returned after Win10 Insider update.
|
|
![]() |
|
chamber32 ![]() Newbie ![]() ![]() Joined: 14 Jun 2018 Location: Bridge Creek, O Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
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 |
|
![]() |
Post Reply ![]() |
|
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |