Other findings from the prior event log:
Code:
Event[277]: Log Name: System Source: Microsoft-Windows-Eventlog Date: 2017-05-24T16:37:02.970 Event ID: 22 Task: Service startup Level: Error Opcode: Info Keyword: Service availability User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Tomer-PC Description: The event logging service encountered an error while initializing publishing resources for channel AirSpaceChannel. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well.
Code:
Event[278]: Log Name: System Source: Microsoft-Windows-Eventlog Date: 2017-05-24T16:37:02.995 Event ID: 22 Task: Service startup Level: Error Opcode: Info Keyword: Service availability User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Tomer-PC Description: The event logging service encountered an error while initializing publishing resources for channel DebugChannel. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well.
Code:
Event[975]: Log Name: System Source: Application Popup Date: 2017-05-31T20:01:55.251 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Tomer-PC Description: Application popup: TslGame.exe - Application Error : The instruction at 0x00007FF97BB90E67 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.Click on OK to terminate the program
Code:
Crash dump initialization failed!
Code:
Startup Repair failed.
Code:
Event[980]: Log Name: System
Source: Display
Date: 2017-05-31T20:34:42.921
Event ID: 4101
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Tomer-PC
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Code:
Event[1928]: Log Name: System
Source: Display
Date: 2017-06-13T01:09:12.930
Event ID: 4101
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Tomer-PC
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Code:
{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.
Please make sure that there is no over clocking.
Sometimes there are problems in the bios that produce bsod.
The bios in your computer: BIOS Version/Date American Megatrends Inc. F4e, 6/28/2013
Please check to see if this is the most up to date version.
To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios.
So please make sure your files are backed up. Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free: Macrium Software | Macrium Reflect Free
And please create a restore point.
Please post an updated zip file so we can troubleshoot the logs: BSOD - Posting Instructions - Windows 10 Forums