CTDs & BSODs with TrackIR 5 and windows 7 64-bit

[pliantkitchen]

This has been happening in DCS Black Shark and DCS A-10C. Latest OEM (non-CCC) ATI catalyst drivers with 64-bit A-10C, 32-bit Black Shark. In-game, if the reflectors are lost and re-sensed, it's as if the 3d output is redrawn. After it does this a number of time, it totally crashes the computer and a restart is needed (looping sound, black screen, no video output, etc). I am downgrading to TrackIR 4 to verify that it is the software causing this issue.

This is day two of using TrackIR. Please let me know if you need more specific information to troubleshoot this issue, or if it's related to the known XP/ATI driver bug.

[NaturalPoint - Mike]

Which version of TrackIR in particular was being used at the time the issue was occuring?

[pliantkitchen]

Version 5.1 - Final
(posted March 2, 2011)

I uninstalled 5.1 and installed

Version 4.1.038 - Final
(posted February 11, 2011)

and I was able to play uninterrupted for 20-30 minutes. I will try in DCS: A-10C and report back. I checked C:\Windows\minidump but couldn't find anything recent - does TrackIR dump logs anywhere on fatal errors or warnings?

[NaturalPoint - Mike]

Standard distribution of the TrackIR software does not contain any logging, although we do have a version that we can send in certain circumstances to get log files of certain behavior.

Was anything recorded with reference to the crashes in the windows event logs? Do you have the error codes from the BSOD?

[pliantkitchen]

I didn't experience a BSOD in the classic sense, it was more of a 'oh shit gotta restart'. It definitely brought the computer to it's knees - the looping sound, lack of video, and total unresponsiveness requires a restart to recover. Upon restart and initial boot, Windows provides me with a prompt to boot into Safe Mode because of (what I assume to be) it's internal error detection logic. I haven't had the same type of event yet with the TrackIR 4 software package.

I've also attached my dxdiag 64-bit information in case that helps.

Code: Select all

------------------
System Information
------------------
Time of this report: 3/3/2011, 17:45:22
       Machine name: QUICHELENSE
   Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.101026-1503)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: P55A-UD3
               BIOS: Award Modular BIOS v6.00PG
          Processor: Intel(R) Core(TM) i5 CPU         760  @ 2.80GHz (4 CPUs), ~2.8GHz
             Memory: 8192MB RAM
Available OS Memory: 8184MB RAM
          Page File: 1668MB used, 14696MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7600.16385 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
          Card name: ATI Radeon HD 5700 Series
       Manufacturer: ATI Technologies Inc.
          Chip type: ATI display adapter (0x68B8)
           DAC type: Internal DAC(400MHz)
         Device Key: Enum\PCI\VEN_1002&DEV_68B8&SUBSYS_21401462&REV_00
     Display Memory: 750 MB
   Dedicated Memory: 1010 MB
      Shared Memory: 3835 MB
       Current Mode: 1920 x 1080 (32 bit) (60Hz)
       Monitor Name: Generic PnP Monitor
      Monitor Model: SyncMaster
         Monitor Id: SAM0589
        Native Mode: 1920 x 1080(p) (60.000Hz)
        Output Type: DVI
        Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,
                     atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1065 (English)
     Driver Version: 8.821.0.0
        DDI Version: 10.1
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 1/26/2011 16:59:10, 708608 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B71EE2-2BF8-11CF-FB73-4A01BEC2C535}
          Vendor ID: 0x1002
          Device ID: 0x68B8
          SubSys ID: 0x21401462
        Revision ID: 0x0000
 Driver Strong Name: oem3.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:8.821.0.0:pci\ven_1002&dev_68b8
     Rank Of Driver: 00E62001
        Video Accel: ModeMPEG2_A ModeMPEG2_C 
   Deinterlace Caps: ***REMOVED BY USER REQUEST***
       D3D9 Overlay: Not Supported
            DXVA-HD: Not Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled

     Name: ATI Radeon HD 5700 Series
