Jump to content

smallmac933

Member
  • Posts

    9
  • Joined

  • Last visited

Awards

This user doesn't have any awards

smallmac933's Achievements

  1. I've been getting this since I bought mine about two years ago. I think it's an issue with widevine DRM specifically although I've not found any fixes yet. Are you on HDMI or DVI to connect to your machine?
  2. So I got a new motherboard and I'm back up and running! I've stopped getting the weird screen turn-offs when I switch my lamp on too so I think dodgy VRMs was spot on! Cheers for your help everyone
  3. I never noticed any issues with voltages or temps across the VRM but I wasn't exactly looking out for it either so that's definitely possible! I don't think I'll ever be going back to gigabyte either!
  4. Unfortunately I'm the only one I know with an AMD chip. I've not tried anything around the PSU, it's a pretty good quality evga gold rated one although I've had chronic issues since day 1 with screens turning off between Netflix episodes and when I turn on the lamp next to my PC. Definitely agree with you about gigabyte though, don't think I'll be going with them again
  5. So I've just checked again without the ram and it's actually the CPU light that comes on when it's out!
  6. It's been a couple of days since I tried this and I'm not by my machine right now but I'm fairly certain when I took the memory out the light switches to the DRAM led which makes me think it's probably not a failure with the CPU or memory (plus both sticks going at once would be a pretty unlikely stroke of bad luck imo). Happy to be proved wrong on all accounts though
  7. Yeah, the CMOS was cleared via the jumpers and the bios was at the latest version I believe
  8. Hi everyone, After two years of working well my rig recently gave up the ghost, and I'd appreciate your help in figuring out why/what the issue is - I'm not entirely sure gigabyte support's response is all that accurate. Firstly, the relevant specs; - Gigabyte GA-AB350-Gaming 3 mobo - Ryzen 7 1700 - Corsair Vengence LPX CMK8GX4M2B3000C15 (4Gb x2) So during a day of normal use, mostly just Netflix, I attempted to load up Bluestacks. The emulator failed to open and came up with an error message recommending restarting the emulator, or the PC. Restarting Bluestacks did nothing so I rebooted the PC. Unfortunately it never posted, and the error indicator leds kept flickering between CPU and DRAM. I took the machine apart, cleaned it up a bit with some compressed air, and reseated the components to make sure it wasn't just a loose connection. None of this seemed to make any difference and the error lights remained the same. I tried swapping the ram into different channels, as well as trying each stick individually. This has no effect either. Finally I tried disconnecting the CPU power, and this was enough to get the error light to turn solid on the CPU. I spoke to Gigabyte support who told me the issue was incompatibility between the mobo and the memory. This is the crux of my first question - the support list contains other versions of ddr4 Corsair Vengence LPX at the same clock speed, so is it really possible it's an incompatibility issue just because it's got less storage? Especially given it worked flawlessly before this. When I questioned their response gigabyte recommended I RMA my mobo as well as my CPU, but obviously I'd like to rule out anything else first before I go through that hassle. Does anyone have any other suggestions on what the issue may be or possible fixes? Thanks!
  9. I joined LinusTechTips some time at the beginning of this year, I remember I was looking for mouse pad reviews and Linus was the only person I found to actually do them! I watched a few of the videos back when he had the terrible blond hair (sorry Linus but it was awful ) and eventually wound up just watching a ton of the videos, completely forgetting what I was originally looking for. I subbed pretty much instantly and watch every video that's put out . Loved the channel ever since, especially the WAN show! Congrats on the 1 mil subs, here's to another million!
×