hmmm I have a pair of BH-5 that can't seem to be reprogrammed. They work fine if a little slow and can be accessed via Thaiphoon and apparently written to but when you reboot they just have their original SPD information on them. Anyone any ideas?
Printable View
hmmm I have a pair of BH-5 that can't seem to be reprogrammed. They work fine if a little slow and can be accessed via Thaiphoon and apparently written to but when you reboot they just have their original SPD information on them. Anyone any ideas?
Everest will not show the mudule with the bad checksum and some others.Quote:
Originally Posted by Giana
For fixing the checksum:
after the hex "editing" load the sdp file edited with Thaiphoon Burner, go to: EEPROM => fix checksum or (ctrl+F) and save the spd file .
^Sure ;) Know this Feature, but i dindt know why i should use it. But thx will Update the Attachment.
Either you didn't follow the steps correctly as described in the first post, or it has write protection and the software doesn't detect that. Hardware write protect can be disabled by unsoldering pin7 of the SPD chip (WP) from the PCB and connecting it to GND.Quote:
Originally Posted by Johnny Bravo
I used dump for G.Skill F1-3200DSU2-1GBLE (TCCD), memory runs OK again,
but cpu-z detect me speed timings:
200Mhz 8-4-4-2.5
and
277 11-6-6-3
but memory are certificated 277 7-3-3-2.5.
Where is problem? Wrong dump?
THe HW write protect isn't on but I suspect the SPD may be at fault. RAM was touch and go in duel-channel now it has black SPD syndrome :( I fear the SPD itself it a little faulty and the PCB too, Vcc line works intermittently, perhaps it's ben flexed in its lifetime and broken internal traces.Quote:
Originally Posted by Micutzu
Replace the SPD.... only way if the original spd is write protected.
Waus-mod, the write protection is activated externally of the SPD chip, trough pin 7 (WP). If pin 7 is grounded, WP is off, if pin 7 is connected to VDD then WP is on and the SPD cannot be rewritten.
How have you determined that WP is off ? I'd suggest inserting the module in the slot, and with the system powered off measure the resistance between pin 7 of the SPD chip and GND; if it's 0 ohms or close to it, WP is off, otherwise it's on and you can't rewrite the SPD unless you do what i've described in the previous post.Quote:
Originally Posted by Johnny Bravo
Just read through this thread and just wanted to double check before trying this. I have a stick of Redline that has issues booting, seems like cold boot but happens all the time. When I can occasionally get the stick to boot it works fine and has 0 errors. Does this sound like symptoms of SPD being screwed up? If so can someone explain why it will boot some of the time still? Thx.
Quote:
Originally Posted by Krimi 2000
It's the same thing with the OCZ PC3200 Gold that i've described on a previous page; the manufacturer puts looser timings in the SPD to ensure compatibility and safe booting on any system. All the SPD's i've posted are correct and double-checked, it's safe to use them.
Holy damm , i had 2X512 ocz rev3 winbond bh5 sticks that does 225-230 2-2-2-5 2.8~2.9vdimm unburned and the one after one day dead [thousand errors even at defaults ,,the max vdimm that i have used 4 this stick was 2.9~3vdiim] .
i sent it back 4 rma ... :(
I think it was fixable :(
Awesome thread by the waY @ Bravo Waus-mod
Ok learned that also :P So when SPD is WP, you have to solder a ground to pin7?Quote:
Originally Posted by Micutzu
Is there somebody, who has dump for corsair TwinX2048-3500LLPRO?
Thanks.
yeah WP is off, turns out it was supply line was at fault, have repaired it and now runs SuperPi 32M @ 260MHz 2-2-2-4. :) Still the programming seems intermittant, when a full rewrite takes place, timing data is passed over but lower section of hex is lost (manufacturer module details etc) strange indeed. How do you detect a software WP btw?
EDIT - inc pic of fixed SPD and marked on the read point for WP for reference for other people
http://img400.imageshack.us/img400/4...drepair2sm.jpg
I don't think there is such thing as a software write potection for the SPD. I don't know what may cause that problem on your system (incomplete reprogramming), maybe the mobo is at fault. What mobo are you using ? Can you try another one ?
When the SPD is write protected you have to unsolder pin 7 of the chip from the PCB and connect it to GND (black wire of the PSU, one of the Vss pins of the DIMM, anything that is GND basically).Quote:
Originally Posted by Waus-mod
<center><font size="5"><font color="red"><b>Warning!</b></font></font><br />
Please read the latest part in the startpost, as someone also told me the same thing i allready thought about it. S7e9h3n said i had to post this as it is very dangerous. So please keep this im mind... and not to blame others when having "really" dead ram!
Fair eough Waus-mod tho I didn't realsie the controller was also at risk ! I'm pretty happy with my mem now anyway so I thik I'll stop pushing my luck :)
Micutzu it's a P4GD1, I have a few other boards lying around but to be honest I'm happy it's back to normal so I think I'll leave it where it is for the time being :D
Here's a dump from "Crucial Ballistix pc3200" 512 mb.
Yay first post here :D
heres mine dump for anyone who might need it.
Micron Chips it is though , wonder if i could upload any dump from gskill ZX or balistx...
http://img356.imageshack.us/my.php?image=back3bg.jpg
I've modded my dump from bh-6 relabeled kingston kvr333 with the same settings of the mushkin special.. I see the same, stick won't really run higher than 177mhz 2.2.2.5.1t... But wait, the stick does run 263mhz 2.2.2.5.2t
I'll update with v-data relabeled utt sticks dump.
that's very interesting as i have the same issue with my UTT BH-5's from Twinmos. before i matched the SPD's i couldn't even get them to run without errors together at low speeds and 2T. i can get 245-250mhz 2-2-2-5 @3.2v's 2T though.
Source?Quote:
Originally Posted by audiojunk66
According to Alonso (a TwinMOS tech) BH-UTT is the exact same chip as original BH-die (175nm).
MorueM and omga14,
If command rate 2T helps your clocks there is only one part to blame: the memory controller.
Command rate is actually not a memory timing. It affects only the memory controller.
I finally got my 2x512 ballistix pc3200 to boot in my sisters comp, it didn't work on my own P4P800SE. thx to Waus and ofcourse the creator(s) of taiphoon i have my ballistix back and saved from rma :D.
Well, my 512mb corsair 3502v1.1 does run 263mhz 2.2.2.5.1t, and my 2x512mb v-data relabeled utt runs dual channel 245mhz 2.2.2.5.1t..Quote:
Originally Posted by largon
But when the 512mb bh-6 is there, then whoops, needs 2t to go past 175mhz..
So my mem.controller is defective? It's my winnie running it, I could try my venice too, but I doubt it'd change something. Anything more enlighting? I'm ready to try things..
MorueM,
Since you can run 1T with other dimms there must be something really wrong with the underperforming dimm. Command rate is a mem ctrl timing, thus results can not vary that much considering your Corsair stick has identical (but higher rated) chips.
Does your "defective" stick run DDR400 at any timings?