Windows 10: BDOD while gaming

Today my pc crashed while gaming(PUBG), got red screen and then reboot after few seconds. After logging in with my Windows account it happened again, but blue screen acutally showed up. First time maybe it didn't because I was playing a game, dump file was created created both times - checked with BlueScreenView (0x00000124) error both times. Second time I was able to log in without BSOD and after 2-3 hours of gaming(PUBG) also no BSOD.

I have overclocked my i5 4670K to 4.4Ghz and had no crashed with this overclock for over 2 weeks, also tested stability with Intel Extreme Tuning utility (8+hrs) with no crash. Maybe I should lower overclock a bit, because this CPU won't do 4.5Ghz without going crazy with voltage <- not the best cpu.

I have no experience in reading .dmp files so I thought someone on this forum could help me to figure out what caused this BSOD. I removed ipconfig.txt and hosts.txt from the .zip file that dm_log_collector created.
JOOSEP-PC-11-Apr-18__03126_55.zip

:)

 

Windows 10 Pro machine reports BOOTMGR image is corrupt. The system cannot boot.

After many attempts to resolve BDOD of various STOP CODES, including clean reinstall of W-10, I purchased DriverUpdate from PUREINFOTECH and voila! Computer is operating like new. Four drivers were updated. Worth the $20.

 

frequent BSOD on Windows 10

There is some evidence in the minidump files that the vtrack.sys may be causing the BDODs.

The vtrack.sys is a component of Symantec System Recovery which may not be compatible with Windows 10.

You could uninstall Symantec System Recovery and see if the BSODs resolve.

 

Both errors are cache write errors reported by the CPU and so I would begin by removing all overclocks and see if they go away.

Code: 3: kd> !errrec ffffcc042fe1f028 =============================================================================== Common Platform Error Record @ ffffcc042fe1f028 ------------------------------------------------------------------------------- Record Id : 01d3d0f122e96d3d Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 4/10/2018 17:27:23 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffcc042fe1f0a8 Section @ ffffcc042fe1f180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 0 CPU Version : 0x00000000000306c3 Processor ID : 0x0000000000000006 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffcc042fe1f0f0 Section @ ffffcc042fe1f240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000006 CPU Id : c3 06 03 00 00 08 10 06 - bf fb da 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffcc042fe1f240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffcc042fe1f138 Section @ ffffcc042fe1f2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHEL0_WR_ERR (Proc 3 Bank 1) Status : 0xbf80000000000124 Address : 0x000000012454a680 Misc. : 0x0000000000000086[/quote]