viben2512 Posted September 18, 2012 Share Posted September 18, 2012 Hi guys, I have recently bought the vengeance 2000 headset. However it makes different games crash. After investigation, the problem is related to some dx9 directInput incompatibility. When I launch DxDiag, dxdiag report an access problem to directInput. The error report is : AppName: dxdiag.exe AppVer: 5.3.2600.5512 ModName: dinput8.dll ModVer: 5.3.2600.5512 Offset: 00016324 Some extract of the DxDiag report: ------------------ System Information ------------------ Time of this report: 9/18/2012, 07:10:25 Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.120504-1619) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: G31M-ES2L BIOS: Award Modular BIOS v6.00PG Processor: Intel® Core2 Quad CPU Q9550 @ 2.83GHz (4 CPUs) Memory: 3198MB RAM Page File: 1314MB used, 3768MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.2600.5512 32bit Unicode DxDiag Previously: Crashed in DirectInput (stage 1) ------------- Sound Devices ------------- Description: Speaker(Vengeance 2000) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: USB\Vid_1b1c&Pid_0a04&Rev_0190&MI_00 Manufacturer ID: 65535 Product ID: 65535 Type: WDM Driver Name: Symphony.sys Driver Version: 5.12.0012.0426 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 4/26/2012 18:02:12, 3013760 bytes Other Files: Driver Provider: C-MEDIA Inc. HW Accel Level: Full Cap Flags: 0xF5F Min/Max Sample Rate: 100, 192000 Static/Strm HW Mix Bufs: 65, 64 Static/Strm HW 3D Bufs: 65, 64 HW Memory: 0 Voice Management: Yes EAX 2.0 Listen/Src: Yes, Yes I3DL2 Listen/Src: No, No Sensaura ZoomFX: No Registry: OK Sound Test Result: Not run Description: Realtek HD Audio output Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_1458C603&REV_1000 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RtkHDAud.sys Driver Version: 5.10.0000.6602 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 3/27/2012 17:03:36, 6100072 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Full Cap Flags: 0xF5F Min/Max Sample Rate: 8000, 192000 Static/Strm HW Mix Bufs: 33, 32 Static/Strm HW 3D Bufs: 33, 32 HW Memory: 0 Voice Management: No EAX 2.0 Listen/Src: Yes, Yes I3DL2 Listen/Src: Yes, Yes Sensaura ZoomFX: No Registry: OK Sound Test Result: Not run --------------------- Sound Capture Devices --------------------- Description: MicIn(Vengeance 2000) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: Symphony.sys Driver Version: 5.12.0012.0426 (English) Driver Attributes: Final Retail Date and Size: 4/26/2012 18:02:12, 3013760 bytes Cap Flags: 0x41 Format Flags: 0x440 Description: Realtek HD Audio Input Default Sound Capture: No Default Voice Capture: No Driver Name: RtkHDAud.sys Driver Version: 5.10.0000.6602 (English) Driver Attributes: Final Retail Date and Size: 3/27/2012 17:03:36, 6100072 bytes Cap Flags: 0x41 Format Flags: 0xFFF ----------- DirectMusic ----------- DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS DLS Version: 1.00.0016.0002 Acceleration: n/a Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port Speaker(Vengeance 2000), Software (Kernel Mode), Output, DLS, Internal Mappeur MIDI Microsoft [Émulé], Hardware (Not Kernel Mode), Output, No DLS, Internal SynthÚ. SW table de sons GS Mic [Émulé], Hardware (Not Kernel Mode), Output, No DLS, Internal Registry: OK Test Result: Not run ------------------- DirectInput Devices ------------------- Poll w/ Interrupt: No Registry: OK When I remove the vengeance USB connector, everything works fine. When I disable the realtek sound card, the problem remain. NB my drivers, dx9 ... are up to date with this issue, the headset is useless. So any ideas ? Thx for your help. Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted September 18, 2012 Corsair Employee Share Posted September 18, 2012 Viben, are you using our Corsair drivers or the default Microsoft drivers when using the headset? Does it crash with either driver? Link to comment Share on other sites More sharing options...
viben2512 Posted September 18, 2012 Author Share Posted September 18, 2012 I have installed the Vengeance2000SW_1_7_051512.exe, so I think I use the Corsair Driver when I plugged the vengeance USB Connector. It crashs with the Vengeance2000SW_1_7_051512.exe installed. I have uninstalled it, so I am using the windows driver, but it crashs also Link to comment Share on other sites More sharing options...
Toasted Posted September 19, 2012 Share Posted September 19, 2012 What games are you trying to run? Link to comment Share on other sites More sharing options...
viben2512 Posted September 19, 2012 Author Share Posted September 19, 2012 - Mass Effect 3 - Ghost Recon Online - Witcher 2 These 3 games crash with the headset. When it is unplugged, everythings works. I have not tried my other games. Link to comment Share on other sites More sharing options...
cchan0535 Posted September 20, 2012 Share Posted September 20, 2012 My significant other is having the same issue on her machine (PC specs are hers). Borderlands 2 crashes on calls to DirectInputCreate() when she tries to load the game with the Vengeance 2000 plugged in. Works fine otherwise, including with a different headset (cheapo Logitech unit). She's running the 1.7 drivers. We've tried uninstalling and reinstalling the Corsair drivers, "repairing" DirectX by running both the consumer and developer redistributables, uninstalling vendor drivers for various other USB devices (webcams, keyboards, etc.) and removing those devices where practical, disabling system audio devices (both the SoundMAX audio on the mobo and the HD audio devices on the vid card), and uninstalling and re-installing the game itself. You can sort of bypass the issue by plugging the Vengeance 2000 in *after* you launch the game. Mic will work and you'll be able to hear all voice communication (in a normal Steam voice chat when we tested), but all the actual audio output from the game is dead, presumably being routed to whatever device the engine latched onto instead of the Vengeance when it loaded up. Any help (aside from "Get off Windows XP," heh) would be greatly appreciated! Edit: One piece of debug info I forgot: dxdiag crashes when the Vengeance is plugged in with the same sort of DirectInput errors. Pull the headset and it runs fine. Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted September 20, 2012 Corsair Employee Share Posted September 20, 2012 We have seen issues with the Vengeance 2000 not working with many games, especially ones on Steam for Windows XP. One of the reasons why I asked the original poster whether the Windows drivers were being used or if it was our drivers is that if the Microsoft drivers crashed too, then there is a conflict with the the OS and our headset when gaming. Due to the cease of support on XP though, it would be difficult to work with Microsoft to get this resolved. So I apologize to anyone experiencing the dreaded issue but unfortunately, at this time we have no fix for this beyond suggesting an upgrade to a newer OS like Windows 7. Link to comment Share on other sites More sharing options...
viben2512 Posted September 20, 2012 Author Share Posted September 20, 2012 I would like to thanks everyone that try to solve my problem. I understand there is no simple solution to solve it. NB. When I plugged after the game has launched, i experienced signifiant drop rate. Thx guys. Link to comment Share on other sites More sharing options...
cchan0535 Posted September 21, 2012 Share Posted September 21, 2012 RAM GUY, Disappointing, but not surprising given that WinXP has finally reached EOL. Guess it's time to upgrade! Thanks for your time! Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted September 27, 2012 Corsair Employee Share Posted September 27, 2012 Viben, or anyone else experiencing this issue, is it possible to get the minidump file for this error? We'd like it to analyze the source of the issue. If you have it, let me know please! Link to comment Share on other sites More sharing options...
cchan0535 Posted October 5, 2012 Share Posted October 5, 2012 Hey RAM GUY, I had stopped following this thread, sorry, but yes, if you still want them, I have all of the Borderlands 2 minidumps from my misadventures. There are north of 20 of them. You can have any or all of them, just let me know where to send 'em. Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted October 8, 2012 Corsair Employee Share Posted October 8, 2012 You can email them to me, cchan0535. They would be greatly appreciated as we're trying to see why it happens. Link to comment Share on other sites More sharing options...
cchan0535 Posted October 10, 2012 Share Posted October 10, 2012 Hey RAM GUY, Think you had a copy/paste issue there when telling me where to send them, but I just discovered the attachment feature is actually enabled on this forum, so I'll just upload them here. Just a note: I went ahead and updated the problem machine to Win7 over the weekend, so the BL2 dumps that I saved before that are all that I'm going to be able to give you, data-wise. Hope it helps!Borderlands2_DX9_Veng2000_Minidumps.zip Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted October 10, 2012 Corsair Employee Share Posted October 10, 2012 Great! These would be a big help! Thank you very much. Link to comment Share on other sites More sharing options...
wmounsey Posted November 30, 2012 Share Posted November 30, 2012 I have recently purchased the vengeance 2000 wireless headset... I have windows XP SP3 and I am having this problem... When dxdiag crashes, it registers the following in the event viewer... Thanks in advance: Faulting application dxdiag.exe, version 5.3.2600.5512, faulting module dinput8.dll, version 5.3.2600.5512, fault address 0x00016324. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.