Surinder,
As frustrating as it sounds, you still aren't giving us a lot of information to help you out here.
If the problem is surfacing ONLY when you run all your tests together at the same time then it very well means that there is a problem in your test code.
As long as all your @Test annotated test methods are self sufficient (i.e., they don't make use of any variables defined as data members in the class and which get initialised by another @Test method ), you should never see such sporadic NullPointerExceptions.
So either you deep dive into your test to see what data is being shared across your @Test annotated test methods and fix them such that there is no such sharing, or you show us a simple reproducible test that can recreate the problem.
Oh btw, I don't think this problem is any more a Selenium WebDriver problem, but seems to be more related to your @Test method [ TestNG google groups would be a better place to ask this question, but even there I am going to tell you the same thing that I already said here :) ]