Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: Lazerr on August 14, 2009, 09:15:28 PM

Title: Lazerr's trials and tribulations
Post by: Lazerr on August 14, 2009, 09:15:28 PM
Still getting lockups like crazy... I dont know what else to do.
Title: Re: Lazerr's trials and tribulations
Post by: Denholm on August 14, 2009, 10:23:04 PM
Here's a list of things to check:

How many processes are running (Make sure you select the option to view processes from all users)?
Are you running onboard video?
Are you using outdated video drivers (possibly faulty)?
Are you running onboard sound?
Do you have security software running while playing the game?
Is there a possibility of malicious software running/hiding in your system?
Title: Re: Lazerr's trials and tribulations
Post by: WMLute on August 15, 2009, 07:43:21 AM
Still getting lockups like crazy... I dont know what else to do.

Lazerr... what kinda lockups are you getting?

The white screen crash so many are having?

Something else?
Title: Re: Lazerr's trials and tribulations
Post by: Eagleclaw on August 15, 2009, 09:06:51 AM
Denholm beat me to the possibility of viruses, need a DXDIAG and a few major game settings please. Also check to see if CPU usage is 100% when you are playing ACES HIGH.
Title: Re: Lazerr's trials and tribulations
Post by: The Fugitive on August 15, 2009, 09:41:51 AM
The problem is you have a real weak computer.....see the dxdiag below.

Start out by first making sure your computer is "clean and mean". Defrag it, then get your processes down to under 30 (hit control alt delete, click the processes tab and see how many you have running in the lower left corner of that window) Alacrity (http://alacritypc.kensalter.com/download.html) is a good program to use to get them turned off.

Once you get your computer lean and mean, you have to set the game up so it will be as easy on your computer. These are Skuzzy's suggestions on those set-ups.

1)  Make sure the "Maximum Texture Size" is set to 256, no higher, in the "Video Settings".
2)  Make sure the anti-alias slider is set to off (all the way left).
3)  In the game, make sure the only "Options->Graphic Detail->Advanced" option checked is "Bump Map Terrain".

Try it out like that at first. See how it works. If you have no troubles with it like that try turning on a few things to get as much "eye candy" with out it crapping out. Good luck!


------------------
System Information
------------------
Time of this report: 8/10/2009, 16:10:37
       Machine name: YOUR-XHTR8HVC4P
   Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 1 (2600.xpsp1.020828-1920)
           Language: English (Regional Setting: English)
System Manufacturer: HP Pavilion 061
       System Model: DM181A-ABA a305w
               BIOS: Version 3.21
          Processor: Intel(R) Celeron(R) CPU 2.70GHz, ~2.7GHz
             Memory: 1526MB RAM
          Page File: 351MB used, 3029MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.0001.0904 32bit Unicode

