TrackIR 5 crashing at startup

[Sophosaurus]

My TrackIR 5 arrived last week, and got installed with latest software some days ago. There have been no older installations before this one. Now trackir.exe frequently crashes at startup giving following reason:

"Application Failure trackir5.exe 5.0.0.300 in ntdll.dll 5.1.2600.5755 at offset 000369da."

Nine of ten failures produce the same message with same offset.
Sometimes offset is 0x00011689, or 0x00010a19, or 0x00010fa6.

Sometimes rebooting the system helps. When closed and started again within the same session it rarely works. Changing compatibility settings does not help.

System is: XP Pro SP3 with all updates. My machine runs 24/7 and there are no other crashes even when it runs for weeks.

Hardware is: Asus Maximus Formula, Q6600, 2*1GB memory, HD3870, Hauppauge Nova-S Plus, and some USB devices (Logitech FF EX Wheel, Quickcam Sphere AF, HP Deskjet).

Once started TrackIR works perfectly without crashing.

EDIT: According to hardware manager driver version is 2.41.0.0 from 04/11/2007.

[Sophosaurus]

Update: Since it's getting worse, here is some more information.

Meanwhile it keeps crashing endlessly, even when my system is booted stripped to the bones (no other software running, 29 tasks left, no other devices on USB).

Changing USB port makes no difference. Used ports run fine with all other devices. My mainboard, CPU and memory perform well running stresstests. Mainboard and graphics card have latest BIOS (with no known errors). All drivers updated regularly.

I tried to start TrackIR over 60 times using 3 different USB ports, rebooting about 20 times, and succeeded 3 times.

Installation has been done successfully using admin account using default location which is 'C:\Programme\NaturalPoint\TrackIR5' for german XP32. Problem occurs using same admin account.

Each time trdb.log looks like this:

[02/01/2010 21:39:24:859] 0x1568: Begin TrackIR...
[02/01/2010 21:39:24:859] 0x1568: Creating TrackIR application instance...
[02/01/2010 21:39:24:859] 0x1568: Detected Operating System : XP_32
[02/01/2010 21:39:24:859] 0x1568: Loading Application Settings...
[02/01/2010 21:39:24:875] 0x1568: Application Settings loaded.
[02/01/2010 21:39:24:875] 0x1568: Loading Profiles...
[02/01/2010 21:39:24:875] 0x1568: Profiles Loaded.
[02/01/2010 21:39:24:921] 0x1568: Loading Game List...
[02/01/2010 21:39:24:921] 0x1568: Game List Loaded.
[02/01/2010 21:39:24:921] 0x1568: Creating Main display...
[02/01/2010 21:39:25:546] 0x1568: Main display created.
[02/01/2010 21:39:25:546] 0x1568: Initializing 3D view...
[02/01/2010 21:39:25:546] 0x1568: OpenGL Version : 2.1.9116
[02/01/2010 21:39:25:546] 0x1568: OpenGL Renderer : ATI Radeon HD 3800 Series
[02/01/2010 21:39:25:546] 0x1568: OpenGL Vendor : ATI Technologies Inc.

Let me know if something else is needed to identify this problem.

[Seth Steiling]

Have you tried the TrackIR 4.1.037 software, to test for similar behavior?

[Sophosaurus]

Good idea. Installed and tested. Started and closed it multiple times without failure. Tried V5 right after closing V4 and it failed like before ("Detecting..."). Started V4 right after V5 crashed and V4 still works. I can start and close it as often as i want, which never worked for me with V5.

Good to see there is no hardware failure.

[VincentG]

What video card drivers do you have installed?

Any opengl settings enabled in the video card drivers settings?

[Sophosaurus]

Catalyst 9.11 and Ati Tray Tools. OpenGL settings at default most of the time. I tried with z-buffer set to 24bit and triple buffering which made no difference. I also tried to run CCC only without Ati Tray Tools. Catalyst setup was done after uninstalling previous version completely.

[batman11]

Hello there!

I have the same problem.
I have a similar (not the same)system to the one above.

It's Win XP Pro(german),SP3 + all updates so far, 2 GB ram, Intel E6750 (not OC'ed,)Mobo is Gigabyte GA-EP-DS3, ATI HD 3870,
and I can't get TrackIR v5 to work.
V4 works fine.

After installing and the first attempt to run the software, it'll start. I get the new GUI, which looks good and the traking feels better than in V4.

Then when I close it I get a Windows Error, in the detailed view it mentions the TrackIR5.exe and the ntdll.dll.
And it won't start anymore, it'll alwas quit with a error.

In the App-log I get 2 Error entries upon 1 attempt to start up:
1.
"Fehlgeschlagene Anwendung trackir5.exe, Version 5.0.0.300, fehlgeschlagenes Modul trackir5.exe, Version 5.0.0.300, Fehleradresse 0x0002308c"
2.
"Fehlgeschlagene Anwendung trackir5.exe, Version 5.0.0.300, fehlgeschlagenes Modul ntdll.dll, Version 5.1.2600.5755, Fehleradresse 0x00010a19"

I got the TrackIR5 last year in August and ever since I haven't been able to run V5. Always been using V4.

Now that the Flaming Cliffs 2.0 is out I'm getting back into simming and would really like you guys (TrackIR Support) to be constructive and help.

I have searched the forums and the net and I haven't found any solution.
The only thing I've found is that someone replaced the ntdll.dll with an older version. I don't know how he did it. The kernel protection of Windows doesn't allow it. The replaced file is being immediately restored with the current version. And besides it cant't be right trying to reinstate older versions of the essential windows files.

I hope someone can help.

Maybe you developers need to look at it closer.

Batman11

[VincentG]

What video card drivers do you have installed?

Have you tried disabling the OPenGL features, within the video card software?

[batman11]

Hi Vincent!

The video driver is Xtreme-G ATI Cat. 9.8

As for OpenGL, I can only see one option that I can change:
Tripple Buffering.
I tried that. Nothing changes.

BUT! I have been able to get V5 to work by setting the start options to compatibility mode for Win NT 4.0. (rightclick on the icon on the desktop etc.)

It seems to be OK. But it'll only work that way.

Is it supposed to be like this?
Is the tracking quality different in compatybility mode?

cheers

[VincentG]

It shouldn't track any different.

Odd that it works in compatability mode.