F5F Stay Refreshed Hardware Desktop Unusual crash after entering Windows login.

Unusual crash after entering Windows login.

Unusual crash after entering Windows login.

N
NinjaaGamer_
Member
189
03-15-2020, 09:01 PM
#1
I updated my motherboard to a new Gigabyte B550 Aorus Elite v2 in December. Since then, I've encountered random BSODs after logging into Windows. Recently, it triggered a completely new BSOD displaying "netwtw06.sys." A search showed this is linked to a Wi-Fi card (Asus PCI card with Intel 8260). Earlier issues included System Service Exception, amdkmdag.sys, unexpected kernel traps, page faults in non-paged areas, and ntoskrnl.exe, among others that didn<|pad|>'s source. I reinstalled Windows and all drivers are up to date. I have four TridentZ sticks running at 3600MHz, and the RAM model appears in their compatibility list. The CPU remains non-overclocked. The rest of the details are still unclear. Could anyone help identify the exact cause and why these crashes occur so frequently right after login?
N
NinjaaGamer_
03-15-2020, 09:01 PM #1

I updated my motherboard to a new Gigabyte B550 Aorus Elite v2 in December. Since then, I've encountered random BSODs after logging into Windows. Recently, it triggered a completely new BSOD displaying "netwtw06.sys." A search showed this is linked to a Wi-Fi card (Asus PCI card with Intel 8260). Earlier issues included System Service Exception, amdkmdag.sys, unexpected kernel traps, page faults in non-paged areas, and ntoskrnl.exe, among others that didn<|pad|>'s source. I reinstalled Windows and all drivers are up to date. I have four TridentZ sticks running at 3600MHz, and the RAM model appears in their compatibility list. The CPU remains non-overclocked. The rest of the details are still unclear. Could anyone help identify the exact cause and why these crashes occur so frequently right after login?

R
Rubicube59
Member
192
03-21-2020, 05:40 AM
#2
Continuing current conversation. No responses needed unless you indicate otherwise.
R
Rubicube59
03-21-2020, 05:40 AM #2

Continuing current conversation. No responses needed unless you indicate otherwise.