Author Topic: unable to connect only get white screen  (Read 332 times)

Offline guncrasher

  • Plutonium Member
  • *******
  • Posts: 17419
unable to connect only get white screen
« on: August 21, 2009, 01:28:14 AM »
I just replaced the ps in my computer and when i cant connect to AH at all.  game will crash as soon as i double click on icon.  any ideas?  game was working fine before i replaced ps nothing else was replaced or any other hardware was added.

semp

System Information
------------------
Time of this report: 8/21/2009, 23:25:58
       Machine name: YOUR-A4C4B6D125
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_qfe.090206-1239)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: EP45-UD3P
               BIOS: Award Modular BIOS v6.00PG
          Processor: Intel(R) Pentium(R) D CPU 2.80GHz (2 CPUs)
             Memory: 3070MB RAM
          Page File: 429MB used, 6570MB 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 sound card was found.  If one is expected, you should install a sound driver provided by the hardware manufacturer.
          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 9800 GTX+
     Manufacturer: NVIDIA
        Chip type: GeForce 9800 GTX+
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0613&SUBSYS_0592196E&REV_A2
   Display Memory: 512.0 MB
     Current Mode: 1440 x 900 (32 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0011.8120 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 12/25/2008 22:08:00, 6168960 bytes
      WHQL Logo'd: n/a
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 12/25/2008 22:08:00, 6301344 bytes
Device Identifier: {D7B71E3E-4553-11CF-6665-992503C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0613
        SubSys ID: 0x0592196E
      Revision ID: 0x00A2
      Revision ID: 0x00A2
      Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
 Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: 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
                   {6CB69578-7617-4637-91E5-1C02DB810285}: 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
                   {6CB69578-7617-4637-91E5-1C02DB810285}: 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
                   {6CB69578-7617-4637-91E5-1C02DB810285}: 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

-------------
Sound Devices
-------------
            Description:
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID:
        Manufacturer ID:
             Product ID:
                   Type:
            Driver Name:
         Driver Version:
      Driver Attributes:
            WHQL Logo'd:
          Date and Size:
            Other Files:
        Driver Provider:
         HW Accel Level: Emulation Only
              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
               Registry: OK
      Sound Test Result: Not run

---------------------
Sound Capture Devices
---------------------
-----------
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
        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: 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: 0x8086, 0x3A35
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 8/10/2004 12:00:00, 57600 bytes
| Driver: usbd.sys, 8/10/2004 12:00:00, 4736 bytes

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

------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 8/10/2004 12:00:00, 52736 bytes
| Driver: kbdclass.sys, 8/10/2004 12:00:00, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/3/2004 18:01:08, 40840 bytes
| Driver: kbdclass.sys, 8/10/2004 12:00:00, 24576 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x0461, 0x4D16
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 8/3/2004 15:58:34, 23040 bytes
| Driver: mouhid.sys, 8/17/2001 13:48:00, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/3/2004 18:01:08, 40840 bytes
| Driver: mouclass.sys, 8/3/2004 15:58:34, 23040 bytes
you dont want me to ho, dont point your plane at me.

Offline Delirium

  • Platinum Member
  • ******
  • Posts: 7276
Re: unable to connect only get white screen
« Reply #1 on: August 21, 2009, 01:47:58 AM »
Maybe I'm just getting old, but I don't see any reference to a sound card in your DxDiag. If you don't have some type of sound device, AH will not run.

Delirium
80th "Headhunters"
Retired AH Trainer (but still teach the P38 selectively)

I found an air leak in my inflatable sheep and plugged the hole! Honest!

Offline guncrasher

  • Plutonium Member
  • *******
  • Posts: 17419
Re: unable to connect only get white screen
« Reply #2 on: August 21, 2009, 01:51:19 AM »
oh crap.  i havent installed the sound card yet.  will try that thanks.

semp
you dont want me to ho, dont point your plane at me.

Offline Delirium

  • Platinum Member
  • ******
  • Posts: 7276
Re: unable to connect only get white screen
« Reply #3 on: August 21, 2009, 02:05:13 AM »
I'll be sniffing the forums until 430am, let me know how it goes.
Delirium
80th "Headhunters"
Retired AH Trainer (but still teach the P38 selectively)

I found an air leak in my inflatable sheep and plugged the hole! Honest!

Offline guncrasher

  • Plutonium Member
  • *******
  • Posts: 17419
Re: unable to connect only get white screen
« Reply #4 on: August 21, 2009, 02:11:42 AM »
your a life saver, spent about  a hour reinstalling and was getting mad.  thanks a million  :salute :salute

semp

you dont want me to ho, dont point your plane at me.

Offline Delirium

  • Platinum Member
  • ******
  • Posts: 7276
Re: unable to connect only get white screen
« Reply #5 on: August 21, 2009, 02:21:22 AM »
I'm glad I could actually help someone, usually I am not worth much more than a feather weight book end.  :D
Delirium
80th "Headhunters"
Retired AH Trainer (but still teach the P38 selectively)

I found an air leak in my inflatable sheep and plugged the hole! Honest!

Offline batch

  • Nickel Member
  • ***
  • Posts: 640
Re: unable to connect only get white screen
« Reply #6 on: August 21, 2009, 02:46:02 AM »
and thus the importance of a dxdiag when presenting a problem....... wtg Del
"theres nothin like wakin up with a Dickens Cider" - Dickens Fruit Stand