Random system hangs, restarts, and screen glitches.

Tried each of the RAM modules individually. One of them brought a system hang almost as soon as I logged in but the other one that I have in at the moment hasn't produced any problems yet. However previously my PC has gone a couple of hours without crashing so only time will tell.
Also I have event viewer open but not sure what i'm looking for.
Is it likely that a faulty RAM module is causing these problems?

Alright I found a critical kernel power error that matches the time when I tested the first ram by itself:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2/17/2016 5:05:40 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: The-Death-Star
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-02-17T17:05:40.501360800Z" />
<EventRecordID>1231</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>The-Death-Star</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

Alright. Thanks for the help man, I'll mark that as the solution for now i'll post on here if the same problem happens. But I guess that would just mean that both modules are faulty?
It's like that module is one of the rebels or something, trying to take down my death star!

Hmm, looks like we spoke too soon here it's just frozen again like it did before. Are both of the modules faulty or is something else at fault?
I checked the event log and found two errors at the time frame. They look pretty unrelated to me but then again I don't know much about it.

Log Name: System
Source: Microsoft-Windows-Eventlog
Date: 2/17/2016 8:54:41 PM
Event ID: 30
Task Category: Service startup
Level: Error
Keywords: Service availability
User: LOCAL SERVICE
Computer: The-Death-Star
Description:
The event logging service encountered an error (5) while enabling publisher {0bf2fb94-7b60-4b4d-9766-e82f658df540} to channel Microsoft-Windows-Kernel-ShimEngine/Operational. This does not affect channel operation, but does affect the ability of the publisher to raise events to the channel. One common reason for this error is that the Provider is using ETW Provider Security and has not granted enable permissions to the Event Log service identity.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Eventlog" Guid="{FC65DDD8-D6EF-4962-83D5-6E5CFE9CE148}" />
<EventID>30</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000020000</Keywords>
<TimeCreated SystemTime="2016-02-17T20:54:41.876617800Z" />
<EventRecordID>1472</EventRecordID>
<Correlation />
<Execution ProcessID="1076" ThreadID="1164" />
<Channel>System</Channel>
<Computer>The-Death-Star</Computer>
<Security UserID="S-1-5-19" />
</System>
<UserData>
<InitChannelPublisherEnableFailure xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
<Error Code="5">
</Error>
<ChannelPath>Microsoft-Windows-Kernel-ShimEngine/Operational</ChannelPath>
<PublisherGuid>{0BF2FB94-7B60-4B4D-9766-E82F658DF540}</PublisherGuid>
</InitChannelPublisherEnableFailure>
</UserData>
</Event>




Log Name: System
Source: NetBT
Date: 2/17/2016 8:54:46 PM
Event ID: 4321
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: The-Death-Star
Description:
The name "WORKGROUP :1d" could not be registered on the interface with IP address 192.168.0.113. The computer with the IP address 192.168.0.107 did not allow the name to be claimed by this computer.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="NetBT" />
<EventID Qualifiers="49152">4321</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-02-17T20:54:46.186021500Z" />
<EventRecordID>1473</EventRecordID>
<Channel>System</Channel>
<Computer>The-Death-Star</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>WORKGROUP :1d</Data>
<Data>192.168.0.113</Data>
<Data>192.168.0.107</Data>
<Binary>000000000400320000000000E11000C001010000010000C000000000000000000000000000000000</Binary>
</EventData>
</Event>

No. Could it be that the power cables are connected to the motherboard wrong? Or even a fault with the RAM slots on the motherboard?

Well, It's pretty much my first build, I helped a little on my brothers, so it's possible that I've messed up somewhere. I'll double check the connections and see if I can borrow a RAM module from my brother's PC.
I ran the windows memory diagnostic and that came up all clear. It did take a long time before that last hang and there hasn't been one since. They were a lot more frequent before I removed the RAM module I've been keeping an eye the memory usage while I've been watching Netflix and it's stayed stable at 1.8GB