Software to avoid

[swarfega]

Its updated from reports we get from forum members. So if things now work when they didnt in beta, the list will get updated.

 

[sexytool]

Understood, thanks <3
Can you remove that which is relevant only to the Beta or perhaps seperate it plz?

 

[swarfega]

if you have any suggestions with citations yes.

 

[sexytool]

Errr? I meant that at the moment, it's difficult (read; impossible) to know which has actually been tested in the RC and which hasn't.

I'm just asking if you can have 2 segments in that first post;;

One segment for software that caused problems with the beta;
Second segment for software that is known / reported to cause problems with the release candidate.

After seeing Flash10 install on IE8 with the RC i'm tempted to say a fair amount of the problems that caused the above software to BSOD the beta, have been fixed in the RC.

I've got the hard drive space, so i'm kinda tempted to make some backup images and then test the list myself...

 

[swarfega]

I think a better solution would be to close this thread down and start a new on for RC to avoid confusion.

 

[sexytool]

/signed.

 

[swarfega]

feel free to start one

 

[screwballl]

AVG 8.0 caused issues but it seems AVG 8.5 is causing problems with not only W7 but Vista, XP and 2000 as well. I have been suggesting people avoid AVG 8.5 completely.

 

[sexytool]

One of my customers runs an internet cafe, they've had massive problems with AVG 8 and several of the largely played games.

Mainly STEAM games but a couple of others were affected pretty badly too, it causes continuous crashing, low performance, corruption and worse.

 

[Zirro]

Agree that avoiding Registry Defraggers on Win 7 for the time being is sensible.
I tried Glary & Advanced System Care free (sole OS is Win 7 64-bit) had to do a system restore in both cases.

 

[sexytool]

I think it's always been a good idea regardless of OS.
I've like the idea OF registry cleaners, but in practicality they're simply buggy and cause more errors than they fix.

 

[Captain Zero]

SiSoft SANDRA. Any edition.

Possibly a coincidence but it's a wild one if it is. On RCx64, it *fried* my motherboard. I mean, bricked it entirely. Sensors went mad and nothing could be done to revive it. Avoid it like the plague...

 

[sexytool]

Have you tried taking out the CMOS battery and unplugging it from mains power at the same time?

Does the motherboard start at ALL? One that's newer than a couple of years old should have dual bios to restore it's bios image automatically.

 

[Captain Zero]

^^ Yes. Yes and yes.

I build systems, I knows my BIOS, batteries and mobos. Thanks for the tip but it's cooked.

 

[sexytool]

Poor bugger, how did you end up lucking out like that XD

EDIT: Like what motherboard?

 

[Night Hawk]

SiSoft SANDRA. Any edition.

Possibly a coincidence but it's a wild one if it is. On RCx64, it *fried* my motherboard. I mean, bricked it entirely. Sensors went mad and nothing could be done to revive it. Avoid it like the plague...

That would be really odd to see since Sandra Lite has always been one of the most preferred tools. I kind of find it hard to believe any software not having direct control over voltages, tmings, and other bios functions would cause a board to cook unless it exposed an existing flaw already present. bad cap, bad eprom, other component?

 

[sexytool]

The full version of SiS Sandra if i'm not mistaken, DOES have full control over timings, voltages etc.
It interfaces with the controllers/bios for these to accurately read the existing settings.
W7 just might have gotten a line of code - or even just a value! wrong in translation to say, SET voltage to 2.2v instead of CHECKING if it was 2.2v

 

[Captain Zero]

Yes, yes and yes. It is possible it was an existing glitch on the board (ASUS Rampage Extreme - read the review by Chris on the first page) it's a nightmare board, I just blamed SiS for frying what was already a flakey board. Maybe I'm just superstitious but, wow, I don't trust that software. It was Sis 2009 Pro Home, if I'm not mistaken. It fired up on first run, I tried a couple of sensors, benches and BLAM-O! The whole thing lit up and the sensors jumped to 256c (max?) and it went down. Yes, possible coincidence but I don't trust it. I use Everest Ultimate v5 now without any problems.

 

[sexytool]

if CPU multiplier, Voltage, FSB, PCI frequency and etc were all cranked up to max with stock cooling on a newer processor, 256*C isn't hard to beleive...

Current max safe temperature for an intel Core processor is 105*c.
AMD's average has been 60-70 for years.
The difference between stock cooling and a 120mm copper fan can be as great as 60*C.

I'm willing to say it's possible it truly was 256*C or higher.... but realistically only if you had stock cooling AND/OR it failed just before the massive overclock.

 

[Captain Zero]

This is my rig. It's far from stock cooled.