YASU 1.3.7070 released

[p22]

Athlon2600+

Same 99% CPU issue.

[NyQuil]

Now I tried it on my new ATHLON X2 6000+

YASU is running fine - even TDU 1.66A is working again.

But on my ATHLON XP 2500+ I have the 100% cpu load problem.

[evlncrn8]

has to be cpu related, check the revision on the chip is it xx00 ?

easiest way to check...

1. run cmd prompt
2. type in "set" (without the quotes) and hit enter/return
3. look for "PROCESSOR_REVISION"

[cryo]

PROCESSOR_IDENTIFIER=x86 Family 6 Model 10 Stepping 0, AuthenticAMD
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0a00

[evlncrn8]

mines 0c00.. lets see if those with 99% cpu have the same xx00

PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 12 Stepping 0, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0c00

[mauke88]

yup

mines 0a00 too and have the 100% cpu prob

[imppe]

Yep, having that Revision too.

PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 12 Stepping 0, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0c00

[Robbie785]

PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 15 Stepping 0, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0f00

AMD 3500+ here. same 100% load prob.

i tried the rename and added -s -c -usuck to a shortcut ...didn't help.

looking forward to a fix! (really want to play TDU!!!) lol

[Jito463]

Well, as someone who does NOT have the problem, here's my info.

PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 15 Model 43 Stepping 1, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=2b01

That's my work PC. My home PC I'm not sure about.

[evlncrn8]

Well, as someone who does NOT have the problem, here's my info.
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 15 Model 43 Stepping 1, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=2b01
That's my work PC. My home PC I'm not sure about.

think thats why

[Benni]

The affected CPUs are all x86. AMD64 seems not to have that problem.

[evlncrn8]

beg to differ, happens on all 3 of my amd64 pc's

[Benni]

Strange, but I am sure that sYk0 will release a fixed version very soon.

[Robbie785]

i already posted my CPU type, and it seems the problem is well known and a fix is in the work, i would just also like to add that i tested this with both windows xp (32 bit) and vista ultimate (64 bit)

both resulted in the same prob everyones talking about... so 32/64-bit doesn't seem to matter.

[evlncrn8]

yup, im sure he will

tested even on vmware, with the same x64 processors, same deadlock, so its 99.9% cpu revision related

i know why, and can patch it to fix it, but i have no intentions of doing so or making the patch public, because syk0 wasnt too happy about the previous ones being patched