The more details, the better. Start with the subject - you've only got a short line, but you can make it count. Don't assume we know what your circuit looks like, what your code looks like, etc. Don't assume that parts of your code/circuit are not the problem - you may be way off base, so include everything.
The farther off topic you are, the less help you can reasonably expect. This is the arduino forum; questions about a really popular arduino clone may get answered, while WinAVR or PIC questions may not get a response at all.
No one may know the answer, at least based on the info you provide. There could be lots of people reading your question, but a bunch of "I don't know" replies aren't particularly useful.
It may be that people are just busy. The person with the answer may be on the other side of the planet, too. I've participated in discussions where responses average 12 hours apart, since my daytime is the other party's nighttime.
It may be that a lengthy discussion on that topic was just concluded yesterday, and everyone is too tired to tell you to go read that thread. 
There can be volume issues, too. If it doesn't get answered in a day or so, you may reply to your own post to bump it up - hopefully with additional info to help your would-be troubleshooters.
-j