PC Crashing when opening games via Steam

Alright guys, a mate of mine has been consistently crashing when trying to launch games in steam. However, he is able to play Battlefield 3 and so on without any problems at all. This seams to be purely Steam related. He has spoken to the computer providers and they told him to try using some software which basiclly sets the system logs out in a nicer fashion. The errors he has been getting is..

On Tue 31/07/2012 13:29:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073112-32058-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD7180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 01/08/2012 14:08:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-35880-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B09CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800DC708F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 31/07/2012 13:29:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD7180, 0x3)
Error: CLO

Anyone got any ideas what this might be as the computer provider seams baffled. Sorry for the long winded error list, just wanted to make the error as clear as possible.

As a side note, the computer is about a week old, has never been able to run games via steam and is running Windows 7 Home Edition.

That is the EXTRK.exe virus, cause the system to state a clause in the system which causes it to skip a file source needed to open external applications.

Best thing to do is to boot into safe mode with networking, download avas anti virus free trail, run the system and driver storage scan folder, it will locate the issue and re download and delete the missing files, also chest the virus.

If this does not work, then I would do a system reinstall.

also in safemode with networking, download and run MBAM and superantispyware, run those scans too, if indeed it is a virus/malware problem.

better yet, just format the computer? surely you have the discs and cant have lost them within a week!

Nice one, hes going to give that a go :) Will report back :>

None of the above worked, PC was squeaky clean. Any other possibilities bar formatting?

ye ive actually has this problem myself so i can relate to the fustration, what you need to do is find all the reboot disks cables manuals etc, walk over to your nearest window, extend your arms fully with all of the above in a firm grasp, release the tension in your hands, relax your forearms and listen for the crashing sounds as it hits the floor.

Please note for this to work window must be at least 10 foot high.

thanks

0x124 is usually a hardware error. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 6 passes. Are you overclocking any hardware? If so, restore defaults. Hardware is not the only cause of 0x124 BSODs, however, just the most common. I have seen SPTD.sys cause 0x124 BSODs not that infrequently. I see the driver spfg.sys loaded in RAM, and has the same timestamp of the most commonly used version of SPTD. I think the best thing you can do to fix it is Get_Fucking_Good_You_Shit_Little_Spastic_Weird_Nerd.

spend £1500 on a pc like me, ive got £5000 in my back pocket right now, sort your money out twK