Win7 BSOD PAGE_FAULT_IN_NONPAGED_AREA (50)

[gifpaste]

Win7 x64 SP1 Retail Original install
Age of system 2 weeks (I built with parts from Newegg)
Age of OS 2 weeks
Using Microsoft Security Essentials

Intel i7-3820
ASRock X79 Extreme4 LGA 2011 Intel X79
Corsair CMPSU-850AX
16GB G.SKILL Ripjaws Series 240-Pin DDR3 SDRAM DDR3 1333
OCZ Agility 3 AGT3-25SAT3-240G
Western Digital Caviar Black WD1502FAEX 1.5TB
EVGA 012-P3-2078-KR GeForce GTX 560 Ti - 448 Cores
EVGA 01G-P3-1302-LR GeForce 8400 GS 1GB

I had the computer on for about an hour or so, Outlook, Firefox, Trillian were running. I was playing WoW when the game froze with sound stuttering and went to BSOD

I tried viewing it myself with WinDbg but not sure if I'm missing something, it says 'could not triage file'

7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8000158744e, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff8000158744e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name
TRIAGER: Could not open triage file : D:\debugger\Debuggers\x64\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c3100
GetUlongFromAddress: unable to read from fffff800034c31c0
fffff8000158744e Nonpaged pool



Memtest time?

 

[zigzag3143]

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

 

[gifpaste]

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

Ah, that jcgriff2 program packed up my old crash in addition to my most recent. I have not had that crash related to the clock_watchdog since updating my bios.

My most recent crash was the 031412-15272-01.dmp file

 

[zigzag3143]

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

Ah, that jcgriff2 program packed up my old crash in addition to my most recent. I have not had that crash related to the clock_watchdog since updating my bios.

My most recent crash was the 031412-15272-01.dmp file

2-DMPS

1-from 3/14 inconclusive

2-3/3 clock watchdog.