Help! ntoskrnl.exe+4b09cc BSOD when trying to run Counter Strike:GO

Yup. Attach them to your first post

Are you sure? I can't find them.

Got them now

BSOD Analyze

BSOD Index | STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR | Usual causes: Hardware, Incompatibility, May be driver corruption

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Yusra\Downloads\oscotto\090712-42089-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02013000 PsLoadedModuleList = 0xfffff800`02257670
Debug session time: Fri Sep  7 23:39:37.309 2012 (UTC + 6:00)
System Uptime: 0 days 0:00:12.386
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007f8c038, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007f8c038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
 
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`01fb85b0 fffff800`022d4ca9 : fffffa80`07f8c010 fffffa80`06a16b50 00000000`00000010 00000000`00000202 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`01fb8ad0 fffff800`021b5547 : fffffa80`07f8c010 fffff800`0222f2d8 fffffa80`06a16b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`01fb8b00 fffff800`0211c945 : fffff800`02290ae0 00000000`00000001 fffffa80`0799b820 fffffa80`06a16b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`01fb8b40 fffff800`0209b841 : fffff880`01073e00 fffff800`0211c920 fffffa80`06a16b00 0009640f`00060f01 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`01fb8b70 fffff800`02328e6a : 0002d6ac`00000001 fffffa80`06a16b50 00000000`00000080 fffffa80`069e55f0 : nt!ExpWorkerThread+0x111
fffff880`01fb8c00 fffff800`02082ec6 : fffff880`01ed0180 fffffa80`06a16b50 fffff880`01edafc0 00019e28`600b700c : nt!PspSystemThreadStartup+0x5a
fffff880`01fb8c40 00000000`00000000 : fffff880`01fb9000 fffff880`01fb3000 fffff880`01fb8180 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner

Please answer:

1. What is the age of the hardware?
2. Is anything overclocked?

See this thread for the bugcheck you are getting Stop 0x124 - what it means and what to try

This seems to somehow relate to your CPU/Processor. I'd suggest you to take a test with IntelBurnTest CPU - Stress Test Using IntelBurnTest then a hardware stress with Prime95 Hardware - Stress Test With Prime95

You can use programs like Speccy to monitor the temps of your computer.
Speccy - System Information - Free Download

Take your time and post back once you've done these.

Looks good, thanks
Let me know the results of the tests

Looks good

Lets try Driver verifier to rule out buggy drivers Driver Verifier - Enable and Disable

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.