puppetmasta

I ran an xp 2200+ in my lpb for a while before purchasing the xp-m 2600. But I haven't ever tried the 2600 in a different board. When I get some more time I'll try that out. For now I'm ok with running at 185x13 (2400mhz) b/c I have to start practicing hard core for a local q4 tournament here in st. louis. Thanks for your help guys!

medianOCer, I have a bios saviour installed so I should be able to recover from bios corruption if it happens. Shouldn't though as long as I clear the CMOS every time I flash. I do know that my ram is TCCD and that the timings need to be loosened when going past 200fsb. But my biggest problem is that I can't even get my system to run at 200 fsb! :confused: I swapped different types of ram out and each combination I tried still only let me go as high as 185fsb. So until I get to 200+fsb I don't think I need to worry about loosening my timings. It seems that my problem is more related to the processor. Everyone keeps telling me that even the crappy xp-m 2600s will boot at 200 x 10, but thats not what i'm seeing. any ideas on the L12 mod?

ok guys, I've tried quite a few things and I am still not able to boot at 200 x 10. First I tried to rule out the ram. So I attempted to boot with 1 stick in the dimm closest to the cpu, no change. Next I tried the ram in the dimm furthest from the cpu, no change. Then I used a different piece of pc3200 from another computer I have and put it in the dimm closest to the cpu, no change. So I think I can rule out that the ram is causing the problem. I then reflashed the bios to 7/28/04, loaded optimized defaults, set all ram timings, voltages, and clocked the cpu at 185 x 13. This booted and seems to be rock solid. I installed 4 new panaflo case fans and a microcool southsink and that combination is keeping my case, cpu, and board extremely cool (CPU 35C (idle) 38C (load), Case 26C, CPU Diode 25C). So I think my heat issues are resolved. I then decided to try some of the modded bios' out there. I flashed to the following bios' : Hellfire's 3EG-Rev3 (Lanparty B) Hellfire's 6/19 Turbo (Lanparty B) and neither of them allowed me to boot in at 200 x 10. So I have to conclude that the mobile I got is just from a bad batch. For some reason it just won't handle 200 fsb. I am glad that I can now boot in at 185 x 13 which gives me a decent overclock (2400mhz), but it still doesnt let me utilize my ram's full speed since its better to run at 1:1 cpu to ram fsb. I looked at the L12 mod a bit and some said it gave them the abililty to boot in at 200 fsb, but then I also read that some bios' enabled this via software. Does anyone know of any bios' that would do this? Thanks for all of your help guys.

I agree that the ram shouldn't be a problem. The issue is that it won't boot in with any fsb above 145. So I would put it at 200 x 10 if I could, but it won't boot!!!! My first steps are probably going to be to reflash the bios and double check that its not corrupted in any way. I can't think of any other reason why it wouldn't boot in with 200 except that maybe the mobile 2600 that I got is a crappy one and won't hold more than 185fsb.

You might also invest in a BIOS Saviour. I had the same issue as you a while back on my LPNF2B. Sent my bios chip in for reflashing and then I bought a bios saviour so I would never have to do that again Its not too expensive maybe $20 at most. Check this review for more info http://www.techspot.com/reviews/hardware/bios_saviour/

I actually have my chipset voltage set to auto now. Forgot to update my sig. That's probably a good idea. The only thing that makes me cautious about that is the last time that I went installing new hardware on the board I got the 4 LEDs of death. I'll make sure to set to defaults before swapping out the ram so I'll hope that will prevent it. I'll keep my bios saviour handy though I'll take a look at the L12 mod. When you say 'L12 to 166' I'm guessing that fsb? Thanks for the suggestions, i'll let ya know what I find out. Oh I also put a box fan up to the side of my case last night and I was running extremely cool at 185x13. My cpu was at 38C - 39C all night and I never had any sound drops after playing Q4 for about 2.5 hours. So my problems there are obviously heat related. I'll see how the southsink does when it arrives. I also have 4 of the high power panaflo 80mm case fans coming as well so hopefully that will help with the airflow.

I just went into BIOS knocked my multiplier down to 10 and left my fsb at 145. Booted into windows and attempted to set my fsb to 200 in clockgen. Instantly froze up. I left my ram at tight timings b/c these ocz sticks are meant to run at DDR400 (200mhz) at 2-2-2-11 and I'm using the 1:1 cpu fsb to ram fsb. Update : Just tested loosening the timings from 2-2-2-11 CPC Enabled (1T) to 2.5-3-3-11 CPC Disabled (2T). I then booted with with 145 x 10 and attempted to raise the fsb to 190 in clockgen... froze up again. So I don't think its my ram. Any ideas? Maybe APIC would make a difference? I've just heard people trying to disable it, not sure what it does really. It's really weird that the processor won't go to 200fsb. It runs really cool at 185 x 13 so I would think the SP-97 I have on there is working really well (41C load). Could it have anything to with the fact that I did the warmod? I thought the warmod only made the lpb's recognize your chip as a mobile and nothing more. Any help from anyone would be awesome! thanks!

Damn charlie those are some hella nice speeds. What do you have your voltages set at (chipset, vdimm, agp, etc.)? I'm trying to get my xp-m 2600 stable and I'm trying to find the perfect clock for it. I noticed you have your ram timings a bit higher 2.5-3-3-7 as opposed 2-2-2-11. Maybe I should try uping my ram timings to see how much higher I can get. The highest I've been so far is 185x13 and thats with clockgen post boot. Can't get it to boot in at any fsb past 145 no matter what the multiplier is.

Thanks for the response guys. king of nothing, I'll try the desk fan and see how it holds up. Will the fan really help if the SB doesn't have a sink on it? dr_bowtie, You may be right about the way I have it overclocked. I am oc'n via the nvidia clockgen utility so I haven't tested trying to boot in with 185 x 13. When I was overclocking previously I had issues booting in with any fsb higher than 145, no matter what my multiplier was set at. It might be that I need to try one of the more specialized bios' out there to achieve the clock I want on boot. What do you think?

Hi all, I'm currently trying to get my overclock stable and have been running into some issues with sound dropping after extended periods of use. I'm running at 185 x 13 (2400 mhz) on my AXP-M 2600+ and all temps seem fine. My cpu temp is stable at 41C and my board temp is stable as well at 39C - 40C. All seems fine except that after a few games of Quake 4 the sound drops. I check the temp on my southbridge by just touching it with my finger and it was incredibly hot. I'm assuming the sound is dropping due to the heat generated by the SB so I have a southsink from microcool in the mail to try and resolve this. Any other ideas? Once the sound drops things still run just fine, I've even run Prime95 for about 30 minutes and its seems solid @ the clock i mentioned above. Is there anything else I should check related to the sound going out? Thanks, Dave

nvidia's 6800 series is the way to go for doom3. The x800 seems to run better in hl2 and the 6800's work better in doom3. I would base my purchase on which type of game i'm more into. Are you a hard core doom3 player?? Either is a good choice, but you can get a better deal with a 6800 than paying an arm and a leg for a x800.

8am - 4:15 pm baby!!! Love checkin dis forum during lunch at my desk

yah i had a 5200 before i got my 6800GT. Doom 3 ran like asszzzzzzzzzzzzzzzzz I'd recommend getting at least a 6800 if you want to be able to enjoy doom3 properly.

If the 100 fsb jumper doesn't work you could try the war mod. Do a search in the forum for 'war mode' or 'wire mod' and see what you come up with. It's really easy to do and should make your board recognize your mobile if thats what's causing the problem.

Its in the configuration section, you just have to turn it on. I believe its tools/configuration.