M11x now advertised at 1.73Ghz OC

CoreTemp and Intel's Processor Identification Utility. Attached is the screenshot from chewietobbacca's review thread where he tested all three side by side. PIU however assumes a stock multiplier of 6.5x to reach 1.6GHz (instead of 6.0x), which causes the FSB speed to display incorrectly.

 

I'm wondering if the CPU is slowing itself down to 1.6 when not in use? Then cranks up to 1.73 when it needs to.

 

Random, it might seem like that, but the one time I had it at 1.733 in CPU-Z it was fluxuating between 1.7333 to 1.7336. Odd

Thanks for the pic RPG

 

I used CPU-Z and CoreTemp for years and they never showed wrong CPU speed, I tend to trust them more than the others, so until they start showing 1,73 I am not convinced the speed is other than 1,6 (no to mention that the Intel program is showing the same).

 

Taking a look at the cpu in Linux.. the CPU Frequency meter in gnome reports 3 speeds.. 1.06, 1.60, and 1.73. dmidecode (reads the DMI/SMBIOS table directly from the motherboard) shows 1730 Mhz @ 1.1 V.

However, before I ran the cpu frequency monitor cpuinfo reported it as being at 1730Mhz. After I started it it now reports it as being at 1066.

I'm not 100% sure if it's actually speedstepping, but it thinks that it is.

 

Soleblaze, any chance you can get some screen shots of that?

 

I've attached a picture of the cpufreq app. I ran john -test on the various clock settings and everything pretty much came out the same. I'm going to have to find a better way to benchmark the cpu.

dmidecode:

Code:

Handle 0x0005, DMI type 4, 35 bytes
Processor Information
        Socket Designation: U2E1
        Type: Central Processor
        Family: OUT OF SPEC
        Manufacturer: Intel
        ID: 7A 06 01 00 FF FB EB BF
        Version: Genuine Intel(R) CPU           U7300  @ 1.30GHz
        Voltage: 1.1 V
        External Clock: 200 MHz
        Max Speed: 1730 MHz
        Current Speed: 1730 MHz
        Status: Populated, Enabled
        Upgrade: ZIF Socket
        L1 Cache Handle: 0x0006
        L2 Cache Handle: 0x0007
        L3 Cache Handle: Not Provided
        Serial Number: Not Specified
        Asset Tag: Not Specified
        Part Number: Not Specified

cat /proc/cpuinfo

Code:

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Genuine Intel(R) CPU           U7300  @ 1.30GHz
stepping	: 10
cpu MHz		: 1733.000
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips	: 3466.95
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Genuine Intel(R) CPU           U7300  @ 1.30GHz
stepping	: 10
cpu MHz		: 1066.000
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips	: 3466.79
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

Looks like the first cpu core freq is set to whatever the cpufreq app is set to. The second core ends up becoming whatever the lowest it's been set to. (When it started at 1.73 both were 1730. when I dropped it to 1600 both were at 1600. When I brought it back up to 1730 the second stayed at 1600. etc)

 

Thought I would post another screen shot. This time Nvidia System Tools System information. 1.73GHz

 

Now it is listed on Dells site. When picking the processor choice both the SU4100 and SU7300 are listed at 1.73Ghz overclock.

 

Confirmed

 

There is an easy way to go. Run 3dmark and super Pi，and compare those results with an overclocked Asus ul30vt which runs exactly at 1.733ghz. The difference will tell you everything!

 

I'm thinking we will see a BIOS update by the end of this month.

 

OK bringing this back up. When I was running 3DMark06 and pulling up CPU-Z for screenshots, I got the same error that was giving me 1.73 GHz. This time I made sure I got what was being stated. It popped up with "CPU-Z error" and stated this in the box:

The error code 0x2 (2)occurred during initialization
Do you want to display the error log file?

Yes/No

I clicked yes to see the error log, and here is what I got. File name "cpuz_driver_2568" Copy and pasted.

bInitDriver(C:\Windows\system32\drivers, 0)
GetCurrentDirectory = C:\Users\My Name Here\Computer Tools\CPU-Z\CPU-Z
GetModuleFileName = C:\Users\My Name Here\Computer Tools\CPU-Z\CPU-Z\cpuz.exe
m_iOSVersion = 2 (6.1)
m_bIsAMD64 = 1
m_hDriverMutex = B8
m_szPath_2 = C:\Windows\system32\drivers
m_szFilename = cpuz132_x64.sys
bOpenDevice
bOpenDevice : WaitForSingleObject error = 0
WinNT_bInstallDriver
szMachineName = MYNAMEHERE
WinNT_bCreateService
szDestName = C:\Windows\system32\drivers\cpuz132_x64.sys
CreateService failed, error code = 1073
WinNT_bStartService
StartService failed, error code = 3
WinNT_dwDeleteService
vCloseDevice release mutex = 0
bInitDriver returned 2
WinNT_dwUninstallDriver
WinNT_dwStopService
WinNT_dwStopService : OpenService failed, errorcode = 1060
WinNT_dwDeleteService
WinNT_dwDeleteService : Openservice failed, errorcode = 1060
CloseHandle(mutex) = 1

