View Full Version : Please contribute, motherboard support E4300 mod strap 266
Benny Lodewijk
02-25-2007, 11:27 PM
Guys, please make contribution for E4300 modification strap 266 motherboard support.
Motherboard Support :
- DFI Infinity 975X/G
- DFI ICFX3200T2R/G
- Gigabyte GA-N680SLI-DQ6 (Rev.1.0)
- Biostar 965PT
Motherboard did not support :
- Gigabyte GA-965P-DS3P (Rev.2.0)
- Gigabyte GA-965P-DQ6 (rev.3.3)
ziddey
02-25-2007, 11:34 PM
As long as the motherboard supports 266, there should be no reason it won't support bsel modded 200fsb. If it's not working, there's a good chance you're not doing it right.
Benny Lodewijk
02-25-2007, 11:37 PM
As long as the motherboard supports 266, there should be no reason it won't support bsel modded 200fsb. If it's not working, there's a good chance you're not doing it right.
but why some gigabyte P965 can't boot after mod ? With another mobo like Gigabyte N680 no problem. Also DFI RD600 and 975X. I did test all the mobo I listed above.
MADMAX22
02-26-2007, 02:30 AM
biostar 965pt works great
123disco
02-26-2007, 07:20 AM
ASROCK 775TWINS-HDTV R.2
I am using DDR1 RAMs, rock stable.
Hazzan
02-26-2007, 08:13 AM
@Benny Lodewijk :still work in progress with ABIT AW9D MAX and IN9 32 Max maybe tomorrow have result...
Calcu
02-26-2007, 08:58 AM
So far, the p5b-deluxe doesn't work with BIOS 1004. If I have time, I'll revert back to an older bios and try it again just to check,
Edit: With BIOS 0711 and down, the E4300 automatically boots at 2.4GHz(266FSB) without any modding but there is a CPU ucode loading error every boot. Also, it boots a modded CPU but so far on mine, there is no change in the FSB "wall" but I'll keep testing and report back,
bob511
02-27-2007, 10:30 AM
My experiences:
-ECS P4M800Pro-M v2.0 (mATX), BIOS 061214: displays a warning about the FSB on boot, but allows the user to continue at 266MHz
-Gigabyte GA-965GM-S2 rev1.0 (mATX), BIOS F2, F4: does not even POST.
Still hoping for a solid mATX board that'll take this mod.
EDIT: A more in-depth testing of the ECS P4M800Pro-M v2.0 at different FSB OC settings; this BIOS has a cap of 300MHz FSB in call cases, and "warning" refers to the message about the FSB of a modded CPU at boot (which requires a Y/N choice the first time, and then simply displays the warning afterwards):
Unmodded E4300:
-Disabled: boots at 200 with no warning
-200: doesn't even POST
-201-231: boots at FSB with no warning
-232-265: boots at FSB with warning (at 265 FSB, Sandra showed the AGP bus at 88MHz)
-266: boots at 200 with no warning
-267-300: boots at FSBs between 201 and 225 with no warning (at a setting of 300 and an actual FSB of 225, Sandra showed the AGP bus at 74MHz)
Modded E4300 (insulated BSEL1, traced over BSEL1 tape with run from BSEL2):
-Default: boots at 266 with warning
-200: doesn't even POST
-201-215: boots at FSBs between 268 and 286 with warning, seems tentatively stable at +.03V CPU (effective 1.324 Vcore), unstable at +.02V and below
-216-239: boots at FSBs between 288 and 317 with warning, unstable even at +.03V CPU (probably Vcore-limited?)
-240-265: doesn't even POST
-266-285: boots at FSB with warning, seems tentatively stable at +.03V CPU (effective 1.324V Vcore), unstable at +.02V and below
-286-300: boots at FSB with warning, unstable even with +.03V (probably Vcore-limited?)
(Sandra never displayed an AGP bus clock speed when the E4300 was modded)
Unmodded E6300:
-Disabled: boots at 266 with no warning
-200-265: no option for booting below 266 with an E6300
-266-300: boots at FSB with no warning, seems stable
Modded E6300 (insulated BSEL1, traced over BSEL1 tape with run from VCC):
-Disabled: boots at 200 with warning
-200-265: no option for booting below 266 with an E6300
-266-300: boots at FSBs between 200 and 225 with warning (at a setting of 300 and an actual FSB of 225, Sandra showed the AGP bus at 74MHz)
I tested these all with a 1GB stick of DDRII-667 RAM, set to the lowest memory multiplier in the BIOS. While instability was readily apparent, I make no promises about statements of stability, as I didn't have the time to run Orthos Prime95's Blend for more than a couple of minutes for each of these cases. I'll admit, I don't recall the previous P4M800Pro-M I tried going as high as 300MHz with the E6300, so some of these values should probably be considered YMMV.
Anyway, it seems like the most I can get out of this board and these CPUs is a modded E4300 at 9x285MHz = 2565MHz or so, about a 43% overclock. Sandra couldn't gauge the AGP bus in that case, but I figure that if at 266MHz FSB AGP should be 66MHz, then it should be at a 1/4 divider and it's probably running around 71MHz, which doesn't seem that out-of-spec, so I'm guessing the instability I saw beyond 285MHz is more an issue of the paltry Vcore options...? If that's the case, the manual pad voltage mods might help out; I'll probably give that some effort when I get some time.
For a chintzy ECS board, I guess 2565MHz from a 1.8GHz chip isn't so bad...
EDIT 2: Should also give my week and code--Q641A268--to put the numbers in perspective.
EDIT 3: Tried one of the pad mods to override the CPU voltage--specifically the one VR-Zone pegs as 1.55V (http://sg.vr-zone.com/?i=3904&s=2), though the BIOS showed it more as 1.5Vish for my particular CPU--and was able to run Orthos Blend for a couple of hours on the modded E4300 at about a 306MHz FSB (set to 228 in the BIOS) x9 = about 2754MHz. I don't know that I'd want to run at 1.5V around-the-clock (it was just the easiest of those mods to tape off quickly), or even if 1.5V is actually needed, but it does at least seem to indicate that Vcore is a factor for my particular CPU. As usual, ECS is typically pretty limited through the BIOS in this regard, so people trying to make the most of the board would probably want to look into forcing a voltage through the pads.
Calcu
02-27-2007, 01:07 PM
Well after further testing, it looks like even with a modded CPU, the p5b deluxe does not switch straps, it's stuck at 800 with the e4300. My max FSB was 395 stable(clockgen or booting) and now I'm testing with a e6600 and just booted at 500 no problem, so it looks like I'll be selling the e4300 and getting a e6300/e6400 to play with once I give this e6600 back :( Funny part is that the modded e4300 booted at 2.4GHz on a Dell Dimension 9200 just fine, so maybe you can add that to the list :slapass:
socrilles
02-27-2007, 05:24 PM
p4m800pro-vm rev. 2 supports BSEL mod
Lestat
02-28-2007, 09:20 AM
p4m800pro-vm rev. 2 supports BSEL mod
can you provide proof of that.
people are wondering about this board so be sure to provide evidence of this.
and are you talking 266 or 333 bsel mod ?
jimborae
03-02-2007, 08:00 AM
Fatality FP-IN9 Sli supports the mod.:rocker:
n91htmare
03-04-2007, 11:35 PM
can you provide proof of that.
people are wondering about this board so be sure to provide evidence of this.
and are you talking 266 or 333 bsel mod ?
I know for sure that my cousin is running the 266 bsel mod on his e4300 and it runs perfectly with the p4m800pro-m v 2.0. He has it running at 2.55 ghz with just regular ddr. Running great for him so far but he just got in his scythe infinity and is waiting on some d9 ddr2 and a new motherboard. He is trying to figure out which mobo he wants though.
I did the mod on his e4300 using a defogger kit, really easy to do imo.
stroths
03-07-2007, 08:49 PM
It works fine on the p4m800pro-m v2. However, it does not run on the Gigabyte 965P-DS3 Rev 3.3. I just got the Gigabyte in the mail today and hooked it up and it would not POST with the modded CPU. I removed the mod and it posted fine. I can still get the CPU up to 333x9 stable with little voltage increase, so its still faster than the ECS I upgraded from. Still, it would be nice if it would have worked with the BSEL mod.
wedfighter
06-02-2007, 01:19 AM
Foxconn 965 and
DFI Infinity P965S
also support for BSEL mod
initialised
10-29-2007, 03:38 AM
Had the BSEL 266 mod on my CPU on an Asrock 4CoreDual, it worked.
Swapped the board for an ASUS P5K and hit 3.8GHz (on a Peltier).
Had some 'issues' (aka condensation/overheating), couldn't boot, removed the strap, can't get past 3.0GHz. Strap is supposedly set in BIOS but I think the mod helps.
thepfy
10-29-2007, 08:56 AM
I believe it works on the Biostar TP35D2-A7 from what I have read at rebels haven