test content
What is the Arc Client?
Install Arc

Unplayable: Character Creation

SystemSystem Member, NoReporting Posts: 178,019 Arc User
[Tech Support Queue #107271]

Unable to get past skill selection screen of character creation. If I select "NEXT" the game crashes.

Tried changing graphic settings etc... but no effect. Worked just fine in OB though I never could edit my uniform or my officers uniforms at the starbase tailor or it would cause the game to crash.

dxdiag info:

System Information
Time of this report: 2/17/2010, 18:01:10
Machine name: DOUG-PC
Operating System: Windows Vista™ Ultimate (6.0, Build 6002) Service Pack 2 (6002.vistasp2_gdr.091208-0542)
Language: English (Regional Setting: English)
System Manufacturer: Foxconn
System Model: BLOODRAGE
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (8 CPUs), ~2.8GHz
Memory: 2294MB RAM
Page File: 1563MB used, 3253MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
DxDiag Version: 7.00.6002.18107 32bit 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 4870
Manufacturer: ATI Technologies Inc.
Chip type: ATI display adapter (0x9440)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_9440&SUBSYS_24411682&REV_00
Display Memory: 1910 MB
Dedicated Memory: 1018 MB
Shared Memory: 891 MB
Current Mode: 5040 x 1050 (32 bit) (59Hz)
Monitor: Matrox TripleHead2Go Digital Edition
Driver Name: atiu9pag.dll,aticfx32.dll,aticfx32.dll,atiumdag.dll,atidxx32.dll,atiumdva.cap
Driver Version: 8.14.0001.6091 (English)
DDI Version: 10.1
BGRA Supported: Yes
Driver Attributes: Final Retail
Driver Date/Size: 12/11/2009 11:50:12, 20480 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71EE2-D700-11CF-F962-4004A1C2C535}
Vendor ID: 0x1002
Device ID: 0x9440
SubSys ID: 0x24411682
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) 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_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) 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_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

