Kopesetic

@Rien102 My guess is that it could be your ram.
 
I remember a couple times in the past that I've had this problem, with replacing the ram (and on at least one occasion replacing the power supply) solving my problem.
 
Considering how you mentioned your problems escalating when you enabled the XMP profile, that does make it seem more like it is the ram. One thing you can try doing is switching the ram to different slots and/or trying just one stick at a time.
 
Also not sure if just me, but that video you posted doesn't work, with only the audio playing.

Can you try one stick of RAM at a time? Try both seperately.

Hey!
 
So a while ago I created a floatplane RSS feed using bash. Now, I recreated it in GOLANG. Before it wasn't reliable. It should be good now though now. I changed my hosting setup and all that sort of jazz.
 
Anyways, each feed now has image tag set for each field along with the name "Floatplane - " Channel name. Each post has a thumbnail for the video. It also has the channel desciption in the feed information along with the description of the video in each post. Each channel (linustechtips, macaddress etc.) have their own feed, this included the fpexclusives. I plan to uplaod the code soon, i will post back here.
 
You can find a link to all of the ones generated here: https://godfrey.online/rss/rss.html
 
Currently adding channels is manual as the JSON feed doesn't expose that.
 
Any problems hit me up!
 
Thanks,
Harley Godfrey
 
FYI, some feeds won't show the channel icon and or the thumbnail because rss image stuff is a mess. I currently have a problem in NewsFlash but it is being fixed and should be good soon.

Nice job!  I was able to add this to my start.me page.

You could always run a VM if that's sufficient enough for your university project.

The OEM license is embedded into your BIOS.  Try this:
 
From an admin Powershell prompt
wmic path SoftwareLicensingService get OA3xOriginalProductKey
 
That should show you the key.

The OEM license is embedded into your BIOS.  Try this:
 
From an admin Powershell prompt
wmic path SoftwareLicensingService get OA3xOriginalProductKey
 
That should show you the key.

The OEM license is embedded into your BIOS.  Try this:
 
From an admin Powershell prompt
wmic path SoftwareLicensingService get OA3xOriginalProductKey
 
That should show you the key.

The way this makes core "under the hood" changes to Windows, I would be surprised if it can be uninstalled.  Unfortunately, this will most likely require a re-install of Windows to correct.

Highly unlikely. That RGB would have to be controlled somehow and it would have to be connected in some way to your new memory. I see absolutely no reason for a memory manufacturer to include the appropriate hardware for RGB on ram that isn't going to be RGB.

I found them and opened it
 
 
yeah I opened it
 
 
 

 
and yes I knew it had no gpu I am planning on getting one
 

Are you using the XMP profile on your RAM?  If so, try disabling it and run your RAM at 2133 and try again.