Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Old Sport on April 07, 2007, 06:31:47 PM
-
XP Home, 2002, SP2
Intel CPU 2.4G
1G ram
I've gone through several lists and have disabled lots of processes in my PC startup profile, and also have FSAutostart set to disable other programs and processes (AV, firewalls, explorer, etc) when I want to run AH. I'm down to 19 processes when I want to fly AH.
There appears to be something still cycling causing CPU usage.
With all the processes disabled, before launching AH, on the Performance tab of Task Manager, the CPU usage stabilizes at 0% with an occasional bump to 1 or 2, then after about 30 seconds CPU usage climbs to 6-8% for about 10 seconds and drops back to 0. It then keeps repeating this 30 seconds of 0% CPU usage and 10 seconds of 8% CPU usage.
On the Processes tab of Task Manager, under the CPU column, there are only two processes that show usage: System Idle Process at 99% (16K), and, simultaneous to the CPU climb to 8%, the TASKMGR.EXE shows usage at about 2% (5.8M).
Of course I don't fly AH with the Task Manager open. But is that all this is? Or is there some other process that I should disable.
Thanks and best regards.
-
Mine is all but zero, then goes to 100 and stays there for the whole time the game is running--my pc is about the same as yours (I get mine down to 29 or so processes, not REAL sure what others I can trash). the little jump ya see probably isnt significant.....do you have one of those mb utilities that constantly changes fan speed for quietness?
-
Originally posted by Old Sport
XP Home, 2002, SP2
Intel CPU 2.4G
1G ram
I've gone through several lists and have disabled lots of processes in my PC startup profile, and also have FSAutostart set to disable other programs and processes (AV, firewalls, explorer, etc) when I want to run AH. I'm down to 19 processes when I want to fly AH.
There appears to be something still cycling causing CPU usage.
With all the processes disabled, before launching AH, on the Performance tab of Task Manager, the CPU usage stabilizes at 0% with an occasional bump to 1 or 2, then after about 30 seconds CPU usage climbs to 6-8% for about 10 seconds and drops back to 0. It then keeps repeating this 30 seconds of 0% CPU usage and 10 seconds of 8% CPU usage.
On the Processes tab of Task Manager, under the CPU column, there are only two processes that show usage: System Idle Process at 99% (16K), and, simultaneous to the CPU climb to 8%, the TASKMGR.EXE shows usage at about 2% (5.8M).
Of course I don't fly AH with the Task Manager open. But is that all this is? Or is there some other process that I should disable.
Thanks and best regards.
I have the same issue, but I use msconfig and a windows hardware profile so I get mine down to 13 processes. Heres the deal, if I boot normally (regular hardware profile, and normal startup in msconfig) and I let my puter sit for 3-4 minutes, and then do my FSautostart equivilant of msconfig and rebooting to my Aces High hardware profile (13 processes), then I have no problems.
But if I boot up and immediately go to msconfig and selective startup and reboot, I get what your describing post FSautostart. I get 6-8% hits every 20 seconds, which causes insta=freeze in AH playing.
My advice to you is to boot up normally, go get a cup of joe, or a coke, come back, then do FSautostart. I bet you will find the issue goes away.
-
What is FSautostart?
-
FSautostart is a program that will shut down any services programs that you have running and dont need to run AH, then it will autolaunch AH, and when you close AH, it will automatically restart everything to normal running conditions.
Its a free download, do a google on it.
-
There are a couple of places in the registry where programs can be started without you being able to stop them. They are not accessible via any external software controls.
Most spyware/malware/virus type software uses them. but a couple of legitmate programs use it as well. Roxio is bad about this.
None of these hidden programs will show up in the Windows Task Manager. The only hint they are running is reflected in the CPU usage. Why Microsoft allows programs to hide like that is something I have never understood.
Those of you who are not worried about registry editing can search for 'Run" in the registry. There will be a lot of instances of this word, but there are two you will note as being the hidden places where programs start. "Runonce" is one of them.
And when the game is running, it should be using 100% of the CPU. That is a good thing. 99% is ok. 98% is fair. Anything less is not good.
-
Originally posted by Skuzzy
And when the game is running, it should be using 100% of the CPU. That is a good thing. 99% is ok. 98% is fair. Anything less is not good.
Oh good, I was afraid I was gonna have to upgrade agin:eek:
(can someone post a list of which Windows processes can be stopped?)
-
Thanks everyone for the input. I still haven't completely solved the issue, though it is diminishing somewhat.
It is perplexing that features of the main AV program I use are detected as dangerous malware by another AV I occasionally run, and vice versa. I wouldn't be surprised if there's something lurking that defies detection. Oh well.
Best regards
-
One other possibility is that TeamSpeak is running. On my system is uses 20% of my CPU, although it only shows as using 2% occasionally.
The best way to stop processes is to look at the bottom right region of your screen from the desktop. Right clicking a lot of those icons can give you a description or an idea of what it is or if it's important. If it's not important, exit / stop it and 1 - 2 processes disappear. I can get mine down to 17 processes when running AH using that method and ending processes manually through the task manager.
-
Originally posted by Skuzzy
...And when the game is running, it should be using 100% of the CPU. That is a good thing. 99% is ok. 98% is fair. Anything less is not good....
And if you aren't, what should I look for? I usually use about 75% of both CPU's
Here is the top part of my dxdiag
------------------
System Information
------------------
Time of this report: 2/19/2007, 13:43:37
Machine name: PRECISION670
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack
2 (2600.xpsp_sp2_gdr.050301-1519)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Precision WorkStation 670
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A07
Processor: Intel(R) Xeon(TM) CPU 2.80GHz (2 CPUs)
Memory: 1022MB RAM
Page File: 111MB used, 2349MB 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 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 Quadro FX 1300
Manufacturer: NVIDIA
Chip type: Quadro FX 1300
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_00FE&SUBSYS_023810DE&REV_A2
Display Memory: 128.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.9136 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 7/12/2006 13:19:00, 4493568 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 7/12/2006 13:19:00, 3934592 bytes
Device Identifier: {D7B71E3E-43BE-11CF-DE50-322203C2CB35}
Vendor ID: 0x10DE
Device ID: 0x00FE
SubSys ID: 0x023810DE
Revision ID: 0x00A2
Revision ID: 0x00A2
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: SoundMAX Digital Audio
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_8086&DEV_24D5&SUBSYS_01681028&REV_02
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: smwdm.sys
Driver Version: 5.12.0001.4060 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 4/9/2004 12:41:30, 612352 bytes
Other Files:
Driver Provider: Analog Devices
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 48000
Static/Strm HW Mix Bufs: 33, 32
Static/Strm HW 3D Bufs: 33, 32
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): Yes
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: SoundMAX Digital Audio
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: smwdm.sys
Driver Version: 5.12.0001.4060 (English)
Driver Attributes: Final Retail
Date and Size: 4/9/2004 12:41:30, 612352 bytes
Cap Flags: 0x41
Format Flags: 0xCCC
-----------
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
SoundMAX Digital Audio, Software (Kernel Mode), Output,
DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel
Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not
Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: Not run
-
Task Manager does not report the correct CPU usage when multiple CPU's are involved.
-
This almost smells like auto-indexing.
-
Coule be Puck. I do forget about the indexing service as it is one of the very first things I shut off in Windows.
-
Far as my rig goes, I've got an AH HW profile with auto indexing disabled, and all unessential stuff as well.
Does anyone know if XP Restore will return the Registry to the restore point?
I've looked at Regedit a little, and searched and found some "Runonce"
HKey_Current User
Three returns are in Software\Microsoft\Advanced INF Setup\IE UserData NT\0.map and under the Data column there are 3 of several dozen strings that include "runonce."
The next one is in Hkey Local Machine in a folder at Software\Microsoft\ Windows\CurrentVersion\RunOnce
In this folder is "FlashPlayerUpdate" REG_SZ and Data is: D:\Program Files\Firefox\plugins\GetFlash.exe -p
This looks like a possibility to me, but what do I know.
------
There is another folder at Windows\CurrentVersion\RunOnce and in it is (Default) REG_SZ (value not set)
Below that is another folder at Windows\CurrentVersion\RunOnceEx and in it is (Default) REG_SZ (value not set)
Under Hkey Local Machine\Software\Microsoft\Windows NT\ CurrentVersion\ Terminal Server\Install\ Software\Microsoft\Windows \CurrentVersion\ Runonce is found (Default) REG_SZ
Hkey Local Machine\ System\ControlSet001\ Control\Nls\MUILanguage\RCV2 \runonce.exe\
Inside this folder are three entries:
(Default) REG_SZ (value not set)
0 REG_BINARY 52 04 f0 0a 00 00 06 00 00 00 28 0a 00 00 06 00
1 REG_BINARY a2 b8 d7 9a 68 20 6a 91 52 97 a6 94 38 24 83 29 3d da 9d 82 b5 00 e5 98 2b fa 27 f2 bc cd d7 b8
(whew!!)
Then the same thing in Hkey Local Machine\ System\ControlSet003
Then the same thing in Hkey Local Machine\ System\CurrentControlSet
Then some repeats of the first couple in Hkey User.
If anyone has any other suggestions, let me know. Thanks!