Windows 10: When hard wired, PC will not find my wifi unless I reboot my PC.

I have a Dell Latitude 5340. I have a Dell WD15 monitor dock plugged into my USB-C for monitors, internet ETC. When I turn my laptop on in the monring, it connects to the internet via, the hardwired dock AND I can see all my Wifi Signals. A few hours later, when I need to undock my laptop and take it with me, it no longer sees any of my wifi signals AND when I click the Wifi button to turn the wifi off and on, it does nothing. If I reboot my PC, I can see the wifi signals again. If I leave it undocked, I can see my wifi signals all day. Once I dock it, a few hours later, I can not see my wifi

:)

 

Wired PC shows in list of WiFi access points

I'm on the fall creators update on a laptop. The laptop is connected to my router via WiFi. I also have one wired PC on the network. I just noticed that the wired PC shows up at the top of the list of networks (complete with a "connect" button) when I
single left click on the WiFi icon in the system tray to show a list of WiFi access points. This is new behavior (with the FCU?) and I can't for the life of me find any information anywhere regarding why the wired PC shows up. If I click "connect", the process
simply stalls until I click "cancel". Is this supposed to be some way to enable connection sharing? Or an RDP connection?

Anyone?

Paul

 

Wired PC shows in list of WiFi access points

I don't think that explains this particular issue. The wired PC that shows up in the laptop's list of WiFi APs is connected to the router via ethernet and does not have a WiFi card. So it can't (or at least shouldn't) advertise an available connection.

The icon next to the wired PC name is also new and unfamiliar.... looks like 3/4 of a simple celtic knot with a "carat" where the fourth loop would be.

I have tried searching for a variety of keywords like "new icon in WiFi list" and "wired PC in list of WiFi connections" and come up virtually empty. I'm sure it is something added in the FCU but I'll be danged if I can figure out what it actually is.

Paul

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?