Computer Keeps Freezing/Crashing/Not Responding

I'm not totally sure what you want. If you could give me more detailed instructions on what to look for in the event log that would be helpful. Am I looking in application, security, setup, system, or forwarded events? Am I looking for information, warnings, errors, critical events or audit success? I've never really been in the event viewer before and I'm not sure what to do.

Looking through event viewer this was the only critical event I noticed:

Event ID: 41. 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.

I'm sure I have shut my PC down before so I'm not really sure what this means.

If it matters, here is an error that happened around the time of a freeze/crash when I first opened event viwer

Event ID: 6008. Description: The previous system shutdown at 8:45:29 PM on ‎10/‎9/‎2017 was unexpected.

Here are some frequent warnings I've received:

Event ID: 129. Description: Reset to device, \Device\RaidPort1, was issued.

Event ID: 414. Description: Task Scheduler service found a misconfiguration in the NT TASK\OneDrive Standalone Update Task-S-1-5-21-1670295881-740973395-2531248363-1001 definition. Additional Data: Error Value: %localappdata%\Microsoft\OneDrive\OneDriveStandaloneUpdater.exe. or Task Scheduler service found a misconfiguration in the NT TASK\Overwolf Updater Task definition. Additional Data: Error Value: C:\Program Files (x86)\Overwolf\OverwolfUpdater.exe. or Task Scheduler service found a misconfiguration in the NT TASK\NVIDIA GeForce Experience SelfUpdate_{B2FE1952-0186-46C3-BAEC-A80AA35AC5B8} definition. Additional Data: Error Value: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe. or Task Scheduler service found a misconfiguration in the NT TASK\NvTmRep_{B2FE1952-0186-46C3-BAEC-A80AA35AC5B8} definition. Additional Data: Error Value: C:\Program Files (x86)\NVIDIA Corporation\Update Core\NvTmRep.exe. or Task Scheduler service found a misconfiguration in the NT TASK\NvTmRepOnLogon_{B2FE1952-0186-46C3-BAEC-A80AA35AC5B8} definition. Additional Data: Error Value: C:\Program Files (x86)\NVIDIA Corporation\Update Core\NvTmRep.exe. or Task Scheduler service found a misconfiguration in the NT TASK\NvTmRepOnLogon_{B2FE1952-0186-46C3-BAEC-A80AA35AC5B8} definition. Additional Data: Error Value: C:\Program Files (x86)\NVIDIA Corporation\Update Core\NvTmRep.exe. or Task Scheduler service found a misconfiguration in the NT TASK\NvTmMon_{B2FE1952-0186-46C3-BAEC-A80AA35AC5B8} definition. Additional Data: Error Value: C:\Program Files (x86)\NVIDIA Corporation\Update Core\NvTmMon.exe. (all of these "task misfigurations" seem to have happened right when I booted up my PC but a lot of other ones have happened more spread out so I'm not sure if it has anything to do with it or not)

Event ID: 508. Description: wuaueng.dll (676) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 0 (0x0000000000000000) for 16384 (0x00004000) bytes succeeded, but took an abnormally long time (29 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. or SettingSyncHost (5456) {19C67A40-6217-4A8D-BE22-C6EFD83652BB}: A request to write to the file "C:\Users\Tyler\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\edb.log" at offset 49152 (0x000000000000c000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (28 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. or wuaueng.dll (676) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 782336 (0x00000000000bf000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (29 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. or taskhostw (4284) WebCacheLocal: A request to write to the file "C:\Users\Tyler\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat" at offset 2588672 (0x0000000000278000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (28 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. or taskhostw (4284) WebCacheLocal: A request to write to the file "C:\Users\Tyler\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 192512 (0x000000000002f000) for 45056 (0x0000b000) bytes succeeded, but took an abnormally long time (26 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. or taskhostw (4284) WebCacheLocal: A request to write to the file "C:\Users\Tyler\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (26 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. (these all seem to have happened around the time that stuff has been freezing so maybe this has something to do with it.

Hopefully this helps.