BlueScreed of death

Hi there,

Window file was blamed in the dmp. I would like you to run system file check and let us know the result
SFC /SCANNOW Command - System File Checker

ruby.exe was the process running at the time of crash. I've searched and it belong to games (is that right?) Do you get that BSODs only while in particular game?

Update this driver:

Code:

AsIO     AsIO.sys     Mon Dec 17 16:10:20 2007 (47663CFC)

Asus PCProbe Utility. Either update it or remove the program.
ASUSTeK Computer Inc.-Support-

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

BUGCHECK SUMMARY:

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.092\090610-12620-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8280d000 PsLoadedModuleList = 0x82955810
Debug session time: Mon Sep  6 21:40:55.571 2010 (UTC + 7:00)
System Uptime: 0 days 1:01:07.100
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4, 2, 0, 88b81946}

Probably caused by : afd.sys ( afd!AfdPoll+4ce )

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

Regard,

Tuan