Sound Devices
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_105B0DEB&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHDA.sys
Driver Version: 6.00.0001.5708 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 9/24/2008 01:31:06, 2171672 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
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: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Realtek Digital Output (Realtek High Definition Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_105B0DEB&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHDA.sys
Driver Version: 6.00.0001.5708 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 9/24/2008 01:31:06, 2171672 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
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: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Sound Capture Devices
Description: Microphone (Realtek High Definition Audio)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: RTKVHDA.sys
Driver Version: 6.00.0001.5708 (English)
Driver Attributes: Final Retail
Date and Size: 9/24/2008 01:31:06, 2171672 bytes
Cap Flags: 0x0
Format Flags: 0x0

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: Saitek Eclipse II Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x8021
FF Driver: n/a

Device Name: Saitek Eclipse II Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x8021
FF Driver: n/a

Device Name: Saitek Eclipse II Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x8021
FF Driver: n/a

Device Name: Saitek Eclipse II Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x8021
FF Driver: n/a

Device Name: Trip
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x18EA, 0x0004
FF Driver: n/a

Poll w/ Interrupt: No

USB Devices
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x3A37
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/10/2009 20:43:16, 196096 bytes
| Driver: usbd.sys, 1/18/2008 21:53:17, 5888 bytes
|
+-+ USB Human Interface Device
| | Vendor/Product ID: 0x18EA, 0x0004
| | Location: Port_#0001.Hub_#0001
| | Matching Device ID: generic_hid_device
| | Service: HidUsb
| | Driver: hidusb.sys, 4/10/2009 20:42:48, 12800 bytes
| | Driver: hidclass.sys, 4/10/2009 20:42:48, 39424 bytes
| | Driver: hidparse.sys, 1/18/2008 21:53:16, 25472 bytes
| |
| +-+ HID-compliant device
| | | Vendor/Product ID: 0x18EA, 0x0004
| | | Matching Device ID: hid_device

Gameport Devices
Post edited by Unknown User on

Comments

  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    ATI has a brand new driver...

    http://game.amd.com/us-en/drivers_catalyst.aspx?p=vista64/common-vista64

    ... and I'm not sure if the game fully supports the Matrox Triple Head 2 Go device.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    USSWasabi wrote:
    ATI has a brand new driver...

    http://game.amd.com/us-en/drivers_catalyst.aspx?p=vista64/common-vista64

    ... and I'm not sure if the game fully supports the Matrox Triple Head 2 Go device.

    I will check out the driver but I played in beta. This game has native support for both the Tripplehead2go and Eyefinity.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    RedRaiders wrote:
    I will check out the driver but I played in beta. This game has native support for both the Tripplehead2go and Eyefinity.

    I am not sure if the game "fully" supports those resolutions. You are pushing quite a bit of grapahics through that single card.

    Keep in mind that STO is not on ATI's list of validated software. This does not mean it wont work, but I doubt ATI or Cryptic is going to rush to get it working 100% or validated.

    Have you tried cutting down to a single display to troubleshoot?

    http://support.amd.com/us/eyefinity/Pages/eyefinity-software.aspx
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Yes and considering I played the game trough beta right up to release it doesn't make much sense that they would suddenly stop supporting it when other widescreen gamers are not having this problem. Believe it or not there were a lot of us during beta had a big thread about it and what not so if that were the case it would be known already.

    To add a little I am almost positive it has to do with editing uniforms since TONS of people had the same problem and they never actually fixed it they just made it less likely. I always had it but could at least create new characters in beta.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Well I guess trying the driver and another thought could be that the specific card you haev in your machines may be having issues handling doing it with 3 panels going. But if you tried it on a single display and it is doing it there too then it may be something else.

    When is the last time you have updated your Realtek drivers? I'm probably grabbing for staws here.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Why is the Realtek device doubled up in the diagnostic readout?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    USSWasabi wrote:
    Why is the Realtek device doubled up in the diagnostic readout?

    I couldn't even guess when the last time I updated those but since it's a sound card I doubt that would be it. Worth a try though.

    It's probably doubled up because it has multiple output devices connected right now and the thing is smarter than I am. It could even be that I was running two EVE clients at the same time. I honestly don't know but per example I can run EVE at max graphics and I have no issue, I have many widescreen games and really have no problems with them. Hell even Planetside works pretty damn well on this rig and thats a FPS.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    RedRaiders wrote:
    I couldn't even guess when the last time I updated those but since it's a sound card I doubt that would be it. Worth a try though.

    It's probably doubled up because it has multiple output devices connected right now and the thing is smarter than I am. It could even be that I was running two EVE clients at the same time. I honestly don't know but per example I can run EVE at max graphics and I have no issue, I have many widescreen games and really have no problems with them. Hell even Planetside works pretty damn well on this rig and thats a FPS.

    I was thinking abou the multiple devices hooked into it, but I think those would be slightly different devices then showing there. Almost seems like you have the device installed twice.

    Since you have Vista you can always try uninstalling the device from the device manager, restart system, and let it reinstall the drivers.

    Another note; some people were having issues with Realtek and Vista 64Bit. You may want to try the following:

    Start the Launcher, click options, and in the "Advanced Command Line" box, paste the following...

    -ignorex64check

    ... accept the changes and try loading the game.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    USSWasabi wrote:
    I was thinking abou the multiple devices hooked into it, but I think those would be slightly different devices then showing there. Almost seems like you have the device installed twice.

    Since you have Vista you can always try uninstalling the device from the device manager, restart system, and let it reinstall the drivers.

    Another note; some people were having issues with Realtek and Vista 64Bit. You may want to try the following:

    Start the Launcher, click options, and in the "Advanced Command Line" box, paste the following...

    -ignorex64check

    ... accept the changes and try loading the game.

    Ok so just reviewed the DxDiag info...

    The realtek device is listed twice because one is a sound card and the other is a digital audio output built into the MB.

    I am using Vista 32 so the 64 bit issues shouldn't effect me.

    It's cool with me though since EVE still runs works like a charm and I already know what awaits me in STO. :)
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    RedRaiders wrote:
    Ok so just reviewed the DxDiag info...

    Bah! I missed that not about 32Bit up in there. One last attempt; have you tried going into the video settings and turning everything to minimum? This happens with any character you make?

    My last question would be have you checked your memory? Memtest86 can determine if the memory is going bad. I've installed games and have had them do funky stuff because of memory while all the other games I was playing worked fine.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    USSWasabi wrote:
    Bah! I missed that not about 32Bit up in there. One last attempt; have you tried going into the video settings and turning everything to minimum? This happens with any character you make?

    My last question would be have you checked your memory? Memtest86 can determine if the memory is going bad. I've installed games and have had them do funky stuff because of memory while all the other games I was playing worked fine.

    Yep tried making different characters/races and killed the graphics as much as possible. Not worried about the memory either though it's an option of course I fail to see how it would work fine everywhere else and not work here when it did work before.

    The problem is with the game I have no doubt about that. I am a patient cat though so they will get it fixed soon enough.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Yep, still here, still can't play. Still no response at all to my ticket.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Error ticket ID: 6433347

    Would have thrown one up earlier but I generally get unknown as a response.
Sign In or Register to comment.