Jump to content

Ozz

Member
 View Profile  See their activity

  • Posts

    33

  • Joined

  • Last visited

Reputation Activity

  1. Informative
    THR2000
    Ozz got a reaction from THR2000 in They Sent me a Broken PC AGAIN - $1500 PC Secret Shopper 3 Part 2   
    Looks like Starforge already took down their tweet. Pretty sus.
     
    i saved the response images though, i'll just post them here if anyone wants them! 


  2. Informative
    Needfuldoer
    Ozz got a reaction from Needfuldoer in They Sent me a Broken PC AGAIN - $1500 PC Secret Shopper 3 Part 2   
    Looks like Starforge already took down their tweet. Pretty sus.
     
    i saved the response images though, i'll just post them here if anyone wants them! 


  3. Like
    Ozz
    Ozz reacted to Eigenvektor in All AMD System unstable after enabling Resizable BAR Support.   
    SAM is AMD's marketing name for resizable bar, so that should be fine. I would try a BIOS update, as was said, you should be good to do so.
     
    ASRock's warning message is worded weirdly. They're basically saying: Please don't update to this BIOS version unless you have at least one of these CPUs. Once you have updated you are good to switch to a Ryzen 5000 G-Series processor.
     
    Since you already have one of these versions and you are already on a 5000 G-Series CPU there's nothing preventing you from updating further.
    You need both a supported CPU a supported GPU. As far as CPUs are concerned Ryzen 3xxx and 5xxx should be supported. However the iGPU of the 5700G is Vega architecture, which is older than RX 5xxx, so that could be the issue. I'd try again after a BIOS update. Might fix it.
     
    5700x or 5700g and are you using its iGPU or do you have a discrete GPU?
  4. Agree
    Eigenvektor
    Ozz got a reaction from Eigenvektor in All AMD System unstable after enabling Resizable BAR Support.   
    I thought they have since included the 5000 series as well... 
  5. Like
    Ozz
    Ozz reacted to David E in chrome managed by organization   
    Are you running some kind of web protection service, for example Avast antivirus built in web protection? 
    This certainly sounds like something Chrome would consider management. If there aren't any policies under chrome://policy/ I wouldn't worry about it. 

    Removing the registry entries won't help if a web protection service is applying it again.
    I think google should address this since this isn't a message that is relevant nor applicable for personal users. 
    However, it is by design and nothing to worry about.

    See this thread for further information.
×