Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Firefox quantum 59.0.1 crash EXCEPTION_ACCESS_VIOLATION_READ

  • 5 replies
  • 1 has this problem
  • 5 views
  • Last reply by Shadow110

nonanche92000
nonanche92000
more options

Hello ,

Since the last update 59.0.1 of firefox quantum , i had a lot of crashes , this happen randomly , sometimes when i try to open a new tab , or when i try to access to one of the tab from my session .

I did a clean install because of this , but even after this the issue is still there .

The reason of the crash is EXCEPTION_ACCESS_VIOLATION_READ, and it seems to be related to inproc_agent.dll and klsihk64l.dll ( the value are in red in the crash details )

Can you help me to solve this ?

Config: - i7 2600 k - gtx strix 980 oc ( 390.65) - 16 Go ram - Windows 7 x64 - Firefox Quantum X64 59.0.1

Hello , Since the last update 59.0.1 of firefox quantum , i had a lot of crashes , this happen randomly , sometimes when i try to open a new tab , or when i try to access to one of the tab from my session . I did a clean install because of this , but even after this the issue is still there . The reason of the crash is EXCEPTION_ACCESS_VIOLATION_READ, and it seems to be related to inproc_agent.dll and klsihk64l.dll ( the value are in red in the crash details ) Can you help me to solve this ? Config: - i7 2600 k - gtx strix 980 oc ( 390.65) - 16 Go ram - Windows 7 x64 - Firefox Quantum X64 59.0.1

Chosen solution

This crash is a problem with the Windows on-screen keyboard (accessibility active; see about:support).

Try to disable accessibility services in Firefox.

Read this answer in context 👍 0

All Replies (5)

FredMcD
FredMcD
more options

inproc_agent.dll = Kaspersky Inproc Agent

klsihk64l.dll = Kaspersky

Update Kaspersky. If the problem continues, disable it

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Now go to the reply box and paste them in.

aboutcrashesFx29

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

nonanche92000
nonanche92000 Question owner
more options

Here are the crash report :

bp-94c9cf1f-e399-4dd8-81b7-1a3ec0180321 21/03/2018 04:12

bp-516b2c14-9103-4e35-ba73-af7e20180321 21/03/2018 04:09

bp-734ae40a-2063-4632-a8e9-24c110180321 21/03/2018 01:58

bp-06d1e7af-07d4-4b29-81e5-223bc0180321 21/03/2018 01:57

bp-cea9c758-2c52-49be-9efa-8b5a00180321 21/03/2018 01:56

bp-5e71fdd0-ef6d-4cd8-8806-83c9e0180321 21/03/2018 01:56

bp-ad25ab66-92d9-431e-88bb-b16cd0180321 21/03/2018 01:53

bp-e039931e-8200-4a5c-9c6a-a64e20180321 21/03/2018 01:53

bp-96bbfb8d-e28e-4a51-9096-7b9140180321 21/03/2018 01:50

bp-4e7ffd3c-9085-4f3f-b87a-d9bbd0180320 20/03/2018 18:15

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Chosen Solution

This crash is a problem with the Windows on-screen keyboard (accessibility active; see about:support).

Try to disable accessibility services in Firefox.

nonanche92000
nonanche92000 Question owner
more options

Thanks Cor-El,

Firefox is stable now, no crash since the accessibility service has been disabled.

Modified by nonanche92000

Shadow110
Shadow110
more options

Hi, please Mark the Solution that Solved the Issue so others can find it.