Recommended Posts

I have the same settings and addons as I had with v4.4. No KERNELBASE.dll crashes with that one. I did have the occasional crash but never so many in quick succession.

The only thing that has changed is the point update of P3D. If I revert to 4.4 and they continue then I know I need to look at settings and/or addons.

If they don’t continue then the finger is most definitely pointing to 4.5.

  • Upvote 1

Share this post


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

On 5/23/2019 at 7:41 PM, Gandalf said:

Hi, still having problems, also wondered if it was Radar Contact related but then there would be more posts on that?

I can assure you Radar Contact is not the problem. It only reads from P3D via FSUIPC. You still running 4.5? Did they happen with 4.4 and earlier?

Share this post


Link to post
Share on other sites
53 minutes ago, Ray Proudfoot said:

You can add me to this group. v4.4 was very stable but since changing to 4.5 I've had lots of CTDs with KERNELBASE.dll being responsible. Twice it crashed lining  up on 27R at EGLL and again when rotating on same runway.

Deleted Prepar3g.cfg and was able to fly up to Manchester. But on the return I'm 10 miles out of 27R and it goes again. Seriously thinking of reverting to v4.4.

Personally, I would revert. Wait until 4.6 or something... BTW Ray, we are well on the way to building the PC.

  • Like 1

Share this post


Link to post
Share on other sites
32 minutes ago, Ray Proudfoot said:

I have the same settings and addons as I had with v4.4. No KERNELBASE.dll crashes with that one. I did have the occasional crash but never so many in quick succession.

The only thing that has changed is the point update of P3D. If I revert to 4.4 and they continue then I know I need to look at settings and/or addons.

If they don’t continue then the finger is most definitely pointing to 4.5.

I agree. I had perfectly stable machine ever since I installed 4.0 and I am also thinking about reverting back, but I've deleted my 4.4 .cab files and possibly the exe too and LM doesn't have these available for download anymore.

Share this post


Link to post
Share on other sites
1 minute ago, Drumcode said:

I agree. I had perfectly stable machine ever since I installed 4.0 and I am also thinking about reverting back, but I've deleted my 4.4 .cab files and possibly the exe too and LM doesn't have these available for download anymore.

I can make the 4.4 client available if you’re struggling. Assuming my Dropbox account is big enough.

Share this post


Link to post
Share on other sites

I would need client and content both.

Share this post


Link to post
Share on other sites
1 hour ago, Drumcode said:

I would need client and content both.

I'm uploading them to my dropbox account . Not sure if the cont1.cab and cont2.cab files are also needed. If so they're probably too large for my free account.

I'll PM you when they're available.

Share this post


Link to post
Share on other sites
Posted (edited)

Ok, beginning to narrow it down (possibly) I uninstalled everything, core programme and all add ons, deleted all remaining folders and files and cleaned the registry. Redownloaded P3d and installed. Did a couple of flights, no problems. Downloaded Aerosoft 318/19 bundle and installed. Did 3 three hour flights, no problem. So far so good. Downloaded and installed fsuipc and makerws (had been getting regular crashes with fsuipc showing as the faulting module) another couple of 3 hour flights, still no problem. Installed and used Radar Contact, all good. Tonight installed AIM OCI and.... crash about 40 mins in. So just about to disable AIM and see what happens.

Ray, I believe you have gone over to AIM? It’s interesting because there is no mention of any crashes on the AIG forum.

I think more testing required at my end, I’d be disappointed to have to either fly with no AI or have to re-install UT Live. 

The other thing I need to try as a long shot is disable AI interaction in Radar Contact.

Hope someone finds this helpful, I’ll keep testing anyway

Regards

G

Sorry Ray, just realised hadn’t answered your question, infrequent crashes before 4.5, almost constant now...

Edited by Gandalf
Additional info
  • Like 1

Share this post


Link to post
Share on other sites

@Gandalf, yes, running AIG Ai if that's what you mean. No restrictions put on how many Ai. So over 300 at EGLL with 200 on ground and 100 airborne. But that takes in all London airports, not just Heathrow. I've disabled the UTL add-on today. Not uninstalled - yet.

