Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello Pete,

 

just a quick question , can you see if this stackhash has got anything to do with fsuipc?

 

Bron
Prepar3D exe
 
Overzicht
Werkt niet meer
 
Datum
‎10-‎10-‎2015 18:34
 
Status
Verzonden rapport
 
Beschrijving
Pad naar toepassing met fout: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe
 
Probleem met handtekening
Naam van probleemgebeurtenis: APPCRASH
Naam van de toepassing: Prepar3D.exe
Versie van toepassing: 3.0.10.14945
Tijdstempel van toepassing: 560b4abe
Naam van foutmodule: StackHash_e70a
Versie van foutmodule: 10.0.10240.16430
Tijdstempel van foutmodule: 55c599e1
Uitzonderingscode: c0000374
Uitzonderingsmarge: PCH_D0_FROM_ntdll+0x0006919C
Versie van besturingssysteem: 10.0.10240.2.0.0.768.101
Landinstelling-id: 1043
Aanvullende informatie 1: e70a
Aanvullende informatie 2: e70a6b6c970fc5795e672aeb48fea89e
Aanvullende informatie 3: 9672
Aanvullende informatie 4: 96726afbdf91c2faff81a251845d260f
 
Extra informatie over het probleem
Bucket-id: 3a7dc09715af649410f789526c3c9d71 (107644420920)
 

 

 

 

 

 

 

Best regards,

Remco

Posted

just a quick question , can you see if this stackhash has got anything to do with fsuipc?

 

No. It looks like a P3D corruption or driver conflict. I'd report it to Lockheed-Martin if Iwere you.

 

Pete

Posted

P3d v3.0 runs good without my cockpit connected , getting stack hash errors with the hardware running . Build a new computer just to check if it wasn't computer related .. Changed Windows and p3d version still stackshash errors .... Puzzle continues

Posted

I've deleted the stock axis in p3d do you usually delete all stock assignments ?

 

No, I always disable controllers in the Sim. You should really do this if assigning in FSUIPC.

 

 

Can fsuipc if over tasked cause stackshash errors ?

 

No. How can it get "over-tasked".?

 

Pete

Posted

Some controller etc causing a buffer overrun or other issue memory leak ?

 

Neither situation is caused by excessive load. Both are caused by poor programming and (in the former) malformed data.

 

Cheers!

 

Luke

Posted

Thank you , at this moment the main suspect is a Flightillusion for 1 gauge , do not know if it is the gauge itself or something in the driver / p3d or fsx causing it . More testing required

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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.