Author Topic: White screen followed by dump in Snapshot 8-12-09 9:45PM  (Read 220 times)

Offline SKColt

  • Copper Member
  • **
  • Posts: 147
      • http://home.alltel.net/wkunkle/b17intro.html
White screen followed by dump in Snapshot 8-12-09 9:45PM
« on: August 12, 2009, 09:47:58 PM »
Successful hit on Rangoon. Began egress, no planes near me. WSOD followed by Aces High must close message.

System Information
------------------
Time of this report: 8/5/2009, 21:26:41
       Machine name: WARREN
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
           Language: English (Regional Setting: English)
System Manufacturer: EVGA__
       System Model: nForce 750i SLI
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz (4 CPUs)
             Memory: 3070MB RAM
          Page File: 444MB used, 4512MB 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 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 9800 GT
     Manufacturer: NVIDIA
        Chip type: GeForce 9800 GT
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0605&SUBSYS_829C1043&REV_A2
   Display Memory: 512.0 MB
     Current Mode: 1920 x 1200 (32 bit) (60Hz)
          Monitor: SyncMaster T240HD(Digital)
  Monitor Max Res: 1920,1200
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0011.8048 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 11/12/2008 15:54:00, 6148864 bytes
      WHQL Logo'd: n/a
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 11/12/2008 15:54:00, 6188320 bytes
Device Identifier: {D7B71E3E-4545-11CF-836C-97A203C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0605
        SubSys ID: 0x829C1043
      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: SB X-Fi Audio [EF00]
 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: 6.00.0001.1368 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 10/8/2008 02:21:50, 526232 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 [EF00]
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1368 (English)
      Driver Attributes: Final Retail
          Date and Size: 10/8/2008 02:21:50, 526232 bytes
              Cap Flags: 0x0
           Format Flags: 0x0

-----------

Offline swareiam

  • Aces High CM Staff
  • Gold Member
  • *****
  • Posts: 3176
Re: White screen followed by dump in Snapshot 8-12-09 9:45PM
« Reply #1 on: August 12, 2009, 10:12:53 PM »
I have had the same problem in Snapshots, including this one, for the last two Snapshots. Any ideas what this might be?
AKWarHwk of the Arabian Knights
Aces High Scenario, FSO, and Combat Challenge Teams
Don't let your ego get too close to your position, so that if your position gets shot down, your ego doesn't go with it. General Colin Powell

Offline swareiam

  • Aces High CM Staff
  • Gold Member
  • *****
  • Posts: 3176
Re: White screen followed by dump in Snapshot 8-12-09 9:45PM
« Reply #2 on: August 13, 2009, 05:13:02 AM »
Doing a little follow up on this issue from last night.

Out of 53 pilots that flew the Snapshot last night a total of 26 of them from both sides "Vanished without a trace"
at approximately 21:40: +- 20. This is the same thing that happened in the Coal Sea Scenario
this past weekend. When just about the entire Team Zulu Strike Force "Vanished without a trace".
On the way to hit the enemy's CV.

Gentlemen,

Are there some setup configurations that we should consider or something. The last frame is Saturday
at 3:00 pm EST. It would be comforting to know that we will win or loose in a fight. Not by having
almost half the attack force white screen.

I thank you in advance for putting some time into this issue. It seems right now that scores are pretty close.
It would be nice for both sides to finish clean.

Thanks...

Redtail7
AKWarHwk of the Arabian Knights
Aces High Scenario, FSO, and Combat Challenge Teams
Don't let your ego get too close to your position, so that if your position gets shot down, your ego doesn't go with it. General Colin Powell

Offline Hepcat

  • Zinc Member
  • *
  • Posts: 21
Re: White screen followed by dump in Snapshot 8-12-09 9:45PM
« Reply #3 on: August 13, 2009, 10:00:35 AM »
I had that white screen crash also at that time, but I had already been shot down, and was just waiting in tower when I had that crash. So, more of us probably had the crash at that moment than is indicated by the "vanished without a trace" entry in the event logs.

I did also have the film recorder running at the moment of the crash.

I am sure that this matter is of the highest priority to the dev team.