Sign in to follow this  
Oxlade1

FSX Hangs after takeoff

Recommended Posts

Hi all,

 

I have another strange problem to figure out. Recently after installing the Majestic Dash 8 Q400 to my sim I've been having an issue.

 

When starting a flight in the Q400, everything is fine, but right after I takeoff (about 5-10 minutes after) the sim hangs, doesn't even crash. I can still hear the engines, but the sim is frozen and I can't minimize or close the game, I've tried waiting it out but nothing happens. And I can't even use the event viewer to diagnose the problem because it doesn't see the crash. Does anyone know why this is happening? And it only seems to happen with the Majestic Dash, even though on previous FSX installs the Dash had worked fine.

 

Any Ideas?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

My guess is that you are exceeding the capabilities of your computer, so it hangs. 

Share this post


Link to post
Share on other sites

The AVSIM CTD Guide provides for fixing freezes after takeoff.  The Majestic Dash 8 Q400 uses a lot of resources so, if you have settings set high and the sim runs out of resources, it will freeze up.  On page 9/10 of the AVSIM CTD Guide, it tells you how to fix most freezes/crashes.  Other than that, you need to investigate what's happening on YOUR system as it does not occur to everyone.  The AVSIM CTD Guide also shows you one location in the Event Viewer where you will see every event, whether associated with FSX or your system activity.  I even included pictures.  Freezes/hangs have shown up in other cases like the one you described but it usually will show an unknown error caused the B1 Hang.  So, in your case, looking at the Event Viewer, even if it shows the events, will probably be useless.  However, if your system was scanning your HDD or SSD or running some other type of event during your flight, this could have taken up enough resources to bring FSX to its knees.  So it is always good to look at it.  You will probably be shocked to see all of the errors happening on your computer system as everything is recorded.

 

The AVSIM CTD Guide can be found by going to the link in my signature or clicking on the link on the right sidebar under Hot Spots.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

The AVSIM CTD Guide provides for fixing freezes after takeoff.  The Majestic Dash 8 Q400 uses a lot of resources so, if you have settings set high and the sim runs out of resources, it will freeze up.  On page 9/10 of the AVSIM CTD Guide, it tells you how to fix most freezes/crashes.  Other than that, you need to investigate what's happening on YOUR system as it does not occur to everyone.  The AVSIM CTD Guide also shows you one location in the Event Viewer where you will see every event, whether associated with FSX or your system activity.  I even included pictures.  Freezes/hangs have shown up in other cases like the one you described but it usually will show an unknown error caused the B1 Hang.  So, in your case, looking at the Event Viewer, even if it shows the events, will probably be useless.  However, if your system was scanning your HDD or SSD or running some other type of event during your flight, this could have taken up enough resources to bring FSX to its knees.  So it is always good to look at it.  You will probably be shocked to see all of the errors happening on your computer system as everything is recorded.

 

The AVSIM CTD Guide can be found by going to the link in my signature or clicking on the link on the right sidebar under Hot Spots.

 

Best regards,

Jim

 

I'm taking a look at the guide right now. It is very good so far. An update on the problem. I ran FSX in windowed mode alongside WhatIsHang.exe and got a "Hang report". See it below, it looks to be that the faulting module is with the Kernelbase.dll and the ntdll.dll, tell me what you guys think.

 

 

Hang report for C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Generated by using WhatIsHang on 2016-09-06 1:44:41 PM
 
 
Remarks:
* The program hangs in a single system call. You can look in the call stack and  stack data to find out which API function cause this hang.
 
 
Strings found in the stack:
assert
getcurrentstatehandle
 
 
Modules found in the stack:
C:\WINDOWS\System32\KERNELBASE.dll , Microsoft Corporation , Microsoft® Windows® Operating System, Windows NT BASE API Client DLL
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dll , Microsoft Corp. , Microsoft® Flight Simulator X, terrain dll
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL , Microsoft Corp. , Microsoft® Flight Simulator X, api dll
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dll , Microsoft Corp. , Microsoft® Flight Simulator X, fsui dll
 
ThreadID: 6252
 
 
Execute Address:
7753F7CC  ntdll.dll!NtWaitForAlertByThreadId+0xc
 
