Titanfall Install Problem
When i try to install titanfall for the first time this error comes up http://s17.postimg.org/dvfkumx0v/Titanfall.png i am really confused as i have windows 7 enterprise and it says you need to ...
Forum Discussion
This is the other half of it
---------------------
Sound Capture Devices
---------------------
Description: Headset Microphone (Sound Blaster Tactic(3D) Alpha)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: USBAUDIO.sys
Driver Version: 6.01.7601.18208 (English)
Driver Attributes: Final Retail
Date and Size: 7/12/2013 10:40:58, 109824 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
-------------------
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: Sound Blaster Tactic(3D) Alpha
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x041E, 0x30DC
FF Driver: n/a
Device Name: Sound Blaster Tactic(3D) Alpha
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x041E, 0x30DC
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a
Poll w/ Interrupt: No
-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x8C2D
| Matching Device ID: usb\root_hub20
| Service: usbhub
| Driver: usbhub.sys, 11/27/2013 01:41:37, 343040 bytes
| Driver: usbd.sys, 11/27/2013 01:41:03, 7808 bytes
|
+-+ Generic USB Hub
| | Vendor/Product ID: 0x8087, 0x8008
| | Location: Port_#0001.Hub_#0001
| | Matching Device ID: usb\class_09
| | Service: usbhub
| | Driver: usbhub.sys, 11/27/2013 01:41:37, 343040 bytes
------------
PS/2 Devices
------------
+ HID Keyboard Device
| Vendor/Product ID: 0x046D, 0xC52B
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 11/20/2010 10:33:25, 33280 bytes
| Driver: kbdclass.sys, 7/14/2009 01:48:04, 50768 bytes
|
+ HID Keyboard Device
| Vendor/Product ID: 0x413C, 0x2005
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 11/20/2010 10:33:25, 33280 bytes
| Driver: kbdclass.sys, 7/14/2009 01:48:04, 50768 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 7/13/2009 23:19:57, 105472 bytes
| Driver: kbdclass.sys, 7/14/2009 01:48:04, 50768 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x046D, 0xC52B
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouhid.sys, 7/14/2009 00:00:20, 31232 bytes
| Driver: mouclass.sys, 7/14/2009 01:48:27, 49216 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 11/20/2010 13:33:57, 63360 bytes
| Driver: sermouse.sys, 7/14/2009 00:00:20, 26624 bytes
| Driver: mouclass.sys, 7/14/2009 01:48:27, 49216 bytes
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 63.8 GB
Total Space: 114.1 GB
File System: NTFS
Model: Samsung SSD 840 Series ATA Device
Drive: D:
Free Space: 937.4 GB
Total Space: 953.9 GB
File System: NTFS
Model: Seagate Expansion USB Device
Drive: E:
Free Space: 0.3 GB
Total Space: 0.3 GB
File System: NTFS
Model: Samsung SSD 840 Series ATA Device
--------------
System Devices
--------------
Name: High Definition Audio Controller
Device ID: PCI\VEN_8086&DEV_8C20&SUBSYS_85761043&REV_05\3&11583659&0&D8
Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.01.7601.17514 (English), 11/20/2010 10:43:43, 122368 bytes
Name: AMD Radeon HD 7800 Series
Device ID: PCI\VEN_1002&DEV_6818&SUBSYS_23211787&REV_00\4&3834D97&0&0008
Driver: n/a
Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_8086&DEV_8C14&SUBSYS_85341043&REV_D5\3&11583659&0&E2
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010 13:33:48, 184704 bytes
Name: PCI standard ISA bridge
Device ID: PCI\VEN_8086&DEV_8C5C&SUBSYS_85341043&REV_05\3&11583659&0&F8
Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 6.01.7600.16385 (English), 7/14/2009 01:48:27, 15424 bytes
Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_8086&DEV_8C10&SUBSYS_85341043&REV_D5\3&11583659&0&E0
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010 13:33:48, 184704 bytes
Name: Intel(R) Management Engine Interface
Device ID: PCI\VEN_8086&DEV_8C3A&SUBSYS_85341043&REV_04\3&11583659&0&B0
Driver: n/a
Name: Standard AHCI 1.0 Serial ATA Controller
Device ID: PCI\VEN_8086&DEV_8C02&SUBSYS_85341043&REV_05\3&11583659&0&FA
Driver: C:\Windows\system32\DRIVERS\msahci.sys, 6.01.7601.17514 (English), 11/20/2010 13:33:44, 31104 bytes
Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.01.7600.16385 (English), 7/14/2009 01:45:46, 48720 bytes
Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.01.7600.16385 (English), 7/14/2009 01:52:21, 24128 bytes
Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.01.7601.18231 (English), 8/5/2013 02:25:45, 155584 bytes
Name: Universal Serial Bus (USB) Controller
Device ID: PCI\VEN_8086&DEV_8C31&SUBSYS_85341043&REV_05\3&11583659&0&A0
Driver: n/a
Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_8086&DEV_0C01&SUBSYS_85341043&REV_06\3&11583659&0&08
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010 13:33:48, 184704 bytes
Name: Standard Enhanced PCI to USB Host Controller
Device ID: PCI\VEN_8086&DEV_8C2D&SUBSYS_85341043&REV_05\3&11583659&0&D0
Driver: C:\Windows\system32\drivers\usbehci.sys, 6.01.7601.18328 (English), 11/27/2013 01:41:11, 53248 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (English), 11/27/2013 01:41:11, 325120 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (English), 11/27/2013 01:41:37, 343040 bytes
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_8086&DEV_0C00&SUBSYS_85341043&REV_06\3&11583659&0&00
Driver: n/a
Name: Standard Enhanced PCI to USB Host Controller
Device ID: PCI\VEN_8086&DEV_8C26&SUBSYS_85341043&REV_05\3&11583659&0&E8
Driver: C:\Windows\system32\drivers\usbehci.sys, 6.01.7601.18328 (English), 11/27/2013 01:41:11, 53248 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (English), 11/27/2013 01:41:11, 325120 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (English), 11/27/2013 01:41:37, 343040 bytes
Name: Ethernet Controller
Device ID: PCI\VEN_10EC&DEV_8168&SUBSYS_85541043&REV_0C\4&33CE3517&0&00E2
Driver: n/a
Name: SM Bus Controller
Device ID: PCI\VEN_8086&DEV_8C22&SUBSYS_85341043&REV_05\3&11583659&0&FB
Driver: n/a
Name: High Definition Audio Controller
Device ID: PCI\VEN_1002&DEV_AAB0&SUBSYS_AAB01787&REV_00\4&3834D97&0&0108
Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.01.7601.17514 (English), 11/20/2010 10:43:43, 122368 bytes
I was particularly interested, myself, in these two:
Driver File Version: 8.17.0010.1247 (English)
Driver Version: 13.251.0.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 12/6/2013 22:01:52, 1318552 bytes
WHQL Logo'd: Yes
Driver Name: HdAudio.sys
Driver Version: 6.01.7601.17514 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 11/20/2010 10:44:23, 350208 bytes
Both are a problem. The first because there is a Beta version that works better, the second because it is well over three years old. Additionally, I saw that there are entries for the Radeon audio system (aboard the GPU). There is a potential conflict between that audio and the Sound Blaster headset's audio. Have you specifically turned that off anywhere?
There may be more, but DxDiag reports aren't a specialty of mine.
