Question Locked

Persistant Images

0 helpful
28 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have been asked and seen on numerous occasions an image that seems to stick to a monitor usually running some version of windows. Often times, this image is of a menu item that the user brought up and selected. The menu clears but part of it leaves it's image behind. To clear it, some people reboot their machine, others log off and log back on, still others have found that merely changing the resolution temporarily makes the image(s) disappear.

My question is, what causes this to begin with. Is it a corrupt video driver or something more serious such as corrupt video memory or a bad GPU. The one thing we know for certain is it is not the monitor. The monitor can be changed out and the problem remains.

Note that I are not looking for a solution so much as the cause. Since an image can not be uploaded here, I have provided this link to show an example of the problem. http://www.borfaxer.com/PersistentMenuItem.jpg

28 replies

by older mycroft

Based on the flimsy amount of fractured information you have supplied ~[i]if this is the extent of your knowledge[/i]~ you cannot possibly rule out ANY possibility.

You ought to be amassing much more information including technical specifications that occur at each of the instances you mention, then by applying simple rules of commonality you can begin to rule out the circumstances which do not apply - leaving you with probabilities from whence to start.

I have neither the time [b]nor the inclination[/b] to fart around playing your guessing games. For instance:

I answer - you say "No, it's not that."
I answer again - you say "No, it's not that either."

Sod it - you answer first.

Either come up with tangible criteria, or have it away on your toes.

I suspect most of the other peers would have you supply far more information also. Your's is a 'question' that is severely lacking in any hint of the genuine. Try again. ;)

BTW - the word is PERSIST[b][u]E[/b][/u]NT.

by wal02

He's not asking for a fix so you don't have to say "Try this...." He's asking for the cause of the problem which is clearly seen in the photo supplied. I have also experienced it and don't know why it happens only how to remove it. Your snide remarks don't help anyone

by older mycroft

Maybe you ought to get new reading glasses, so's you can spot when posts have been edited.

When I replied to his original post there WASN'T any image link!

If I hadn't been so strong, no-one would have an image to look at. ;)

by ron k.

I have that problem occasionally. I have 2 computers sitting here, an old Dell Pentium D and a new quad-core. The fragment lingers longer on the older, slower pc than it does on the new one. I've always chalked it up to being a bug in Windows. I'm running XP MCE on one, XP Pro on the other.
I don't recall ever having a fragment stick long enough to make me want to reboot.

by older mycroft

The only times I've witnessed what your newly supplied image is showing, the problem lay with an underpowered system that had widgets sitting on the right-hand side of the screen.

Try running without ANY widgets visible. I think the widgets are sucking clock cycles for their individual screen refreshes, leaving these ghosts on the main desktop background.

by ic-it

Yahoo search and Widgets.
All are eating up the performance.

by userfriendlypc

I was able to reproduce the problem on an older HP laptop with nothing more than XP Home addition on it. Nothing else installed. I am beginning to suspect that this is a Windows problem as I could not produce it using Ubuntu.

by older mycroft

What is the spec of this machine? CPU, RAM, on-board graphics? Which Service Pack? Was it fully updated?

What resolution was it running at?

How many possible TSR programs might there have been on it?

How many SysTray entries?

How many minutes before the latent images began to appear?

I'm sorry, but simply saying you reproduced the problem on 'an older HP laptop' tells us nothing.

by userfriendlypc

OldER Mycroft is correct. The last paragraph including the link to the picture was added after however, the remarks were in poor taste and lacked professionalism. Correct me if I am wrong that this forum is here to help others and 90% of that post failed to do so. I just chalked them up to a lack of communication skills and pettiness. With that said, I should have been a little more clear thus the reason for the additional paragraph.

by santeewelding

Taste and professionalism are not your ward.

The ward is two-way.

You dropped yours. You drop it now.

No amount of recrimination will save you.

by neal j

I stumbled upon this thread and thought I would research the problem within my own department as we have seen this before and not just on Windows machines though it has been awhile. I was dismayed by the responses made by two individuals here.

First, the original response was totally unnecessary and fails by any stretch of the imagination to help this gentleman whatsoever. You vehemently express, "I have neither the time nor the inclination to fart around playing your guessing games" and yet you respond in kind. Your reply was neither helpful or warranted.

From reading the 1st paragraph alone, I knew what he was asking, perhaps because I have seen this phenomenon before however the question could have been phrased better.

The bottom line here is that if you don't have an answer or a solution, either ask, use constructive criticism to correct or don't reply at all. Replying in such a non-helpful manner only shows your lack of maturity and makes you look like a common playground bully.

I'll get off my soapbox now and try and find the answer you seek.

by older mycroft

