Monitor No Signal

[ubik]

Hello,

I have a system that a few months back just started to give me "No Signal" from the monitor everytime i turned it on. After much research and looking into this on the internet and such. I have come to a theory that I think caused the problem, I came across this on the internet today:



AGP operation frequency is 66.6MHz, and PCI is 33.3. Those frequency are calculated from the fsb, so by raising the fsb, you raise those frequencies too. Those stocks usually don't like working above their stock frequencies, and will cause lots of trouble, or just burn out. Besides, I think the pci frequency also controls the ide devices, so that could lead to data corruption in your HDDs That's why you should check if your motherboard has the pci lock feature, or if it's natively locked (usually in newer boards, my asus a7n8x deluxe has PCI locked)


that system I have uses an ECS K7VTA3 motherboard and i dont think that board locks the agp/pci and i remember overclocking it to varied FSB settings and i also remember it crashing on me when the FSB was too high. So i think i burnt out my AGP/PCI slots and the board has no onboard video, so basically has this board been reduced to junk? and also how does one know how much the AGP/PCI can be increased regarding BUS Frequency?

[Exis]

It does sound like you either burnt out your AGP/PCI slots, or the video card itself. To make sure: Do you have another machine you can test the AGP card on? If it works on another machine its obviously a board error. If you are going to replace it, you may as well go bigger if you can afford it and get an AMD board with Hyper Threading Technology on it, as that will eliminate the need for a FSB, and you won't have to worry about OCing it and frying all the rest of your components :D.

[mark87]

Hmm you may have explained a problem of my own!

I was experiencing 3-4 BSOD's/errors a day before, and I put this down to bad RAM (even though no errors were shown in Memtest - because I didn't leave it running for more than a few hours).

I had overclocked 1.8Ghz Opty to 2.4Ghz (yes, a 600Mhz o/c!), and also overclocked/unlocked the graphics card. It wasn't quite stable at 2.4Ghz (even though I knew I should be able to push it much further), so I was running it near 2.3Ghz - and this was when all of the BSOD's occured. I left it because I thought I'd get the RAM replaced, but days turned into weeks, and it was only the other day when I decided to cut it back even further to near 2.2Ghz.

Result, far fewer BSOD's - 1 every 2/3 days or so (and I use the machine 24/7).

Now... I wonder if the PCI is unlocked! :o

I haven't checked for now (can't be bothered to restart), but if it is it could explain errors occuring with the graphics card too.

Had a look and the PCIE is locked to 100Mhz so I wonder if I should lower that... guess I better find out!