This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

I had firefox 4 installed and my pc kept on freezing whilst browsing the net and an error nvidia 266.66 kernal driver driver stopped and succesfully reovered after uninstalling firefox 4 and reinstalling 3.6.16 problem has gone

  • 1 ŋuɖoɖo
  • 6 masɔmasɔ sia le wosi
  • 1 view
  • Nuɖoɖo mlɔetɔ Phi1ip

more options

I had firefox 4 installed and my pc kept on freezing whilst browsing the net and an error nvidia 266.66 kernal driver driver stopped and succesfully reovered after uninstalling firefox 4 and reinstalling 3.6.16 problem has gone so it looks like some conflict with nvidia drivers

I had firefox 4 installed and my pc kept on freezing whilst browsing the net and an error nvidia 266.66 kernal driver driver stopped and succesfully reovered after uninstalling firefox 4 and reinstalling 3.6.16 problem has gone so it looks like some conflict with nvidia drivers

All Replies (1)

more options

The problem is Firefox 4. I have two PC's with one XP OS, the other Win7.

Only problem on XP is the search drop down options do not work when clicked on. I too have nvidia drivers on this PC.

However on the Win7 OS, with MSE and MS firewall, the PC freezes regularly and is unresponsive for several minutes.

Mozilla recommend running browser in safe mode after turning off all add ons and then reintroducing one by one until the culprit is discovered!! People have tried doing as suggested without finding a solution.

You have probably noticed there are numerous topics about this problem in Google. What is clear is that people have various different set ups but that the one connecting factor is the change to Firefox 4.

Instead of telling us what the problem might be with our set ups, and asking us to waste substantial time on work a rounds, perhaps Mozilla should look at Firefox 4 and tell us why it is causing the problems?