Hello. I'm installing Windows 7 on my MacBook Air. I've installed all BootCamp drivers, updated everything, updated graphic drivers and everything else. When I started index rating, I've got this results:
http://prikachi.com/images/402/2529402m.png
Nothing else is installed, but drivers.
Windows 7 Home Premium, 32 bit (BootCamp doesn't officially support 64 bit on MacBook Air).
What's the issue?
The winsat tests scored it at a 3.1 - I doubt anything's wrong here, other than the L9400 is a slow CPU comparatively (and dual cores get lower scores than quad cores - I have never seen a Core2 Duo get anything higher than a 5.3 (and heavily overclocked at that), although I've seen a Core2 Extreme get a 5.9 (the highest a dual-core CPU can score, if memory serves). A 3.1 for a sub-2GHz CPU is actually pretty good. I think you'll find if you were to overclock it above 2GHz, you'd score in the low-to-mid 4's.
That's entirely not true. Other people with the same processor are getting 4.5-4.6 rating for it. Something is wrong with the drivers.
Also, on my desktop PC with C2D E8400 @3.0 I'm getting 6.5 rating, and a friend with notebook with C2D at around 2.0 is getting 5.2. So there's something wrong.
C2Ds can perform well above 6.0 in the Win7 WEI ratings...
My Mobile C2D T9550 @ 2.793 Ghz rates at about 6.4 on the scale..
Don't be putting down the Core 2s bro!
To the OP, try making sure your performance setting in the power option @ Control Panel is set for High Performance, then run WEI assessments again, i guarantee higher scores.. your CPU throttled itself down to save energy is what happened!
Interesting - I've never seen a 6.x C2D, and at launch dual-cores were capped at 5.9. I'm wondering if an update to Windows 7 unlocked that at some point? Anyway, given it's running under bootcamp and with Apple's drivers, I think the OP may be on to something. It might be interesting if someone with the same C2D processor running Win7 on non-Apple hardware could post their WEI score for comparison.
http://prikachi.com/images/753/2530753s.png
I guess it is fixed?! That's weird. I did nothing special. I did:
-Cleaned up the system drive
-Defragmented it
-Scanned the NTFS partition from Disk Utility, it fixed some issues.
On the next reboot, I re-ran the WEI. It showed up these stats.
After that I switched to High Performance mode - got the same results.
So I guess the problem was fixed by itself?!
You won't need to keep it on 'High Performance', Windows maxes all of the clocks when running the test, it even hesitates and caches before testing to rule out any issues.
I've had the WEI score my Gpu low, but only because I did a lazy driver update, just dl'ing and running the executible. I then uninstalled the driver, removed everything, restarted, let Win install the WDDM driver, then updated, and walla, back to full speed. And WEI was accurate, benchmarks were lower because I was lazy with the driver...heh.
I doubt that's what happened in your situation, but either whatever was fixed in the system held back the score, or possibly there was a process going a little rogue on you during the test the first time.
Quote