Buspeed 160mhz OC Drops down to 133mhz randomly?

I was overclocking to 166mhz and I noticed on cpuz that my buspeed dropped down to 133mhz after a hour or too. I figure I went to high so I clocked down to 160mhz. Same problem after a hour or two I went down to 150 and same issue. Its fine for awhile then I come back to it and its down to 133mhz. I use throttlestop and have it setup exactly like the thread says. I really am unsure whats going on here.

 

I have had the same prob a few times. A reboot seems to do the trick, but not sure what is causing it..

 

Agreed. It kind of sucks though to wonder if your at 133 or 166 and to have to reboot. I wonder if it could be something in throttle stop? My multiplier stays locked around 16-17 pretty nicely.

 

When this happens I have to go into BIOS.My OC is there but I have to F10(save)for it to take..Wierd.

 

Yep same here and it lasts for a few hours like I said then just goes back down to 133.

 

This is a common problem with the M11x-R2. Some users have come up with some very stable overclocked settings and everything works great but there is a bug in the bios that sometimes when you boot up, the base clock gets reset to the default 133 MHz speed. I haven't heard of a solution for this. As far as I know this only happens when you boot up or maybe do a resume from stand by or hibernate. If you boot up and CPU-Z shows 160 MHz then I think it is OK as long as your laptop doesn't automatically go to sleep. If it does, you'll have to check it each time to make sure the overclock didn't get reset. I'm not sure if some different memory might help out with this issue.

I'm pretty sure ThrottleStop is innocent but you could try running without it for a week. You might not last a week though without it.

 

Funny, I don't use TS, and mine runs like a dream, I don't even need to OC to play Starcraft 2.

Those of you with the problem, all you need to do is uninstall TS and see if cpu-z still shows the same results of it down-clocking the bus speed.

 

Is not ThrottleStop, I used to have that problem before UW released ThrottleStop, or at least when I found about it...

 

Well fyi, I don't have TS installed and I OCed my m11x to 160. Did my usual tasks and left my m11x running for 2+ hours, according to cpu-z my bus speed never dropped down, always staying at a constant 160.4, turboboosting up to 2.7Ghz.

 

When you overclock an M11x-R2 in the bios to over 160 MHz, this can cause your full load performance to decrease compared to using the default 133 MHz bus speed. Dell is the only company I know that can create an overclocking feature that at full load makes a CPU run slower, not faster.

This was proven several times in the M11x Supercharge thread. Here are some examples.

http://forum.notebookreview.com/6845641-post482.html

http://forum.notebookreview.com/6852424-post488.html

http://forum.notebookreview.com/7161458-post805.html

Here is a user with this exact same problem where the base clock keeps getting reset to 133 MHz after he boots up a couple of times.

http://forum.notebookreview.com/7211352-post893.html

Sometimes the overclock sticks and sometimes it doesn't. Dell had no solution for this problem.
The M11x-R2 has an overclocking option but Dell doesn't guarantee your results when using it.

 

Mine does the same thing all the time (on reboot). I have to go into BIOS to enable 166.

 

Guys, I've tried everything you guys said to try to reproduce this (i.e. rebooting, sleep, hibernate, leaving it on for 2+ hours), and I cannot reproduce this bug, so hard to say what's causing it.

Ideally, I would suggest to do a factory/clean install, update drivers, and test. If there's no sign of bus down-clocking, then install TS, and see test again.

 

I have done a fresh install since the problem appeared. It appears the BIOS is not implementing saved settings on reboots or hardboots. The funny thing is, the settings when you go into the BIOS all read correct. All I have to do is hit F10 and it will boot into the FSB mode I select.

 

This is a common motherboard safety feature. When booting up, if everything isn't perfect, motherboards are designed to ignore your overclocked settings and automatically switch to the default settings instead. This insures that your computer will at least boot up if you choose an overly aggressive overclock.

The desktop boards have been doing this for years when overclocking and its a good feature in theory but there seems to be a bug in the M11x-R2 where even 100% stable overclock settings can cause this to happen. It doesn't happen to every M11x-R2 but it does happen to more than 1 or 2 of them. ThrottleStop is not causing this because it happens at the bios level before ThrottleStop starts running and there is no code in ThrottleStop that can change the bus speed anyhow.

Frequently problems like this are a slight memory incompatibility issue but unless you have a couple of spare modules to test with, I wouldn't recommend running out and buying some new memory. Some users have backed their overclock way down to barely over default settings and this problem was still happening. It's just one of those things that you will have to live with if you are overclocking your M11x-R2.

 

I was overclocking just fine before dell replaced my mobo. Wonderful so I have a lemon basically for overclocking it sounds like.

 

I changed to Davy's A03 Bios for the R2.

http://forum.notebookreview.com/ali...5m-nvidia-bios-flashing-increase-voltage.html

And have not had this problem for at least 2 days now. Seems to work great! Will let you know if it drops down again.