RickL

Hi guys, I picked up my laptop tonight for the first time in a couple of weeks as I knew this worked perfectly fine with the network share, it has confirmed that the "server" PC or the router is the issue, not the desktop PC. Saves another install job I guess. I'll let you all know if the network PC is resolved with a fresh copy of windows which im planning to do at the weekend.

Hi All, A fresh copy of windows did indeed work to resolve all my lock up issues. Thank you all for your suggestions

So, hit reset network on both PC's, rebooted. Nothing. No change. Reset, changed straight to private networks, nothing. All network discovery is turned on and auto set-up. Tried to connect to the computer on "network", nope, tried to map network drive using the correct address, nope.

When the connection to the router was first made, it did register as an unidentified network, then auto set to public. Then I had to manually change it to private. So currently, its on private. Isnt there a way to completely "forget" a network, unplug it and let it start again from a virgin config?

Yup its pinging the static IP of the network drive's pc correctly and returning all 4 pings as received.

I have tried connecting to the PC in both ways, Hostname and the IP (The IP address is static in the router). SMB? Im only a little familiar with the term but I dont know what part that plays in any of this. Nope, keeps on coming up with "Windows cannot access \\Rick-pc\g" (Note that I recreated a share and named it "g" out of frustration in trying to get it to work.

Tried that one bud, sorry I forgot to mention. That is how I would normally do it as I need to use different log-in credentials but its not been an issue. Upon trying to connect, it just spools or it says; "The mapped network drive could not be created because the following error has occurred: The specified network name is no longer available".

Hi! So I have a Windows 10 PC in the cupboard that has always acted as my NAS, Plex Media Server, FTP, NVR, Teamspeak Server and other things. I have set up one of the drives with a Windows Share. This has been working perfectly for the last 3 years. I built a new PC recently for gaming etc, it connected straight to the network share without any issues as soon as I enabled file sharing, the network PC with the share came straight up. I then needed to reinstall windows to my new PC as I had a few software issues and since then it wont see the network share, even though I carried out exactly the same as when I first set it up. Also at the same time I'm not sure if my router took a sh!t or if it was the new install of the PC but there were some issues connecting to the network with it right after the fresh install. My router HAD been giving me issues around 6 months ago but otherwise now seems fine. So, couldn't see the network PC under "Network", but I can see it under "Media Devices" with the "Plex Media Server". I went through on both PC's to ensure that the drive was being shared correctly and that the advanced sharing settings appeared correct with the file sharing turned on etc. So after more googling I entered the windows services and ensured that the below services were set to auto or auto with delay startup; SSDP Discovery uPNP Device Host Function Discovery Provider Host Function Discovery Resource Publication Success! I then could see the network PC under the network tab "computers" however when I when trying to connect (Note that I can only see the PC but not the actual shared directory yet) I was getting the old "0x80070035" error, so more googling... entered windows services, ensured that the TCP/IP NetBIOS Helper was set to start up automatically. Went to the network adapter settings, IPv4 Advanced Properties, entered WINS, ensured that "Enable NetBIOS over TCP/IP" was checked, all correct. Gone in to Regedit and deleted out MSLicensing HardwareID and Store files. But.. to no avail. I rebooted both PC's and now I cant see the network PC at all. Do I need to re-install windows on BOTH PC's? Can anybody shed any light on my situation?

So, I went back to basics tonight and re-installed a fresh copy of windows, so far all appears well. Currently im thinking it may have been all of the software that I was installing along the way that interacts with the motherboard etc. Ryzen Master, MSI Afterburner, AMD Radeon software (required for drivers), Crystal disk, all the bench-marking and monitoring software. Fingers crossed.

F**king thing. Locked up randomly tonight, so entered Ryzen Master program and forced everything to default, I believe it was anyways. The discord locked up. But now it seems fine? What on earth is going on.

Soooo XMP is off again now, didnt resolve anything. Currently manually clocked to 3000mhz now, maybe that could resolve it?

I thought that, overlocking or the MoBo playing around with the CPU as it had happened to a friend but.... nope, this is stock. Just re-booted and XMP was DISABLED... However, I noticed that it was running my RAM at 2100mhz or so, so flicked XMP to profile 1 auto and its auto set it to 3000mhz, the correct speed for the RAM. No, I have not yet tested it. I'll do it now but already just after a reboot and Discord not crashing.. YET, could it have been the RAM settings? I'll report back shortly.

It happened with world of warships once, now its started doing it with Chrome.

Hi wonderful people, I have a problem with my new rig, the build is listed below. Since I built it a few weeks ago it has been a little temperamental, I put it down to airflow and overheating so I installed a Corsair closed loop watercooler for the CPU and an additional fan to get some airflow over the chipset and NVME drive. The CPU according to Ryzen Master now sits at 50-60c, but "Core Temp" seems to think its sat at 60-70c. The chipset, NVMe etc sit at 45-55c. So my issues are random crashes of progams, Discord client LOVES to lock up and crash on me, so I changed to using the web based version in Chrome, then that started to lock up. For what is a brand new build with genuine software etc, I cannot understand why I am having these issues. I have not updated the BIOS on the motherboard as it states it has a May '19 driver. Also, I run / ran my keyboard, headset and mouse from a small USB dock as to keep all my cables neat but the head set after 2 weeks, keeps on disconnecting. When I start the PC there is a horrible noise that comes from the headphones so I am having to unplug and re-plug it in. Finally tonight I have taken the headset out of the dock and plugged it in directly. So far after a few hours, no issue of D/C'ing. Also, I can game on it just fine, it doesnt block up. Its behaving very strange... So what do you guys think? Any advice? Windows 10 64-Bit Home Ryzen 5 3600 with Corsair H60 16GB Vengance 3000mhz RAM Crucial CT500P1SSD8 P1 500 GB Aorus B450 I AORUS PRO WIFI Corsair SF600 Platinum Fully Modular Power Supply XFX Radeon RX 5700 XT

Oh wow guys! Thank you so much! Looking at all of these builds (which are extremely similar to each other) has returned my confidence to make a build. Some of these suggested cases are VERY nice indeed! I'll let you all know what I end up doing but it's certainly looking like a Ryzen 3600 paired with the 5700 XT at the moment.