vista SOOOO slow - what am I missing?

[James Long]

took 4 hours to install
takes 9 minutes to boot up
takes 16 minutes to log in

the gui is ridiculously slow
its useless.

I installed drivers for it but result is the same.
updated my SoundBlaster and ati x800,
now they work better and I get sound
but OS is slow.

this system runs 3.0 GHZ Pentium, has 1 GB ram
currently using a 40gb 5400 rpm drive -
yes it would be faster if a 7200 was used
BUT that is NOT the problem.

its SLOW SLOW SLOW SLOW SLOW.

it feels like its timing out fully on something global all the time
for most everything. getting the event viewer up is
an 1/2 hour event. this is especially worse after a
fresh reboot. for a reboot I go watch an episode of
star gate.

installing the sound driver took almost an hour.
I was taking a nap because I am sick of waiting for it.

there has to SOMETHING MAJOR wrong here
but 2 installs the same way,

my ASUS hardware works perfect under win2k and winxp pro.
(smokes like all get out, too. )

I've been working on computers for 17 years so I know basically
what I am seeing. some common function is delaying the system
until it times out and this happens all the time.


I'm getting many error 10016 from dcom all the time.

Log Name: System
Source: DCOM
Date: 6/12/2006 5:36:51 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: POLARIS\james
Computer: POLARIS
Description:
The application-specific permission settings do not grant Local Launch
permission for the COM Server application with CLSID
{69486DD6-C19F-42E8-B508-A53F9F8E67B8}
to the user POLARIS\james SID
(S-1-5-21-4167444558-3471686261-2636888726-1000) from address LocalHost
(Using LRPC). This security permission can be modified using the Component
Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="DCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}"
EventSourceName="DCOM" />
<EventID Qualifiers="49152">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2006-06-12T21:36:51.000Z" />
<EventRecordID>10645</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>POLARIS</Computer>
<Security UserID="S-1-5-21-4167444558-3471686261-2636888726-1000" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Launch</Data>
<Data Name="param4">{69486DD6-C19F-42E8-B508-A53F9F8E67B8}</Data>
<Data Name="param5">POLARIS</Data>
<Data Name="param6">james</Data>
<Data
Name="param7">S-1-5-21-4167444558-3471686261-2636888726-1000</Data>
<Data Name="param8">LocalHost (Using LRPC)</Data>
</EventData>
</Event>




windows also has many of error 100,
I feel this is the root cause of the problem:


Log Name: System
Source: Microsoft-Windows-Eventlog
Date: 6/12/2006 4:15:39 PM
Event ID: 100
Task Category: Runtime problem with processing an event
Level: Error
Keywords: Service availability
User: LOCAL SERVICE
Computer: POLARIS
Description:
The service encountered an error while processing an incoming event
published from Microsoft-Windows-TaskScheduler .
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Eventlog"
Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
<EventID>100</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000020000</Keywords>
<TimeCreated SystemTime="2006-06-12T20:15:39.562Z" />
<EventRecordID>10310</EventRecordID>
<Correlation />
<Execution ProcessID="980" ThreadID="1068" />
<Channel>System</Channel>
<Computer>POLARIS</Computer>
<Security UserID="S-1-5-19" />
</System>
<UserData>
<EventProcessingFailure
xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
<Error Code="15007" />
<EventID>119</EventID>
<PublisherID>Microsoft-Windows-TaskScheduler</PublisherID>
</EventProcessingFailure>
</UserData>
</Event>


Any help would be greatly appreciated.
I have to wait for any-most-everything to happen
under this OS. this is 2nd install.
first one was same and it died.
(both were clean installs).


I have cut down the display overhead,
stopped indexing and tried to find this
but don't know what to fix.



Thanks in advance,
James

 

[R. McCarty]

Have you added DevMgr_Show_NonPresent_Devices to the
System Environment variable table and checked your Device
Manager map ( With Show Hidden Devices checked) ? -
It sounds like a system level driver is wrong or missing. I would
check the SMBus controller is properly enumerated. Vista is
also an ACPI 'Only' OS - so correct BIOS ACPI compatibility
is very important.

 

[Stephan Schaem]

I believe its a known issue and beta is not optimized yet.

- What I noticed is that is take 30% of the CPU to move a simple window around (with a X800 and latest ATI driver)
- App switching is slow, but thats ATI fault since their Vista driver (unlike nvidia) have yet to support DMA transfer for texture
swapping.
- Use insane amount of memory... my 1 gig system doing barely anything was swapping and everything took ages to open.
- Even slower then XP to boot and shutdown.

So not a speed demon, but it does make XP look antiquated. (BTW: The calculator and clock remind me of windows98 addon : Gizmos 98


Stephan

 

[James Long]

Thanks.

yes its still slow.

I did that and nothing spectacular shows up as missing.
I am however missing fs_red in non-plug-and-play-drivers if that's
anything.

None of the "Microsoft streaming this or that" stuff is connected,
probably because either ATI's or Creative's drivers aren't the latest
(creative did not have drivers for this release but DID have for an earlier
one so I used them)

I did not see any other system level drivers missing or malfunctioning.

I disabled the creative joystick port there was no driver for
and I disabled a third party pci serial port card I can't find the driver
for.
these are the only devices that did not get drivers in device manager,
when it installed.

I do not know how to "check if the SMBus controller is properly enumerated",
but...and please correct me, I'm hoping I don't need to go there.

The below listing comes out of "Problem Reports and Solutions":

Host Process for Windows Services
Description
Windows has detected a slowdown in the responsiveness of the system
Problem signature
Problem Event Name: DiagPerfShellScenario
OsBuildNumber: 5384
TroubleshooterVer: 1
Scenario Subtype: Response Monitor
OS Version: 6.0.5384.2.0.0.256.1
Locale ID: 1033

Files that help describe the problem
snapshot.tell
rundown.tell
ShellPerformanceDiagnostics_System Data.bin
View a temporary copy of these files


And, the same app, "Problem Reports and Solutions" also says
there is no keyboard or mouse driver loaded but the device manager
says there are. I believe the device managers version of that.

anyway, most Slowing down occur when you click stuff, or click stuff that
hasn't been clicked,
or invoke stuff. once its been clicked, most of the controls are slow but
using them
again and again speeds them back up. eventually, if you go through
everything a couple times,
it will all run pretty fast finally about a day later. if you have that
kind of time.


Hitting CTL-ALT-DEL during what appears to be a slowdown
alleviates the delay (mostly alleviates it)
and then, whatever I "clicked on", "asked for" or "was doing"
(which was was not happening as fast as it was supposed to...)
suddenly works at normal speed.

so this slowdown affects execution of all software.
Like I said. the event viewer takes a long time to come up the first time.

if the system has been on for an hour,
AND I have PREVIOUSLY invoked stuff once,
then THAT STUFF Works at normal speed thereafter.

but a reboot is ALWAYS SLOW.
and a first invocation of anything is always slow.

If I stop the task scheduler then things work faster.
maybe this is a false perception but it seems that way.


its really a pain, because It should not operate slow like this.
I don't know how else to describe it.


I would accept a condition in which, having booted up,
it was a little slow at first, then got going,
but that is definitely not the case here.

James