BSOD Playing WoW and Diablo 3

[Duraphobics]

Hi,

I've had 3 bluescreens in the last 2 days.
Two while playing WoW and one playing Diablo 3 Beta.

I'm having some trouble with the permon /report, when i try to run it i get and an error saying 'The system cannot find the path specified' I've uploaded a screenshot of this, so if anyone can help with that as I couldn't work out how to get it to work.
The most recent BSOD (Today) it crashed as it was creating the dump, so I don't think that is included, but there were two yesterday that worked, I think.
I've included the system dumps, any help is very much appreciated.

- 64 bit
- It is the original OS
- Full Retail Version

- The mobo,ram and cpu about 8 months, everything else 1.5-2 years.
- The OS install is about 6 months old.

Thanks for any help, and if you need more information just ask, I think that is everything.

Thanks.

 

[writhziden]

Security Software (this is just to check that it is installed and working properly; nothing needs to be done with this information at this time):

avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	464	8	200	1380	22/04/2012 13:18	12.0.0.1786	507.34 KB (519,520 bytes)	15/08/2011 06:21
avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	3928	8	200	1380	22/04/2012 13:20	12.0.0.1786	507.34 KB (519,520 bytes)	15/08/2011 06:21
avgemca.exe	c:\program files (x86)\avg\avg2012\avgemca.exe	2564	8	200	1380	22/04/2012 13:19	12.0.0.1854	1.52 MB (1,593,696 bytes)	21/09/2011 19:53
avgfws.exe	c:\program files (x86)\avg\avg2012\avgfws.exe	1644	8	200	1380	22/04/2012 13:19	12.0.0.1881	2.28 MB (2,391,832 bytes)	19/08/2011 06:24
avgidsagent.exe	c:\program files (x86)\avg\avg2012\avgidsagent.exe	3224	8	200	1380	22/04/2012 13:20	12.0.0.1855	4.23 MB (4,433,248 bytes)	12/10/2011 07:25
avgnsa.exe	c:\program files (x86)\avg\avg2012\avgnsa.exe	2128	8	200	1380	22/04/2012 13:19	12.0.0.1883	1.90 MB (1,987,424 bytes)	13/09/2011 10:33
avgtray.exe	c:\program files (x86)\avg\avg2012\avgtray.exe	3048	8	200	1380	22/04/2012 13:19	12.0.0.1912	2.30 MB (2,416,480 bytes)	24/01/2012 17:24
avgwdsvc.exe	c:\program files (x86)\avg\avg2012\avgwdsvc.exe	1872	8	200	1380	22/04/2012 13:19	12.0.0.1773	188.26 KB (192,776 bytes)	02/08/2011 06:09

Loading Dump File [D:\Kingston\BSODDmpFiles\Duraphobics\Windows_NT6_BSOD_jcgriff2\042112-50154-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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03049000 PsLoadedModuleList = 0xfffff800`0328d650
Debug session time: Fri Apr 20 17:26:16.557 2012 (UTC - 6:00)
System Uptime: 0 days 3:19:21.338
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800a8fb028, be200000, 5110a}

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
---------

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: fffffa800a8fb028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, 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

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0336da58 fffff800`03012a3b : 00000000`00000124 00000000`00000000 fffffa80`0a8fb028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0336da60 fffff800`031d5b33 : 00000000`00000001 fffffa80`0a9d4010 00000000`00000000 fffffa80`0a9d4060 : hal!HalBugCheckSystem+0x1e3
fffff880`0336daa0 fffff800`03012700 : 00000000`00000728 fffffa80`0a9d4010 fffff880`0336de30 fffff880`0336de00 : nt!WheaReportHwError+0x263
fffff880`0336db00 fffff800`03012052 : fffffa80`0a9d4010 fffff880`0336de30 fffffa80`0a9d4010 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0336dc50 fffff800`03011f0d : 00000000`00000004 00000000`00000001 fffff880`0336deb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0336dc90 fffff800`03005e88 : 00000000`00000000 fffff880`03365180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0336dcc0 fffff800`030c456c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0336dcf0 fffff800`030c43d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0336de30 fffff880`073c69c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0338db58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

The above crash information can be found by reading through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html


To supplement the information in 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. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. 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 http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html 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.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• 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).
  
  For Part 3: If You Have Errors: 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.

I would also recommend you check for Windows corruption since the driver that the timestamp could not be verified for was a Windows driver.

• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Make sure to read through the http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html link carefully.