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 too have stop code IRQL not less or equal. Tried safe mode but still get the same message

  • 4 replies
  • 1 has this problem
  • 1 view
  • Last reply by Haltham

more options

Problem started on 9th January after latest windows 10 update. Tried putting TB in safe mode but still get same stop code message. Tried system restore to day previous but comes up with file error and will not restore.

Problem started on 9th January after latest windows 10 update. Tried putting TB in safe mode but still get same stop code message. Tried system restore to day previous but comes up with file error and will not restore.

Chosen solution

re :Tried running TB in safe mode

But did you reboot the computer and run computer in 'Safe Mode with Networking' and run Thunderbird as normal ?

Read this answer in context 👍 0

All Replies (4)

more options

re :Problem started on 9th January after latest windows 10 update. Does it occur when you start computer ? Or can you run various other programs ok ?

Suggest you make sure all your various drivers are up to date.

Assuming this only occurs when you start Thunderbird. Start computer in 'Safe mode with Networking' and then start Thunderbird do you still have the same problem ?

more options

All other programs seem fine. only when I click on TB for my e-mails. Tried running TB in safe mode but still get the same stop message.

more options

Chosen Solution

re :Tried running TB in safe mode

But did you reboot the computer and run computer in 'Safe Mode with Networking' and run Thunderbird as normal ?

more options

Problem was solved when I went back to the previous version of Windows 10.