Device ID: PCI\VEN_1002&DEV_68B8&SUBSYS_21401462&REV_00\4&932E434&0&0018
   Driver: C:\Windows\system32\DRIVERS\atikmdag.sys, 8.01.0001.1123 (English), 1/26/2011 17:37:20, 9085952 bytes
   Driver: C:\Windows\system32\DRIVERS\ati2erec.dll, 1.00.0000.0019 (English), 1/26/2011 16:11:46, 53248 bytes
   Driver: C:\Windows\system32\DRIVERS\atikmpag.sys, 8.14.0001.6187 (English), 1/26/2011 16:13:32, 299520 bytes
   Driver: C:\Windows\system32\atiumd64.dll, 7.14.0010.0812 (English), 1/26/2011 16:21:58, 5316096 bytes
   Driver: C:\Windows\system32\atiumd6a.dll, 8.14.0010.0296 (English), 1/26/2011 16:32:00, 3222016 bytes
   Driver: C:\Windows\system32\atitmm64.dll, 6.14.0011.0023 (English), 1/26/2011 16:54:20, 120320 bytes
   Driver: C:\Windows\system32\atiicdxx.dat, 12/17/2010 10:00:44, 227587 bytes
   Driver: C:\Windows\system32\amdpcom64.dll, 8.14.0010.0023 (English), 1/26/2011 16:08:46, 53760 bytes
   Driver: C:\Windows\system32\atimpc64.dll, 8.14.0010.0023 (English), 1/26/2011 16:08:46, 53760 bytes
   Driver: C:\Windows\system32\atiadlxx.dll, 6.14.0010.1054 (English), 1/26/2011 16:14:14, 354304 bytes
   Driver: C:\Windows\system32\atiumd6a.cap, 1/26/2011 16:29:38, 756736 bytes
   Driver: C:\Windows\system32\atimuixx.dll, 6.14.0010.1002 (English), 1/26/2011 16:53:36, 16384 bytes
   Driver: C:\Windows\system32\atiapfxx.exe, 6.14.0010.1001 (English), 1/26/2011 17:00:44, 143360 bytes
   Driver: C:\Windows\system32\atiapfxx.blb, 1/26/2011 17:00:48, 145280 bytes
   Driver: C:\Windows\system32\atiumd6v.dll, 7.14.0010.0184 (English), 1/26/2011 16:32:46, 1208320 bytes
   Driver: C:\Windows\system32\atiesrxx.exe, 6.14.0011.1085 (English), 1/26/2011 16:55:36, 203776 bytes
   Driver: C:\Windows\system32\atieclxx.exe, 6.14.0011.1085 (English), 1/26/2011 16:56:14, 479232 bytes
   Driver: C:\Windows\system32\atipdl64.dll, 6.14.0010.2563 (English), 1/26/2011 16:54:00, 423424 bytes
   Driver: C:\Windows\system32\atiedu64.dll, 6.14.0010.2514 (English), 1/26/2011 16:53:32, 59392 bytes
   Driver: C:\Windows\system32\ATIDEMGX.dll, 2.00.4043.32294 (English), 1/26/2011 16:56:30, 462848 bytes
   Driver: C:\Windows\system32\atio6axx.dll, 6.14.0010.10524 (English), 1/26/2011 17:22:18, 22295040 bytes
   Driver: C:\Windows\system32\aticaldd64.dll, 6.14.0010.1016 (English), 1/26/2011 16:27:30, 6982144 bytes
   Driver: C:\Windows\system32\aticalrt64.dll, 6.14.0010.1016 (English), 1/26/2011 16:27:52, 51200 bytes
   Driver: C:\Windows\system32\aticalcl64.dll, 6.14.0010.1016 (English), 1/26/2011 16:27:42, 44544 bytes
   Driver: C:\Windows\system32\atipblag.dat, 12/20/2010 20:27:20, 3113 bytes
   Driver: C:\Windows\system32\atiu9p64.dll, 8.14.0001.6187 (English), 1/26/2011 16:12:32, 38400 bytes
   Driver: C:\Windows\system32\atiuxp64.dll, 8.14.0001.6187 (English), 1/26/2011 16:12:46, 39936 bytes
   Driver: C:\Windows\system32\atig6pxx.dll, 8.14.0001.6187 (English), 1/26/2011 16:13:56, 14848 bytes
   Driver: C:\Windows\system32\atig6txx.dll, 8.14.0001.6187 (English), 1/26/2011 16:13:50, 39936 bytes
   Driver: C:\Windows\system32\atibtmon.exe, 2.00.0000.0000 (English), 5/11/2009 16:35:28, 118784 bytes
   Driver: C:\Windows\system32\atidxx64.dll, 8.17.0010.0337 (English), 1/26/2011 16:40:02, 4847616 bytes
   Driver: C:\Windows\SysWOW64\atiumdag.dll, 7.14.0010.0812 (English), 1/26/2011 16:28:52, 4170752 bytes
   Driver: C:\Windows\SysWOW64\atiumdva.dll, 8.14.0010.0296 (English), 1/26/2011 16:24:18, 3463680 bytes
   Driver: C:\Windows\SysWOW64\amdpcom32.dll, 8.14.0010.0023 (English), 1/26/2011 16:08:40, 52736 bytes
   Driver: C:\Windows\SysWOW64\atimpc32.dll, 8.14.0010.0023 (English), 1/26/2011 16:08:40, 52736 bytes
   Driver: C:\Windows\SysWOW64\atiadlxy.dll, 6.14.0010.1054 (English), 1/26/2011 16:14:08, 249856 bytes
   Driver: C:\Windows\SysWOW64\atiumdva.cap, 1/26/2011 16:23:50, 756736 bytes
   Driver: C:\Windows\SysWOW64\atiumdmv.dll, 7.14.0010.0184 (English), 1/26/2011 16:32:12, 1912832 bytes
   Driver: C:\Windows\SysWOW64\atipdlxx.dll, 6.14.0010.2563 (English), 1/26/2011 16:53:54, 356352 bytes
   Driver: C:\Windows\SysWOW64\Oemdspif.dll, 6.15.0006.0006 (English), 1/26/2011 16:53:42, 278528 bytes
   Driver: C:\Windows\SysWOW64\ati2edxx.dll, 6.14.0010.2514 (English), 1/26/2011 16:53:26, 43520 bytes
   Driver: C:\Windows\SysWOW64\atioglxx.dll, 6.14.0010.10524 (English), 1/26/2011 16:59:46, 17204736 bytes
   Driver: C:\Windows\SysWOW64\atidxx32.dll, 8.17.0010.0337 (English), 1/26/2011 16:49:44, 4105728 bytes
   Driver: C:\Windows\SysWOW64\aticaldd.dll, 6.14.0010.1016 (English), 1/26/2011 16:25:50, 5580800 bytes
   Driver: C:\Windows\SysWOW64\aticalrt.dll, 6.14.0010.1016 (English), 1/26/2011 16:27:50, 46080 bytes
   Driver: C:\Windows\SysWOW64\aticalcl.dll, 6.14.0010.1016 (English), 1/26/2011 16:27:40, 44032 bytes
   Driver: C:\Windows\SysWOW64\atipblag.dat, 12/20/2010 20:27:20, 3113 bytes
   Driver: C:\Windows\SysWOW64\atiu9pag.dll, 8.14.0001.6187 (English), 1/26/2011 16:12:24, 28672 bytes
   Driver: C:\Windows\SysWOW64\atiuxpag.dll, 8.14.0001.6187 (English), 1/26/2011 16:12:40, 30720 bytes
   Driver: C:\Windows\SysWOW64\atigktxx.dll, 8.14.0001.6187 (English), 1/26/2011 16:13:42, 32768 bytes
   Driver: C:\Windows\SysWOW64\atiglpxx.dll, 8.14.0001.6187 (English), 1/26/2011 16:13:52, 12800 bytes
   Driver: C:\Windows\atiogl.xml, 1/25/2011 16:42:00, 30707 bytes
   Driver: C:\Windows\system32\ATIODCLI.exe, 1.00.0000.0001 (English), 6/22/2009 10:34:36, 51200 bytes
   Driver: C:\Windows\system32\ATIODE.exe, 1.00.0000.0001 (English), 8/27/2010 13:33:08, 332800 bytes
   Driver: C:\Windows\system32\atiglpxx.dll, 8.14.0001.6187 (English), 1/26/2011 16:13:52, 12800 bytes
   Driver: C:\Windows\system32\aticfx64.dll, 8.17.0010.1065 (English), 1/26/2011 16:59:10, 708608 bytes
   Driver: C:\Windows\SysWOW64\aticfx32.dll, 8.17.0010.1065 (English), 1/26/2011 17:00:30, 596480 bytes
   Driver: C:\Windows\system32\coinst.dll, 1.00.0003.0005 (English), 1/26/2011 16:20:46, 58880 bytes

