[Asus] BH5/UTT killer

Well i will start off with the problem i occured.

I had my p4c800e-deluxe and the ct-479 and my dothan 760 in house, so is started to play with it. First run was 28xx on stock voltage. Then i gave it more vcore and more vagp to achieve almost the 3ghz on air. Then a blue screen came and the system didnt boot anymore.

So i placed the pci vga card in a other pc and it worked. Placed mem in my Dfi nf4 and it booted. While on the dfi and in windows i saw i only had 256 of ram :slapass: so 1 stick died. Well ok its a problem, yes im angry but i did go further.

I placed the still working stick in de p4c800 and yes, he booted again. Went 2995mhz on air and another bluescreen. And yes, also this stick died

I didnt have any vmod on the board for the vddr, and everything was stock. Mem was running 2.85v and vagp on 1.7v ....................

User DaWan had the same with 1 bh6 stick..

WTF my xms3500 2x 281 2-2-2-5 stable sticks died because of???????????????? :slap:

Some one knows about this?

Had the same problem with my P4P800se.

Killed both my Mushkin Black lvl2 3500s and one of my KHX 3200 bh5s.

First died at 200MHz 2.85V 2-2-2 [I think - don't remember - May have died something higher but I remember having it at 200 and it still erroring, after a reboot no post]
Second died at 284MHz 3.6V - although was weird, clockgen would let me set anything (only tried up to 297MHz and CPUz showed 297MHz as well [though I find it hard to believe, used to freeze instantly above 284MHz - concluded it wasn't actually clocked at that] - error'd instantly in superpi though at that, even clocked down it error'd, rebooted and no post with no memory inserted beeps).
KHX died at 266MHz 2-2-2, 3.3V - same prob as the 2nd.

Yes it kills RAM, sorry for that. It seems that asus adapter + dothan + any Asus MB might do this

Here is my story on pci-e boards + dothan

If your system crashes try this to save RAM:
Immediately Power OFF, remove RAM, clear CMOS, Power ON, Power OFF again, reinstall RAM and power ON again.

Hope this helps

But how can the mem be killed if you dont have vmods or somethin like that. I mean then it is an engineering problem.... man ! :clap: well done asus.

@ kiwi.... i see in youre thread every one has the problem with dimm slot 1?
Hmm from now on i take a other motherboard and use dimm 2 and 4.

i had a stick of bh5 die not long ago, i thought it was just me putting too much voltage through it (3.4v with 17c room temp + 2x80mm fans over). reading all the dead ram threads is making me wonder?

p.s sorry i posted in the other thread too (the empty one) didnt see this active one :)

Never had this problem(yet) with my P4C800-E and 2x256MB Corsair PC3500@3,5V(ocz booster),i had many crashes while finding the max oc of my M740.
I use the latest beta bios(1024.001) and sticks in dimm 1&3,no mods,turbo-2-2-2-5-4-infinite-7,8us-pat.
I use the sticks only to find the max oc and Pifast/Super Pi,for 24/7 i use 2x512Mb Twinmos UTT BH-5@200Mhz 2,55V(they only do 215Mhz max,2,85 or 3,3V doesn't matter so i still hope that Asus makes a bios that is optimized for Winbond UTT but that will be wishfull thinking:mad:).
Always 1:1 so no divider.

I just had this with a p4p800se i do have a vdimm mod but it was set to 2.8 in the bios and 2.8 on the mod from a meter.
i had my nice gskill tccd in slots 1 and 2 only running at 256 2.5-3-3-5 whic is nothing i was running at 278 2.5-3-3-5 happy before.
i pushed a pm780 to 3120 260x12 and the pc reset and wouldnt boot.
checked the ram and the ram close to the cpu died.
i did notice that once or twice the vdimm was showing 2.9 instead of 2.85.

This is worrying. full story about mine above.

2x xms3500 in slots 1 & 3 with a booster in slot 4

i managed to run super pi at 11x260 with 3.4v (1.55cpu) without error but the pc locked on shutdown. i restarted it and just got a blank screen, tried resetting cmos etc etc... but nothing. So i tested each stick in my shuttle one at a time and one stick just gave me 3 short beeps (dram error?).

I did the same to a stick of tcc5 the other day only 2.85Vdimm,saaya says if you are using clockgen and cupz at the same time it can kill ram also.

Same thing here http://xtremesystems.org/forums/showthread.php?t=83398

i was using clockgen and cpuz at the sam time wont do it again.

I've had tons of lockups, restarts, BSOD's while overclocking with my P4GD1 and Dothan 740 (not sufficient Vcore etc, used high Vdimm with Booster as well), nothing bad has happened so far for me. However, there is one thing I cannot recall whether I ever did those times: clockgen and cpu-z simultaneously. I think, I usually had one or the other open but never both of them.

We need somebody with an old crappy stick to test this theory (with clockgen and cpu-z open, and without), this has been told already before but nobody has answered the call with verified results yet. Saaya has duplicated the clockgen/cpu-z death story by killing multiple sticks but we aren't sure yet whether or not using these two programs simultaneously is the key to ram survival. What is already clear, is that this happens on all Asus boards while using the CT-479 adapter so both i915 as well as i875/i865 users should beware.

So basically people, if you report dead sticks, please specify whether you were using clockgen/cpu-z simultaneously when the sticks died.

I have a bad mushkin 256 stick that I can try killing completely :)

One of my G.skill PC4400-LE with TCCD chips died on my Asus p4p800-SE. 2 weeks running on 290 5-3-3-2.5 2.65V with no problems.

Fuc*ing ASUS.

This board killed my 6800GT, 9500PRO and 6600GT. Every card died with another PSU(Etasis, Tagan easycon 480W, Tagan 2force 430W) and ran only one day. System was booting normal, but no signal there. It looked as no graphic card bios. I tried reflash 6800GT than 2hours was working, but when i restarted pc no signal there and i cannot reflash again.

Now i have Sapphire x800gt and everything is OK.

Sorry for my english.

Krimi 2000, welcome to XtremeSystems :toast:

i already contacted asus about this 2 weeks ago but no reply :(

One Kick-Ass Kingston Value ram BH-6 died after a bench session, and yes, same problem, only at 2,85V after a freeze (clocked too high) and dead :( On a P4P800SE with CT-479. **** we must mail asus about this and I want another 340WF stick of BH-6:(

My P4C800 killed a stick of Mushkin Redline UTT XP3200 (3.4v with DDR booster). In denial, I did some research and read about a cold-boot problem with UTT that can make the RAM 'appear' to be dead. So as a last ditch effort I tried switching the slots on the mobo, and the stick literally fried with smoke. Two of the contacts on the memory burnt right off. I'm not sure if this was an installation error on my part, or the residual effect of the dead memory stick. Needless to say it doesn't work anymore.

Forget about mailing asus customer support. They have the worst service ever and never reply :slapass: They even can't be reached by phone. The only option I guess is to go to their office. I hope their security guards won't kick you out :slap: :D

By the way, your stick might not be as dead as it looks! Here is the update of my kingston sticks.

They do NOT work on P4GPL-X + dothan. They don't work on i845E gigabyte mb. But they do work on gigabyte Kt266 board, memtest error free and prime stable. WTF?

Sorry, no more boards to test at the moment but this is strange.

so kiwi.... the sticks still works on other motherboards..... WTF

i have P4GD1 and 4 x 256mb Corsair XMS 3500 BH5 sticks.
i have had them over 6 months and no problems:D

I have 3 mb, it works only on kt266

I had a chance to change my p4gpl-x to p4gd1 which will arrive on friday. I will test then on p4gd1 :)

Hmm, KT266? That's 133fsb and DDR266, right? I've had damaged BH-5 (also from Kingston but I don't think it matters here), which crash at their rated speeds and lower, but still run fine at low fsb (like that 133, for example).

When babyelf get's back from Malaysia I'll try out my mushkin blacks (he's got 'em atm) at DDR266 and see how they go...

Ok..... saaya was right.

Last thing i remember was the validation where i had clockgen and cpuz open for max suicide. i pushed the validation button on 3g and then came the bluescreen....

SO PLEASE PEOPLE..... stop using clockgen and cpuz at the same time

If someone could try if this is the problem.... then this is something everyone should know if owning a asus+ct+dothan.