BSOD while rendering in Sony Vegas and playing games

You are running an ASUS Product ID (PID) on a Gigabyte board.
This makes your installation counterfeit.
Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.

Code:

Konfigurace operaŸn¡ho syst‚mu:      Samostatn* pracovn¡ stanice
Typ sestaven¡ operaŸn¡ho syst‚mu:    Multiprocessor Free
Registrovanì vlastn¡k:               uzivatel
Registrovan* spoleŸnost:             
ID produktu:                         00371-OEM-8992671-00407 <-- ASUS PID on Gigabyte board
Datum p…vodn¡ instalace:             22.3.2016, 10:36:45
¬as spuçtØn¡ syst‚mu:                7.4.2016, 18:39:13
Vìrobce syst‚mu:                     Gigabyte Technology Co., Ltd.

I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

It seems everytime a minidump couldn't be created (thanks Google Translate for translating).
Unfortunately there is currently not much to suggest since there is nothing to analyze.

Code:

Event[3854]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2016-04-09T12:06:59.000
  Event ID: 1005
  Task: N/A
  Level: Chyba
  Opcode: N/A
  Keyword: Klasické nastavení
  User: N/A
  User Name: N/A
  Computer: HUNTER-PC
  Description: 
Ze souboru úplného výpisu nelze vytvoøit soubor s minimálním výpisem.

Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial

Please remove Gigabyte software temporary to ensure it won't cause problems.
This driver, Driver Reference Table - AppleCharger.sys part of Gigabyte software, may cause BSODs.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Few times right after reboot I got this BSOD, if I didn't get that one everything went fine.


Should I keep running Driver verefier for those 48 hours or till the PC crash ?

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

You should do what you normally would do, but do not do anything that requires too much, that may cause performance problems with driver verifier.