[NaturalPoint - Mike]

Was there anything listed in the event log? Specifically in application or system?

[pliantkitchen]

Chronological System/Application errors below. Looks like it's an ATI-related resource contention issue? I'll definitely be going with nVidia next time. This is ridiculous. I've noticed amdkmdap entries spamming my System Events log, I will need to disable this type of logging in the Registry. Tens of events per second for Task Category DVD_OV during the times when I've been playing games. Could the driver be competing with TrackIR somehow?

First Warning in System Events in between thousands of amdkmdap entries: Source - Display @ 3/2 9:17PM

Code: Select all

Display driver amdkmdap stopped responding and has successfully recovered.

First Error in Application Events: TrackIR 5 Application Hang @ 3/2 9:19 PM:

Code: Select all

- System 
 
   [ Name]  Application Hang 
  - EventID 1002 
   [ Qualifiers]  0 
   Level 2 
   Task 101  
   Keywords 0x80000000000000 
 
  - TimeCreated 
   [ SystemTime]  2011-03-03T03:19:03.000000000Z  
   EventRecordID 1411  
   Channel Application 
   Computer quichelense  
   Security 
 

- EventData 
   TrackIR5.exe 
   5.1.0.200 
   1160 
   01cbd95009a015de 
   33 
   C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe 
   fbef640d-4544-11e0-8ba9-005056c00008 
   55006E006B006E006F0077006E0000000000 