------------
DxDiag Notes
------------
  DirectX Files Tab: No problems found.
      Display Tab 1: The file nv4_disp.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
        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 FX 5500
     Manufacturer: NVIDIA
        Chip type: GeForce FX 5500
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0326&SUBSYS_00000000&REV_A1
   Display Memory: 256.0 MB
     Current Mode: 1024 x 768 (32 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0010.7776 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 7/16/2005 17:09:00, 3908608 bytes
      WHQL Logo'd: No
  WHQL Date Stamp: None
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 7/16/2005 17:09:00, 3198208 bytes
Device Identifier: {D7B71E3E-4066-11CF-D07D-0A2000C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0326
        SubSys ID: 0x00000000
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
 Deinterlace Caps: {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {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
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {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_BOBVerticalSt retch
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {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: Realtek AC97 Audio
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_8086&DEV_24C5&SUBSYS_3189109F&REV_02
        Manufacturer ID: 65535
             Product ID: 65535
                   Type: WDM
            Driver Name: ALCXWDM.SYS
         Driver Version: 5.10.0000.5260 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 7/1/2003 02:05:36, 756444 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 100, 48000
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
Title: Re: Lazerr's trials and tribulations
Post by: chewiex on August 16, 2009, 07:56:34 AM
Windows XP SP1? WOW, you might want to get the Windows updates and get it up to SP3. I had issues a while back running AH2 in Win XP SP2 until I updated to SP3. That could make a difference.

 :salute
DasChewy
Title: Re: Lazerr's trials and tribulations
Post by: Blooz on August 16, 2009, 08:34:42 AM
The vid driver shown is not compatible with the Geforce 5500FX card for starters.

Didn't I tell you that earlier? Maybe it was someone else.

You need to delete it and roll back to an older driver like 66.93 or so.

Also, go with default skins and sounds..custom skins and sounds may be causing problems too.
Title: Re: Lazerr's trials and tribulations
Post by: bj229r on August 16, 2009, 08:54:48 AM
I had an FX5700 with an AMD 3200 or somethin, as I recall the newest drivers gave me a lock-up white screen on alt-tab back in (ya spend LOTS of time surfing web as P47 climbs out)...I tried 6-7 different drivers, I think the older 66.93 worked best. At the end of that machine, I would get freezups for 5-10 seconds...(ALWays seemed to occur while plane was in dive) Sometimes it came back, usually in tower, sometimes had to hard reboot--Looking back, may have been heat-related, damn hard to keep AMD's cool--same fans have my Intel chip running in low 30's
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 17, 2009, 03:54:01 PM
Thanks for the tips guys, ill try some out.  Are the drivers I want to delete in my NVIDIA folder then?
Title: Re: Lazerr's trials and tribulations
Post by: Skuzzy on August 17, 2009, 03:55:54 PM
I assume you are not running with the "Detail Terrain" option checked.  I also assume you have not installed the high resolution texture pack.

With that 5000 series video card, you should not have done either.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 17, 2009, 04:00:06 PM
Yeah I have detailed terrain turned off, and just bump map selected.

Game runs okay when before its locked up too.. ive ran all the spyware tools, and AH is basically the only thing I have installed on this PC.
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 17, 2009, 04:05:20 PM
If what fugitive posted is indeed your dxdiag output:

Sound driver outdated.
Video driver outdated.
Windows XP needs SP3

Do an uninstall of the video and sound card drivers...then get a program called "driver cleaner" and run that to get rid of the latent stuff left behind from the uninstalls...then install the new drivers.
Title: Re: Lazerr's trials and tribulations
Post by: WMLute on August 18, 2009, 02:23:04 AM
Thanks for the tips guys, ill try some out.  Are the drivers I want to delete in my NVIDIA folder then?

I posted this for a squaddie.  Hope it helps. 
The CCleaner bit is "optional" but it is something I always do.
The rest is "Nvidia driver removal 101" and should be followed.

Uninstall the driver using ADD/REMOVE progarms in the Contol Panel.

Unplug the cable to your NIC card.

Reboot into SAFE MODE.  (hit f8 a bunch when you reboot).

When it boots up if Windows tries to find the driver hit CANCEL.

Run DriverSweeper (found HERE (http://www.guru3d.com/category/driversweeper/))

Run CCleaner (found HERE (http://download.cnet.com/ccleaner/)) and delete all registry entries associated w/ the driver you uninstalled.

Reboot.

Install new driver.
Title: Re: Lazerr's trials and tribulations
Post by: Denholm on August 18, 2009, 09:19:39 AM
XP SP3 may be too much. He does need SP2, though. Just in case you're wondering, some systems will crash when updating their XP service packs. I know our family's system will go BSOD when attempting to switch to SP3.
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 18, 2009, 09:57:04 AM
XP SP3 may be too much. He does need SP2, though. Just in case you're wondering, some systems will crash when updating their XP service packs. I know our family's system will go BSOD when attempting to switch to SP3.
If that happens, you have an internal issue or a missing prerequisite for SP3. Are you using Microsoft update or Windows update? What anti-virus are you using?



I recommend using Microsoft update by going to update.microsoft.com and choose custom...it will scan your system (hardware and all) then show you a list of recommended and optional updates...assuming you haven't tried that already.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 18, 2009, 10:15:34 AM
Thats what I did... Ive got SP3 installed. 

I might be onto something heat related..
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 18, 2009, 11:29:09 AM
When using driver cleaner, do I just clean Nvidia Display choice, and leave "Nvidia Chipset" and "NVIDIA Physx" alone?
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 18, 2009, 11:34:55 AM
When using driver cleaner, do I just clean Nvidia Display choice, and leave "Nvidia Chipset" and "NVIDIA Physx" alone?
No dump them all.

Question, that last crash you had and posted for Skuzzy...did that happen before you started changing drivers?
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 18, 2009, 11:41:26 AM
Ya, Happened in game. 
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 18, 2009, 11:56:49 AM
Ya, Happened in game. 
Ok...time to update the drivers because that last crash was definitely a conflict of some sort.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 18, 2009, 12:03:32 PM
I see I only had Microsoft Framework 1.0 installed, I couldnt even run driver cleaner till I got 2.0.

jeeesh talk about being bad at updates. :D
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 18, 2009, 12:09:18 PM
Yeah...  :aok ...I think most people are that way.
Title: Re: Lazerr's trials and tribulations
Post by: Denholm on August 18, 2009, 12:09:26 PM
If that happens, you have an internal issue or a missing prerequisite for SP3. Are you using Microsoft update or Windows update? What anti-virus are you using?



I recommend using Microsoft update by going to update.microsoft.com and choose custom...it will scan your system (hardware and all) then show you a list of recommended and optional updates...assuming you haven't tried that already.
I tried manual install, Microsoft Update, and Windows Update. All I can say is that HP stinks when it comes to making sturdy systems.

No, I'm not interested in installing SP3.
Title: Re: Lazerr's trials and tribulations
Post by: WMLute on August 18, 2009, 01:29:24 PM
Try DriverSweeper, not DriverCleaner.

Do NOT uninstall the CHIPSET drivers.

Video and PhysX only.
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 18, 2009, 01:41:24 PM
Lute...never mind...I was gonna go through this step by step explanation but I'm not gonna waste the time...just suffice to say, uninstall everything to do with the piece of hardware you're doing the update on.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 18, 2009, 03:39:50 PM
thanks for your time guys.. I learn a lot through this game. :D
Title: Re: Lazerr's trials and tribulations
Post by: WMLute on August 18, 2009, 03:45:12 PM
Lute...never mind...I was gonna go through this step by step explanation but I'm not gonna waste the time...just suffice to say, uninstall everything to do with the piece of hardware you're doing the update on.

If you are wanting to "uninstall everything to do w/ the piece of hardware you're doing the update on", and the hardware is the Video Card, the chipset has nothing to do with it and needs to be left ALONE.  Two totally seperate pieces of hardware.

Uninstall the chipset drivers if you are upgrading your motherboard.

He just happens to have a mobo w/ an nvidia chipset on it.

What you suggested would be like uninstalling the Via drivers on for your mobo to upgrade a driver for a video card.  It's just plain wrong.

One of the reasons I say use DriverSweeper over DriverCleaner (besides the fact it's free) is that DriverSweeper will knows the diff. between a Chipset and a Video driver.
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 18, 2009, 04:08:58 PM
Well then Lute, you and I are talking totally different things...for one thing if that dxdiag Fugitive posted is Lazerr's system, that is not a video chip on the mobo...secondly removing the chipset driver for a video card or any other peripheral card is not the same as trying to remove the chipset driver for a mobo chipset...and believe it or not if there is a driver for a mobo chipset that had to be installed in the first place, then it can be uninstalled without a problem and then upgraded just like any other hardware driver...Intel does it all the time with their mobos.

This is where the base drivers, et al should be removed unless the uinstall of the front end management program removes the drivers as well (some do, some don't) but it's best to check here to make sure:

(http://i25.tinypic.com/2uszgck.jpg)



I agree that drive rsweeper has a more intuitive system than driver cleaner...I guess I'm too used to the back end processes of driver cleaner (pro version)...
Title: Re: Lazerr's trials and tribulations
Post by: WMLute on August 18, 2009, 05:57:27 PM
If you have an NForce chipset on your mobo, when you go to uninstall the Video Driver in Add/Remove you are given the options to remove...

Chipset
Video
PhysX

Lazer would want to pick the Video and PhysX and NOT the Chipset as he would be uninstalling the Chipset driver for his motherboard, and that is NOT what he wants to do to upgrade the driver for his FX series card.

He only needs to remove the Video and PhysX and should leave the Chipset alone.

Where you seem to be confused is the NForce chipset his mobo apparently uses.

When you use DriverCleaner it cleans ALL The Nvidia stuff, including the mobo chipset drivers, whereas DriverSweeper will not.
(At least that is a problem DC used to have and I have not really used the program since it went to $ for it)
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 18, 2009, 08:00:59 PM
Sorry Lute, but HP doesn't use the Nforce mobos in their celeron based systems...it was the AMD based mobos...and there is no sign of Nforce chipset in that dxdiag.

Here is a screen cap of a system with an Nforce chipset based mobo (XFX nForce 680i LT SLI Motherboard) and an Nvidia 9500GT graphics card...using the driver unistall option in device manager:

(http://i28.tinypic.com/sfgfw6.jpg)




If you would like me to go further and post blow by blow pics on the video driver uninstall I can...not gonna affect my Nforce chipset drivers since they are separate driver instances:


(http://i29.tinypic.com/a3flvb.jpg)

Title: Re: Lazerr's trials and tribulations
Post by: WMLute on August 18, 2009, 09:37:00 PM
I was confused about his post.

He musta been using DriverCleaner and THAT had the option for the chipset uninstall.

I misunderstood and thought he saw that in Add/Remove programs when he selected Nvidia for the uninstall.
(which gives you the option for chipset, video, and physX when you use it)

But please do post pics of a full uninstall of a video driver for me.

Lord knows I don't have a clue about such things and will probably learn something.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 03:10:04 PM
Why is it, that after uninstalling my Onboard Graphics... (Intel 82845G) it always reappears after restarting my computer? 
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 19, 2009, 03:15:16 PM
Why is it, that after uninstalling my Onboard Graphics... (Intel 82845G) it always reappears after restarting my computer? 
It's because Windows still recognizes it...I think it's one of those chips that SP2 or SP3 has embedded in the driver set...see if you can turn it off in your bios...should be something in there to redirect the default video output.

Title: Re: Lazerr's trials and tribulations
Post by: Skuzzy on August 19, 2009, 03:22:26 PM
You have to disable the chip in the system BIOS.  Failing that, you can disable it in the device manager, but that often has some side effects.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 03:24:32 PM
thanks, for another prompt reply. :D
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 03:32:12 PM
These dang lock-ups.  Sometimes I can play an entire day without a lock, sometimes not even 30 seconds.  AH2.13 ran perfect on this system, with moderate framerates, and NEVER a disco..unless there was maybe a arena reset.  These lock-ups record as a disco on my score.  I've updated drivers, and ran all the spyware toold, cleaned old drivers out.  Im at a loss, what else can a guy do short of buying a new PC?

Any tips would be appreciated, you guys have been more than enough help already! :salute
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 19, 2009, 03:47:22 PM
You have made a lot of changes in the past couple of days...has there been any common event happening when you lock up?

What is your current settings in the video settings? (resolution and texture size)
Post a screen shot of your running processes before and after you use whatever system game optimizer you're using please.
What directory is the game installed in?
Custom sounds?
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 03:56:02 PM
Custom sounds yes..
Running game at 1024 textures..
Resolution 1024X768

This is what usually happens when I lockup.  It is very random remember.  The screen will freeze, sometimes my desktop mouse pointer will appear and I can move it over my frozen AH screen.  I can hit any random button on the keyboard and you will her the "dunk" sound, like an invalid keystroke.  In order to get rid of the locked screen, I have to hit the power button on the computer.  Sometimes, I need to hit Ctrl+Alt+Delete to get that pointer I was talking about to appear. I've only got 19 processes running, just the vitals to keep the computer stable.

I guess I can try running the game in 256 textures, but Im sure it will lock running that too.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 04:16:06 PM
Got another serious error message after reboot (lockup @ 256 textures), same as before.  This time before the system shutdown, there was a blue screen with a bunch of white text on it, that came and went so fast I couldnt read a word off it.:(
Title: Re: Lazerr's trials and tribulations
Post by: Tigger29 on August 19, 2009, 04:36:00 PM
I once had a similar problem a while ago...

My problem ended up being improper sound drivers.  I was using a 'LTB' brand of USB headphones, and the drivers they had posted on their website were for a 'newer' version of hardware, which coincidentally looked almost identical to the 'older' version.  I ended up finding their FTP site for drivers and was able to find the proper drivers which corrected my problems.

I would only have problems during specific times though... Shutting off the engine in almost any GV would cause a lockup like that... likewise sometimes some tread noises and once in a rare while just launching a GV would cause it.  It never acted up while in an aircraft though.

Now this might not be your exact problem, but try to pay attention to what was happening in the game when the lockups occur... maybe we can isolate it that way...
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 04:38:04 PM
Im downloading updated sound drivers right now.  No new noises are introduced when the lockups occur, just seems very random. :(
Title: Re: Lazerr's trials and tribulations
Post by: Tigger29 on August 19, 2009, 04:38:12 PM
Yes, when you uninstall a device, windows will simply reinstall it next start up.  You have to 'disable' it from device manager, or from within BIOS (if you have this option, it is the preferred way to do it)
Title: Re: Lazerr's trials and tribulations
Post by: Eagleclaw on August 19, 2009, 04:57:58 PM
Making changes to my computer, I always Defragment, this helps the RAM do its stuff. Clears out clutter and moves it, etc. This may or may not help your problem, but I recommend it after driver changes, deleting and uninstallation either way.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 05:44:40 PM
Would my page file being set entirely too high maybe cause this?
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 19, 2009, 06:16:17 PM
Paging file "usage" could contribute to it...that is all the processes running while your system is on...total allocated paging file has no effect.

This is going to be painful I know...find your settings and sounds folders for Aces High and copy them somewhere safe...then uninstall the game...run Wise Registry Cleaner or RegCure to clean out the old registry entries...update the sound drivers as Tigger said...then defragment your hard drive...reboot...re-install the game...no custom sounds, no hi res pak...copy your settings folder back to the Aces High directory...download IOBit game booster (if you don't already have it)...turn it on...and start the game...set your textures to 512...disable the downloading of custom skins...set detailed terrain and bumpmap terrain to on...object detail to fastest...ground detail range to center...leave gamma alone...play the game.

If you don't have any lockups...reinstall the hires pak...and try again with 1024 textures...if no lockups again, copy your sounds folder back and try again...

The testing phases should take you 2 or 3 days before you make further changes.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 06:30:02 PM
sounds good..im going to start that tonight before I go to bed :)
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 08:37:21 PM


Technical Information
Error Message: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER (Q293078)
 
 

 
 
Follow these steps to solve the problem with a video device driver

You received this message because a device driver installed on your computer caused Windows to stop unexpectedly. This type of error is referred to as a "stop error." A stop error requires you to restart your computer.

Solution

--------------------------------------------------------------------------------


There are two options you can use to try to fix the problem. If the first option doesn't work, then try the second.

Option 1: Install the most current device driver for your video card

Use Windows Update to check for and install updates.

Go online to the Windows Update website:


Windows Update


Note
If Microsoft Update is installed, you'll be taken to the Microsoft Update website.

Click Custom to check for available updates.

In the left pane, under Select by Type, click Hardware, Optional. Select the updates for a video device driver, click Review and install updates, and then click Install Updates.


Notes

If there are no updated drivers listed on Windows Update, we recommend you contact the manufacturer of the video card for additional support. Let them know that you received an error for a video device driver and ask if product updates are available.

If there are no updated drivers on Windows Update and you don't know the name of the video card manufacturer, we recommend you contact your computer manufacturer for additional information and support.

How do I find my computer manufacturer?

Click Start, click Run, type msinfo32, and then click OK. Your computer manufacturer is listed as the System Manufacturer in the right pane of the System Information window.

Click to go online to see contact information for most computer manufacturers

Option 2: Manually decrease Hardware Acceleration for your video adapter

This procedure prevents the display device driver from programming the hardware incorrectly, but you might lose some display functionality and performance.

Click Start, click Control Panel, and then double-click Display.
Click the Settings tab, and then click Advanced.
Click the Troubleshoot tab, move the Hardware Acceleration slider to None, and then clear the Enable Write Combing check box.
Click OK, and then click OK.
 

--------------------------------------------------------------------------------
 
look at this... this is after Deleting game, defrag, deleting skins, sounds, and running at 512 textures.  Registry cleaned and all.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 08:38:53 PM
Is this for my Gforce card or the damn onboard crap I cant get to stay uninstalled?
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 08:45:34 PM
Here is my up to date DXDIAG after a few changes...


System Information
------------------
Time of this report: 8/19/2009, 20:43:11
       Machine name: YOUR-XHTR8HVC4P
   Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp.080413-2111)
           Language: English (Regional Setting: English)
System Manufacturer: HP Pavilion 061
       System Model: DM181A-ABA a305w
               BIOS: Version 3.21
          Processor: Intel(R) Celeron(R) CPU 2.70GHz
             Memory: 1014MB RAM
          Page File: 142MB used, 2301MB 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 FX 5500
     Manufacturer: NVIDIA
        Chip type: GeForce FX 5500
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0326&SUBSYS_00000000&REV_A1
   Display Memory: 256.0 MB
     Current Mode: 1024 x 768 (16 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0010.6693 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 10/29/2004 16:50:00, 3736704 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 10/29/2004 16:50:00, 2826944 bytes
Device Identifier: {D7B71E3E-4066-11CF-9579-0A2000C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0326
        SubSys ID: 0x00000000
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
 Deinterlace Caps: {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {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
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {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_BOBVerticalSt retch
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
                   {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: Realtek AC97 Audio
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_8086&DEV_24C5&SUBSYS_3189109F&REV_02
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ALCXWDM.SYS
         Driver Version: 5.10.0000.6300 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 9/24/2008 10:40:22, 4122368 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Standard
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 8000, 192000
Static/Strm HW Mix Bufs: 26, 25
 Static/Strm HW 3D Bufs: 26, 25
              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
---------------------
            Description: Realtek AC97 Audio
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: ALCXWDM.SYS
         Driver Version: 5.10.0000.6300 (English)
      Driver Attributes: Final Retail
          Date and Size: 9/24/2008 10:40:22, 4122368 bytes
              Cap Flags: 0x41
           Format Flags: 0xFFF
Title: Re: Lazerr's trials and tribulations
Post by: Delirium on August 19, 2009, 08:52:15 PM
Did you try updating the video drivers and then saw the error?

For a video card that old, I wouldn't recommend the newest drivers, it can cause a lot more trouble than they fix. I'm trying to remember what driver Skuzzy recommended but I'm getting old and my memory isn't what it used to be.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 08:54:01 PM
Im using the 66.93 or some numbers close to that, that they have recommended :)
Title: Re: Lazerr's trials and tribulations
Post by: Blooz on August 19, 2009, 10:51:45 PM
The driver listed in the dxdiag as nv4_disp.dll is the latest nvidia driver (the 190.38).

You haven't changed anything yet.

I also noticed your in 16bit color ...that should be 32bit. That's an easy fix in your Control Panel under Display.

And my advice is to turn everyhing in game down or off until you at least get the game running. Then you can turn on stuff. You're choking your vid card to death with the settings you're using.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 11:41:17 PM
okay this is what I just figured out.  My computer said nv4_disp.dll is failing....

How can I have the 190.38 when it said I was installing 66.93?   Im confused.  Can anyone get me a link to the driver I should have?

Ive tried running the game at 256 textures with no skins and sounds, and it still locked up.  That low of settings shouldnt be killing my card.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 19, 2009, 11:42:05 PM
Driver Version: 6.14.0010.6693 (English)


No, i have the 66.93 installed.
Title: Re: Lazerr's trials and tribulations
Post by: ColTomb on August 19, 2009, 11:47:09 PM
This is for FX5500 Windows XP     http://www.nvidia.com/object/winxp_175.19_whql.html
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 20, 2009, 12:04:03 AM
IIRC. that driver does not support the 5500FX. 
Title: Re: Lazerr's trials and tribulations
Post by: TequilaChaser on August 20, 2009, 12:47:21 AM
Heya Lazer,
if it was me, 1st thing I would do is completely remove / uninstall every and all  video display drivers, even use a drive cleaner/sweeper to make sure you have not overlooked or left any remants of drivers on your system

then when you reboot your PC, go directly into your BIOS , and make sure if possible that you have disabled your "onboard video" in the bios.....that is if you have the option to do this....

next, once you boot up and are back at the desktop of your PC....go directly to control panel/system/hardware/device manager and try to locate the display adapter........ seeing that you have both onboard integrated video and also an add-on video card, you will probably have 2 listed under display adapter tab, make sure you rightclick on the onboard video click propertys then click disable this device....

then go install the driver needed for your add-on video card and make sure it is set to use this device ( enabled )  in the control panel/system/hardware/device manager area...... the onboard video should have a RED X showing it as disabled......

also it should be at 32 bit True Color / Highest ( or at least 24 bit  although I am not sure if any, that 24 bit even listed on Display settings anymore since like windows98 or 2000? )

hope this helps......

edit: he is using a 5 yr old video driver LOOK AT THE DATE OF IT:
Quote
Driver Name: nv4_disp.dll
   Driver Version: 6.14.0010.6693 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 10/29/2004 16:50:00, 3736704 bytes

(others please correct me if I have misinformed Lazer, please )
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 20, 2009, 12:49:40 AM
Thanks TC! Ill give it a shot in the mornin.
Title: Re: Lazerr's trials and tribulations
Post by: Skuzzy on August 20, 2009, 06:34:18 AM
Lazerr, please do not keep starting threads.  It makes it more difficult to get a time line of what and how things are progressing.
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 20, 2009, 01:53:39 PM
Sounds good.. things still suck. :D
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 20, 2009, 01:55:22 PM
All of the above steps complete, still total lockup.  Same error each time, driver is failing. 
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 20, 2009, 02:01:40 PM
Skuzzy do you know which driver I should be using?  Is there a way you can link it for me?  When i installed the last driver I could have swore it was 66.93, the recommended one.
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 20, 2009, 03:36:55 PM
This is for FX5500 Windows XP     http://www.nvidia.com/object/winxp_175.19_whql.html
Lazerr...according to the advanced search on Nvidia's website going through the archived drivers search...the one ColTomb linked is the latest available for that video card.

The only other choice is to uninstall the driver under your device manager then go to update.microsoft.com and see if there is a driver there...it's going to be at least a year old and you won't have the forceware software with it but it will work with that card.

After everything you have done the only other thing I can think of is that video card is about to puke on you...  :(
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 20, 2009, 04:08:38 PM
Well, that card he listed is an error on Nvidia's part, It will not work with this card.  Other 5500FX users have the same review.   WHAT i did get to work so far, is using Omega Drivers in the 66.93 version, so far things seem to be running pretty damn good, I guess tonight will tell.


I really appreciate all the help you guys were, learned quite a bit through all this hassle.  I guess thats what you get for running a dinosaur system. :D
Title: Re: Lazerr's trials and tribulations
Post by: Eagleclaw on August 20, 2009, 04:35:31 PM
Mine is a 2000 XP Home Edition and I run the game fine. Mine is a sad, sad dino.  :D
Title: Re: Lazerr's trials and tribulations
Post by: gyrene81 on August 20, 2009, 04:42:44 PM
Hey Lazerr...how do you think we learned this stuff? Weren't born with it...just had the Excedrin moments before you did, and probably more frequently...  :huh  :lol  :D


Eagleclaw...how do you get 2000 XP Home Edition...did you upgrade to XP from Win2000?
Title: Re: Lazerr's trials and tribulations
Post by: Eagleclaw on August 20, 2009, 04:47:05 PM
okay, I feel really stupid, mine is a 2001 XP, not the 2000 XP. I have the Memory of two comps in this baby. Cha-ching! This thing is really old but could prolly out-do any 2002 model! Haha
Title: Re: Lazerr's trials and tribulations
Post by: Lazerr on August 20, 2009, 05:37:51 PM
okay, I feel really stupid, mine is a 2001 XP, not the 2000 XP. I have the Memory of two comps in this baby. Cha-ching! This thing is really old but could prolly out-do any 2002 model! Haha
  :lol