View Full Version : I lost the Lotto!
DarkPurity
01-29-04, 02:46 PM
my new 2500+ came in today.
A
Q
Z
F
A
OK, OK, so far it's about 50/50 to whether or not it's locked.
0
3......ok ok, I can still win....
4......Bugger.....85% chance or so it's locked but THERE"S STILL A CHANCE IT ISN'T!
9. Ouch. 99.9% chance it's locked unless it's one of the slip-throughs.
Interesting bit on the warranty though. If you use any heat sink or fan other than the one that COMES WITH THE PROCESSOR the fine print says your warranty is void. OC'ers, NEVER mention your SLKs or Volcanos to AMD! If you do you were just as well off buying OEM.
AL Romero
01-29-04, 03:57 PM
i dont think to many of these peps buy retail anyway. i never do. cwork the shi* outta them with when u get them with a hard core burn in fot a day or 2. thats all you need to find out if its gunna fail.
Arkangyl
01-29-04, 06:43 PM
besides, its pretty cheap to RMA a CPU that you wreak via OC'ing.. so who cares bout that warrenty info, right?
Originally posted by Arkangyl
besides, its pretty cheap to RMA a CPU that you wreak via OC'ing.. so who cares bout that warrenty info, right?
:rolleyes:
http://www.ocforums.com/showthread.php?s=&threadid=265666
DarkPurity
01-30-04, 12:35 PM
Update: Not only is it locked but I've hit a snag.
I can't get it prime at 2200 mhz. I haven't tried increasing voltage yet but I'm hesitant to, since the stock sink and fan are what I'm using. I'm pulling around 41c when I run at 190 fsb, and I only have one case fan in the side of the case right now. The moment I hit 200 the system posts but WinXP Pro returns the following error:
IRQL_LESS_THAN_OR_NOT_EQUAL
My 1700+ used to do this when heat caused instability. I'm convinced it's the ratios but I'm afraid to crank the voltage. Should I? Or is there a better way?
Edit: my CPU reports 43c when I run at 200.
L337 M33P
01-30-04, 02:51 PM
What motherboard you running? XP gave me that error when the PCI bus was out of spec.
DarkPurity
01-30-04, 03:46 PM
I'm using Albatron's nForce2 Ultra board...don't have the model # on hand.
Quailane
01-30-04, 04:32 PM
It's not a lottery if it is guaranteed locked.
DarkPurity
01-30-04, 04:34 PM
There's sporadic reports of e-tailers still having unlocked procs in the mix. Therefore, it = lotto.
Quailane
01-30-04, 04:42 PM
I'd rather buy a powerball ticket where I don't have to rely on sporadic reports of e-tailers that seem iffy at best and I know that someone will win millions of dollars. (I can't buy the lottery tickets but youknow, it's just an example.)
DarkPurity
01-30-04, 04:50 PM
But you don't know someone will win millions of dollars.
THe processor is either locked or unlocked, and that's that. All or nothing.
Lotteries typically give 3000 winners 25 bucks.
What kinda Ram are you running? Are you sure it's not the ram holding you back?
DarkPurity
01-30-04, 05:58 PM
wouldnt surprise me, its some old pc2100.
Originally posted by DarkPurity
wouldnt surprise me, its some old pc2100.
Wow you got 2100 to hit 190FSB!?
Try a divider that keeps the ram as close to 133 as possible and crank the CPU as high as it can go. This will help find the max of the CPU.
Quailane
01-30-04, 08:16 PM
Peice of cake. I bought some pc2100 valueram for 10 bucks a 256mb stick at office max and I got 2 sticks. Awesome deal considering it does dual channel at 189 fsb completely stable at 11-4-4-2.5 at 2.7 volts. I want to try single channel with 2.9 volts.
DarkPurity
02-03-04, 09:31 AM
I got it do dual channel as well but I hit some sort of peak. I cranked it to 195 and my Proc. hit 50c on stock cooling. The ram worked fine the first time but when I rebooted it read as 251 instead of the 266 I had shown the first time. I forced it up to 200 and it read as 245. I started having heat problems after that because the case only has a side fan (just empty ports in the back, i'll hafta fix that) and bluescreened a few times attempting to boot WinXP Pro. I just dropped my system back to stock speeds for now until I can get better RAM and more cooling. I hate doing things halfway.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.