jerky screen saver= deeper issues?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

A while back I installed new ram (I added 512, per the manual) and experienced an occasional crash, did some research and determined that the old and new ram were incompatible. Took out the 256 stick and all was well (my pc is supposed to handle 1g, according to the manufacturer, but the new memory was from a different manufacturer). Everything seems fine, except that my screen saver is still running jerky after several diagnostic attempts including a recommended hardware test that I downloaded and I reinstalled xp, but didn't reformat. I am not sure how to look for "event logs" and they may not sho this issue since I reinstalled xp. Question: is this a screen saver issue or something deeper?
 
A key question - did the screensaver behavior happen
BEFORE you installed new RAM ? Only AFTER ?

Event Viewer - go to Control Panel (Classic View),
Administrative Tools, Event Viewer.

Could be any one of many things. I would:
Run TASKMGR (ctrl-alt-del) and see what's running under
the Processes tab and which processes are getting the most
CPU time. Disregard the System Idle Process. Just LOOK,
don't terminate anything. Then exit TASKMGR and go to
Start, Run, type MSCONFIG , hit OK and look at the
Startup tab (on System Configuration Utility) and see if
there's any commonality between high-CPU-use processes
that you saw in Task Manager and those on MSCONFIG's
Startup tab. If so disable the process on the Startup tab
by unchecking it, hit Apply, OK, and re-boot.

http://netsquirrel.com/msconfig <- tutorial

You also might want to look at updating your video driver,
although, it sounds more like a rogue process sucking up
CPU time than a video driver problem . . .

I assume you have:
Done all Windows Critical Updates,
Have anti-virus software,
Have anti-spyware software
Use the Internet Connection Firewall (or other)

Also see these:
THE PARASITE FIGHT QUICK FIX PROTOCOL
http://aumha.org/a/quickfix.htm

THE PARASITE FIGHT
Finding, Removing & Protecting Yourself From Scumware
http://aumha.org/a/parasite.htm

Bugs, Glitches & Stuffups
http://www.mvps.org/inetexplorer/Darnit.htm

Dealing with Unwanted Spyware and Parasites
http://mvps.org/winhelp2002/unwanted.htm

Unexplained computer behavior may be caused by deceptive
software
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;827315#appliesto

Post back . . .

Good Luck !


-----Original Message-----
A while back I installed new ram (I added 512, per the
manual) and experienced an occasional crash, did some
research and determined that the old and new ram were
incompatible. Took out the 256 stick and all was well (my
pc is supposed to handle 1g, according to the
manufacturer, but the new memory was from a different
manufacturer). Everything seems fine, except that my
screen saver is still running jerky after several
diagnostic attempts including a recommended hardware test
that I downloaded and I reinstalled xp, but didn't
reformat. I am not sure how to look for "event logs" and
they may not sho this issue since I reinstalled xp.
Question: is this a screen saver issue or something deeper?
 
MGGP said:
A key question - did the screensaver behavior happen
BEFORE you installed new RAM ? Only AFTER ?

********

Well, I have a lot of crappola to dig through!

To answer your first question, the pc ran as smooth as can be BEFORE the install. Now there are these small issues and more program crashes than ever before.

I have been real diligent (as possible), have used Norton for years and Ad-aware for a long time also. Firewalls up, (XP standard) So as far as protection goes, I do as good as the average user. I don't think that is the issue here, but thanks for the xtra links.

I found no commonality between high-CPU-use processes and what was in MSCONFIG's startup processes.

I reviewed the event viewer, there seem to be a lot of errors, I have no clue what they all were so I will list some of them here (these are the most common AFTER the ram install)...

Under "Applications"

"Cleaning up corrupt content index metadata on c:\system volume information\catalog.wci. Index will be automatically restored by refiltering all documents."
"The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error."

Under the "systems" ...
"The server {F3A614DC-ABE0-11D2-A441-00C04F795683} did not register with DCOM within the required timeout."
"The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007041F from line 44 of d:\nt\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error."
"Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206

This is all greek to me...
 
Hello?

Damzish said:
********

Well, I have a lot of crappola to dig through!

To answer your first question, the pc ran as smooth as can be BEFORE the install. Now there are these small issues and more program crashes than ever before.

I have been real diligent (as possible), have used Norton for years and Ad-aware for a long time also. Firewalls up, (XP standard) So as far as protection goes, I do as good as the average user. I don't think that is the issue here, but thanks for the xtra links.

I found no commonality between high-CPU-use processes and what was in MSCONFIG's startup processes.

I reviewed the event viewer, there seem to be a lot of errors, I have no clue what they all were so I will list some of them here (these are the most common AFTER the ram install)...

Under "Applications"

"Cleaning up corrupt content index metadata on c:\system volume information\catalog.wci. Index will be automatically restored by refiltering all documents."
"The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error."

Under the "systems" ...
"The server {F3A614DC-ABE0-11D2-A441-00C04F795683} did not register with DCOM within the required timeout."
"The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007041F from line 44 of d:\nt\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error."
"Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206

This is all greek to me...
 
Hi Damzish,

I noticed your post after I listed mine:
"Hi all. I have a strange behavior with my screen saver. When I use Plus!
My
Pictures or Marquee mode the text or pix move in a stittering motion; they do
not smoothly move across the screen. Not a big deal but I was looking for
some ideas as to why this happens. This behavior was not happening when the
system was new about two years ago. I religiously use AV, Spybot, firewall
and I'm careful to make sure ther are no uneeded programs loading at startup
as listed in msconfig/startup. My system is Intel 2.53MHz, 1 GB memory. Any
ideas?
--
Thanks,
Russ"

Have you gotten to the bottom of your problem?
 
Sometimes if the picture files are too large that will happen. also if the
temp folders are too full it can cause problems. There are programs on the
net to help with that. Even FREE ones that work well. I am not sure if I am
allowed to mention their names here though. When you use the tools in windows
to clear all of the junk in your temp folders it leaves a lot still there.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Back
Top