Call Stack:
03B8F4C4  747ED786  KERNELBASE.dll!UnhandledExceptionFilter+0xd6
03B8F558  7479C6AF  KERNELBASE.dll+0x10c6af
03B8FFEC  7476EB16  KERNELBASE.dll!GetCPHashNode+0x2c6
 
 
Stack Data:
03B8F474  7750AE88  ntdll.dll!RtlAcquireSRWLockExclusive+0x128
03B8F478  74806820  KERNELBASE.dll+0x176820
03B8F47C  00000000
03B8F480  00000000
03B8F484  00000000
03B8F488  00000000
03B8F48C  03B8F4B0
03B8F490  774F390B  ntdll.dll!RtlQueryProtectedPolicy+0x3b
03B8F494  01224538  fsx.exe+0x224538
03B8F498  00000000
03B8F49C  044CF853
03B8F4A0  044CF850
03B8F4A4  03B8F4A0
03B8F4A8  00000000
03B8F4AC  0000186C
03B8F4B0  FFFFFFFF
03B8F4B4  00000005
03B8F4B8  00000004
03B8F4BC  00000000
03B8F4C0  00000000
03B8F4C4  03B8F558
03B8F4C8  747ED786  KERNELBASE.dll!UnhandledExceptionFilter+0xd6
03B8F4CC  74806820  KERNELBASE.dll+0x176820
03B8F4D0  AB32BFE3
03B8F4D4  00000000
03B8F4D8  00000000
03B8F4DC  00000000
03B8F4E0  03B8FB8C
03B8F4E4  00000000
03B8F4E8  029B9DF4
03B8F4EC  00000001
03B8F4F0  00000006
03B8F4F4  03B8F588
03B8F4F8  090D0F10
03B8F4FC  00000000
03B8F500  00000000
03B8F504  00000000
03B8F508  74789330  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x1a0
03B8F50C  03B8F540
03B8F510  7750F1B2  ntdll.dll!RtlImageNtHeaderEx+0x312
03B8F514  775DF654  ntdll.dll+0x10f654
03B8F518  74789330  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x1a0
03B8F51C  03B8F6AC
03B8F520  0009FDA0
03B8F524  00000000
03B8F528  0009EF70
03B8F52C  00000000
03B8F530  7473DB50  KERNELBASE.dll+0xadb50
03B8F534  03B8F574
03B8F538  74789330  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x1a0
03B8F53C  AB32BFE3
03B8F540  03B8F4D0
03B8F544  7752E98F  ntdll.dll!RtlUnwind+0x36f
03B8F548  03B8F5BC
03B8F54C  74789330  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x1a0
03B8F550  DCF50C5B
03B8F554  FFFFFFFE
03B8F558  03B8FFEC
03B8F55C  7479C6AF  KERNELBASE.dll+0x10c6af
03B8F560  03B8F588
03B8F564  74789570  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x3e0
03B8F568  03B8FFDC
03B8F56C  FFFFFFFE
03B8F570  00000000
03B8F578  747893AE  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x21e
03B8F590  747F3C40  KERNELBASE.dll+0x163c40
03B8F59C  747F3C30  KERNELBASE.dll+0x163c30
03B8F5A8  775523B2  ntdll.dll!RtlConvertUlongToLargeInteger+0xa2
03B8F5C0  775523D0  ntdll.dll!RtlConvertUlongToLargeInteger+0xc0
03B8F5CC  77552384  ntdll.dll!RtlConvertUlongToLargeInteger+0x74
03B8F5E0  74789330  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x1a0
03B8F5F0  7752E8AF  ntdll.dll!RtlUnwind+0x28f
03B8F604  74789330  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x1a0
03B8F698  7753FF1F  ntdll.dll!KiUserExceptionDispatcher+0xf
03B8F724  20D8CA39  terrain.dll+0x4ca39
03B8F72C  20D45DD8  terrain.dll+0x5dd8
03B8F7D0  20D8CA39  terrain.dll+0x4ca39
03B8F7D8  20D45DD8  terrain.dll+0x5dd8
03B8FA50  20D4C924  terrain.dll+0xc924
03B8FA58  741C61C0  KERNEL32.DLL!InterlockedIncrement
03B8FA64  200F4D8E  API.DLL!Ordinal307+0xaf6
03B8FA7C  7753DCCC  ntdll.dll!NtSetEvent+0xc
03B8FA80  74763A70  KERNELBASE.dll!SetEvent+0x10
03B8FA90  200F57C3  API.DLL+0x157c3
03B8FAAC  200F61AF  API.DLL!Ordinal244+0x8a
03B8FABC  200F61BF  API.DLL!Ordinal247+0xd
03B8FAC4  20D4C99B  terrain.dll+0xc99b
03B8FACC  20DC0669  terrain.dll+0x80669
03B8FAE4  20DC2EB4  terrain.dll+0x82eb4
03B8FAF8  20D9E03D  terrain.dll+0x5e03d
03B8FB04  20DC2EB4  terrain.dll+0x82eb4
03B8FB18  20D63B16  terrain.dll+0x23b16
03B8FB28  20DDAD92  terrain.dll+0x9ad92
03B8FB34  20D59E02  terrain.dll+0x19e02
03B8FB48  20DDADB4  terrain.dll+0x9adb4
03B8FB5C  20DDBDF7  terrain.dll+0x9bdf7
03B8FB84  20DFCCF0  terrain.dll+0xbccf0
03B8FB90  20DD7E97  terrain.dll+0x97e97
03B8FBFC  20E01559  terrain.dll+0xc1559
03B8FC08  20D7A5E8  terrain.dll+0x3a5e8
03B8FC7C  20570000  fsui.dll+0x90000
03B8FCE0  7751B10D  ntdll.dll+0x4b10d
03B8FD30  7751AB99  ntdll.dll+0x4ab99
03B8FD7C  77518755  ntdll.dll!RtlFreeHeap+0xf65
03B8FD84  77518419  ntdll.dll!RtlFreeHeap+0xc29
03B8FDAC  77518755  ntdll.dll!RtlFreeHeap+0xf65
03B8FDB4  77518419  ntdll.dll!RtlFreeHeap+0xc29
03B8FE54  77517951  ntdll.dll!RtlFreeHeap+0x161
03B8FE64  20E00CD0  terrain.dll+0xc0cd0
03B8FE70  20D7A0AF  terrain.dll+0x3a0af
03B8FEC4  20DE8C40  terrain.dll+0xa8c40
03B8FECC  20E0254A  terrain.dll+0xc254a
03B8FED8  20D79D5D  terrain.dll+0x39d5d
03B8FF58  20D79FA3  terrain.dll+0x39fa3
03B8FF64  7750F700  ntdll.dll!RtlLeaveCriticalSection
03B8FF68  200F4F7A  API.DLL!Ordinal307+0xce2
03B8FF74  200F4E7A  API.DLL!Ordinal307+0xbe2
03B8FF98  201ED819  API.DLL+0x10d819
03B8FFA8  200F4E8C  API.DLL!Ordinal307+0xbf4
03B8FFB4  7476EB68  KERNELBASE.dll!GetCPHashNode+0x318
03B8FFE0  74789330  KERNELBASE.dll!GetAdjustObjectAttributesForPrivateNamespaceRoutine+0x1a0
03B8FFF0  7476EB16  KERNELBASE.dll!GetCPHashNode+0x2c6
 

