Jump to content

Tombfoot

Member
  • Posts

    52
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Profile Information

  • Gender
    Male
  • Location
    England, UK

System

  • CPU
    Ryzen 7 1800X
  • Motherboard
    ASRock X370 Professional Gaming
  • RAM
    G.Skill TridentZ RGB 16GB (2 x 8GB) 2933MHz
  • GPU
    Sapphire Radeon 5700 XT Pulse
  • Case
    Fractal Design Define R5
  • PSU
    EVGA Supernova 1000 G+
  • Display(s)
    ViewSonic
  • Keyboard
    Corsair K55
  • Mouse
    Corsair Harpoon Wireless
  • Operating System
    Windows 10
  1. Yeah I assumed as much. That's a real shame. The auto switching still seems to be working for me at the minute even though I have uninstalled the UWP app. I guess it must work on a driver level now? I might end up getting a soundcard at this rate.
  2. Hey dudes, I have (as I am sure most of us do) a Realtek sound chip on my motherboard. In my case its an ALC1220 chip. It's a decent chip and I have no real problems with it, but the last driver update killed the old audio console software UI which I was quite fond of and has replaced it with a Windows store UWP app which, in my opinion, is a crime against humanity and several steps back. I still have the drivers installed of course, but I no longer use that app. My question is this: Is there any kind of third party solution to the audio console? An app that launches with windows and provides options and controls for my audio setup in a way that is more robust than the stock windows app? I am doubtful but if anyone knows of such a thing that would be awesome. Thanks!
  3. Does anyone have any suggestions at all? I'm still at a loss. I currently have the adaptor disabled in device manager. The second I enable it the adaptor will keep making the "disconnected hardware" sound every 2 seconds. Willing to try any ideas!
  4. Hey dudes, So I've been having more problems with my 5700 XT. I couldn't launch Monster Hunter and trying to launch it would lock my PC (similar issue I previously had with Ghost Recon Wildlands). I managed to get around this by enabling DX12 in the config file for Monhun and now it seems to launch completely fine. Just one small thing... During one of those hard locks I was using my bluetooth controller and now when I sign in to Windows the Bluetooth adaptor keeps resetting like its found new hardware every 2 seconds. It's maddening. The only way I can stop the constant beeply booping is to disable the bluetooth adaptor in device manager. I've tried reinstalling the drivers thinking it might have just been a corrupted driver but that has not helped. I tried disbaling the Bluetooth in the BIOS, restarting, then re-enabling it which seemed to work for about 15 minutes and then it went haywire again. Does anyone have any ideas/solutions? The bluetooth is part of my ASRock X370 Professional Gaming, it's an Intel Wireless-AC 3168 according to AIDA. Any suggestions would be awewsome. Cheers! ?
  5. Major Update: The issue has seemingly vanished. I can now successfully launch and play Ghost Recon: Wildlands. The only thing that has changed is there was a Uplay update on the 18th of December. This seems to have solved the issue entirely as far as I can tell. What a weird thing.
  6. The thread in question I found that info from -- the guy who had the same issue returned his CPU thinking it was faulty only to have the same problem upon arrival of a brand new replacement processor.
  7. Wait. I just did a google search for Ryzen and your error code and found the following- Guy with the same issue reinstalled Windows using the latest build of Windows 10. If you use an older version of Win10 apparently Ryzen does not play nice with it. Make sure you use an installation media with a very recent version of windows and try doing a fresh install of that. Also make sure to install the AMD chipset drivers.
  8. Could you inspect the Ryzen chip for me and make 100% sure that all the pins on the chip are good and not bent? I would have suspected the memory but it seems you have covered yourself by using your old memory. If after inspecting your CPU all pins are good then my suspicion is faulty CPU or motherboard.
  9. Yeah GPU is definitely dead. Double check the SATA data and power cables on your vertex on both ends and make sure they are snug and secure. It's possible the MBR and MFT rebuild did work but it just didn't take on the first restart? Which is strange but not outside the realm of possibility. Glad it seems to be working for you anyway! Let us know when you get a new GPU and everything is hunky dory. ?
  10. Oh you mean the brass standoffs? Yes they are incredibly important, they stop the motherboard shorting to the case and prevent the motherboard from flexing too much in areas where it might be otherwise prone to a bit of flex.
  11. Yeah give that a try or if you want, you can use a Windows recovery drive/disk to boot into a command prompt and rebuild the MFT and boot partition and see if that does you any good and then if not just go ahead and do a fresh install.
  12. The BIOS recognises the drive? If the drive shows up in the BIOS then it should be okay. Try a fresh install of windows on it. If the drive is very old though you should be careful, make sure all your important data is backed up and if you hear any strange noises or notice the drive behaving strangely it is probably time to get a new drive.
  13. If you can't decipher the beep code record a video of the start up on your phone including the beeps and then post that video. ?
  14. I agree. That kind of artifacting is nearly 100% GPU. Also if you smell burning electronics have you checked the capacitors? Make sure none of the capacitors have ballooned tops or look otherwise comrpomised. They should be perfectly cylindrical and not have any bulges. Is there any charring around the gold plated connectors on your GPU? It definitely sounds like something has died related to the GPU.
  15. What do you mean by gold rinses? I'm not 100% sure what you mean. Could you post a picture or find one to show me?
×