XP MCE - BSOD 0x50 - ati2mtag.sys

[Zxian]

I've got a slight problem with a new system I've got setup. System specs are as follows:

Gigabyte GA-MA78GM-S2H

AMD X2 5200+

2x1GB OCZ Gold DDR2-800

WD3200AAKS

Pioneer DVR-212D

Antec 380W PSU (came with NSK2480 case)

The system is connected from the onboard video to an LCD TV via HDMI. All standard stability tests (memtest, Prime95, etc) run without any errors or hiccups.

The system stays on 24/7, since it acts as the media center as well as a backup server and central file storage for the household. Every so often when the system is idle, it will bluescreen with error code 0x50, pointing at ati2mtag.sys as the culprit. I've attached a complete memory dump here (12.3MB 7-zip compressed).

All the drivers, as well as the motherboard BIOS, have been updated to the latest version. The system is running XP MCE 2005 SP3.

It seems as though the graphics are to blame. I've heard that ATI and HDMI still don't always play nice, so on my list of things to try in the near future is the following:

1. Connect the system using a DVI-HDMI cable instead of the straight HDMI cable
   
2. Install a dedicated graphics card (both ATI and nVidia) and connect it via DVI-HDMI
   
3. Connect the system temporarily to a regular monitor via DVI and see if I can reproduce the problem
   

I was hoping that someone might be able to have a look at the memory dump mentioned above and figure out if there's anything else software/driver-wise that I can try in the meantime.

[cluberti]

Probably want to try compressing and uploading again:

