i7 + winafc = sad Doozer

Doozer

2[H]4U
Joined
May 30, 2001
Messages
2,548
Anyone having any luck running winafc on an i7?
I can't seem to get it to detect the CPU correctly.
It worked maybe twice and now it doesnt do anything but throw up a long list of red text in the console.
 
I have it running on mine and never have problems with it. I do have a delay on when it starts though. I have a 90 second delay from after program startup. There is a lot of CPU usage at startup and that may cause WinAFC to not be able to read the CPU heuristics correctly. I have a 90 second delay on all my boxes.
 
i'll have to give that a try when i get home then.
Posted via [H] Mobile Device
 
post your config

Mine runs flawlessly
I also use a 90 sec delay.
Then a 180 sec delay on my VM's starting( I have these set as scheduled task and start each one 25 seconds apart)
 
This is what I want to use and what should work

Code:
*\vmware-vmx.exe := PAIR0+PAIR1+PAIR2+PAIR3 [assign=2,priority=idle]
*\FahCore_*.exe := PAIR0+PAIR1+PAIR2+PAIR3 [priority=high]

Since the heuristic fails I'm stuck using this.
I don't know if it works the same but I've seen some odd CPU usage using this one.

Code:
*\vmware-vmx.exe := CPU0+CPU1+CPU2+CPU3+CPU4+CPU5+CPU6+CPU7 [assign=2,priority=Idle]
*\FahCore_*.exe := CPU0+CPU1+CPU2+CPU3+CPU4+CPU5+CPU6+CPU7 [priority=High]


The WinAFC log shows this when the heruistic fails to detect the CPU

Code:
Auto detecting CPU configuration. Please wait.
6/9/2009 7:39:55 AM: ERROR build_cpu_sets: Unsupported set size (8).
6/9/2009 7:39:55 AM: ERROR build_cpu_sets: Please send the above error message and the numbers listed below to: baobab13@users.sourceforge.net
0, 3, 11855.5
2, 5, 11882.5
1, 2, 11891
0, 5, 11964.9
2, 6, 12031.1
0, 7, 12083.3
0, 4, 12126.1
2, 4, 12135.2
2, 7, 12145.4
5, 6, 12175.5
0, 6, 12190.8
0, 2, 12253.4
5, 7, 12311.2
3, 6, 12321.4
3, 4, 12353.4
1, 5, 12462.5
1, 3, 12487.5
1, 4, 12535.1
3, 7, 12538.8
4, 7, 12560.7
4, 6, 12564.5
1, 7, 12578.5
1, 6, 12620.7
3, 5, 12649.7
0, 1, 13471.8
6, 7, 13704.3
2, 3, 13763.9
4, 5, 13768
6/9/2009 7:39:55 AM: ERROR build_cpu_sets: Unable to determine the logical CPU sets. Use only physical CPU IDs.
6/9/2009 7:39:58 AM: WARNING CWinAFCDlg::TraverseProcessList: There are no valid application profiles. The program will auto-pause.


Once in a blue moon it works and I get this :)

Code:
Auto detecting CPU configuration. Please wait.
6/9/2009 7:37:42 AM: Found 8 CPUs:
	 CPU0 has mask 0000000000000001
	 CPU1 has mask 0000000000000002
	 CPU2 has mask 0000000000000004
	 CPU3 has mask 0000000000000008
	 CPU4 has mask 0000000000000010
	 CPU5 has mask 0000000000000020
	 CPU6 has mask 0000000000000040
	 CPU7 has mask 0000000000000080
6/9/2009 7:37:42 AM: Found 4 PAIRs:
	 PAIR0<CPU0,CPU1> has mask 0000000000000003
	 PAIR1<CPU2,CPU3> has mask 000000000000000C
	 PAIR2<CPU4,CPU5> has mask 0000000000000030
	 PAIR3<CPU6,CPU7> has mask 00000000000000C0
 
Try this

*\vmware-vmx.exe := PAIR0+PAIR1+PAIR2+PAIR3 [priority=idle]
*\FahCore_*.exe := PAIR0+PAIR1+PAIR2+PAIR3 [priority=high]
 
Doozer, did you get this up and running on the i7?
Posted via [H] Mobile Device
 
Yeah, I got it running by turning of the cpu detection and using

*\vmware-vmx.exe := CPU0+CPU1+CPU2+CPU3+CPU4+CPU5+CPU6+CPU7 [assign=2,priority=Idle]
*\FahCore_*.exe := CPU0+CPU1+CPU2+CPU3+CPU4+CPU5+CPU6+CPU7 [priority=High]

I'm trying to decide what HSF fan I should get now so that I can overclock a little.
 
You can get decent prices on TRUEs now so I dont see any reason to get anything else.
 
Instead of using CPUx+CPUx or PAIRx, you can just use ALL to indicate all cores.
 
Last edited:
You can get decent prices on TRUEs now so I dont see any reason to get anything else.
Well, the Xigmatek Dark Knight can be found for around $40 and includes a fan, so for lighter overclocking it would be a better choice than the TRUE. Realistically, you could probably go up to 3.8-4GHz with the Dark Knight while maintaining reasonable temperatures.
 
Just messing around with it a little got me up to 4.2 but I didnt do much more than check my email and reboot to take it back down to stock speeds. I didn't want to push anything since I'm on stock cooling still. :)
 
Back
Top