Whoa!!! just got a notification that the HS (CPU part) has arrived! Will pick it up tomorrow and post a few pics.![]()
![]()
![]()
-
oooooh can't wait -
-
That, and the "It cost to much" crowd always chiming in. (like i never owned a top of the line clevo before (Twice to be exact))
Last edited by a moderator: Feb 6, 2015 -
Thanks, Brother John. Looking forward to playing with the system now that it's back from the depot.
-
Waiting to see a few quick run through's on the cpu. which can be done on the desk and no ac or cold needed...
-
Last edited by a moderator: Feb 6, 2015
-
Looking good Brother Fox
-
wPrime 1M 7.621 / 32M 236.373 @ 44x
(wPrime for some reason got a BSOD @ 45x - see inside spoiler below - any ideas?)
This was the BSOD (x3)... did not see any indication of thermal issue. Had to reset BIOS defaults to get Windows to stop crashing. Kept looping through BSOD.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: OWNER-M18X
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2920XM CPU @ 2.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17160810496 total
VM: 2147352576, free: 1936171008
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 1/20/2012 10:04:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012012-23571-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800FD3E028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 1/20/2012 10:04:25 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800FD3E028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 1/20/2012 9:51:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012012-18111-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800FD58028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Vantage: NVIDIA GeForce GTX 580M SLI benchmark result - Intel Core i7-2920XM Processor,Alienware M18xR1 score: P28350 3DMarks
Last edited by a moderator: Feb 6, 2015 -
-
FINALLY a proper 2920xm has arrived!
Attached Files:
-
-
-
Along with that calculator to properly account for money well spent!.
-
Here's are some benches with the 2920XM QS for the leaderboard.
-
-
Freq : 4526.73 MHz (102.88 * 44)
Question: does a higher or lower flex VID flex work better? Something seems to be holding things back a little bit. Just starting to get the hang of the XM proc. 3DMark11 (which seems to favor the AMD GPU) seems like it's going to be the tough one. Having a hard time beating my own AMD 3DMark11 scores, even with the 2760QM proc.
(Edit: I think I answered this for myself. Dropping flex VID from 25 to 15 seems to have helped a lot.)Last edited by a moderator: Feb 6, 2015 -
Hi Mr Fox , the lower the flex the better at around 4500 i run around 3 and increase only if you get a bsod like 00000101 and 000000124 then add 1 flex... in 4.5ghz range you shouldnt need over 12 flex, but i would start a 3 then work up until no bsod and then adjust the amps to keep it stable i run about 950 0n the priplane then run any program i use throttle stop the benching program to check the multiplier your using is working if say you are runing 45 and only 44 shows when you use throttle stop then increase amps 50 at a time until it does , anyway thats what i do and i think its the best way to keep ur temps down anyway hope it helps i no expert either.
Cheers -
3DMark06: NVIDIA GeForce GTX 580M SLI benchmark result - Intel Core i7-2920XM Processor,Alienware M18xR1 score: 31894 3DMarks
Running at 4.5GHz, my max temps are at 80°C on the CPU package and GPU 72°C on GPU0 (slightly less on GPU1) running 3DMark06 and Vantage.
murphy - thanks for the tips - +1 rep. I lowered the flex to 12. Still getting the CPU settings dialed in and it always helps to know what is working well for others. I've got less than 48 hours experience with an XM CPU, LOL.Last edited by a moderator: Feb 6, 2015 -
, the lower the flex the better, will help keep the throttling down to a minimum because of less heat as we all think the faster(Mhz) we have our cpu the better the overal performance but thats not true unless you have some special cooling, but i am talking everyday use and not sat on top of a a/c unit, because if you can get a constant speed your overall cpu score would be better as an average , i found by playing with amps and flex and getting them to the minimum i could run the cpu at 45 x and get a better score than running at say 47 x ,well over 10k on cpu on 3dmark 2011 and my score was less on 47x , all down to heat , lets hope akimon comes up with these 3 piped heatsinks should help a fair bit , anyway its all good fun and like i said i am no expert and if i am wrong then please correct me as i am learning myself.
Cheers.Last edited by a moderator: Feb 6, 2015 -
This is the bench marking thread, not the bench marking thread for 24/7 stability thread.
Side note:
Guys, most are not running these high over clocks on an every day basis. That's just crazy and not even remotely close to needed. Benching is just for SPEED only in here. Any where from 3.7 to 4 ghz on all 4 cores is a nice over clock to keep, but what is better is a staggered core setting. As suggested in the bios by dells setup.
People need to let that "look at me" attitude go. Even if it shows all 8 threads sitting at 4.5 ghz...90 percent of the time you are not using it at that speed on all 8 threads. And most apps are still better suited on a dual core platform. You don't need 50 cores to run microsoft office or a web browser or basic office software.... And that's what they are catering to at the end of the day....
Last edited by a moderator: Feb 6, 2015 -
I have made any changes to the front page yet because I'm sitting here thinking on just how to update the cpu portion....Ideas welcomed.
-
Cheers -
Increasing my multiplier from 44x to 45x actually lowered my wPrime score by a fraction, so we can go with the previous post for the leader board.
Looks like 3rd place for SuperPI: 8.020 1M / 7.39.030 32M.
CPU temps are holding well, with the max reached of 91°C running 1024M wPrime bench. Idle temps are 65°C at CPU Freq 4673.84 (103.86 * 45). Thumbnails attached.
Crysis benchmarks are in the spoiler.
Attached Files:
-
-
I understand what you are saying, but he has been at this a whole 14 hours at best and has already caught and past some of the vets. So I'm going to have to say some of what he and I talked about....is actually working...( Not to mention a nice chip to work with as well). You too can go farther, bu you also have to be willing to try.
.
-
Brother John, I probably would have struggled a long time at this without your help. I learned a lot from you man, and it's cool putting it to good use. +1 and thank you.
-
No problem! And your numbers are looking outstanding!
I may just have to double up the cpu portion and just give points for the users highest rank in that category. -
By recording the other scores without doubling up on points, it gives other users with the same hardware configuration something to aim for. In other words, a person could hold records for the same benchmark test in two categories, but only receive the points for the runs that place higher in rank and net more points. -
Screen shots are in the spoiler...
Freq : 4903.33 MHz (100.07 * 49)
OCZ Vertex Agility 3 480GB RAID0 Results
(compressible and incompressible tests)
.Last edited by a moderator: May 6, 2015 -
What's up fellas, so I finally got my 2920xm installed. Still figuring out all the settings for it so these are my early runs so far, it looks like I still have some headroom with the CPU.
Attached Files:
-
-
What is your max voltage so far?
Nice scores by the way! -
Sent from my GT-N7000 using Tapatalk -
electrosoft Perpetualist Matrixist
Very nice start. I guess you can change your sig now Joker.
-
-
Max of 1.35 but I'm seeing some throttling at 46x so I might need to give it more juice. Which bios are you guys using?
Sent from my GT-N7000 using Tapatalk -
very nice score, but shouldn't your max voltage be around 1.5V ?
-
I dunno I noticed that when I raise the VID in the bios TS still reports 1.35v, what gives? It doesn't matter what i set pri plane to etiher. Lately I'm seeing that if i set it at 45x, 0 flex and 900 pri plane, it runs wprime 1.55 fine up to about 50% when it drops from 45x to base 25x and then back up and down a few times. If I raise the flex to 25 it makes no difference. Its as if the CPU is reaching the throttling hard limit at around 50% and scaling back. Temps are fine too, highest is 87-88C.
Also can't get Intel xtu to work, it gets stuck at the splash screen.
Edit: So I pumped pri plane to 2000 and sure enough the cpu is perfectly stable at 45x. So what gives? Is this a sign of a good or crappy CPU? I can drop flex to like 0 and it still holds at 45x as long as pri plane is in the stratosphere.Attached Files:
-
-
one sec....
-
Great scores BTW! -
Joker, I need to keep my flex VID at between 15 to 25 or I get a BSOD at 45x. My 2920XM will not hold 45x even with C states disabled unless I set pri plane to the max (8191). If I lower my pri plane to 900, 1000, 1020, 1050 or 2000 the CPU refuses to run at 45x. (I can set it there, but it only runs like 3.5-3.8GHz at the most.)
I'm sure there is a sweet spot, but I got tired of rebooting and trying different settings to stop the BSOD and just set it up for Dell factory OC settings and called it a day on the testing. I played about 3 hours of Crysis 2 and feel better now.
I'll tinker with it more when I'm not frustrated. If you find settings that work good for you, please let me know and I'll give them a shot. -
I think it was a temperature problem somewhere. I opened a window and let the room cool down and now it does it at 900 pri plane and zero flex. -
it's a voltage/temp problem. And just like the rest of us...seems you're capped at 1.35V's(when I had my es.). So trying to do 46x or higher on 8 threads will crash more than likely. But the experiment door is always open...
Brother Fox, can you boot higher than 46x? -
-
Well, no one really had a qs before so no one really knew. Other than it has a 25x multiplier...
just set 25 flex and boot and see what your vid shows. Oem shows max 1.5012V -
I may be having temp problems also. Had been running cool, without any throttling the other day, but now the temps are going too high under load (93°C) and I am getting throttling. Idle temps are 46 to 48°C.
Will set flex to 25 and check my voltage with CPU-Z. Be back in a bit. -
You need xtu to run the multiplier above 45x on all cores.
-
-
-
Last edited by a moderator: Feb 6, 2015 -
You just need to play with it. 1.47 is way better than 1.3511.
We need to find out the difference. -
Should the Level 1-3 menu be set to "disabled" with only the core multipliers showing in BIOS, or does it even matter?
Should C7 be enabled or disabled in BIOS? I have it set to enabled. What about Bi-Directional PROCHOT? Enabled or disabled? -
-
OK, progress... Enabling C7 may have been part of the issue. I had also enabled "Power Efficient States" in the BIOS. With those disabled, I lowered my pri plane to 1020, still have flex at 25 and no BSOD.
I can also now boot with XTU set at 46x, but it does not appear that the multipliers are going above 45x even though XTU is still set at 46x after rebooting. See thumbnails.
I will see if I can lower flex now without a BSOD. I was able to run it at 15 yesterday and my temps were fine, so maybe this will be the ticket. Will try it and post what happens next.Attached Files:
-
*OFFICIAL* Alienware M18x Benchmark Thread - Part 2
Discussion in 'Alienware 18 and M18x' started by BatBoy, Dec 15, 2011.