H
Hondo_Man
Guest
Right then,
I think through the process of elimination I might have the matter at hand, but not completely.
At the end of January, I ordered a customer made PC for my workshop. Nothing spectacular, but good enough for my work.
Specs:
Gigabyte A320M-S2H Mainboard
AMD4 Ryzen 5, 2600X CPU
Nvidia GeForce GT 710 graphics on-board
16GB DDR4 RAM
Windows 10 Pro
All drivers and the BIOS are up-to-date and I have only the bear essential programmes. Windows 10, Firefox & Thunderbird, Acrobat Adobe, CPU-Z, Belarc, Kaspersky, Whatsapp and Spotify.
When I ordered the PC, I didn't care for the WLAN card they had on offer, so I bought it separately. A TP-Link Archer TX50E AX3000 WiFi 6 PCIe Adapter with Bluetooth 5.0. Basically an Intel AX200.
Initially, the card worked perfectly. No issues. After a week, I would boot the PC in the morning and the card was not listed in the Device Manager. Odd, that. I restarted the PC and still not there. I powered down, unplugged the card's cable from the mainboard, waited about 20sec, plugged back in, re-booted and it worked fine.
This then became a few times per week to everyday.
However there is a change in this routine. What I've discovered is that I need only boot the PC in the morning (as is everyday, see that there is no connectivity and the card is not in the Device Manager), power down, wait about 4min, boot again and the PCIe card is recognised in the Device Manager and works.
To add to this, I can restart the PC during the day without issue. I can also power down at the end of the work day, say 18.00. Come back to the shop at 21.00 or 22.00, boot back up and the PCIe card is immediately recognised.
It's as if something changes after midnight. I've not bothered the check at, say, half past midnight, as I am asleep in bed.
Yes, I have tested the card in the other PCIe slot. No change.
I have asked on the TP-Link, Intel and Gigabyte forums. They all point a finger at each other as to what the issue is.
I am no computer expert. I have owned and worked with computers since 1992. To me, with my limited knowledge, it would seem that something is changing in the computer on the 'following day'. Date change - BIOS - Windows 10? A process that changes each day and is effecting the WLAN or Bluetooth when the computer initialises. What that is I cannot say.
I have run Task Manager and Task Schedule, Powershell's Get-Process, sfc /scannow, etc. I see nothing that might be a red-flag. I cannot figure out where the issues lays.
In googling potential ideas, I have discovered that I am not the only one to experience this. There are others and the mainboards vary, so I believe my mainboard is not the issue. Could be, but I don't think so. Perhaps a combination of events.
As a process of elimination, could this be a Windows conflict issue? Might someone at MS have an idea to this?
Looking forward to responses of ideas and thoughts.
Cheers!
Continue reading...
I think through the process of elimination I might have the matter at hand, but not completely.
At the end of January, I ordered a customer made PC for my workshop. Nothing spectacular, but good enough for my work.
Specs:
Gigabyte A320M-S2H Mainboard
AMD4 Ryzen 5, 2600X CPU
Nvidia GeForce GT 710 graphics on-board
16GB DDR4 RAM
Windows 10 Pro
All drivers and the BIOS are up-to-date and I have only the bear essential programmes. Windows 10, Firefox & Thunderbird, Acrobat Adobe, CPU-Z, Belarc, Kaspersky, Whatsapp and Spotify.
When I ordered the PC, I didn't care for the WLAN card they had on offer, so I bought it separately. A TP-Link Archer TX50E AX3000 WiFi 6 PCIe Adapter with Bluetooth 5.0. Basically an Intel AX200.
Initially, the card worked perfectly. No issues. After a week, I would boot the PC in the morning and the card was not listed in the Device Manager. Odd, that. I restarted the PC and still not there. I powered down, unplugged the card's cable from the mainboard, waited about 20sec, plugged back in, re-booted and it worked fine.
This then became a few times per week to everyday.
However there is a change in this routine. What I've discovered is that I need only boot the PC in the morning (as is everyday, see that there is no connectivity and the card is not in the Device Manager), power down, wait about 4min, boot again and the PCIe card is recognised in the Device Manager and works.
To add to this, I can restart the PC during the day without issue. I can also power down at the end of the work day, say 18.00. Come back to the shop at 21.00 or 22.00, boot back up and the PCIe card is immediately recognised.
It's as if something changes after midnight. I've not bothered the check at, say, half past midnight, as I am asleep in bed.
Yes, I have tested the card in the other PCIe slot. No change.
I have asked on the TP-Link, Intel and Gigabyte forums. They all point a finger at each other as to what the issue is.
I am no computer expert. I have owned and worked with computers since 1992. To me, with my limited knowledge, it would seem that something is changing in the computer on the 'following day'. Date change - BIOS - Windows 10? A process that changes each day and is effecting the WLAN or Bluetooth when the computer initialises. What that is I cannot say.
I have run Task Manager and Task Schedule, Powershell's Get-Process, sfc /scannow, etc. I see nothing that might be a red-flag. I cannot figure out where the issues lays.
In googling potential ideas, I have discovered that I am not the only one to experience this. There are others and the mainboards vary, so I believe my mainboard is not the issue. Could be, but I don't think so. Perhaps a combination of events.
As a process of elimination, could this be a Windows conflict issue? Might someone at MS have an idea to this?
Looking forward to responses of ideas and thoughts.
Cheers!
Continue reading...