PDA

View Full Version : Please help, random crashes in new setup


xxxAgentxxx
06-10-2005, 08:47 PM
I previously owned p4c800-e, xms 3200LL 2x512 bh-5, and yesterday installed dothan 730 on the ct-479, along with ocz ddr booster. This morning I could boot into windows @ 2.7GHz / 225fsb and it was totally stable. I could never reach a high fsb, and I thought that was likely that the ram (2 years old) has never really been burned in, it's been run at, or just above stock for most of its lifespan.

I restarted, got into bios and set 2-2-2-8, 230, 3.3v, restarted into memtest86 and before the first test even finished it froze. After resetting, it froze @ post screen with a 2 inch strip of artifacting near the center of the screen. Power down, start up, got to bios and it froze before I could get to fsb selection, same as before with roughly a 2 inch layer of artifacting across the screen. Eventually, I got back in, lowered the fsb down to 215, but even at this fsb system will load into windows, but randomly crash. I can tell crashs occur more under load, but there was a couple times now where it crashed idle... temps are 34c idle, up to 48c at full load.

Now, I'll mention this, the ddr booster (right before I restarted to get into memtest) was going goofy. It would sit at 3.1 for hours, then I looked down and saw it set itself to 2.6... I was leniant to adjust it upwards back to 3.1 thinking "what happens if it recorrects itself and adjusts upward again..." but I did. I kindof kept a close eye on it, and while doing a super pi 4m run I looked down to see it at 4.0, let out a "oh @#$%" and turned it down quick. That was just a moment before I restarted to run memtest, and system didn't hang or seem unstable in any way.

After the freezing, I managed to get into bios and saw ddr speed set at "auto" (I did it for testing purposes), and the auto was adjusting the fsb down to 133, causing some issues with the fsb being 230 when I ran memtest. Changing that "auto" to 400mhz stopped the post / bios freezing, and memtest ran for 1:45.38 before stopping on an error after.

My question, did I fak my ram up here, or could it be the CPU is kindof shot, perhaps the PSU or ddrbooster?? I've never had a RAM chip die on me before, and I can't really tell the symtoms. I HAVE saw artifacts like that before, relating to a power supply nearing it's death, and ofcoarse I've never had any issues with a ddrbooster before, I've owned one for less than 48hours now... I really need your help here fellas, I could use some veteran recommendations on how to come to a conclusion on where the problem is coming from ;)

Thank you very much for reading,
Agent

perkam
06-10-2005, 09:00 PM
perhaps the PSU or ddrbooster??

Which PSU ??

Perkam

xxxAgentxxx
06-11-2005, 01:24 AM
As I was posting on that comp, with a post saying "I got it stable @ 210fsb, I thought i'd be cute and add a snapshot from cpuz, clicking on "manage attachments" was like clicking the reset button. I loaded right back into windows, only for it to instantly crash upon loading to desktop... help... D: No spare ram / cpu to test with. Temps still look good, so I don't know wtf to think here. Perhaps it's software related... the crashes might have fuct windows? Anyway, I loaded back into windows after the second consecutive crash only to notice my firewall was wiped clean. Now I'm getting pissed. With the firewall on, it detected the network wrong, allowing no connectivity, not to mention I get to go ahead and reset programs access and trusted sites all over again...

HEEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPPPPP!!!1!

oh yea, TT 480w silent pp to answer your question

TheDude
06-11-2005, 02:13 AM
I suspect the DDR Booster, have you tried removing it from the loop? Have you modded the booster?

xxxAgentxxx
06-11-2005, 04:23 AM
I suspect the DDR Booster, have you tried removing it from the loop? Have you modded the booster?

It's funny you should mention that. I removed it to try and run the ram at 200fsb (i can live with 2.4ghz for now), and it runs flawlessly. You were absolutely correct on that one. My question now, does this mean that the booster is bad, or that my system just wont push it?

What a sigh of relief, of all the components that turns out to be causing the problem, its the cheapest of them all. Looks like its time to vmod :cool: