Odd issue with Windows Explorer

[Guest]

Win 7 x 64 Professional.

New clean install to new SSD.

When I scroll the folder (left) panel in Windows
Explorer the folder and file names get misaligned
vertically (the rows of text overlap, scrubbing the
mouse pointer along the list re-aligns the text.

This did not happen with the identical hardware before
the new install.

Any ideas?

Thanks in advance,

 

[fritz]

Win 7 x 64 Professional.

New clean install to new SSD.

When I scroll the folder (left) panel in Windows
Explorer the folder and file names get misaligned
vertically (the rows of text overlap, scrubbing the
mouse pointer along the list re-aligns the text.

This did not happen with the identical hardware before
the new install.

Any ideas?

I have seen that happen when the Favorites, Libraries and/or Homegroup
are removed from the Windows Explorer navagation pane - causing
verticle spacing problems.

The solution, in that case, is to restore those items.

 

[Guest]

fritz> I have seen that happen when the Favorites, Libraries and/or
fritz> Homegroup are removed from the Windows Explorer navagation
fritz> pane - causing verticle spacing problems.

fritz> The solution, in that case, is to restore those items.

I have removed the favorites and the homegroup, but then I did that
on the original installation too, and did not have this problem.

I do not want that clutter on my explorer.

Anyone have any other ideas?

Thanks,

 

[Char Jackson]

fritz> I have seen that happen when the Favorites, Libraries and/or
fritz> Homegroup are removed from the Windows Explorer navagation
fritz> pane - causing verticle spacing problems.

fritz> The solution, in that case, is to restore those items.

I have removed the favorites and the homegroup, but then I did that
on the original installation too, and did not have this problem.

I do not want that clutter on my explorer.

Anyone have any other ideas?

My idea aligns well with the first idea. Enable the missing features and
test the functionality. You can always disable that stuff again if you'd
like, and who knows, maybe you'll get a few more months of trouble free
service, or however long it lasted to this point. Or maybe you'll discover
that it's not really as much clutter as you originally thought.

 

[charlie]

My idea aligns well with the first idea. Enable the missing features and
test the functionality. You can always disable that stuff again if you'd
like, and who knows, maybe you'll get a few more months of trouble free
service, or however long it lasted to this point. Or maybe you'll discover
that it's not really as much clutter as you originally thought.

Where is the page file?
How large is it?

 

[Char Jackson]

Where is the page file?
How large is it?

Did you mean to start a new thread?

 

[The Razor's Edge]

It sounds to me like a video driver problem or some memory issue.

I would download the latest drivers for your video card and not trust the
updated drivers from Microsoft. Go directly to the manufacturer.

 

[John Williamson]

It sounds to me like a video driver problem or some memory issue.

I would download the latest drivers for your video card and not trust the
updated drivers from Microsoft. Go directly to the manufacturer.

Not always the best idea. I've got a homebrew machine here running XP,
and it was running perfectly for a month 24/7 with the built in drivers.
Download and install the latest drivers for the Radeon 7000 series video
card, and it started freezing totally at random intervals, needing a
power down to recover. I reverted to the MS drivers, and the problem was
solved.

 

[John Williamson]

Did you uninstall the MS drivers before installing the real ones? Did
you disable your anti virus and any other real time malware apps before
proceeding?

Yes to all that. I have also re-installed the OS on this particular
system a number of times, with consistent results. The latest rebuild
was needed after installing a larger HD, but the problem had been there
before, with the old HD.

I have been building and modifying PCs for almost 30 years.

 

[John Williamson]

I don't know what to tell you, then. Personally, I prefer nVidia.

I'm not fussed. It's working well enough to do the job, I was only
saying that it doesn't *always* pay to go for the latest and greatest
drivers. I've had a few bits of kit "broken" by updating drivers over
the years. Rolling a driver back may lose some of the new functionality,
but it also loses the new bugs. <Shrug>

 

[Paul]

I'm not fussed. It's working well enough to do the job, I was only
saying that it doesn't *always* pay to go for the latest and greatest
drivers. I've had a few bits of kit "broken" by updating drivers over
the years. Rolling a driver back may lose some of the new functionality,
but it also loses the new bugs. <Shrug>

In my view, the *worst* driver, was the Nvidia one where the fan
control was broken, and some video cards were operating without
the fan spinning.

It's one thing, to make the odd game unplayable, quite another to
cause hardware damage by overheating. So yes, drivers should be
vetted. Let someone else test a new driver, before you do. If
the early adopters give it the OK, then install it. Don't be
the first person to try a new driver.

Paul

 

[J. P. Gilliver (John)]

I'm not fussed. It's working well enough to do the job, I was only
saying that it doesn't *always* pay to go for the latest and greatest
drivers. I've had a few bits of kit "broken" by updating drivers over
the years. Rolling a driver back may lose some of the new
functionality, but it also loses the new bugs. <Shrug>

In my view, the *worst* driver, was the Nvidia one where the fan
control was broken, and some video cards were operating without
the fan spinning.[/QUOTE]
[]
Not as drastic as that, but the drivers for the graphics "card" in this
(XP) Samsung Netbook (NC-20) which the Samsung update wizard tried to
get us to use - for months if not years after this was known (probably
still; the update wizard itself is broken on this machine) - is widely
known to cause freezes. If it wasn't for those on the sammynetbook
forum, I'd have not known to roll back the driver (lots of people had
it; lots of people had no more freezes once they rolled back), but would
have assumed the problem was somewhere else; I haven't had those freezes
since (some years now). So going for the manufacturer's latest [IIRR,
the latest from the actual video hardware manufacturer caused the same
problems as the one from Samsung] isn't always the best solution. Unless
Windows 7 is significantly different, which I doubt.

[Device Manager says the Display adapter is "VIA Chrome9 HC3 IGP"; I
don't remember what the discussions said it was, they were some years
ago.]

 

[Paul]

In my view, the *worst* driver, was the Nvidia one where the fan
control was broken, and some video cards were operating without
the fan spinning.

[]
Not as drastic as that, but the drivers for the graphics "card" in this
(XP) Samsung Netbook (NC-20) which the Samsung update wizard tried to
get us to use - for months if not years after this was known (probably
still; the update wizard itself is broken on this machine) - is widely
known to cause freezes. If it wasn't for those on the sammynetbook
forum, I'd have not known to roll back the driver (lots of people had
it; lots of people had no more freezes once they rolled back), but would
have assumed the problem was somewhere else; I haven't had those freezes
since (some years now). So going for the manufacturer's latest [IIRR,
the latest from the actual video hardware manufacturer caused the same
problems as the one from Samsung] isn't always the best solution. Unless
Windows 7 is significantly different, which I doubt.

[Device Manager says the Display adapter is "VIA Chrome9 HC3 IGP"; I
don't remember what the discussions said it was, they were some years ago.]

Yes, one other poster was trying to get his VIA based piece of crap
running, and ran into the same problem. Couldn't really find a
graphics driver that wasn't a disaster. If you have VIA built-in graphics,
best to use your time machine and go back to the year 2000 or so. Then
run Win2K or something. I don't know what VIA is "doing for a living"
these days. Presumably, not working on their graphics drivers.

Paul