Sudden BSOD after weeks of stability

What recent software or services have you installed on your system recently? Do you have more minidump files?

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Please remove Eset Nod32 from your system. Third party antivirus software are known for causing BSODs and Eset Nod is not an exception. I would recommend you to remove it for testing. If you need an alternative one, you can use MICROSOFT SECURITY ESSENTIAL and make sure firewall is on.
How to uninstall or remove ESET Nod32 antivirus totally?
http://www.microsoft.com/security_essentials <<----MSE

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.710\080110-10233-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Sun Aug  1 14:11:17.867 2010 (UTC + 7:00)
System Uptime: 0 days 7:01:23.882
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c2c29010, 0, fffff9600014b300, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!GreSelectFont+40 )

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

OLD DRIVER:

Code:

pcouffinu pcoffin.sys Tue Dec 05 21:39:30 2006 (457584A2)

low level access layer for CD devices (A part of many different CD/DVD burning programs), http://www.vso-software.fr

run a system file check to verify and repair any damaged system files
(to do that type cmd in search>right clip and run as admin>sfc /scannow)


Let us know if you need more help

Tuan