first OC, comp died, what happened?

[anonboy]

Just got a 1.3 Ghz T-bird for my a7v133 and wanted to start OCing as a hobby, after a couple months of trolling and getting various problems with my comp figured out (and 1 prob still), i decided to try and OC. I referred to this article at overclockers.com for a guide:
http://forum.oc-forums.com/vb/showt...afb76b&threadid=83663&perpage=30&pagenumber=2

By default when i installed my 1.3 it started up at CPU 10x, FSB 100 mhz, so i started upping the FSB (which also upped the DRAM frequency at the same time)

10x 110 mhz FSB = 1100 Mhz, 28C mobo/41C cpu- status OK
10x 120 mhz FSB = 1200 Mhz, 28C mobo/42C cpu- status OK
10x 130 mhz FSB = 1300 Mhz, 28C mobo/44C cpu- status OK
10x 140 mhz FSB = 1400 Mhz, status- comp wont boot

I had to clear the CMOS settings today allready so i know how to get it up and running again, but i was wondering what caused it to not boot, i didnt see a POST or anything just black screen.

The CPU is advertised as 1.33 Ghz so i dont suppose its coincidence that it failed when i past that, i would just like to know why. Was it the vCore, memCore, FSB, ?

Be kind I'm green and learning

 

[anonboy]

o the ram is pc133 sdram and its a clean install of win2k havnet touched anything besides installing mbm5, a couple other progs, havnet touched anything in BIOS from default cept for the fsb (which raised 1:1 with the fsb 100 mhz fsb = 100 mhz dram , 110 = 110, etc)

 

[Batman5177]

no post usually means that some component has hit it's limit

more vcore or vdimm *might* help, but usually not

 

[Cerberus8080]

Originally posted by: Batman5177
no post usually means that some component has hit it's limit

more vcore or vdimm *might* help, but usually not

I had a no-post problem with my new system when I OC my 2.4BGHz C1 to 2.88GHZ and the DDR400 Ram to 425MHZ. I had already tested the OC with the RAM at 400MHZ so I new the processor was fine (had to bump the porc voltage to 1.575). So, I increased the RAM voltage from 2.5 to 2.6 and it work fine....prime95 tested 16 hours. Try to increase the voltages, not too much, and see if it will post.

EDIT: You can try making your memory timings a bit more conservative as well