Author Topic: Saitek X52 Causes Reboot (Read 462 times)

WarpigNJ · « **on:** April 18, 2007, 08:35:15 PM »

Yesterday I installed the Saitek X52 controllers (stick & throttle). It seems whenever there is alot going on graphically in AH, my system decides to reboot without warning. Just *poof* *beep* reboot.

I've got the latest Saitek drivers and the latest DirectX patch as posted on these forums. I've run Dxdiag and there are no problems. Installed the latest AMD dual core drivers. This is a new system, about a month old, so there shouldn't be any hardware issues.

AH only uses 30% of RAM and 20% of processor resources at any given time. PC runs fine in WoW, COD2 and BF2142. I played AH for 2 days with my old Microsoft Sidewinder with no problems. It's got to be the Saitek.

Is anyone else experiencing a similar issue?

EDIT: I just read on another thread about a powered USB hub solving some Saitek issues. Since this stick is powered (lights and lcd display) I'm wondering if that will help?

System:
WinXP SP2
AMD 64 FX 60 2.6
2GB Ram
Nvidia GeForce 7950GT 512mb
Creative SBXFI
ASUS A8S-X Mobo
500w Power Supply

Simaril · « **Reply #1 on:** April 19, 2007, 07:53:12 AM »

I've had saitek X52 for over a year, with no problems whatsoever. Not sure I have the absolutely most recent drivers...

but I'm really suspicious the problem may be coming from somewhere else, or from a conflict.

I don't think the powered USB would be a solution, and in fact my X52 really dislikes running off a powered USB extension. Often get failure to recognize the stick, etc with that port used, where I have no problem at all with the saitek directly connected to the PC.

May want to post a DXDIAG output. I not a tech guy, but skuzzy and others can read through that stuff and pick up problems.

Denholm · « **Reply #2 on:** April 19, 2007, 09:10:15 AM »

How many sticks of RAM do you have in your system? And if you have more than one stick, does your motherboard support dual-channeling? If you have an uneven amount of sticks in your system (1 is excluded) it could cause these issues, I found out the hard way. Also, if you have SDRAM and DDR/DDR2 RAM combined in your system it could cause issues if your motherboard does NOT support Dual-Channeling.

Works kinda like this. The RAM is recognized, yet not to it's full potential. So the system has to decide to run on the SDRAM or the DDR/DDR2. Whatever it chooses it can not use any resources from the opposite type RAM. However, your system still sees that RAM and thinks it can use it. Whenever the RAM reaches a level of resources used that it attempts to use some from the other type (SDRAM or DDR/DDR2) it can't. Once the system realizes this it freaks thinking it maxed out and the only way to recover is a re boot.

That's exactly what happens. Although I highly doubt this could be the case since you're running high-end games without a problem. If it is the joystick this is the first case I've heard of. I've had 0 problems with my X52, don't see what could be causing it other than a system-issue.

WarpigNJ · « **Reply #3 on:** April 19, 2007, 12:56:56 PM »

Thanks for the replies guys!

I will post my Dxdiag tonight when I get home from work.

And I will forego the powered USB hub. Thanks, you just saved me $60.

I'm running 2 matched 1 gig sticks of DDR PC3200 Ram. I spent the extra $ to get the RAM from Crucial so I could get the matched set. My mobo does support dual channel and I loaded them into those slots.

And I agree that is definitely sounds like a hardware issue, but I am running other games that far exceed the requirements of AH, and the problem did not start until I added the Saitex. So, I am officially stumped!

WarpigNJ · « **Reply #4 on:** April 19, 2007, 03:53:10 PM »

My DXDIAG:

------------------
System Information
------------------
Time of this report: 4/19/2007, 16:51:36
Machine name: JIM
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 12/19/05 20:03:51 Ver: 08.00.10
Processor: AMD Athlon(tm) 64 FX-60 Dual Core Processor, MMX, 3DNow (2 CPUs), ~2.6GHz
Memory: 2046MB RAM
Page File: 377MB used, 3562MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode

------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.

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

