ORTS.Processes.ThreadHangException at ORTS.Program.Main (1.0.1.3095, Marias Pass, crashes a short distance after the train starts moving)

[Randal Merzdorf]

Running Open Rails 1.0

Application starts fine. Tried the two default MSTS routes (Northeast and Marias Pass). Sim starts but crashes shortly after the train has begun to move. Crash also kills windows.

Log file is attached.

Thanks for the help!

[Carlo Santucci (carlosanit1)]

I didn't get the crash with the path shown in the logfile, and by the way I don't see crashes in the logfile. Are you sure you attached the logfile of the faulty run and not of a successful run?

[Randal Merzdorf (rmerzdorf)]

I guess it is possible that the app crashed before it was able to write any errors to the log file - correct?

The crash doesn't just kill the app - it crashes Windows - to the point I been to control-alt-delete to get Windows to restart.

I ran the route through Route Writer before starting Open Rails just to make sure there were no errors with that.

This crash happens in the same manner with any route I have tried - Open Rails starts, allows me to select a route and train, and starts the sim with no issues. Nothing crashes until I start moving the train - and I always get to move the train forward a short distance, which is when both Open Rails and Windows crash with a black screen.

Are there any other logs that would be helpful that I could look for?

Thanks!

Sent from my Verizon Wireless 4G LTE DROID

Carlo Santucci <email address hidden> wrote:

I didn't get the crash with the path shown in the logfile, and by the
way I don't see crashes in the logfile. Are you sure you attached the
logfile of the faulty run and not of a successful run?

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1518760

Title:
  Open Rails crashes a short distance after the train starts moving
  (1.0.1.3095, Marias Pass)

Status in Open Rails:
  New

Bug description:
  Running Open Rails 1.0

  Application starts fine. Tried the two default MSTS routes (Northeast
  and Marias Pass). Sim starts but crashes shortly after the train has
  begun to move. Crash also kills windows.

  Log file is attached.

  Thanks for the help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/or/+bug/1518760/+subscriptions

[Carlo Santucci (carlosanit1)]

Randal,
I filed a request for suggestions here http://www.elvastower.com/forums/index.php?/topic/27872-black-screen-crash-few-after-or-start/page__view__findpost__p__193581 , as I have no idea about what could happen.
Do you run OR in full screen mode or in windowed mode? If you run it in full screen mode, pls. try running it in windowed mode and check if it is the whole screen that gets black, or only the OR window.

[Randal Merzdorf (rmerzdorf)]

After correcting some video driver issues, the log file is now capturing some error messages:

Error: ORTS.Processes.ThreadHangException: Thread 'Render Process' has hung; the consistent stack trace is shown below:
   at Microsoft.Xna.Framework.WindowsGameHost.ApplicationIdle(Object sender, EventArgs e)
   at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at Microsoft.Xna.Framework.WindowsGameHost.Run()
   at Microsoft.Xna.Framework.Game.Run()
   at ORTS.Program.Main(String[] args) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Program.cs:line 55

I have attached file with all messages.

Also - yes this same activity and consist works in MSTS without an issue.

Thanks!

[Carlo Santucci (carlosanit1)]

The thread hang error occurs when there is an unwanted endless loop or when the computer is too slow loading or executing the program. Was your computer doing some other activity while loading the game. Have you tried loading this activity more than once with the same result?

[Randal Merzdorf (rmerzdorf)]

Carlo:

I restarted the machine to make sure nothing else was running in the background. The behavior is very consistent - the application crashes Windows after about 4 minutes - whether the train is moving or not.

 I downloaded a 'blue screen' crash reporter app and it highlighted three items as potential culprits;
hal.dll
ntoksrnl.exe
pci.sys

Does any of this help?

Thanks!

Randal
________________________________________
From: <email address hidden> <email address hidden> on behalf of Carlo Santucci <email address hidden>
Sent: Thursday, December 10, 2015 4:57 AM
To: <email address hidden>
Subject: [Bug 1518760] Re: Open Rails crashes a short distance after the train starts moving (1.0.1.3095, Marias Pass)

The thread hang error occurs when there is an unwanted endless loop or
when the computer is too slow loading or executing the program. Was your
computer doing some other activity while loading the game. Have you
tried loading this activity more than once with the same result?

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1518760

Title:
  Open Rails crashes a short distance after the train starts moving
  (1.0.1.3095, Marias Pass)

Status in Open Rails:
  New

Bug description:
  Running Open Rails 1.0

  Application starts fine. Tried the two default MSTS routes (Northeast
  and Marias Pass). Sim starts but crashes shortly after the train has
  begun to move. Crash also kills windows.

  Log file is attached.

  Thanks for the help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/or/+bug/1518760/+subscriptions

[Carlo Santucci (carlosanit1)]

I'm sorry, this seems to be a system level incompatibillity between OR and the system software of your computer. I'm not able to help you on this.