Freeze problems with msi gtx 683r

Question

Hello ive bought a msi gtx 683r private and i seem to have been scammmed. From the start i had some problems with kernal driver update crashed my games after i rebooted the laptop it was gone.
Now my computer freezes after playing for 30mins - 1h and the sound also. I have changed the freeze pasta in the cpu fan dont know what its called in english but nvm. I even use laptop fan the thing you put under laptops that has fans too chill it from under. I usually have problems when the temps goes over 70. Ive runned that  program that makes your comp raise in temp so you can see how much it can go it went too 85 celsius in 20 min and nothing
I can play for 1-2h but after first freeze it happends much more often and i play wow with low settings. Ive turned in my comp too a computer store and they couldnet fins the problem. Please i need help ive prob forgot to write something just ask

Answer 1

Both the screen and sound freezes and i need to force reboot by holding the power button. Sometimes the screen also turn black  for 2 seconds and then this kernal driver update problem comes
 I dont know which one error to copy since there are many but here are some:
Display driver nvlddmkm stopped responding (WARNING)
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000117 (0xfffffa8009a8b010, 0xfffff8800f223e20, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\041914-21340-01.dmp. Report Id: 041914-21340-01. (error)
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. (Critical)
Session "Microsoft-Windows-Setup" stopped due to the following error: 0xC000000D (Error)
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be   (error)
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data  (error)