---------------
Display Devices
---------------
Card name: NVIDIA GeForce 7950 GT
Manufacturer: NVIDIA
Chip type: GeForce 7950 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0295&SUBSYS_220719F1&REV_A1
Display Memory: 512.0 MB
Current Mode: 1680 x 1050 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.9371 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 10/22/2006 13:22:00, 4527488 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 10/22/2006 13:22:00, 3994624 bytes
Device Identifier: {D7B71E3E-41D5-11CF-DA5E-0D0200C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0295
SubSys ID: 0x220719F1
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
Deinterlace Caps: {212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run

WarpigNJ · « **Reply #5 on:** April 19, 2007, 03:54:04 PM »

-------------
Sound Devices
-------------
Description: SB X-Fi Audio [B400]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.1187 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 8/17/2006 12:17:10, 500480 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Full
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run

---------------------
Sound Capture Devices
---------------------
Description: SB X-Fi Audio [B400]
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.1187 (English)
Driver Attributes: Final Retail
Date and Size: 8/17/2006 12:17:10, 500480 bytes
Cap Flags: 0x0
Format Flags: 0x0

-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: Enabled
Ports: SB X-Fi DMusic Synth [B400], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
SB X-Fi Audio [B400], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB X-Fi Synth A [B400] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB X-Fi Synth B [B400] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal
Registry: OK
Test Result: Not run

-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Internet Keys USB
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC30A
FF Driver: n/a

Device Name: Internet Keys USB
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC30A
FF Driver: n/a

Device Name: Saitek X52 Flight Controller
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x075C
FF Driver: n/a

Poll w/ Interrupt: No
Registry: OK

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x1039, 0x7001
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 2/28/2006 08:00:00, 57600 bytes
| Driver: usbd.sys, 2/28/2006 08:00:00, 4736 bytes
|
+-+ Microsoft USB Trackball Optical
| | Vendor/Product ID: 0x045E, 0x0023
| | Location: Microsoft Trackball Optical®
| | Matching Device ID: usb\vid_045e&pid_0023
| | Service: HidUsb
| | Driver: hidclass.sys, 8/3/2004 23:08:20, 36224 bytes
| | Driver: hidparse.sys, 8/3/2004 23:08:18, 24960 bytes
| | Driver: hid.dll, 2/28/2006 08:00:00, 20992 bytes
| | Driver: hidusb.sys, 8/17/2001 14:02:20, 9600 bytes
| |
| +-+ Microsoft USB Trackball Optical (IntelliPoint)
| | | Vendor/Product ID: 0x045E, 0x0023
| | | Matching Device ID: hid\vid_045e&pid_0023
| | | Upper Filters: Point32
| | | Service: mouhid
| | | Driver: mouhid.sys, 8/17/2001 14:48:00, 12160 bytes
| | | Driver: mouclass.sys, 8/3/2004 23:58:34, 23040 bytes
| | | Driver: point32.sys, 11/8/2006 00:02:36, 21760 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ HID Keyboard Device
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 8/3/2004 23:58:36, 14848 bytes
| Driver: kbdclass.sys, 8/3/2004 23:58:34, 24576 bytes
|
+ Logitech HID-Compliant Keyboard
| Vendor/Product ID: 0x046D, 0xC30A
| Matching Device ID: hid\vid_046d&pid_c30a&mi_00
| Service: kbdhid
| Driver: kbdhid.sys, 8/3/2004 23:58:36, 14848 bytes
| Driver: kbdclass.sys, 8/3/2004 23:58:34, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 02:01:08, 40840 bytes
| Driver: kbdclass.sys, 8/3/2004 23:58:34, 24576 bytes
|
+ HID-compliant mouse
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 8/3/2004 23:58:34, 23040 bytes
| Driver: mouhid.sys, 8/17/2001 14:48:00, 12160 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x046D, 0xC30A
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 8/3/2004 23:58:34, 23040 bytes
| Driver: mouhid.sys, 8/17/2001 14:48:00, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 02:01:08, 40840 bytes
| Driver: mouclass.sys, 8/3/2004 23:58:34, 23040 bytes

-

WarpigNJ · « **Reply #6 on:** April 19, 2007, 03:55:37 PM »

---------------------------
DirectPlay Service Providers
----------------------------
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)

DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: Not run
Registry: OK

-------------------
DirectPlay Adapters
-------------------
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: Local Area Connection - IPv4 -

-----------------------
DirectPlay Voice Codecs
-----------------------
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s

-------------------------
DirectPlay Lobbyable Apps
-------------------------

------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 271.2 GB
Total Space: 305.2 GB
File System: NTFS
Model: ST3320620AS

Drive: D:
Model: SONY DVD RW DW-G120A
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 49536 bytes

--------------
System Devices
--------------
Name: Intel(R) PRO/1000 MT Network Connection
Device ID: PCI\VEN_8086&DEV_100E&SUBSYS_80EE1043&REV_02\3&267A616A&0&58
Driver: n/a

Name: Creative SB X-Fi
Device ID: PCI\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00\3&267A616A&0&48
Driver: C:\WINDOWS\system32\ksuser.dll, 5.03.2600.2180 (English), 8/4/2004 01:56:44, 4096 bytes
Driver: C:\WINDOWS\system32\ksproxy.ax, 5.03.2600.2180 (English), 8/4/2004 01:56:58, 130048 bytes
Driver: C:\WINDOWS\system32\drivers\ks.sys, 5.03.2600.2180 (English), 8/4/2004 00:15:22, 140928 bytes
Driver: C:\WINDOWS\system32\drivers\drmk.sys, 5.01.2600.2180 (English), 8/4/2004 00:08:00, 60288 bytes
Driver: C:\WINDOWS\system32\drivers\portcls.sys, 5.01.2600.2180 (English), 8/4/2004 00:15:50, 145792 bytes
Driver: C:\WINDOWS\system32\drivers\stream.sys, 5.03.2600.2180 (English), 8/4/2004 00:08:04, 48640 bytes
Driver: C:\WINDOWS\system32\wdmaud.drv, 5.01.2600.2180 (English), 8/4/2004 01:56:58, 23552 bytes
Driver: C:\WINDOWS\system32\drivers\ctac32k.sys, 5.12.0001.1187 (English), 8/17/2006 12:14:24, 502272 bytes
Driver: C:\WINDOWS\system32\drivers\ctaud2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:17:10, 500480 bytes
Driver: C:\WINDOWS\system32\drivers\ctoss2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:15:00, 116224 bytes
Driver: C:\WINDOWS\system32\drivers\ctprxy2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:17:12, 7168 bytes
Driver: C:\WINDOWS\system32\drivers\ctsfm2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:14:42, 143872 bytes
Driver: C:\WINDOWS\system32\drivers\emupia2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:14:38, 78336 bytes
Driver: C:\WINDOWS\system32\drivers\ha10kx2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:15:24, 765952 bytes
Driver: C:\WINDOWS\system32\drivers\haP16v2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:15:32, 154112 bytes
Driver: C:\WINDOWS\system32\drivers\haP17v2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:15:38, 180224 bytes
Driver: C:\WINDOWS\system32\drivers\ha20x2k.sys, 5.12.0001.1187 (English), 8/17/2006 12:16:32, 1110528 bytes
Driver: C:\WINDOWS\system32\drivers\pfmodnt.sys, 3.00.0000.0012 (English), 8/17/2006 12:32:56, 8192 bytes
Driver: C:\WINDOWS\system32\ctdlang.dat, 8/17/2006 12:22:58, 323640 bytes
Driver: C:\WINDOWS\system32\ctdnlstr.dat, 8/17/2006 12:22:58, 44567 bytes
Driver: C:\WINDOWS\system32\ctstatic.dat, 8/17/2006 12:11:10, 313207 bytes
Driver: C:\WINDOWS\system32\ctdaught.dat, 8/17/2006 12:11:10, 53932 bytes
Driver: C:\WINDOWS\system32\a3d.dll, 80.00.0000.0003 (English), 8/17/2006 12:32:46, 33792 bytes
Driver: C:\WINDOWS\system32\commonfx.dll, 5.12.0001.1187 (English), 8/17/2006 12:20:36, 87552 bytes
Driver: C:\WINDOWS\system32\ctaudfx.dll, 5.12.0001.1187 (English), 8/17/2006 12:20:48, 536576 bytes
Driver: C:\WINDOWS\system32\ctsblfx.dll, 5.12.0001.1187 (English), 8/17/2006 12:21:30, 548352 bytes
Driver: C:\WINDOWS\system32\cteapsfx.dll, 5.12.0001.1187 (English), 8/17/2006 12:21:12, 160768 bytes
Driver: C:\WINDOWS\system32\CTEXFIFX.dll, 5.12.0001.1187 (English), 8/17/2006 12:21:44, 1170432 bytes
Driver: C:\WINDOWS\system32\CTHWIUT.DLL, 5.12.0001.1187 (English), 8/17/2006 12:22:02, 61952 bytes
Driver: C:\WINDOWS\system32\CT20XUT.DLL, 5.12.0001.1187 (English), 8/17/2006 12:22:00, 158720 bytes
Driver: C:\WINDOWS\system32\ctemupia.dll, 5.12.0001.1187 (English), 8/17/2006 12:22:02, 108032 bytes
Driver: C:\WINDOWS\system32\piaproxy.dll, 5.12.0001.1187 (English), 8/17/2006 12:14:28, 73728 bytes
Driver: C:\WINDOWS\system32\ctdproxy.dll, 5.12.0001.1187 (English), 8/17/2006 12:16:38, 71680 bytes
Driver: C:\WINDOWS\system32\sfman32.dll, 5.12.0001.0130 (English), 8/17/2006 12:14:50, 21504 bytes
Driver: C:\WINDOWS\system32\data\cts20x.dat, 8/17/2006 12:11:10, 2091 bytes
Driver: C:\WINDOWS\system32\data\ctd20x.dat, 8/17/2006 12:11:10, 15899 bytes
Driver: C:\WINDOWS\system32\SBXFi.ico, 2/7/2005 18:45:22, 766 bytes
Driver: C:\WINDOWS\system32\XFi.bmp, 2/7/2005 18:45:22, 3128 bytes
Driver: C:\WINDOWS\system32\ctcoinst.dll, 3.00.0002.0036 (English), 8/17/2006 12:33:36, 81920 bytes
Driver: C:\WINDOWS\system32\ctdvinst.dll, 0.04.0000.0036 (English), 8/17/2006 12:33:36, 146432 bytes
Driver: C:\WINDOWS\system32\drivers\ctdvda2k.sys, 5.13.0001.0461 (English), 8/17/2006 12:23:00, 340176 bytes

WarpigNJ · « **Reply #7 on:** April 19, 2007, 03:56:30 PM »

Name: NVIDIA GeForce 7950 GT
Device ID: PCI\VEN_10DE&DEV_0295&SUBSYS_220719F1&REV_A1\4&797C7A&0&0008
Driver: C:\WINDOWS\system32\DRIVERS\nv4_mini.sys, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 3994624 bytes
Driver: C:\WINDOWS\system32\nv4_disp.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 4527488 bytes
Driver: C:\WINDOWS\system32\nvsvc32.exe, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 159810 bytes
Driver: C:\WINDOWS\system32\nvhwvid.dll, 6.14.0010.9371 (), 10/22/2006 13:22:00, 581632 bytes
Driver: C:\WINDOWS\system32\nvapi.dll, 6.14.0010.9371 (), 10/22/2006 13:22:00, 212992 bytes
Driver: C:\WINDOWS\system32\nvoglnt.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 5644288 bytes
Driver: C:\WINDOWS\system32\nvcpl.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 7700480 bytes
Driver: C:\WINDOWS\system32\nvmctray.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 86016 bytes
Driver: C:\WINDOWS\system32\nvwddi.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 81920 bytes
Driver: C:\WINDOWS\system32\nvnt4cpl.dll, 6.14.0010.11060 (English), 10/22/2006 13:22:00, 286720 bytes
Driver: C:\WINDOWS\system32\nvmccs.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 229376 bytes
Driver: C:\WINDOWS\system32\nvdisps.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 5619712 bytes
Driver: C:\WINDOWS\system32\nvdispsr.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 5255168 bytes
Driver: C:\WINDOWS\system32\nvgames.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 3047424 bytes
Driver: C:\WINDOWS\system32\nvgamesr.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 3203072 bytes
Driver: C:\WINDOWS\system32\nvmccss.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 188416 bytes
Driver: C:\WINDOWS\system32\nvmccssr.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 458752 bytes
Driver: C:\WINDOWS\system32\nvmobls.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 888832 bytes
Driver: C:\WINDOWS\system32\nvmoblsr.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 2859008 bytes
Driver: C:\WINDOWS\system32\nvvitvs.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 2924544 bytes
Driver: C:\WINDOWS\system32\nvvitvsr.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 2973696 bytes
Driver: C:\WINDOWS\system32\nvwss.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 1236992 bytes
Driver: C:\WINDOWS\system32\nvwssr.dll, 6.14.0010.9371 (English), 10/22/2006 13:22:00, 1732608 bytes
Driver: C:\WINDOWS\help\nvcpl.hlp, 10/22/2006 13:22:00, 177897 bytes
Driver: C:\WINDOWS\help\nvwcplen.hlp, 10/22/2006 13:22:00, 55444 bytes
Driver: C:\WINDOWS\system32\nvcod.dll, 1.00.0000.0035 (English), 10/22/2006 13:22:00, 35840 bytes
Driver: C:\WINDOWS\system32\nvcodins.dll, 1.00.0000.0035 (English), 10/22/2006 13:22:00, 35840 bytes

Name: SiS PCI to USB Enhanced Host Controller
Device ID: PCI\VEN_1039&DEV_7002&SUBSYS_70021039&REV_00\3&267A616A&0&1B
Driver: C:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 26624 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/3/2004 20:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 57600 bytes
Driver: C:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 7168 bytes

Name: SiS 7001 PCI to USB Open Host Controller
Device ID: PCI\VEN_1039&DEV_7001&SUBSYS_70011039&REV_0F\3&267A616A&0&1A
Driver: C:\WINDOWS\system32\drivers\usbohci.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 17024 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/3/2004 20:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 57600 bytes

Name: SiS 7001 PCI to USB Open Host Controller
Device ID: PCI\VEN_1039&DEV_7001&SUBSYS_70011039&REV_0F\3&267A616A&0&19
Driver: C:\WINDOWS\system32\drivers\usbohci.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 17024 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/3/2004 20:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 57600 bytes

Name: SiS 7001 PCI to USB Open Host Controller
Device ID: PCI\VEN_1039&DEV_7001&SUBSYS_70011039&REV_0F\3&267A616A&0&18
Driver: C:\WINDOWS\system32\drivers\usbohci.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 17024 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/3/2004 20:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 57600 bytes

Name: SiS PCI IDE Controller
Device ID: PCI\VEN_1039&DEV_5513&SUBSYS_55131039&REV_01\3&267A616A&0&15
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 95360 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 2/28/2006 08:00:00, 3328 bytes

Name: PCI standard ISA bridge
Device ID: PCI\VEN_1039&DEV_0965&SUBSYS_00000000&REV_48\3&267A616A&0&10
Driver: C:\WINDOWS\system32\DRIVERS\isapnp.sys, 5.01.2600.0000 (English), 2/28/2006 08:00:00, 35840 bytes

Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1039&DEV_0756&SUBSYS_00000000&REV_02\3&267A616A&0&00
Driver: n/a

Name: Standard Dual Channel PCI IDE Controller
Device ID: PCI\VEN_1039&DEV_0182&SUBSYS_01801039&REV_01\3&267A616A&0&28
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 95360 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 2/28/2006 08:00:00, 3328 bytes

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_1039&DEV_000A&SUBSYS_00000000&REV_00\3&267A616A&0&38
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 68224 bytes

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_1039&DEV_000A&SUBSYS_00000000&REV_00\3&267A616A&0&30
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 68224 bytes

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_1039&DEV_0004&SUBSYS_00000000&REV_00\3&267A616A&0&08
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 2/28/2006 08:00:00, 68224 bytes

Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&267A616A&0&C3
Driver: n/a

Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&267A616A&0&C2
Driver: n/a

Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&267A616A&0&C1
Driver: n/a

Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&267A616A&0&C0
Driver: n/a

-

Denholm · « **Reply #8 on:** April 19, 2007, 06:41:38 PM »

Another quick question. Do you have the AMD Dual Core Patch?

WarpigNJ · « **Reply #9 on:** April 19, 2007, 09:58:36 PM »

I do. Installed it on Monday.

airhog99 · « **Reply #10 on:** April 20, 2007, 06:35:10 AM »

Even if the problem showed up when adding the Saitek it could still be a problem in AH which is exposed by subtle timing or scheduling differences. I have no idea why mucking with FPS-limiting in AH fixed my problems, but it did. I also blamed hardware and drivers, but ALL my other programs worked just fine (Flightsim X and FarCry, etc).

BTW, did you consider a force feedback stick such as Sidewinder? I'm still trying to decide which stick to get.

Denholm · « **Reply #11 on:** April 20, 2007, 08:34:06 AM »

I have no other ideas at this time. I myself have an X52 which had 0 problems with AH. The only things I could've thought of would be the AMD Dual Core Patch, the RAM not being correctly inserted, two different types of RAM in the system not supported by the MB, and the un-even amount of RAM in the system.

WarpigNJ · « **Reply #12 on:** April 20, 2007, 08:38:30 AM »

Quote

Originally posted by airhog99
Even if the problem showed up when adding the Saitek it could still be a problem in AH which is exposed by subtle timing or scheduling differences. I have no idea why mucking with FPS-limiting in AH fixed my problems, but it did. I also blamed hardware and drivers, but ALL my other programs worked just fine (Flightsim X and FarCry, etc).

BTW, did you consider a force feedback stick such as Sidewinder? I'm still trying to decide which stick to get.

I will try that tonight to see if it makes a difference. My display shows a constant 60, so I imagine limiting it to 60 won't impair the graphics.

To be honest, I did not consider a force feedback. I've had 2 versions of the Microsoft Sidewinder since Air Warrior and I've loved both. The second one, the Pro, I've had since AWIII and it had gotten a little loose over the years. When I came back to AH this week after a 4 year hiatus, I decided to treat myself to a new stick. I heard great things about the Saitek X52 in online reviews and from squaddies, so I ran with it.

IMHO, earlier Saitek's that I tried over the years seemed a little cheap and junky. This one, however, is nice and meaty and really feels like it can take a beating. Plus the LCD clock on the throttle just makes me happy.