Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FPS limiter gives this error...

Featured Replies

  • Author
See: Turning UAC On or Off.Cheers,- jahman.
already did that as well as move fsx from x86 into C:FSX same error although now it also gives me the send info to microsoft option
800driver.jpg
...move fsx from x86 into C:FSX
You mean you reinstalled FSX? (You can't just move FSX because registry entries need to be adjusted).
same error although now it also gives me the send info to microsoft option
Maybe it only seems to be the same error as now Windows is doing something different. Can you post the new error info just to be sure?Cheers,- jahman.
  • Author
You mean you reinstalled FSX? (You can't just move FSX because registry entries need to be adjusted).Maybe it only seems to be the same error as now Windows is doing something different. Can you post the new error info just to be sure?Cheers,- jahman.
Yes reinstalled - This is both sides of the log, general 1st and details with both "system" and "event data" extended. Its always the same error. I tried antilag fps limiter and fsx crashes as soon as fly now is hit so neither work. Good luck to anyone who can read and decypher this error logLog Name: ApplicationSource: Application ErrorDate: 11/10/2011 10:52:35 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: Josh-PCDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58Exception code: 0xc0000005Fault offset: 0x0003a6a7Faulting process id: 0x14f4Faulting application start time: 0x01cc9fc8de2cd786Faulting application path: C:FSXfsx.exeFaulting module path: C:WindowsSysWOW64ntdll.dllReport Id: 638b762e-0bbc-11e1-bf83-14feb5b1723eEvent Xml:<Event xmlns="http://schemas.micro...08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-11-10T16:52:35.000000000Z" /> <EventRecordID>4704</EventRecordID> <Channel>Application</Channel> <Computer>Josh-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>ntdll.dll</Data> <Data>6.1.7601.17514</Data> <Data>4ce7ba58</Data> <Data>c0000005</Data> <Data>0003a6a7</Data> <Data>14f4</Data> <Data>01cc9fc8de2cd786</Data> <Data>C:FSXfsx.exe</Data> <Data>C:WindowsSysWOW64ntdll.dll</Data> <Data>638b762e-0bbc-11e1-bf83-14feb5b1723e</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 11/10/2011 10:52:35 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: Josh-PCDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58Exception code: 0xc0000005Fault offset: 0x0003a6a7Faulting process id: 0x14f4Faulting application start time: 0x01cc9fc8de2cd786Faulting application path: C:FSXfsx.exeFaulting module path: C:WindowsSysWOW64ntdll.dllReport Id: 638b762e-0bbc-11e1-bf83-14feb5b1723eEvent Xml:<Event xmlns="http://schemas.micro...08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-11-10T16:52:35.000000000Z" /> <EventRecordID>4704</EventRecordID> <Channel>Application</Channel> <Computer>Josh-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>ntdll.dll</Data> <Data>6.1.7601.17514</Data> <Data>4ce7ba58</Data> <Data>c0000005</Data> <Data>0003a6a7</Data> <Data>14f4</Data> <Data>01cc9fc8de2cd786</Data> <Data>C:FSXfsx.exe</Data> <Data>C:WindowsSysWOW64ntdll.dll</Data> <Data>638b762e-0bbc-11e1-bf83-14feb5b1723e</Data> </EventData></Event>
800driver.jpg
  1. Do you get the CTD without the FPS limiter?
  2. Rename your FSX.cfg to something else and let FSX rebuild it from scratch.
  3. Another general suggestion is to enable Windows Update and make sure all your MSVC and .NET Runtimes are up-to-date.

Cheers,- jahman.

  • Author
  1. Do you get the CTD without the FPS limiter?
  2. Rename your FSX.cfg to something else and let FSX rebuild it from scratch.
  3. Another general suggestion is to enable Windows Update and make sure all your MSVC and .NET Runtimes are up-to-date.

Cheers,- jahman.

1. No more than whats expected2.Ive done that several times3.it is, and they areIts just an odd bug with my laptop. I got my gaming rig and it worked fine on it so it doesnt matter anymore to me but Im sure it will happen to someone else in the futer. It worked on seperate pc with vista and mcafee security. It now works on gaming rig with same win7 and security as current lappy that errors. So thanks for trying to help
800driver.jpg

You're welcome! We've unfortunately reached the end of my expertise, so hopefully someone else with more knowledge might care to jump in?Cheers,- jahman.

  • Author
You're welcome! We've unfortunately reached the end of my expertise, so hopefully someone else with more knowledge might care to jump in?Cheers,- jahman.
How do u close yours when using limiter because if i close fsx normally it crashes every damn time with a fatal error blah blah blah. Is there a way or order to close fsx or what?
800driver.jpg

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.