Asus Q-FAN control and X-Fi bluescreen of death possibly related ?

Hello,

Since two days or so I have re-enabled Asus's Q-FAN control in the bios to
make the cpu fan spin slower when cpu heat is low.

I was just playing Dirt 2 Full version with reduced back fan settings. The
audio settings where using Rapture3D this made the cpu unusually hot 51
degrees !

I wanted hardware support for the audio so I changed it to hardware... I
shutdown Dirt 2... I increased fan speed of the computer case...

Then I started Dirt 2 again and bang... blue screen of death !

Naturally this was one a cracked version of Dirt 2... but even a cracked
version shouldn't crash the os like this ?!

Minidump is available at:

http://members.home.nl/hbthoupperman...i120509-01.dmp

(I could switch my OS to kernel mode debugging and do a stacktrace as well ?
if anybody is interested in that then I might do that )

For now here is the analysis:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini120509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.090805-1438
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Sat Dec 5 15:03:50.062 2009 (GMT+1)
System Uptime: 0 days 13:54:25.997
Loading Kernel Symbols
................................................................
.................................................................
.........................
Loading User Symbols
Loading unloaded module list
...................................................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {20, 2, 0, fffffadfc6f492e8}

Unable to load image \SystemRoot\system32\drivers\ha20x2k.sys, Win32 error
0n2
*** WARNING: Unable to verify timestamp for ha20x2k.sys
*** ERROR: Module load completed but symbols could not be loaded for
ha20x2k.sys
Probably caused by : ha20x2k.sys ( ha20x2k+a22e8 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at
an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffadfc6f492e8, address which referenced memory

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


READ_ADDRESS: 0000000000000020

CURRENT_IRQL: 2

FAULTING_IP:
ha20x2k+a22e8
fffffadf`c6f492e8 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: dirt2_game.exe

TRAP_FRAME: fffff8000007a7b0 -- (.trap 0xfffff8000007a7b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffadfcdddefc0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffffadfc6f492e8 rsp=fffff8000007a940 rbp=fffff8000007aa88
r8=0000000000001002 r9=0000000054a36af1 r10=fffffadfc6fe01b0
r11=00000000001c6000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
ha20x2k+0xa22e8:
fffffadf`c6f492e8 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000102e5b4 to fffff8000102e890

STACK_TEXT:
fffff800`0007a628 fffff800`0102e5b4 : 00000000`0000000a 00000000`00000020
00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`0007a630 fffff800`0102d547 : fffffadf`ce9f1101 00000000`00000000
fffffadf`c73c7c00 fffffadf`c73b71d8 : nt!KiBugCheckDispatch+0x74
fffff800`0007a7b0 fffffadf`c6f492e8 : 3f795430`9500f56c 00000000`00000000
3ff00000`00000000 00000000`00000000 : nt!KiPageFault+0x207
fffff800`0007a940 3f795430`9500f56c : 00000000`00000000 3ff00000`00000000
00000000`00000000 fffffadf`cdddeeb0 : ha20x2k+0xa22e8
fffff800`0007a948 00000000`00000000 : 3ff00000`00000000 00000000`00000000
fffffadf`cdddeeb0 fffffadf`c6f22885 : 0x3f795430`9500f56c


STACK_COMMAND: kb

FOLLOWUP_IP:
ha20x2k+a22e8
fffffadf`c6f492e8 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ha20x2k+a22e8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ha20x2k

IMAGE_NAME: ha20x2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48eb8d23

FAILURE_BUCKET_ID: X64_0xD1_ha20x2k+a22e8

BUCKET_ID: X64_0xD1_ha20x2k+a22e8

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

Bye,
Skybuck.