Good info about AutoGKnot problem with Hyperthreading

[booga]

Just letting you guys know that it is possible to workaround the AutoGKnot crash on P IV with HT enabled, but simply changing the executble to win 9x Compatibility mode. I could test this on only one PC, so P IV owners would be nice to test this "solution" also. Thanks.

Booga

[colordog]

What issue are you referring to? Can you post more specific info?

I've done hundreds of encodes with my P4 HT processor, and never encountered an issue related to having HT enabled while encoding, thoughout several versions of GKnot.

If your computer is crashing when you have HT enabled, but forcing it to run unthreaded in compatibility mode works, you made need to update your MB BIOS.

[len0x]

He's talking about AutoGK only (GK is fine). Many users experience strange crashes of AutoGK GUI (weird) on the launch of application.

Are you saying that you never had any problems with AutoGK on HT-enabled system ?

[buzzqw]

i had use all autogk beta till now, and never get a problem in gui
System : p4 2.8HT enabled, 2*512mb ram dual channel, 120*2 hd raid, gigabyte 8knxp, ati 9700pro AIW, win xp (sp1+fix).

BHH

[colordog]

@len0x

No I'm not - Sorry, my brain just didn't catch the "auto" when I read the post. I've actually never installed AutoGK, but I'll do that later this afternoon to check what happens with my rig. Apologies.

[al2k]

Hmmm, I will give that a try, however I think I already did a while back without success.

Either way I'd say this launch issue doesn't affect all P4 HT systems, as on my system it works just fine if I downclock to 3.0GHz (running a 2.4C), however at 3.2 it only launches ~25% of the time and at 3.4GHz maybe 5%, and at 3.6GHz (what I normally run at) it almost never launches (however when it does it runs perfectly).

Now I can run two instances of Prime95 on my system 24/7 without issues (not to mention MemTest86), and in the 5 months of owning this system (always been OC'd to 3.4 or 3.6GHz) I've never had issues with any other programs relating to the speed. I would have to guess it's some weird memory or cpu timing issue or something. I've already tried with various amounts of RAM in various slots running at different multipliers, however that hasn't made a difference either. My systems specs are below, maybe we can narrow it down to a certain combination.

Asus P4P800 Deluxe - 2GB PC4000 (4 x 512MB Hynix D43) - Two WD1200JBs (non RAID) - ATI Radeon 9700PRO - Intel P4 2.4GHz (D1 Stepping @ Stock Voltage [1.525]) - Antec 550W TruePower - WinXP Pro SP1 + All Updates

[booga]

al2k:

I think your theory is interesting. Timing would definitely important when trying to handle an application using Hyperthreading. Switching to Windows 9x Compatibility mode does, I think, disable HT handling for the application, preventing the issue.

My system is also OC'ed (2.8 to 3.2), but I havent' trying without OCing yet. I will test and let you know if I make the same observation.

[booga]

You are perfectly right, I tried unoverclocking, and AutoGK started fine all the time. Going from 2.8 to 3.2, and it barely ever starts normally.

I also noticed that using the app in win98 compatibility mode as some drawbacks. When starting the actual encoding in Vdubmod, the OS becomes quite sluggish, and the enconding fps is not very good. It finishes though.

It's a bummer, because AutoGK IVTC algorythm is very good. It makes encoding bad NTSC series a breeze!!

[bilu]

So AutoGK's problem is to break the 3.0 GHz barrier! :D

@booga
Better to have HT@2.8 than CompWin95@3.2 , no?

May be helpful:

The NEW PC Slow Down Page
http://www.geocities.com/kulhain/


Bilu

[booga]

For Bilu:

You are right about "Better to have HT@2.8 than CompWin95@3.2 , no?" as far as AutoGK is concerned, but for all the other apps, 3.2 Ghz gives me a nice boost. I guess I am just spoiled:devil:

Thanks for the link, I will check it out and report if I figure any useful workaround. Take care

[Meestor_X]

With the latest alpha .86 (could be all versions, I don't know), if I set AutoGK to run in compatibility mode, on my P4/3.00HT VirtualDub runs on only 1 CPU, and takes FOREVER!!! If I open task manager and set it's affinity there to use both CPUs, it takes off as normal. Unfortunately, each time VirtualDub opens, it goes back to using one CPU. Not much good for batch jobs as you can imagine.

Changing AutoGK's affinity to running on both CPUs after it's loaded doesn't affect VirtualDub.

I hope someone can get to the bottom of this issue with >3.0gig HT CPUs!!

[Sharktooth]

Get rid of those HT CPUs...

[len0x]

Originally posted by Meestor_X
I hope someone can get to the bottom of this issue with >3.0gig HT CPUs!!

As soon as donation amount reaches the price of HT-enabled PC I'll buy one and will be able to debug on it :)