BSOD when using google Chrome and playing CS:GO

Please use the tool again and upload the zip file.
This for up to date information about your system, in case something has changed.

I see you have running driver verifier.
Please reset driver verifier.

The past 2 days there were only 0x124 WHEA (Windows Hardware Error Architecture).
That says you're hardware is likely damaged, but it could also be caused by overclocking and drivers.
Because driver verifier was enabled every time and in the stack I saw the following (marked in red)

Code:

STACK_TEXT:  ffffd000`4c8b86f8 fffff803`6f64694f : 00000000`00000124 00000000`00000000 ffffe000`254f4028 00000000`b2000000 : nt!KeBugCheckEx
ffffd000`4c8b8700 fffff803`6f8d50e0 : ffffe000`254f4028 ffffe000`2445d400 ffffe000`2445d400 ffffe000`2445d400 : hal!HalBugCheckSystem+0xcf
ffffd000`4c8b8740 fffff803`6f646e3c : 00000000`00000728 00000000`00000003 ffffd000`4c8b8b30 00000000`00000000 : nt!WheaReportHwError+0x258
ffffd000`4c8b87a0 fffff803`6f64719c : ffffe000`00000010 ffffe000`2445d400 ffffd000`4c8b8948 ffffe000`2445d400 : hal!HalpMcaReportError+0x50
ffffd000`4c8b88f0 fffff803`6f647088 : ffffe000`2445cd50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
ffffd000`4c8b8940 fffff803`6f6472c6 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`4c8b8980 fffff803`6f647450 : ffffe000`2445cd50 ffffd000`4c8b8bb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`4c8b89b0 fffff803`6f7d9b7b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`4c8b89e0 fffff803`6f7d9931 : 00000000`00000000 fffff803`6f7d98b0 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`4c8b8b20 fffff801`a6af2778 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd000`4c8db858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18 (driver from your CPU)

The cause is most likely the driver from your CPU.

Taking a look at the date from the driver doesn't say much, but check Intel for driver updates

Code:

3: kd> lmvm intelppmstart             end                 module name
fffff801`a6af0000 fffff801`a6b19000   intelppm   (pdb symbols)          c:\windows\symbol_cache\intelppm.pdb\89FABBD09556447FB6B157B5A3A81CD91\intelppm.pdb
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: c:\windows\symbol_cache\intelppm.sys\559F383B29000\intelppm.sys
    Image path: intelppm.sys
    Image name: intelppm.sys
    Timestamp:        Fri Jul 10 05:12:59 2015 (559F383B)
    CheckSum:         0001FAC6
    ImageSize:        00029000
    File version:     10.0.10240.16384
    Product version:  10.0.10240.16384
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     intelppm.sys
    OriginalFilename: intelppm.sys
    ProductVersion:   10.0.10240.16384
    FileVersion:      10.0.10240.16384 (th1.150709-1700)
    FileDescription:  Processor Device Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Benny said:

Ok. From the tests you asked me to do, only CPU stress test is left. I will do that tonight and let you know. CPU might be case since I bought second hand CPU without checking it. Also, I will reset driver verifier today.

Please first try to update the drivers and see if you still getting BSOD's before doing the stress test :)

Nobody here will recommend you any software that updates drivers for you, this because these software can't be trusted.
You should manually check the site of Intel for drivers.

Windows Device Manager isn't the place to update your drivers, in almost all cases it will say your driver is up to date.
Even when a driver is from 2006 and there are updates available from this year windows device manager will say the driver is up to date. (This is the case with my SSD )