BSOD while playing online game and doing multiple actions

Just zip the dump(s) and upload to the site as an attachment. We can tell right away whether more info is needed to be specific about the problem but at least the dump will indicate the problem area. The dump is produced by the OS at the time of the fault. It has no personal info--Just system info at the time of the fault.

The dump(s) will be located at C:\Windows\Minidump if your system is set to provide minidumps. (This is the default location. It may be different if you've changed the location.)

We work here as volunteers, so it is difficult for us to ask one of the other volunteers to provide the source code due to one user being afraid to use it. You are welcome to send a private message to the developer of the application and ask for the source code. I do not know what the response to such a private message will be, but I would be curious to find out...

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\MonsterMMORPG\030712-13587-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0321c000 PsLoadedModuleList = 0xfffff800`03461670
Debug session time: Wed Mar  7 08:08:05.978 2012 (UTC - 7:00)
System Uptime: 1 days 15:44:14.837
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800f325028, be000000, 800400}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware

Followup: MachineOwner
---------

1: 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: fffffa800f325028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`03d08b58 fffff800`03817a3b : 00000000`00000124 00000000`00000000 fffffa80`0f325028 00000000`be000000 : nt!KeBugCheckEx
fffff880`03d08b60 fffff800`033a9513 : 00000000`00000001 fffffa80`0f328a60 00000000`00000000 fffffa80`0f328ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`03d08ba0 fffff800`03817700 : 00000000`00000728 fffffa80`0f328a60 fffff880`03d08f30 fffff880`03d08f00 : nt!WheaReportHwError+0x263
fffff880`03d08c00 fffff800`03817052 : fffffa80`0f328a60 fffff880`03d08f30 fffffa80`0f328a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03d08d50 fffff800`03816f0d : 00000000`00000008 00000000`00000001 fffff880`03d08fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03d08d90 fffff800`0380ae88 : 00000000`00000000 fffff880`03d00180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03d08dc0 fffff800`0329752c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03d08df0 fffff800`03297393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03d08f30 fffff880`014c88f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03d28b00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x28f5


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

Start with Stop 0x124 - what it means and what to try and let us know if you have any questions. To supplement that link:

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.