--------------------------------------------------------------

Binary data:
In Words
0000: 006E0055 006E006B 0077006F 0000006E 
0008: 0000    
In Bytes
0000: 55 00 6E 00 6B 00 6E 00   U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00   o.w.n...
0010: 00 00                     ..

I tried Alt-Tabbing from dcs to TrackIR software and it crashed dcs upon switching back to the program:

Second Error in Application Events: dcs.exe @ 3/2 9:29 PM

Code: Select all

- System 
- Provider 
   [ Name]  Application Error 
  - EventID 1000 
   [ Qualifiers]  0 
   Level 2 
   Task 100 
   Keywords 0x80000000000000 
  - TimeCreated 
   [ SystemTime]  2011-03-03T03:29:20.000000000Z 
   EventRecordID 1412 
   Channel Application 
   Computer quichelense 
   Security 
- EventData 

   dcs.exe 
   1.1.0.5 
   4d5bd920 
   MSVCR90.dll 
   9.0.30729.4926 
   4a1750b0 
   c0000417 
   0000000000054fc0 
   a84 
   01cbd95204ec320c 
   C:\Program Files\Eagle Dynamics\DCS A-10C\bin\dcs.exe 
   C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554\MSVCR90.dll 
   6ccdf3c2-4546-11e0-8ba9-005056c00008

There are three or four more dcs.exe appcrash entries in the logs, all due to faulting module MSVCR90.dll (trackIR plugin, or DCS coding error?)

I also have 4 relevant .wer files created in this directory:

Code: Select all

C:\Users\<user>\AppData\Local\Microsoft\Windows\WER\ReportArchive

The entries for the restarts are the generic Critical 'System has recovered from an unexpected shutdown' logs.

[pliantkitchen]

Ran driversweep and reinstalled the older catalyst 10.12 drivers, still getting same issue.

After some testing, I've found that TrackIR, regardless of version, will 'hang' momentarily. Checking the Event Viewer shows 29 of the following amdkmdag events, all within 1 second (!!!):

Code: Select all

- System 

  - Provider 

   [ Name]  amdkmdag 
 
  - EventID 62464 

   [ Qualifiers]  16384 
 
   Level 4 
 
   Task 61 
 
   Keywords 0x80000000000000 
 
------------

Binary data:


In Words

0000: 00600000 00000001 0000003D 4000F400 
0008: 00000000 00000000 00000000 00000000 
0010: 00000000 00000000 FFFFFFFF 58060300 
0018: 00000003 0000000F 0000000B 00000003 
0020: 0000000F 0000000B 00000003 00000000 
0028: 00000000 007FFB0F 003E8000 0000003C 
0030: 00000000 00000003 00000003 00000003 
0038: 00000003 00000003 00000003 00000003 
0040: 00000003 00000003   


In Bytes

0000: 00 00 60 00 01 00 00 00   ..`.....
0008: 3D 00 00 00 00 F4 00 40   =....�.@
0010: 00 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: FF FF FF FF 00 03 06 58   ����...X
0030: 03 00 00 00 0F 00 00 00   ........
0038: 0B 00 00 00 03 00 00 00   ........
0040: 0F 00 00 00 0B 00 00 00   ........
0048: 03 00 00 00 00 00 00 00   ........
0050: 00 00 00 00 0F FB 7F 00   .....�.
0058: 00 80 3E 00 3C 00 00 00   .&#128;>.<...
0060: 00 00 00 00 03 00 00 00   ........
0068: 03 00 00 00 03 00 00 00   ........
0070: 03 00 00 00 03 00 00 00   ........
0078: 03 00 00 00 03 00 00 00   ........
0080: 03 00 00 00 03 00 00 00   ........

[pliantkitchen]

Disabled 'AMD External Events Utility' in services. My guess is the Event Service writing hundreds of of those entries to the log every few seconds caused the system to become unstable.

I'll report back to see if this helps.

Edit: Could someone edit my second post and remove the unnecessary dxdiag output? I'm unable to edit [color:#FF0000]I see it removed now, thanks![/color]

Apparently, this is a known issue: http://forums.amd.com/game/messageview. ... did=119718

Both DCS titles are working as expected with both TrackIR 4 & 5. There's a redraw at the beginning of each mission, but that's it. No lagging/slowdowns/restarts yet. The excessive logging must have been so bad that it brought down the kernel. Wow.

Is there a known-working ATI Catalyst driver for TrackIR 5 on 64-bit systems?

[NaturalPoint - Mike]

MSVCR90 is part of the Visual C++ 2008 runtime library. This would indicate to me that it's an internal DCS crash, however the cause could be fairly widespread.