Hi
I have recently upgraded my PC massively, but for some reason the new install keeps on crashing on certain routes (mostly GEML and ECML KX-PBO). I know it shouldn't be my pc as I have a i5 4690K OC to 4.8ghz, 2xGibabyte GTX 770 OC (stock) in SLi and 8gb ram.
I get no other clues other than TS2015 has created a dump file (TS2015 - v48.9a). Is there any way to open this file in a readable format to find out whats going wrong. When I open it in notepad its just 'gibberish'. It only seems to happen when I go to an outside view
Please help
Many thanks
Mark
How do you work out why it crashes
Moderator: Moderators
-
electric
- Established Forum Member
- Posts: 368
- Joined: Mon Mar 29, 2004 3:38 pm
- Location: Albrighton, Nr. Wolves, Shrops
How do you work out why it crashes
Move with your heart, live with your conscience
<<she's gorgeous<<
Signalling engineering technician apprentice
A.K.A nutter and grinch on other forums
<<she's gorgeous<<
Signalling engineering technician apprentice
A.K.A nutter and grinch on other forums
- Dave4468
- Well Established Forum Member
- Posts: 859
- Joined: Tue Jan 24, 2012 10:15 pm
- Location: Norwich
Re: How do you work out why it crashes
For many reasons most of which can be traced back to a, in computer terms, ancient (2007) core TS can crash and stutter on high end PCs. There are a few solvable reasons but to deduce those we will need some more specific info about the route and scenario.
And TS is far more open on its crashes than it used to be, now it tells you about a dump file as opposed to the now extinct "Something Bad Has Happened" popup...
And TS is far more open on its crashes than it used to be, now it tells you about a dump file as opposed to the now extinct "Something Bad Has Happened" popup...
If only all problems on the big railway could simply be TAB'd past...
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: How do you work out why it crashes
Any hardware forum would soon tell you that such an overclock can lead to unexpected crashes; as soon as you take any component outside of it's designed limits and have bother the first step is to go back to a default configuration, so have you tried the game with the CPU running at it's base frequency of 3.5Ghz?electric wrote:I know it shouldn't be my pc as I have a i5 4690K OC to 4.8ghz,
- alanch
- Very Active Forum Member
- Posts: 4907
- Joined: Mon Feb 27, 2006 6:07 pm
- Location: Leeds, England
- Contact:
Re: How do you work out why it crashes
You haven't told us which operating system you have - should we assume that it is 64 bit so it can use all that 8Gb of memory?electric wrote:I know it shouldn't be my pc as I have . . . . and 8gb ram.
Alan
My railway photos are now on Google + - links to the albums are in this thread http://forums.uktrainsim.com/viewtopic. ... 9&t=149558
Lots of steam and early diesels from 1959 to 1963.
My railway photos are now on Google + - links to the albums are in this thread http://forums.uktrainsim.com/viewtopic. ... 9&t=149558
Lots of steam and early diesels from 1959 to 1963.
-
electric
- Established Forum Member
- Posts: 368
- Joined: Mon Mar 29, 2004 3:38 pm
- Location: Albrighton, Nr. Wolves, Shrops
Re: How do you work out why it crashes
Hi
Yes its windows 7 64 bit.
And no I haven't, but my understanding was almost all CPU crashes brought up the blue screen 'of death' (It happened when I was doing the overclock with the Asus software) from past experiences of when CPUs have thrown in the towel.
I can run FSX and x-plane 10 on full settings without any issues, so wouldn't have though TS2015 would have been any more cpu intensive. Maximum CPU temp I've ever had was 52oC and that was flying over london in FSX with a shed load of add-ons (ok that time it crashed as FSX ran out of RAM :/) and I'd forgotten to turn up my fan settings, normal temp is between 25 and 33oC.
I have tried it on a reduced overclock of 4.6 and still have the same issue.
On GEML its any scenario (I only use career ones at the moment) and ECML it was happening until this evening when I managed to finish the 801 PBO-KX run without any issues.
I will try running GEML at stock speeds tomorrow. Any other ideas in the mean time just let me know
Many Thanks
Mark
Yes its windows 7 64 bit.
And no I haven't, but my understanding was almost all CPU crashes brought up the blue screen 'of death' (It happened when I was doing the overclock with the Asus software) from past experiences of when CPUs have thrown in the towel.
I can run FSX and x-plane 10 on full settings without any issues, so wouldn't have though TS2015 would have been any more cpu intensive. Maximum CPU temp I've ever had was 52oC and that was flying over london in FSX with a shed load of add-ons (ok that time it crashed as FSX ran out of RAM :/) and I'd forgotten to turn up my fan settings, normal temp is between 25 and 33oC.
I have tried it on a reduced overclock of 4.6 and still have the same issue.
On GEML its any scenario (I only use career ones at the moment) and ECML it was happening until this evening when I managed to finish the 801 PBO-KX run without any issues.
I will try running GEML at stock speeds tomorrow. Any other ideas in the mean time just let me know
Many Thanks
Mark
Move with your heart, live with your conscience
<<she's gorgeous<<
Signalling engineering technician apprentice
A.K.A nutter and grinch on other forums
<<she's gorgeous<<
Signalling engineering technician apprentice
A.K.A nutter and grinch on other forums
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: How do you work out why it crashes
Yes, but the game is crashing not the CPUelectric wrote: but my understanding was almost all CPU crashes brought up the blue screen 'of death'
unexpected, random, seemingly unconnected; and many more descriptors. It may not be related to the OC but the only way to find out is to start with the obvious.gptech wrote:.....an overclock can lead to unexpected crashes
How FSX, or any other program, behaves can't be taken as a yardstick to measure/evaluate any other program by; they all have their own ways of finding the weakness that can bring a PC down and unfortunately having powerful hardware doesn't negate that. This is even more true when you consider that the core of TS2015 is still 'pretty ancient' as Dave eloquently and accurately described it.electric wrote:Maximum CPU temp I've ever had was 52oC and that was flying over london in FSX with a shed load of add-ons (ok that time it crashed as FSX ran out of RAM :/) and I'd forgotten to turn up my fan settings, normal temp is between 25 and 33oC.
Try a standard scenario, there are plenty in the library here or even drop into the editor and create a simple free roam one--just stick a light engine on the track somewhere and see if it drives.electric wrote:On GEML its any scenario (I only use career ones at the moment)
- Trev123
- Very Active Forum Member
- Posts: 4403
- Joined: Tue Oct 19, 2010 9:13 pm
- Location: Home Of The Americas Cup
Re: How do you work out why it crashes
You could also run Logmate from your main TS2015 directory. Start it before you start TS2015 by double clicking on it.
Intel i5-2500K 3.3GHz Quad Core, Asus P8Z 68-V LE MB, Asus GTX 1060 Strix 6GB Gaming graphics card, Windows 10 Home 64 bit, 16gb Corsair Vengeance DDR3 ram, Viewsonic VX2452mh LED 1080P HD Monitor. Seagate Barracuda 1 TB HD, Seagate Firecuda 2 TB HD,
Re: How do you work out why it crashes
I overclocked my last cpu (i5 3570K) to 4.4 Ghz. It ran various stress tests fine but found that TS would sometimes crash (fine at stock frequency and settings). I had to up the voltage of the cpu overclock slightly which cured the problem. TS can be very fussy when it comes to hardware!
Regards,
Len
Regards,
Len
-
electric
- Established Forum Member
- Posts: 368
- Joined: Mon Mar 29, 2004 3:38 pm
- Location: Albrighton, Nr. Wolves, Shrops
Re: How do you work out why it crashes
I've overclocked it using asus AI suite software as I didn't want to risk frying anything by increasing the voltages too much.
I just ran the 17:50 Liverpool street - Norwich at 3.6 Ghz (lowest AI suite will do) and got much much further than before, about 20 miles short of Maingtree rather than just past Gilders Park and that was whilst prating around with excessive use of external views so I think this is where the problem is. Interestingly this time there were many points of severe stuttering where I thought it would crash but in the last couple of minutes it got worse before crashing, So I think we may be onto something here
One surprise for me was that between 3.6 and 4.8 I only lost 2 FPS
I had logmate running at the time. There are too many characters to post (over 500,00) but from a quick scan there were lots of run time errors looking like this:
then others looking like this
Then others looking like this
One thing I will mention in regards to the last one is that since moving PCs everything except windows is on a seperate partition drive Z:
By the looks of it I'm missing something when I downloaded everything off steam
Many thanks
Mark
I just ran the 17:50 Liverpool street - Norwich at 3.6 Ghz (lowest AI suite will do) and got much much further than before, about 20 miles short of Maingtree rather than just past Gilders Park and that was whilst prating around with excessive use of external views so I think this is where the problem is. Interestingly this time there were many points of severe stuttering where I thought it would crash but in the last couple of minutes it got worse before crashing, So I think we may be onto something here
One surprise for me was that between 3.6 and 4.8 I only lost 2 FPS
I had logmate running at the time. There are too many characters to post (over 500,00) but from a quick scan there were lots of run time errors looking like this:
Code: Select all
[RunTimeError 23:22:03]
[RunTimeError 23:22:03] cCurveEasement.cpp : 787
[RunTimeError 23:22:03] Assertion failed
[RunTimeError 23:22:03]
[RunTimeError 23:22:03] ASSERT(t >= kNormFloat::start && t <= kNormFloat::end);
[RunTimeError 23:22:03]
[RunTimeError 23:22:03] cCurveEasement::getTangent()
[RunTimeError 23:22:03]
[RunTimeError 23:22:03] cCurveEasement.cpp : 903
[RunTimeError 23:22:03] Assertion failedCode: Select all
[RunTimeError 23:22:21] Unexpected case: 5C68 17:16 Ilford E.MU.D. - London Liverpool Street @ node: 12729
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] DispatcherV1::cOccupancyEnumerator::TestOccupationOrder()
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] cOccupancyEnumerator.cpp : 659
[RunTimeError 23:22:21] Unexpected case: 5C68 17:16 Ilford E.MU.D. - London Liverpool Street @ node: 12729
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] DispatcherV1::cOccupancyEnumerator::TestOccupationOrder()
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] cOccupancyEnumerator.cpp : 659
[RunTimeError 23:22:21] Unexpected case: 5C68 17:16 Ilford E.MU.D. - London Liverpool Street @ node: 12729
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] DispatcherV1::cOccupancyEnumerator::TestOccupationOrder()
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] cOccupancyEnumerator.cpp : 659
[RunTimeError 23:22:21] Unexpected case: 5C68 17:16 Ilford E.MU.D. - London Liverpool Street @ node: 12729
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] DispatcherV1::cOccupancyEnumerator::TestOccupationOrder()
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] cOccupancyEnumerator.cpp : 659
[RunTimeError 23:22:21] Unexpected case: 5C68 17:16 Ilford E.MU.D. - London Liverpool Street @ node: 12729
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] DispatcherV1::cOccupancyEnumerator::TestOccupationOrder()
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] cOccupancyEnumerator.cpp : 659
[RunTimeError 23:22:21] Unexpected case: 5C68 17:16 Ilford E.MU.D. - London Liverpool Street @ node: 12729
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] DispatcherV1::cOccupancyEnumerator::TestOccupationOrder()
[RunTimeError 23:22:21]
[RunTimeError 23:22:21] cOccupancyEnumerator.cpp : 659
Code: Select all
[RunTimeError 23:50:52] Track Rule missing: ////
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] ASSERT(mTrackRule != 0);
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] Network::iTrackNetworkTrackRule::cPropertyValue::setTrackRule()
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] C:\build\CoreRelease\Code\\PublicInterfaces\iTrackNetworkProperties.d.h : 84
[RunTimeError 23:50:52] Track Rule missing: ////
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] ASSERT(mTrackRule != 0);
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] Network::iTrackNetworkTrackRule::cPropertyValue::setTrackRule()
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] C:\build\CoreRelease\Code\\PublicInterfaces\iTrackNetworkProperties.d.h : 84
[RunTimeError 23:50:52] Track Rule missing: ////
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] ASSERT(mTrackRule != 0);
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] Network::iTrackNetworkTrackRule::cPropertyValue::setTrackRule()
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] C:\build\CoreRelease\Code\\PublicInterfaces\iTrackNetworkProperties.d.h : 84
[RunTimeError 23:50:52] Track Rule missing: ////
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] ASSERT(mTrackRule != 0);
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] Network::iTrackNetworkTrackRule::cPropertyValue::setTrackRule()
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] C:\build\CoreRelease\Code\\PublicInterfaces\iTrackNetworkProperties.d.h : 84
[RunTimeError 23:50:52] Track Rule missing: ////
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] ASSERT(mTrackRule != 0);
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] Network::iTrackNetworkTrackRule::cPropertyValue::setTrackRule()
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] C:\build\CoreRelease\Code\\PublicInterfaces\iTrackNetworkProperties.d.h : 84
[RunTimeError 23:50:52] Track Rule missing: ////
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] ASSERT(mTrackRule != 0);
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] Network::iTrackNetworkTrackRule::cPropertyValue::setTrackRule()
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] C:\build\CoreRelease\Code\\PublicInterfaces\iTrackNetworkProperties.d.h : 84
[RunTimeError 23:50:52] Track Rule missing: ////
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] ASSERT(mTrackRule != 0);
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] Network::iTrackNetworkTrackRule::cPropertyValue::setTrackRule()
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] C:\build\CoreRelease\Code\\PublicInterfaces\iTrackNetworkProperties.d.h : 84
[RunTimeError 23:50:52] Track Rule missing: ////
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] ASSERT(mTrackRule != 0);
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] Network::iTrackNetworkTrackRule::cPropertyValue::setTrackRule()
[RunTimeError 23:50:52]
[RunTimeError 23:50:52] C:\build\CoreRelease\Code\\PublicInterfaces\iTrackNetworkProperties.d.h : 84By the looks of it I'm missing something when I downloaded everything off steam
Many thanks
Mark
Move with your heart, live with your conscience
<<she's gorgeous<<
Signalling engineering technician apprentice
A.K.A nutter and grinch on other forums
<<she's gorgeous<<
Signalling engineering technician apprentice
A.K.A nutter and grinch on other forums