Jump to content

tommchowat

Members
  • Content Count

    55
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

1 Neutral

About tommchowat

  • Birthday 04/14/1987

Profile Information

  • Gender
    Male
  • Location
    Saint Albans, UK
  • Interests
    Aviation, Tennis, Football

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Managed to complete the flight with beautiful visuals and performance. I rebuilt the CFG file and didn't tweak it at all apart from Optimize Parts. Think that's the lesson now, no more messing with sliders and configs and tweaks... It works, so leave it. Thanks.
  2. I filtered the log file to only show gdiplus access, and there were two logs at 17:09:06 with the same path to gdiplus that Event Viewer showed, both were a 'SUCCESS'.
  3. Sorry to drag this up again, I'm sure you're bored of it but the same rubbish is happening still, this time at exactly the same spot elsewhere. Taxiing towards runway 12 in Kingston, about halfway to the runway I'm always getting a gdiplus.dll error. The flight to Kingston from Gatwick went brilliantly last week. I've been testing it all day and can't get to the bottom of it. I got Process Monitor and made a note of the exact time it crashed and had a look to see if I could spot something, but I can't. Here's the message from Event Viewer, time 17:08:57 Faulting application name: Prepar3D.exe, version: 2.5.12946.0, time stamp: 0x555f2e54 Faulting module name: gdiplus.dll, version: 6.1.7601.18852, time stamp: 0x555633d1 Exception code: 0xc0000005 Fault offset: 0x000c7e85 Faulting process id: 0x104c Faulting application start time: 0x01d0cadf99272dfe Faulting application path: D:\Prepar3D v2\Prepar3D.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18852_none_72d5ba7586659cb4\gdiplus.dll Report Id: 47f72e93-36d5-11e5-9122-bc5ff436a2d8 Here's the associated bits of the log file at around that time: Now the sim itself froze at 17:08:52, so here are the associated bits of the log file at that time: Now at the time the sim crashed (above picture), I can't spot anything out of the ordinary in the log file there, partially because everything says "SUCCESS". At the time Event Viewer recorded the crash (first two pictures) I can't really make head or tail of what any of it means!
  4. Thanks for the help anyway, I've made alot of adjustments to my configuration which will probably help to avoid future crashes.
  5. It doesn't have a scenery library entry, I just installed the models and made an entry in the Sim Objects CFG. To be honest it's not worth the time or effort to figure out what is causing this, it's just a short hop which I'm probably never going to do again, so I'm just going to have to come to terms with it!
  6. I only have UT2 installed for the models as I only fly on Vatsim so I'd be surprised if it was that. The EGLL - OMAA flight went without a hitch, as did the OMAA - OOMS. There must be something, somewhere on that route in that exact place which my computer just doesn't get on with. Strange indeed.
  7. After all that, still getting the same crash in exactly the same place, every time. Descending through 190 on the way into OMAA. Disabled all addon scenery too. I'll do the longer OMAA-EGLL and if that goes well then I'll just have to put it down to that particular route!
  8. Update: I started up everything at Muscat in the 777 like I normally would, full procedure, GSX running and all, and I set up everything all the way up to ready to push and left it like that - it's usually after about 5-35 minutes that I'd get the crash. However, it just sat there behaving with no crashes for about an hour. Didn't have time to actually take off as I have to go to work, but it looks promising so far. Only weird thing is that Active Sky Next on my networked laptop decided not to start up at all on double clicking the icon - hopefully that's a fairly straightforward reinstall. Thanks for your help so far.
  9. Thanks for replying Jim. I did mean 353.06, not 353.03, not sure those even exist! I uninstall video card drivers in Add/Remove programs then restart in safe mode and use driver sweeper. However when I install a new one I don't disable anti-virus protection - I'll do this now. I've taken ownership of all relevant P3D folders. I've got UAC disabled and P3D running as admin. I've added the P3D directory in my exception list for scanning by my anti-virus. I also realised I didn't have any chipset drivers installed, and found some on the Asrock site. I also updated the firmware for both my Samsung SSD's. We'll see how it goes.
  10. Hi Guys, I'm at the end of my tether with this. I moved over to P3D from FSX a while ago, and have had nothing but trouble on a totally fresh install of Windows 7. I can't complete a flight in the PMDG 777 from Muscat to Abu Dhabi, the sim is constantly crashing either on the ground or during the descent. More often than not it's caused by gdiplus.dll. I remember I had this a while ago with FSX and it helped to go back to a previous Nvidia driver (344.65 I think worked). Didn't work this time though. With the latest driver (353.30) I get a gdiplus.dll error without fail, like this: Faulting application name: Prepar3D.exe, version: 2.5.12946.0, time stamp: 0x555f2e54 Faulting module name: gdiplus.dll, version: 6.1.7601.18852, time stamp: 0x555633d1 Exception code: 0xc0000005 Fault offset: 0x000c7fa0 Faulting process id: 0x10a4 Faulting application start time: 0x01d0b69c99ed9031 Faulting application path: D:\Prepar3D v2\Prepar3D.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18852_none_72d5ba7586659cb4\gdiplus.dll Report Id: cdc55e57-2296-11e5-b74a-30b5c218a6ad Reverting back to the previous driver (353.06) I get a crash I've never seen before: Faulting application name: Prepar3D.exe, version: 2.5.12946.0, time stamp: 0x555f2e54 Faulting module name: nvwgf2um.dll, version: 9.18.13.5306, time stamp: 0x55668242 Exception code: 0xc0000096 Fault offset: 0x006ebd85 Faulting process id: 0xc64 Faulting application start time: 0x01d0b6970c8dd0c1 Faulting application path: D:\Prepar3D v2\Prepar3D.exe Faulting module path: C:\Windows\system32\nvwgf2um.dll Report Id: a48852f4-228b-11e5-87b6-bc5ff436a2d8 And now using 344.65 which fixed the gdiplus.dll error when I was using FSX, I get this: Faulting application name: Prepar3D.exe, version: 2.5.12946.0, time stamp: 0x555f2e54 Faulting module name: gdiplus.dll, version: 6.1.7601.18852, time stamp: 0x555633d1 Exception code: 0xc0000005 Fault offset: 0x000c7f80 Faulting process id: 0xbfc Faulting application start time: 0x01d0b6a9c19f005e Faulting application path: D:\Prepar3D v2\Prepar3D.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18852_none_72d5ba7586659cb4\gdiplus.dll Report Id: 8623f651-229f-11e5-8833-bc5ff436a2d8 It's getting a bit ridiculous. Background information: Fresh install of Windows 7 x64, UAC off, fully up to date P3D 2.512946 running as admin FSUIPC 4.939 registered .NET verification tool ran and confirms no issues with 2.0 up until 4.5.2 .NET repair tool run SFC /SCANNOW run with no integrity violations System: i5 3570 @ 4.7GHz 16GB DDR3 RAM 128GB SSD 4GB GTX 970 There isn't much out there about this sort of crash, so I certainly hope someone can help me, as I'm about to lose it. I moved from FSX to P3D in the hope of getting a more stable sim and it's just getting worse.
  11. Hi guys, Recently switched from FSX to P3D. I was using DX10 in FSX and was having the d3d11.dll crashes so removed the above KB fix from Microsoft which solved the issues. My question though... now that I'm using P3D, which actually uses DX11, would it be wiser to reinstall the KB or leave it out?
  12. I can try it with leaving the auto throttle in I suppose, but usually when I fly an approach I disconnect the auto throttle and then the autopilot (and yes, I'm aware the purists will tell me that Boeing recommend leaving the auto throttle engaged during a manual approach but I don't do it in the 737 so won't do it here!)
  13. Thanks. If it biases it ANU then surely I would have good pitch up authority...
  14. Hi Guys. This has been an ongoing issue for a while, I'm not sure if it's a 777ism or not! Basically during landing there is a distinct lack of pitch up authority. Example, if you get slightly above the glide and pitch down to compensate, then try to recorrect with a pitch up for the flare, even full rearward movement of the controls does little to nothing, which results in a rather... Positive landing. If I disconnect early on the approach it flies fine, all control inputs are responsive, but it's only the last fifty feet or so where I've little to no control in nose up effort. I've noticed on approaches where I'm bang on the glide all the way down it remains responsive enough to start a flare at around 50 or 40 feet for a nice touch down. So I'm wondering if a nose down correction late in the approach is affecting the ability to pitch up... Seems a bit strange. Trim issue? I'm not sure where the trim is at this stage as I haven't looked but I'm assuming it should be around 5-7 units ANU. No issues during takeoff rotation or manual flight in other stages. I seem to have made no less than four of these posts. Feel free to delete the others!
  15. Chaps, I'm having the same crash with the same module in exactly the same place - just coming up to GORLO flying West towards Heathrow - happened twice now and both times it's referenced gdiplus.dll, which is a new one on me. Here's the message from Event Viewer: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: gdiplus.dll, version: 6.1.7601.18455, time stamp: 0x535b14fb Exception code: 0xc0000005 Fault offset: 0x000c7e75 Faulting process id: 0x101c Faulting application start time: 0x01d010634e80bd87 Faulting application path: E:\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll Report Id: e5f179aa-7c87-11e4-995a-bc5ff436a2d8 Just done a fresh FSX install too, literally did it yesterday. Am in the middle of Googling but it's all a bit wishy washy. Anyone seen this before? After doing a bit of research on it I've made sure I've got all up to date .NET frameworks, reinstalled all the default Windows 7 fonts and rolled back my Nvidia driver to the previous (344.65).
×
×
  • Create New...