Share this post


Link to post
Share on other sites

So the hang was caused by the kernelbase.dll.  According to the AVSIM CTD Guide, page 31:

 

Kernelbase.dll – No known fix but some have solved this problem by -

  • Updating or reinstalling their video card drivers.
  • Scanning your system for corrupt/missing files.
  • Disable startup programs by typing msconfig in the Windows search box. When open, look at the Startup tab and disable all startups (they are all not needed for operation of your computer)(see page 22 of the guide).
  • User Profile Corrupted – last resort, fix possible corrupted user profile.

In the guide I have links to websites that tell you exactly how to do scan for corrupt files or fix a possible corrupted user profile.  Fixing a possible corrupted profile should be a last resort but it saves you from reinstalling Windows.  You might also check to make sure you are running FSX in Admin mode (see page 10 to see how to check this).  You may not have all of the privileges required to run FSX and the M400.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Figured it out! Turns out the FSX settings were too high. I was getting a buttery smooth 40FPS but the sim just wasn't happy with the workload, which is why it was hanging. I toned down the settings and it all worked out!

Share this post


Link to post
Share on other sites

 

 


Figured it out! Turns out the FSX settings were too high. I was getting a buttery smooth 40FPS but the sim just wasn't happy with the workload, which is why it was hanging. I toned down the settings and it all worked out!

 

It's more likely you had a race condition - changing the timing (in any direction) prevented it from happening.

 

Cheers!

 

Luke

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this