I'll have to check if I have Ai Interaction on in RC4. Tomorrow now. So just to confirm you're on 4.5 still?

Share this post


Link to post
Share on other sites

Yes, running 4.5. The reason I mentioned Radar Contact was that I was/am getting fsuipc showing as the faulting module and RC is the only add on I have that uses fsuipc and wondered if there was a rogue AI somewhere. 

I’m probably clutching at straws... 

Regards

G

Share this post


Link to post
Share on other sites

That's a red herring I'm sure. If FSUIPC was genuinely the issue the board would be swamped. A rogue Ai? Ouch! That could be tricky to find.

All you can do is run the same test at the same sim time. I have a saved scenario lined up on 27R at EGLL that I'm using. Good luck!

Share this post


Link to post
Share on other sites

As I am very limited on time related to flight simulation, I am reverting back (thank you Ray!) and will report back whether 4.4 is problematic still. It may take me a few days to report back. 

Share this post


Link to post
Share on other sites
8 minutes ago, Drumcode said:

As I am very limited on time related to flight simulation, I am reverting back (thank you Ray!) and will report back whether 4.4 is problematic still. It may take me a few days to report back. 

Good luck, hope it works! And sorry to hijack your thread 😊

Share this post


Link to post
Share on other sites

So it seems a DLL is faulting, FSUIPC, but only after the inclusion of an AI package. Remember I said often the cause of CTD is due to an attached module. Even though a dll is at fault it may not be the fault of that dll itself, it could be something it reports on or uses. Perhaps an AI aircraft that FSUIPC is culling or that culling is not reliable in some other way with that AI package. Since no CTD was seen with RC4 with FSUIPC then possibly that part of the system is sound.

Share this post


Link to post
Share on other sites

AI traffic can be selecting a set of paints different in other areas and less frequent flights in certain locations or times of day so a particular model causing an issue might not come up all the time. One idea to check out a suspicious model is to try halving the ai models to see if the problem goes away with one or other half in use.

  • Upvote 1

Share this post


Link to post
Share on other sites
3 minutes ago, SteveW said:

AI traffic can be selecting a set of paints different in other areas and less frequent flights in certain locations or times of day so a particular model causing an issue might not come up all the time. One idea to check out a suspicious model is to try halving the ai models to see if the problem goes away with one or other half in use.

Now that’s a good idea, well, better than mine which was removing all AI then adding it in one at a time 🙂 a job I’m not looking forward to!

Haven’t totally nailed it to AIM OCI but I’m having strong suspicions. The one thing that makes me doubt is that there’s no reports of anything similar on the AIG boards and I can’t be the only one using AIM with Radar Contact.

Anyway, I’ll keep testing and see what turns up...

Regards

G

Share this post


Link to post
Share on other sites
19 minutes ago, Gandalf said:

Now that’s a good idea, well, better than mine which was removing all AI then adding it in one at a time 🙂 a job I’m not looking forward to!

Haven’t totally nailed it to AIM OCI but I’m having strong suspicions. The one thing that makes me doubt is that there’s no reports of anything similar on the AIG boards and I can’t be the only one using AIM with Radar Contact.

Anyway, I’ll keep testing and see what turns up...

Regards

G

That’s the benefit of so many Ai BGLs. Do a binary chop and take it from there. I flew from EGLL this morning without RC4 running and P3D still crashed so you can forget that.

Share this post


Link to post
Share on other sites
1 hour ago, Gandalf said:

Good luck, hope it works! And sorry to hijack your thread 😊

No need to be sorry, precisely the opposite, keep the discussion going. 

Share this post


Link to post
Share on other sites
8 hours ago, Ray Proudfoot said:

That’s the benefit of so many Ai BGLs. Do a binary chop and take it from there. I flew from EGLL this morning without RC4 running and P3D still crashed so you can forget that.

Ok thanks, that’s good to know. We’re you using AIM OCI for your AI? And if so have you tried without? I flew with both again last night and sure enough crash, this time approximately 1hour in. 

 

Share this post


Link to post
Share on other sites
55 minutes ago, Gandalf said:

Ok thanks, that’s good to know. We’re you using AIM OCI for your AI? And if so have you tried without? I flew with both again last night and sure enough crash, this time approximately 1hour in.

