Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

continuous crashing

  • 1 antwoord
  • 0 hebben dit probleem
  • Laatste antwoord van Paul

more options

THIS is the latest error log from YOUR app Log Name: Application Source: Application Error Date: 7/19/2024 3:12:06 PM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: X\vernf Computer: X Description: Faulting application name: firefox.exe, version: 128.0.0.2295, time stamp: 0x6686b62a Faulting module name: xul.dll, version: 128.0.0.2295, time stamp: 0x6686b68b Exception code: 0xc0000409 Fault offset: 0x000000000266982d Faulting process id: 0x0x105C Faulting application start time: 0x0x1DADA28690F6D67 Faulting application path: C:\Program Files\Mozilla Firefox\firefox.exe Faulting module path: C:\Program Files\Mozilla Firefox\xul.dll Report Id: ef22ede9-e0c9-4f1b-a1bd-3a610d046e01 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

 <System>
   <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
   <EventID>1000</EventID>
   <Version>0</Version>
   <Level>2</Level>
   <Task>100</Task>
   <Opcode>0</Opcode>
   <Keywords>0x8000000000000000</Keywords>
   <TimeCreated SystemTime="2024-07-19T22:12:06.5585951Z" />
   <EventRecordID>66459</EventRecordID>
   <Correlation />
   <Execution ProcessID="12268" ThreadID="23600" />
   <Channel>Application</Channel>
   <Computer>X</Computer>
   <Security UserID="S-1-5-21-1031570895-3094223114-2762588158-1001" />
 </System>
 <EventData>
   <Data Name="AppName">firefox.exe</Data>
   <Data Name="AppVersion">128.0.0.2295</Data>
   <Data Name="AppTimeStamp">6686b62a</Data>
   <Data Name="ModuleName">xul.dll</Data>
   <Data Name="ModuleVersion">128.0.0.2295</Data>
   <Data Name="ModuleTimeStamp">6686b68b</Data>
   <Data Name="ExceptionCode">c0000409</Data>
   <Data Name="FaultingOffset">000000000266982d</Data>
   <Data Name="ProcessId">0x105c</Data>
   <Data Name="ProcessCreationTime">0x1dada28690f6d67</Data>
   <Data Name="AppPath">C:\Program Files\Mozilla Firefox\firefox.exe</Data>
   <Data Name="ModulePath">C:\Program Files\Mozilla Firefox\xul.dll</Data>
   <Data Name="IntegratorReportId">ef22ede9-e0c9-4f1b-a1bd-3a610d046e01</Data>
   <Data Name="PackageFullName">
   </Data>
   <Data Name="PackageRelativeAppId">
   </Data>
 </EventData>

</Event>

WHAT THE FUCK IS GOING ON THIS HAS BEEN HAPPENING FOR MONTHS NOW .... FIX YOUR SHIT OR LOOSE ANOTHER CUSTOMER. NONE OF YOUR OTHER "FIXES" WORKED.

THIS is the latest error log from YOUR app Log Name: Application Source: Application Error Date: 7/19/2024 3:12:06 PM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: X\vernf Computer: X Description: Faulting application name: firefox.exe, version: 128.0.0.2295, time stamp: 0x6686b62a Faulting module name: xul.dll, version: 128.0.0.2295, time stamp: 0x6686b68b Exception code: 0xc0000409 Fault offset: 0x000000000266982d Faulting process id: 0x0x105C Faulting application start time: 0x0x1DADA28690F6D67 Faulting application path: C:\Program Files\Mozilla Firefox\firefox.exe Faulting module path: C:\Program Files\Mozilla Firefox\xul.dll Report Id: ef22ede9-e0c9-4f1b-a1bd-3a610d046e01 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2024-07-19T22:12:06.5585951Z" /> <EventRecordID>66459</EventRecordID> <Correlation /> <Execution ProcessID="12268" ThreadID="23600" /> <Channel>Application</Channel> <Computer>X</Computer> <Security UserID="S-1-5-21-1031570895-3094223114-2762588158-1001" /> </System> <EventData> <Data Name="AppName">firefox.exe</Data> <Data Name="AppVersion">128.0.0.2295</Data> <Data Name="AppTimeStamp">6686b62a</Data> <Data Name="ModuleName">xul.dll</Data> <Data Name="ModuleVersion">128.0.0.2295</Data> <Data Name="ModuleTimeStamp">6686b68b</Data> <Data Name="ExceptionCode">c0000409</Data> <Data Name="FaultingOffset">000000000266982d</Data> <Data Name="ProcessId">0x105c</Data> <Data Name="ProcessCreationTime">0x1dada28690f6d67</Data> <Data Name="AppPath">C:\Program Files\Mozilla Firefox\firefox.exe</Data> <Data Name="ModulePath">C:\Program Files\Mozilla Firefox\xul.dll</Data> <Data Name="IntegratorReportId">ef22ede9-e0c9-4f1b-a1bd-3a610d046e01</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event> WHAT THE FUCK IS GOING ON THIS HAS BEEN HAPPENING FOR MONTHS NOW .... FIX YOUR SHIT OR LOOSE ANOTHER CUSTOMER. NONE OF YOUR OTHER "FIXES" WORKED.

Alle antwoorden (1)

more options

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

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

  1. Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted (and Unsubmitted, if any) Crash Reports will appear, similar to the one shown below.
  2. Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

Fx115aboutcrashes

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

Behulpzaam?

Een vraag stellen

U moet zich aanmelden bij uw account om op berichten te antwoorden. Stel een nieuwe vraag als u nog geen account hebt.