But like earlier, once I clicked yes, it opened CPU-Z and gave me the Codename "Wolfdale" and was adjusting from 1.733 to 1.736 GHz as it was reading the chip.

 

Thanks DR for the info. It might be an idea to e-mail CPU-Z with the above error details explaining the situation with the varying CPU clock readings to see what they say. I can do it if you like?

 

Sure, Sounds good if you want to email them. You can also include my screenshots as well. I will also email them tommorrow if I remember. I saved the error log on my M11X

 

Good idea. I just sent off an e-mail there now, hopefully they can offer some insight into the situation. I didn't want to bombard them with all the information we've collected but I did summarise briefly what we found. I'll update the thread with any response.

 

Well here's something interesting when I went to configure some Mass Effect settings.

 

Yes, I noticed the same clock speed when I installed ME2 last night

 

DR650SE, he responded and asked us to try out the beta version (v1.53.6) to see what it reports (and if the error can be replicated). It's available to download here.

 

Thanks, I'll D/L it now and work on that. Thanks again for that, I never got a chance today.

 

seems to me that it's more and more likely that it truly is 1.73ghz. One day if we can hit that 2ghz... oh man it would be sweet.

 

Well I remember at the very beginning back when the laptop where first arriving that CPU-Z might be wrong considering it was a new laptop. Everyone taught I was crazy.

 

Well I thought I'd throw in another screen shot for good measure. This one is take from a 3DMark Vantage bench run at native resolution. It' is compared to one of my runs on the M17X which is shown next to the M11X. The results show an accurate assesment of what my CPU over clock was in the M17X. The screen shot for the P13474 run can be found here

 

Thanks for the info DR650SE. Putting the CPU speed aside for a second, let's talk about the RAM speed. Or lack thereof.

In standard mode (i.e. overclock off) the RAM runs at a 1:2 FSB: DRAM ratio - FSB = 200MHz, DRAM = 400MHz x 2 ( Double- Data- Rate) = RAM running at 800 MHz.

So you'd think when you overclock, it would run the same ratio (1:2) - FSB = 266MHz, DRAM = 533MHz x 2 = RAM running at 1066MHz. Right?

Well, it doesn't. Not on my M11x anyway. The ratio on the OC is 2:3 - FSB = 266MHz, DRAM = 400MHz x 2 = RAM running at 800MHz. So there's no need for 1066MHz RAM at all. It's a gimmick.



This is happening on both the stock Samsung RAM, and my Kingston HyperX RAM. With no way to change the FSB: DRAM ratio, we're stuck.

I have to say I'm getting pretty upset with how things were configured on the M11x. I was expecting a machine that would overclock to a CPU speed of 1.73GHz (sorry guys, I'm still on the 1.6GHz side!) and a RAM speed of 1066MHz. But instead, we get a machine that overclocks to a CPU speed of 1.6GHz, and a RAM speed of 800MHz.

Just to confirm for sure, it would be great if a couple of owners would post up some screenshots. You don't have to use CPU-Z, MemSet is another suitable tool which will display all the required information also.

 

Assuming we can overclock more than 1.73 GHz with some method (I guess pin modding, or if Alienware is kind to offer new BIOS), isn't there dividers to make sure the RAM stays at the same speed?

 

@rpg

These should make you happy. You have to look under speed.

Whole System


Memory


CPU @ 1.73 GHz

 

