Author Topic: Problems with last patch.  (Read 2790 times)

Offline Gary26

  • Nickel Member
  • ***
  • Posts: 433
Re: Problems with last patch.
« Reply #30 on: August 19, 2009, 12:46:48 PM »
Ok this is with my AV shut down and im running the game booster you spoke of and I had it shut down background stuff. I also updated my graphics driver since the last dxdiag. I took some of waffles tips and stopped auto download of skins and disabeld others skins. Playing the game at 1280x1024 and it seems to be doing ok.
-----------------
System Information
------------------
Time of this report: 8/19/2009, 10:29:10
       Machine name: HOFFSTEA-OMVMDG
   Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
           Language: English (Regional Setting: English)
System Manufacturer: Dell Computer Corporation
       System Model: Dimension 8300               
               BIOS: Phoenix ROM BIOS PLUS Version 1.10 A05
          Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz (2 CPUs)
             Memory: 1022MB RAM
          Page File: 244MB used, 2219MB 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 7600 GS
     Manufacturer: NVIDIA
        Chip type: GeForce 7600 GS
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_02E1&SUBSYS_0380196E&REV_A2
   Display Memory: 512.0 MB
     Current Mode: 1680 x 1050 (32 bit) (60Hz)
          Monitor: HP w2207 Wide LCD Monitor
  Monitor Max Res: 1680,1050
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0011.9038 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 7/14/2009 11:54:00, 5842816 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 7/14/2009 11:54:00, 7741664 bytes
Device Identifier: {D7B71E3E-41A1-11CF-9059-8B2303C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x02E1
        SubSys ID: 0x0380196E
      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 Live! 24-bit
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_10021102&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: P17.sys
         Driver Version: 5.12.0001.0514 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 6/15/2007 11:47:26, 1127936 bytes
            Other Files:
        Driver Provider: CREATIVE
         HW Accel Level: Full
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 4000, 96000
Static/Strm HW Mix Bufs: 64, 63
 Static/Strm HW 3D Bufs: 64, 63
              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 Live! 24-bit
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: P17.sys
         Driver Version: 5.12.0001.0514 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/15/2007 11:47:26, 1127936 bytes
              Cap Flags: 0x41
           Format Flags: 0xFFF
C.O. VMF-213 Hell Hawks
                                          
  VMF4

Offline 2Slow

  • Nickel Member
  • ***
  • Posts: 720
Re: Problems with last patch.
« Reply #31 on: August 19, 2009, 01:45:45 PM »
Gary, what's the status on your issues now? Did you remove your anti-virus and run some other diagnostics?

Your paging file usage is still pretty high...have you run any anti-spyware/malware programs on your system besides the anti-virus program that crashes your system?

Spybot is a good free spyware cleaner.  http://www.safer-networking.org/en/download/

Ad-Aware is another good free one.  http://www.lavasoft.com/products/ad_aware_free.php

I have used, and continue to use, both of them.  My practice is to run Spybot and then Ad-Aware. 

I also use RegCure to clean and fix my registry.  There are several flavors of registry repair products.  I would defer to which ever one gyrene81 recommends.
2Slow
Secundum mihi , urbanus resurrectio
TANSTAAFL

Offline Gary26

  • Nickel Member
  • ***
  • Posts: 433
Re: Problems with last patch.
« Reply #32 on: August 19, 2009, 02:17:30 PM »
Well my webroot has AV and AnitSP. I use ARO to fix registry issues.
C.O. VMF-213 Hell Hawks
                                          
  VMF4

Offline AKDogg

  • Gold Member
  • *****
  • Posts: 2309
      • http://aksquad.net/
Re: Problems with last patch.
« Reply #33 on: August 19, 2009, 02:32:11 PM »
To be honest with u all, the registry fix it programs are more problems then there worth.  They may fix some problems but can and will create others.  I have used registry cleaners/fixer's and I have never had good luck with them.  They may fix the immediate problem but in time they do more harm then good.  They sometimes remove registry items that shouldn't be removed and your system will start to have slow start ups (hangs for extended amount of time before finish loading to desktop), system crashing, lockups, system slowdowns, funny things happening like icons disappearing, etc...  I strongly reccommend not using registry cleaners and such.

To explain what a registry is, I refer it to a post office.  It has all the address's to files, programs, window configurations and drivers that are installed on your computer.  Windows uses this post office to find where that file, program or driver is located.  If you delete the address, guess what, windows no longer knows where that file, program or driver is at and hence u start getting errors like BSOD, lockups, program errors, icons disappearing, IE not working properly, etcc.

Believe it or not, Microsoft reccommends you reinstall your computer at least once a year if not every 6 months depending on how much you install and unistall or change hardware, or at least they did during Win98 and WinXP.  So far I am finding this to be true as I end up reinstalling my computer because of performance issues or getting errors that I can't seem to correct.
AKDogg
Arabian knights
#Dogg in AW
http://aksquad.net/

Offline gyrene81

  • Plutonium Member
  • *******
  • Posts: 11629
Re: Problems with last patch.
« Reply #34 on: August 19, 2009, 02:57:07 PM »
Good calls there 2slow...never even considered the registry cleaners...I use a couple of different ones...and I always do everything possible to double check the entries that the programs "recommend fixing"...haven't had a failure since XP Sp1.

Gary, looks like you're in pretty good shape for now.


AKDogg...there have been some registry cleaners/tweakers that caused more issues than they fixed...and yeah, it can be a real nightmare when the wrong keys get tweaked...old programs like Symantec's pc doctor are prime examples of what not to use...research is the best way to avoid things happening. I have been using Wise registry cleaner for fast scans and minor cleaning after I have uninstalled software...then the only entries I let it remove are those associated with the software...RegCure that 2Slow recommends is also a very good tool. Caution is the best policy, if you're not sure about anything to do with the registry...don't mess with it.

I guess I just ignore Microsoft advice...most of the time it's based on usage above the average home user.
jarhed  
Build a man a fire and he'll be warm for a day...
Set a man on fire and he'll be warm for the rest of his life. - Terry Pratchett

Offline AAIbyteu

  • Zinc Member
  • *
  • Posts: 22
Re: Problems with last patch.
« Reply #35 on: August 20, 2009, 04:48:08 PM »
I switched the texture to 256.  Detail on only took 20 meg more memory out of 1 gig available.  Running at 86 meg.
I don't have any problems with freezing up etc.  Runs good other than the 'white screen of death' . 
Thanks for the help, I will see how it goes.
 :aok

Offline 2Slow

  • Nickel Member
  • ***
  • Posts: 720
Re: Problems with last patch.
« Reply #36 on: August 24, 2009, 10:28:33 AM »
I have NOT had anymore "WSOD's".  I suspect the original issue must have been a fluke.  Perhaps a subsequent reboot cleared up the issue.
2Slow
Secundum mihi , urbanus resurrectio
TANSTAAFL

Offline 2Slow

  • Nickel Member
  • ***
  • Posts: 720
Re: Problems with last patch.
« Reply #37 on: August 26, 2009, 01:51:05 PM »
Hmmm....any ideas.  This is with patch 6.  Now a repeating error.

Event Type:   Error
Event Source:   Application Error
Event Category:   None
Event ID:   1000
Date:      8/26/2009
Time:      4:58:34 AM
User:      N/A
Computer:   JOEY
Description:
Faulting application aceshigh.exe, version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 61 63 65   ure  ace
0018: 73 68 69 67 68 2e 65 78   shigh.ex
0020: 65 20 30 2e 30 2e 30 2e   e 0.0.0.
0028: 30 20 69 6e 20 75 6e 6b   0 in unk
0030: 6e 6f 77 6e 20 30 2e 30   nown 0.0
0038: 2e 30 2e 30 20 61 74 20   .0.0 at
0040: 6f 66 66 73 65 74 20 30   offset 0
0048: 30 30 30 30 30 30 30 0d   0000000.
0050: 0a       
2Slow
Secundum mihi , urbanus resurrectio
TANSTAAFL

Offline gyrene81

  • Plutonium Member
  • *******
  • Posts: 11629
Re: Problems with last patch.
« Reply #38 on: August 26, 2009, 02:04:15 PM »
Yeah I had that error last night after trying tweaks to get patch 7 to work on my system...I don't read hex.  :eek:
jarhed  
Build a man a fire and he'll be warm for a day...
Set a man on fire and he'll be warm for the rest of his life. - Terry Pratchett

Offline Chalenge

  • Plutonium Member
  • *******
  • Posts: 15179
Re: Problems with last patch.
« Reply #39 on: August 26, 2009, 09:38:59 PM »
Ha! Its a memory dump and the hex says (read at the right):

Application Failure aceshigh.exe 0.0.0.0 in unknown 0.0.0.0 at offset 00000000
If you like the Sick Puppy Custom Sound Pack the please consider contributing for future updates by sending a months dues to Hitech Creations for account "Chalenge." Every little bit helps.

Offline gyrene81

  • Plutonium Member
  • *******
  • Posts: 11629
Re: Problems with last patch.
« Reply #40 on: August 26, 2009, 09:44:08 PM »
Ha! Its a memory dump and the hex says (read at the right):

Application Failure aceshigh.exe 0.0.0.0 in unknown 0.0.0.0 at offset 00000000
ROFL...wasn't even paying attention to it.  :D  :P  I need to go put in some sorties...eyeballs are buggin out and brain is disconnecting.
jarhed  
Build a man a fire and he'll be warm for a day...
Set a man on fire and he'll be warm for the rest of his life. - Terry Pratchett

Offline 2Slow

  • Nickel Member
  • ***
  • Posts: 720
Re: Problems with last patch.
« Reply #41 on: August 27, 2009, 02:19:14 AM »
I have resolved the issue I was having.  I uninstalled the ATI Radeon HD 2600 Pro AGP driver and the Catalyst software.

This returned me to the VGA mode.  After numerous attempts to get the "latest" driver from ATI installed I realized that with the error "No compatible hardware not found" that I would have to drill down and specify the driver to be installed.  One also had to ignore the warning from Windows about the driver not being WHQL.

This restored the desktop graphics to full mode and allowed one to run AH again (patch 6).

More investigation revealed a new installer from ATI that had a hot fix to stop the driver and Catalyst installs from failing.  http://support.amd.com/us/kbarticles/Pages/CatalystAGPHotfix.aspx 

This brings up a good point to consider for helping others in the future.  Just because a driver is "dated" does not mean there is a better one.  Nor does it mean that a package named '9.8' has a newer driver in it.

I am fairly certain that the issues I experienced were self inflicted by attempts to tweak things.

Fingers are now crossed.  I have dloaded the complete AH install package (patch 8).  I will install in tomorrow.
2Slow
Secundum mihi , urbanus resurrectio
TANSTAAFL