BugCheck 50, {ba197009, 0, b5a3b64e, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Windows XP Kernel Version 2600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x00000000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Sep 26 23:57:42.687 2008 (GMT-4)
System Uptime: 1 days 21:48:21.366
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************

[Zxian]

Odd.... I'll have to check that again....

[Zxian]

Here's another memory dump from last night:

Memory dump file - 1.3GB

[cluberti]

This was also seen in atikmdag back in 2006 (I remember it vividly, still have a dump file) that was fixed when ATI released 8.31.100.2 of that driver (for x64). Note that both caused a page fault by trying to access a memory address that was either paged out or invalid (thus a page fault, thus a 0x50 bugcheck), for clarification on the crash. So, here's *your* callstack, which is awfully close to the *old* callstack I've got (I'll post them both for comparison):

// Yours:
0: kd> k
ChildEBP RetAddr  
b56614d4 8052036a nt!KeBugCheckEx+0x1b
b566153c 80544578 nt!MmAccessFault+0x9a8
b566153c b5a3b64e nt!_KiTrap0E+0xd0
b56615c8 b5a3bb55 ati2mtag!GetParametersIndirect+0x17
b56615d4 b5a3b0a5 ati2mtag!ProcessCompare+0x20
b5661638 b59e93ea ati2mtag!ParseTable+0x158
b5661660 b59e5b7c ati2mtag!ATOM_ExecuteBIOSTable+0x6d
b5661680 b58a4ac8 ati2mtag!CAIL_ExecuteBIOSTable+0x7b
b56616a0 b58fdb06 ati2mtag!MCIL_ExecBiosTable+0x46
b56616f4 b5a2c885 ati2mtag!GxoExecBiosTable+0x32
b566171c b5a30cab ati2mtag!bDigitalTransmitterControl+0x91
b5661744 b5d801bd ati2mtag!vRV620LvtmEnableOutput+0x49
b5661774 b5a3a5fb ati2mtag!DigitalEncoderActivate+0x171
b5661794 b595a109 ati2mtag!vGxoEncoderActivate+0x5d
b56617b4 b58c4222 ati2mtag!R520DfpSetDisplayOn+0x8f
b56617d0 b58c8f21 ati2mtag!vSetDisplayPowerState+0x64
b56617e8 b5d64504 ati2mtag!DALSetDisplayDPMS+0x23
b566183c b5d64ef6 ati2mtag!SetDisplayPowerState+0x1d6
b566185c b5d5b457 ati2mtag!SetNonACPIDisplayPowerState+0x4c
b566187c b588e63a ati2mtag!AtiSetPowerState+0x6d
b56618e0 804ef18f VIDEOPRT!pVideoPortPowerDispatch+0x476
b56618f0 80526afb nt!IopfCallDriver+0x31
b5661904 80527015 nt!PopPresentIrp+0x57
b5661924 80527185 nt!PoCallDriver+0x195
b5661940 b5892809 nt!PoRequestPowerIrp+0x129
b5661a14 804ef18f VIDEOPRT!pVideoPortDispatch+0xb9f
b5661a24 bf85a1ae nt!IopfCallDriver+0x31
b5661a54 bf93e53d win32k!GreDeviceIoControl+0x93
b5661a84 bf88585a win32k!DrvSetMonitorPowerState+0x52
b5661ad4 bf89fd38 win32k!ProcessQueuedMouseEvents+0x3b
b5661d30 bf884705 win32k!RawInputThread+0x5b9
b5661d40 bf80110a win32k!xxxCreateSystemThreads+0x60
b5661d54 8054161c win32k!NtUserCallOneParam+0x23
b5661d54 7c90e4f4 nt!KiFastCallEntry+0xfc
006effe0 75b6ba1a ntdll!KiFastSystemCallRet
00000000 f000e816 winsrv!NtUserCallOneParam+0xc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 0xf000e816

// Here's the trap, and the bad math:
0: kd> .trap 0xffffffffb5661554
ErrCode = 00000000
eax=ba187007 ebx=b5661650 ecx=00000002 edx=00000002 esi=b56615ec edi=8970c400
eip=b5a3b64e esp=b56615c8 ebp=b5661638 iopl=0		 nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000			 efl=00010282
ati2mtag!GetParametersIndirect+0x17:
b5a3b64e 8b0408		  mov	 eax,dword ptr [eax+ecx] ds:0023:ba187009=????????

0: kd> ? ba187007+00000002
Evaluate expression: -1172803575 = ba187009

// Just to prove it's bad:
0: kd> dc ba187009 L1
ba187009  ????????

// The version and driver you've got, so that you know who / what to point to when talking to AMD:
0: kd> lmvm ati2mtag
start	end		module name
b5898000 b5da6000   ati2mtag   (pdb symbols)		  C:\symbols\ati2mtag.pdb\5F422667FF7243918D0A8E909671DA531\ati2mtag.pdb
	Loaded symbol image file: ati2mtag.sys
	Image path: \SystemRoot\system32\DRIVERS\ati2mtag.sys
	Image name: ati2mtag.sys
	Timestamp:		Wed Aug 20 22:17:42 2008 (48ACD046)
	CheckSum:		 00330EE7
	ImageSize:		0050E000
	File version:	 6.14.10.6860
	Product version:  6.14.10.6860
	File flags:	   8 (Mask 3F) Private
	File OS:		  40004 NT Win32
	File type:		3.4 Driver
	File date:		00000000.00000000
	Translations:	 0000.04b0
	CompanyName:	  ATI Technologies Inc.
	ProductName:	  ATI Radeon WindowsNT Miniport Driver
	InternalName:	 ati2mtag.sys
	OriginalFilename: ati2mtag.sys
	ProductVersion:   6.14.10.6860
	FileVersion:	  6.14.10.6860
	FileDescription:  ATI Radeon WindowsNT Miniport Driver
	LegalCopyright:   Copyright (C) 1998-2004 ATI Technologies Inc.

// The old one I had from 2006 - it's x64, but it's basically the same as your x86 crash:
0: kd> k
ChildEBP RetAddr  
fffff980`046270d8 fffff800`01854e18 nt!KeBugCheckEx
fffff980`046270e0 fffff800`0184cdd9 nt!MmAccessFault+0x137c
fffff980`046271e0 fffff980`03c26c12 nt!KiPageFault+0x119
fffff980`04627378 fffff980`03c26ce4 atikmdag!GetParametersIndirect+0x22
fffff980`04627380 fffff980`03c2665b atikmdag!ProcessMove+0x3c
fffff980`046273c0 fffff980`03bf18f3 atikmdag!ParseTable+0x1f7
fffff980`04627460 fffff980`03bf1cc7 atikmdag!ATOM_ExecuteBIOSTable+0x6b
fffff980`046274c0 fffff980`03bf1d50 atikmdag!ATOM_InitFanCntl+0x57
fffff980`04627510 fffff980`03bf1e24 atikmdag!ATOM_PostVBIOS+0x74
fffff980`04627580 fffff980`03becfe7 atikmdag!ATOM_NoBiosInitializeAdapter+0xc0
fffff980`046275d0 fffff980`03a7e0f5 atikmdag!CAILNoBiosInitializeAdapter+0x6b
fffff980`04627610 fffff980`041cf200 atikmdag!AsicInit::InitializeAdapter+0xa1
fffff980`04627710 fffff980`041ec051 atikmdag!AtiStartDevice+0x158
fffff980`046277d0 fffff980`039541fe atikmdag!DlpStartDevice+0x49
fffff980`04627830 fffff980`0394ea72 dxgkrnl!DpiDxgkDdiStartDevice+0x62
fffff980`04627880 fffff980`0394eee2 dxgkrnl!DpiFdoStartAdapter+0x37e
fffff980`046279e0 fffff980`039499bf dxgkrnl!DpiFdoStartAdapterThread+0x17a
fffff980`04627a70 fffff980`0360f1b2 dxgkrnl!DpiSessionCreateCallback+0x1b
fffff980`04627aa0 fffff980`0360f0ea watchdog!SMgrSessionOpen+0x42
fffff980`04627ae0 fffff960`000059b3 watchdog!SMgrNotifySessionChange+0x22
fffff980`04627b20 fffff960`00005d4c win32k!InitializeGreCSRSS+0x23
fffff980`04627be0 fffff800`0184dcf3 win32k!NtUserInitialize+0x13c
fffff980`04627c20 000007fe`fd63ca0a nt!KiSystemServiceCopyEnd+0x13
00000000`0032f598 00000000`00000000 0x7fe`fd63ca0a

I'd say an email or phone call to AMD/ATI is in order, as it looks like this is still broken in a different driver. Good luck.

[Zxian]

Thanks for the info. I've contacted ATI support and have an open ticket at the moment. I'll keep this thread updated with the responses as I get them.