Having some issues with mine (Related more towards the SSD I'm using than the machine itself) and I'm running memtest86 to remove the possibility of a bad RAM module.. And memtest86 reads the memory as being 400Mhz (DDR800). It also lists the cpu as running at 1600Mhz.

 

@ villosa
where can you get that program?

 

PMed you with suggestions

 

I think rpg you might be right. Something is fishy here, going to try and find out.



Also, sorry for the double post. Forgot I had a previous one..oops.

 

lot of conspiracy theories over 133MHz lol.

Most tools are reporting 1.73GHz, I'm assuming speedstep is throwing off some results.

 

Well I'm fairly certain 1.73 is real but now we have this ram conspiracy lol. Check my previous post and analyze away!

 

again, its likely that the tool is misreporting it. the difference in RAM speed is going to be even smaller then the difference in CPU speeds...

 

Guy's I have 1333MHz RAM sitting in a drawer. I'll put it in and see if the M11x Will take it, and if so if it will downclock, and to where.

 

Thanks man. My ram RAM is coming tomorrow and I will be doing some more testing as well.

 

Dropped it in, couldn't get it to post. Keyboard lights and the power button were on, but no screen.

 

OK, I think I didn't have it properly the first time. Here is what CPU-Z brings up as far as memory is concered. I have GSkill 8GB 1333MHz Memory installed. Any other memory speed tests? If CPU-Z is wrong on the CPU, then it may be wrong on the RAM as well.

 

As I said before in relation to the CPU speed, believe which tool(s) you want to believe. I believe the CPU speed to be 1.6GHz with a 6x multiplier. Here's another program for the 1.6GHz argument:



Everest is all over the place with it's calculations. It claims the bus clock is running at 288.9MHz (i.e. 1155MHz FSB) which we know isn't true. Alienware clearly stated that in overclock mode it raises the bus clock from 200MHz to 266MHz (not 289MHz). So, while I am interested in other tools reporting 1.73GHz, this is certainly not one of them.

DR650SE, thanks for doing that. If the RAM was running at 1066MHz on your machine the DRAM frequency would be 533MHz, the DRAM:FSB ratio would be 1:2 and the timings would be 7-7-7-20. It reports exactly the same as my Kingston HyperX 1333MHz RAM (and the stock Samsung 1066MHz RAM). All RAM on the M11x, whether in overclock or standard mode runs at 800MHz.

Whether you want to agree with this information or not is up to you, but for those who do agree with the information I've provided, I'm sure you'll also agree that AW really need to get their act together and sort out this disaster of a BIOS.

 

Yea, I definately believe that as far as RAM goes,anythiing installed is going to operate at 800MHz. As Far as the CPU, I'm going to go 1.73GHz, But it would be nice to see what a BIOS revision changes. I'm not sure it'll be out anytime soon as there are no major flaws like the M17X has had, ie, screen flicker, latency ect.

 

from the purchase order:

1 313-9589 Intel Core2 Duo SU7300 1.3GHz (3MB Cache, 800MHz FSB) Overclockable to 1.73GHz

pretty clearly stated..

So - technically, by all the analysis on this forum - the processor is running at the advertised specifications..

 

Huh? Not really sure what you're getting at by highlighting 800MHz FSB?

Standard mode : 800MHz FSB - RAM (1:2 ratio) = 800MHz

Overclock mode : 1066MHz FSB - RAM (2:3 ratio) = 800MHz.

The FSB speed does not equal the RAM speed. The RAM speed is calculated by using a memory divider (a.k.a. DRAM:FSB ratio).

If the memory ratio on the overclock was 1:2, then we would have the RAM running at 1066MHz. My point is why bother selling us 1066MHz RAM when they've configured it to always run at 800MHz.

At least 4 programs have reported a speed of 1.6GHz. I don't see how that's "running at advertised specifications" when it clearly states it's overclockable to 1.73GHz.

 

Sorry -

I guess I meant to say that potentially these programs that we're using to identify the OC speed may be (or obviously are) calculating differently, either via the current RAM speed or a direct read from the CPU. Not sure - either way - I agree that it's all confusing... Hoping that it does get resolved soon either with an explanation from the software developers of these various programs, or via a BIOS fix from Dell (assuming that the unit isn't truly OC'ing to the reported/expected speeds).

I'm kinda in the same camp as some other members here - it's a 133 difference - maybe a 1-2% increase? However, I am a proponent of you should get what's advertised. In this case - it's starting to appear a little muddy...

 

I do too, and hopefully sooner rather than later. I'm wasting valuable M11x time on this CPU speed malarkey.

Well, 133MHz is 10% of the SU7300's stock clock speed. No, it won't make a huge difference but on an already weak CPU that's holding things back, I'd certainly appreciate the extra bit of power. But, I can't say 100% that it is in fact 1.6GHz, so I guess we'll just have to wait and see.

 

The M11x supports overclocking. In normal mode, it runs at 1.3. In overclocked mode, it runs at 1.73.

 

Is it true that battery life actually increases with overclocking because the processor ends up drawing less power?

 

Hello? Normal mode it runs at stock 1.3 GHz. The only contention is whether the BIOS overclock option increases clock to 6.5 or 6.0 so either 6.5x266 = 1.73GHz or 6.0x266 = 1.60GHz

 

1.3 is the default

 

+1

Quite the opposite. In order to run more cycles per second, the CPU must use more power. OCing= more battery drain.

 

Got my new RAM installed, HyperX 1600 everything is still the same.

Everest used to list chipset properties as 1066mhz with the Dell RAM, now it's 1333mhz with the HyperX. As far as actual readings from Everest, it's still 433.3mhz or 867mhz total.

 

Correct - my bad. Typo. 1.3 or 1.73.