By your own admission, the image link was added AFTER my response and you "[i]should have been a little more clear thus the reason for the additional paragraph.[/i]"

So, correct ME if I'm wrong - but where's the rub? Without the image and the extended text, your post WAS just a guessing game.

You didn't express yourself clearly, you didn't supply any image to illustrate the problem (every picture tells a story) and if I hadn't prompted you into action you'd never have supplied any further info.

So, you've felt it necessary to point out that I [u]WAS CORRECT[/u] in that my initial response arose from an unillustrated & unamended post, yet you fail to have recognised the beneficial effect that came from said post? Very odd!

I also notice you are giving out the Thumb to anyone who defends you - [b]NOT ANYONE WHO SUPPLIES THE ANSWER YOU WANT![/b]

That only reinforces my original judgment of you and your post.

by neal j

6 responses of which 5 appear to be a rant. Grow up and quit acting like a 5 year old throwing a tantrum. I see from other posts that you do this a lot. It's time you were called on it.

As for the amount of time I have spent on here, that has little to do with my credentials as I have over 30 years experience, a Masters Degree in Computer Science and a Bachelor of Science in Computer Engineering with years of Continuing Education. How about you?

Enough said.

by older mycroft

Eight days on TR and you've appointed yourself as the Witch-finder General?

I refer you to my explanation because I can't be bothered to type the same thing twice:

https://www.techrepublic.com.com/5208-7343-0.html?forumID=101&threadID=324968&messageID=3242270&tag=content;leftCol

Also - [u]BE AWARE[/u] - you are judging me by how you 'think' I responded to an initial post that was [b]HEAVILY AMENDED[/b] quite a few days before you even saw it. Had you read the original post you would not be so quick to climb up on your cross!

by choppit

If the issue goes away, then it's probably related to hardware performance (or lack of). Not that I'd trust it, but what does the windows experience test tell you?

by neal j

In my research, the problem IS a Windows Bug that has continued through many versions of windows. This does not appear to be video card or driver specific but has been known to occur across many hardware configurations with the commonality that the OS is a version of Windows.

The solution I found is to go into Windows Performance Options and deselect the option for "Fade out menu items after clicking".

In XP you can access this at: Control Panel > System > Advanced (tab) > Performance settings (button) > Visual effects (tab)

I'm certain that the locations are similar in Vista and Windows 7.

by userfriendlypc

That solved the problem on the machine I was testing it with. Thanks Neil

by older mycroft

Which is what Myself, IC-IT & Choppit all mentioned before you 'came up with the answer'.

Oddly, despite your "[i]30 years experience, a Masters Degree in Computer Science and a Bachelor of Science in Computer Engineering with years of Continuing Education[/i]" you still missed the fact that shutting off all the eye candy mainly only helps vastly underpowered systems.

Just as ALL Nvidia and ATI/AMD graphics cards also feature settings for Image Quality vs Performance Level.

Windows Bug - MY ARSE!

Did you get your MSc and your BSc off the internet?

by userfriendlypc

When I started this thread, remember, I mentioned that I had been asked about this which prompted the thread in the first place.

Here are the specs of the machine that I was first asked about. Since there were so many different machines this occurred on, I didn't find it necessary to list them all. The question was as follows:

"Just to add to the wackiness of this issue. I have experienced the same thing on Windows XP 64-bit, with a PCIe ATI card, with all the latest patches. The thing is that it was fine until sometime in the last couple of days!

The system contains a 700 Watt P/S, i5 650 Intel processor, 8 gigs of ram on an Asus MB.
The video card is an ATI Radeon 5570 with 1 GB of memory."

That doesn't sound under powered to me. I'm going with a Windows BUG since it also does not appear to occur with any other operating system to include Linux and the Mac OS.

Have a nice day!

by santeewelding

[i]Note that I are not looking for a solution so much as the cause.[/i]

If I read you both right.

by ic-it

A bug can not be fixed with an adjustable windows setting. ;-)

It was a display performance adjustment that you made to correct the issue.

by userfriendlypc

However wouldn't disabling that setting also disable the underlying instruction set sent by the OS to the GPU?

by ic-it

Mostly the second para., but it is all a nice read.

I don't think anyone should have gotten testy, however I must admit, I over-estimated your skill level and did not initially present a very thorough explaination due to time constraints.
take care.

http://techinfo.co.in/wordpress/?p=830

by nexs

After reading this thread, I'm glad i wasn't involved Gulp.
But I'd say it would not be a windows bug or an underpowered machine (i've seen some pretty shite PCs and i've never seen this problem before), I'd be content to call it a 'mismatched setting choice'.

This discussion is closed to new replies.