Yes, I have the AIG Ai. I haven't tried a flight without it yet. I'll be constructing a series of tests today to try and establish where the problem lies. I will stick to 4.5 and use 100% AIG Ai for the first test at EGLL. If it crashes then repeat with 50% of the BGLs. If it still crashes then substitute those 50% with the other 50% just in case it's a bad BGL.

Incidentally, please state what build of P3D you're using and what the crash type was. MIne are KERNELBASE.dll with 4.5.

Share this post


Link to post
Share on other sites

Sorry for gatecrashing your topic @Drumcode. I've tried my test flight 6 times this morning and cannot get P3D to crash. Even used the same time as yesterday's crash but still it works. Frustrating isn't the word. Still on v4.5.

Share this post


Link to post
Share on other sites

just having a read through...as you do..not that im having these probs as i dont use ai yet...but:

If you test today at the same time, nothing happens , all good, great.

But if you have a bad Ai plane...that only gets used on a tuesday, you wont see a crash untill next tuesday...if you follow..(that particular airline may not fly there more than once a week...)

....just an observation from reading the thread....i have no experience with the programs.

Share this post


Link to post
Share on other sites
Posted (edited)

After 6 successful tests with the scenario that crashed yesterday I setup a new flight from EGLL to EHAM. Taxied out and lined up on 27R. On rotation the sim crashed. Looking at Event Viewer the reports show what happened in sequence...

11:57:24

Application: PREPAR3D.EXE
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFF0C7B11F8
Stack:

11:57:26

Faulting application name: PREPAR3D.EXE, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: FSUIPC5.dll, version: 5.1.5.1, time stamp: 0x5ce4055a
Exception code: 0xc0000005
Fault offset: 0x00000000000e11f8
Faulting process ID: 0xff0
Faulting application start time: 0x01d516082b1b1d1a
Faulting application path: D:\P3Dv4\PREPAR3D.EXE
Faulting module path: D:\P3Dv4\Modules\FSUIPC5.dll
Report ID: e9fe369f-f2e6-4e9a-8461-7fd94e909d99
Faulting package full name:
Faulting package-relative application ID:

11:57:29

Faulting application name: PREPAR3D.EXE, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: FSUIPC5.dll, version: 5.1.5.1, time stamp: 0x5ce4055a
Exception code: 0xc000041d
Fault offset: 0x00000000000e11f8
Faulting process ID: 0xff0
Faulting application start time: 0x01d516082b1b1d1a
Faulting application path: D:\P3Dv4\PREPAR3D.EXE
Faulting module path: D:\P3Dv4\Modules\FSUIPC5.dll
Report ID: b0d2595a-b1f0-4ead-832d-34d9890080e6
Faulting package full name:
Faulting package-relative application ID:

So whilst FSUIPC5 may look like the problem it isn't because it was caused by a .NET runtime 1026 error.

I've spoken to Pete and he suggests reverting to 4.4, deleting shaders and trying the tests again. Doing that now.

Luke, I tested at exactly the same time as the crash yesterday. Good idea but probably not a bad Ai texture/

Edited by Ray Proudfoot

Share this post


Link to post
Share on other sites
Posted (edited)

@Ray Proudfoot Just curious, right before it crashes, do you hear like 3 or 4 break ups of P3D sound? I did, every time. I reverted back to 4.4 yesterday, but did not have the time to actually do a flight yet. I hope we can all get to the bottom of it, as I really like how they improved the night lights and the DL.

Edited by Drumcode

Share this post


Link to post
Share on other sites
48 minutes ago, Drumcode said:

@Ray Proudfoot Just curious, right before it crashes, do you hear like 3 or 4 break ups of P3D sound? I did, every time. I reverted back to 4.4 yesterday, but did not have the time to actually do a flight yet. I hope we can all get to the bottom of it, as I really like how they improved the night lights and the DL.

Yes I did. Certainly some break in the sound but the crash comes so quickly nothing lasts long. I reverted to 4.4 and flew EGCC-EGLL and no crash on approach (unlike yesterday) so I'm staying with 4.4 for now.

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