EDIT: I do not overclock, and seeing as it is on start up of these games I don't believe it is a heat issue.
Your CPU information:
Code:
AMD FX(tm)-8120 Eight-Core Processor, 3100 Mhz, 4 Core(s), 8 Logical Processor(s)
But it actually says:
Code:
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3332
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 21 Model 1 Stepping 2
ProcessorNameString = REG_SZ AMD FX(tm)-8120 Eight-Core Processor
VendorIdentifier = REG_SZ AuthenticAMD
So apparently it is appearing that the system is overclocked. It is running on more megahertz than stock.
As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.
You may not believe that it is a heat related issue, but as the computer is years old, we need to check the heat, as the bugcheck codes are mostly stop 0x124 and sometimes stop 0x101. Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
NETGEAR WG111v3 Wireless-G USB Adapter driver is failing here.
Code:
fffff880`09f41b08 fffff880`05d8349eUnable to load image \SystemRoot\system32\DRIVERS\wg111v3.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for wg111v3.sys
*** ERROR: Module load completed but symbols could not be loaded for wg111v3.sys
wg111v3+0xc49e
And the driver is too old.
Code:
fffff880`05d77000 fffff880`05def000 wg111v3 T (no symbols)
Loaded symbol image file: wg111v3.sys
Image path: \SystemRoot\system32\DRIVERS\wg111v3.sys
Image name: wg111v3.sys
Timestamp: Wed Nov 18 15:17:46 2009 (4B03C2C2)
CheckSum: 0007A170
ImageSize: 00078000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
For an online game, it is enough reason for an instant BSOD.
Update the driver from WG111v3 . If there is no feasible driver update available, better you opt to use another adapter with an up-to-date driver.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Stress test the CPU.
Hardware - Stress Test With Prime95
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Let us know the results.
________________________________________________________________________________________
Code:
BugCheck 124, {0, fffffa80071da8f8, 0, 0}
Probably caused by : AuthenticAMD
Followup: MachineOwner
--------------------------------------------------------------
BugCheck 101, {19, 0, fffff88002fd7180, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------