|
Post by dl1011 on Jul 13, 2021 0:32:23 GMT
greetings im not sure if this is the right place to talk here but have been struggling on FSX for the past 2 days going through random CTD which the faulty module turns out it was the DSound.dll and another time ended up with ntdll.dll error as well a few times with the sounds which i barely use high settings because i have a slower computer. i have not seen much around other forums on this as this dont seem to be big on many. I had figured out what did it and discovered it was most of the sound packs from HJG which was new to me and ive never had this problem. Ive even deleted and rebuild a new fsx.cfg and reinstalled SP1/SP2 and everything else and it turns out the CTD continues when using the HJG sound packs as each time the sim is paused while in flight, the sound fades out or it goes silent and then fatal error keeps on happening. i have not had any problems with other soundpacks like from TSS or several others which performs well, just trying to diagnose the problem and can use help. drivers and video card have been updated a couple weeks ago with no new updates to do
Memory.4GB Processor: Intel(R) Pentium(R) Silver N5000 CPU @ 1.10GHz{Cores4} Logical Processors 4
Description
Faulting Application Path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61472.0
Application Timestamp: 475e17d3
Fault Module Name: DSOUND.dll
Fault Module Version: 10.0.19041.1
Fault Module Timestamp: 59a065c9
Exception Code: c0000005
Exception Offset: 00037ee6
OS Version: 10.0.19043.2.0.0.768.101
Locale ID: 1033
Extra information about the problem
Bucket ID: 91adbfb2167fa6ee2f67ff142fbd4e9a (2263057799942327962)
sorry for convenience and any help would be useful
|
|
|
Post by aerofoto - HJG Admin on Jul 13, 2021 2:47:50 GMT
One for Nathan to look at .... I think. Where the HJG sound packs are concerned .... There's nothing non-standard about them. What we offer's been produced in accordance with the same audio protocols/methodology we've been using for more than the past 7 years. I acknowledge some of the WAV samples, that make up what we offer within any sound pack, are "larger" .... primarily because they're mostly all sampled from actual and high quality real world recordings, but even so, our sound packs aren't engineered to work in relation to any SOUND.DLL's unlike is the case with some panel/gauge specific sounds/audio. "In so far as I can immediately recall" .... I'm not aware of anyone else whom has ever reported any such issue/s in relation to the add-on sound packs we offer and very much doubt these could be the cause of any issue/s. You say this's only become a problem during the past couple of days .... "suggesting" .... there wasn't any issue issue previously ? Don't suppose you've installed any WINDOWS/system related update around this same time .... by any chance ? Mark C AKL/NZ
|
|
|
Post by Nathan Ford - HJG on Jul 13, 2021 5:31:23 GMT
Hi Dl1011,
Need a bit more info if that’s ok. I assume you are using Windows 10? Is it 64 or 32 bit version? Which aircraft and sound pack are you using? I also notice that FSX is installed in the default location, C:\Program Files (x86) which isn’t recommended as it can cause problems. I also notice that you are getting the Exception Code: c0000005 which indicates a Memory Access Violation. What it usually means is when you are flying along and suddenly FSX crashes, FSX was trying to find something to call up or render or do a task and it could not find it so it crashed.
Another thing, if you are using Win10 64bit, have you put the recommended uiautomationcore.dll into your FSX folder?
Just getting an idea about your system and setup so that I can try and figure out what may be happening.
Cheers, Nathan
|
|
|
Post by dl1011 on Jul 13, 2021 14:27:09 GMT
One for Nathan to look at .... I think. Where the HJG sound packs are concerned .... There's nothing non-standard about them. What we offer's been produced in accordance with the same audio protocols/methodology we've been using for more than the past 7 years. I acknowledge some of the WAV samples, that make up what we offer within any sound pack, are "larger" .... primarily because they're mostly all sampled from actual and high quality real world recordings, but even so, our sound packs aren't engineered to work in relation to any SOUND.DLL's unlike is the case with some panel/gauge specific sounds/audio. "In so far as I can immediately recall" .... I'm not aware of anyone else whom has ever reported any such issue/s in relation to the add-on sound packs we offer and very much doubt these could be the cause of any issue/s. You say this's only become a problem during the past couple of days .... "suggesting" .... there wasn't any issue issue previously ? Don't suppose you've installed any WINDOWS/system related update around this same time .... by any cha Mark C AKL/NZ as far as the updates go, nothing was installed all around the same time, as that was done weeks ago, this is all new to me, i never used to have an issues with any of the soundpacks until now, ive tested again with a HJG DC-10 last night and waited till i got in flight and as i had paused in mid flight, lost all sound this time however this time no CTD but sound came back. another time the sound will fade and then CTD with the same cause of fatal module of DSOUND which was the 7th CTD and another reason was Ntdll which im familiar on that but i dont really use high settings or AI traffic
|
|
|
Post by dl1011 on Jul 13, 2021 14:34:34 GMT
Hi Dl1011, Need a bit more info if that’s ok. I assume you are using Windows 10? Is it 64 or 32 bit version? Which aircraft and sound pack are you using? I also notice that FSX is installed in the default location, C:\Program Files (x86) which isn’t recommended as it can cause problems. I also notice that you are getting the Exception Code: c0000005 which indicates a Memory Access Violation. What it usually means is when you are flying along and suddenly FSX crashes, FSX was trying to find something to call up or render or do a task and it could not find it so it crashed. Another thing, if you are using Win10 64bit, have you put the recommended uiautomationcore.dll into your FSX folder? Just getting an idea about your system and setup so that I can try and figure out what may be happening. Cheers, Nathan sorry having a hard time with the quating lol yes im using windows 10 thats 64/32 bit version. sound packs, this was with the DC-10-10 CF6-6 pack and DC-10-40 JT9Ds as well as the DC-8 of all variety. I havent experience much of the others just yet but so far it had been 7 CTDs from this, i never used to have this kind of issue as ive used your wonderful packs from here with the aircraft for a very long time without a problem. i have uiautomationcore.dll in fsx folder, always have been there after originally installing all my service packs
|
|
|
Post by aerofoto - HJG Admin on Jul 13, 2021 18:44:05 GMT
Whatever the cause may be (and CTD's are often "the most difficult event to try'n troubleshoot in FS) It's "extremely unlikely" to be induced by the sound packs .... for the reason/s I've mentioned above.
Mark C AKL/NZ
|
|
|
Post by dl1011 on Jul 13, 2021 19:12:23 GMT
could be true but i have no way to fully know . i appreciate the help
|
|
|
Post by aerofoto - HJG Admin on Jul 13, 2021 19:42:45 GMT
I can almost totally "guarantee/reassure" you it's "NOT" and by virtue of the fact that .... (a) there's "never ever" been (so far as my long and normally almost faultless memory is aware) any issue reported in relation to the sound packs we offer causing CTD's (these sound packs despite their size are fine even when used on/with lower end systems/hardware) .... and because (b) there's no direct relationship between these add-on sound packs and any other DLL that can be required to run particular simulations. SOUND DLL's that aid the running some Panels/Gauges can be a different story though, but, CTD's concerning these are "an extremely rare event" and would normally only occur if such are installed in the wrong folder .... the result thn being a CTD occurring "at the very moment a simulation is selected within the FS Aircraft Selection Menu". If everything was running fine up until a few days ago (as you imply), then, logic possibly dictates that something's either .... (1) changed .... or (2) is possibly beginning to fail on your system .... only I'd be inclined to suspect #1 and more-so if you've been subjected to any OS updating over the past few days. Nathan's pretty good at investigating these sorts of issues, so, I'm going to leave you with him/his expertise .... given I don't think there much more I can really try to add and that I haven't already said Mark AKL/NZ
|
|
|
Post by Nathan Ford - HJG on Jul 13, 2021 21:41:46 GMT
Thanks for all of the info. When an app crashes in Win10 the faulting module shown is the module that was being loaded at the time of the crash, in most of your cases, it’s the DSOUND.dll, but it’s the Exception code that tells us what’s going on. Exception Code: c0000005 indicates a Memory_Access_Violation. Could be caused my a multitude of issues. Settings too high in FSX will cause this crash. Virtual memory settings not set to System Managed Size will cause this crash. Overheating etc. With all the updates Microsoft have been pumping out lately, Win10 is starting to fill up with “Bloatware” taking up valuable memory. Can we start by having a look at your virtual memory settings? Open Settings. Click on System. Click on About. Under the "Related settings" section, click the System info option. Click the "Advanced system settings" option from the left pane. Click the Advanced tab. Under the "Performance" section, click the Settings button. Click the Advanced tab. Under the "Virtual memory" section, click the Change button. Clear the Automatically manage paging files size for all drives option. Select the System Managed size option. Click the Set button. Click the OK button. Click the OK button again. Restart your computer.
Next, check that you have the latest version of FSUIPC installed. It has been updated recently 🤭 Make sure you have the latest and updated C++Library2005 (download from Here ) Reboot Go to Windows Update and under options update the VC++2010 libraries Reboot Check Windows update again to see if there are any newer versions again and reboot. As you have rebuilt the FSX.cfg, make sure that you have included HIGMEMFIX=1 to the [GRAPHICS] section. In the [Main] section, ensure you have DisablePreload=1 Reboot the system and restart FSX. Make sure you have no car or boat traffic in you settings and AI is kept at a minimum that you are prepared to accept. Set FPS to 30 I’m worried about the amount of RAM you have for your system though. Windows10 is getting fatter and fatter and squeezing out the amount of memory you have for FSX. Cheers, Nathan
|
|
|
Post by dl1011 on Jul 14, 2021 18:14:10 GMT
Thanks for all of the info. When an app crashes in Win10 the faulting module shown is the module that was being loaded at the time of the crash, in most of your cases, it’s the DSOUND.dll, but it’s the Exception code that tells us what’s going on. Exception Code: c0000005 indicates a Memory_Access_Violation. Could be caused my a multitude of issues. Settings too high in FSX will cause this crash. Virtual memory settings not set to System Managed Size will cause this crash. Overheating etc. With all the updates Microsoft have been pumping out lately, Win10 is starting to fill up with “Bloatware” taking up valuable memory. Can we start by having a look at your virtual memory settings? Open Settings. Click on System. Click on About. Under the "Related settings" section, click the System info option. Click the "Advanced system settings" option from the left pane. Click the Advanced tab. Under the "Performance" section, click the Settings button. Click the Advanced tab. Under the "Virtual memory" section, click the Change button. Clear the Automatically manage paging files size for all drives option. Select the System Managed size option. Click the Set button. Click the OK button. Click the OK button again. Restart your computer.
Next, check that you have the latest version of FSUIPC installed. It has been updated recently 🤭 Make sure you have the latest and updated C++Library2005 (download from Here ) Reboot Go to Windows Update and under options update the VC++2010 libraries Reboot Check Windows update again to see if there are any newer versions again and reboot. As you have rebuilt the FSX.cfg, make sure that you have included HIGMEMFIX=1 to the [GRAPHICS] section. In the [Main] section, ensure you have DisablePreload=1 Reboot the system and restart FSX. Make sure you have no car or boat traffic in you settings and AI is kept at a minimum that you are prepared to accept. Set FPS to 30 I’m worried about the amount of RAM you have for your system though. Windows10 is getting fatter and fatter and squeezing out the amount of memory you have for FSX. Cheers, Nathan Nathan thanks much for the help. I've done all of the recommendations you wrote down. I do suspect also updates probably have played many roles as well as the DSound.dll mainly only affect the hjg sound packs this far. I test flew last night with a DC-10-10 with the CF6-6 soundpack which all pack are all in corrected locations. I managed to get through a flight without ctd so far. The newest I found is that the sound lowers when I talk to default ATC as I didnt find it a big deal but I played with the fsx sound settings and there was no major change. However in mid flight I paused then shortly unpaused the flight. The sound of the sound vanished again however it came back like 20 seconds later however still kept flying. This time no ctd. But was wondering about that as well. All my settings on fsx are the recommendations settings. I dont use AI traffic as it does make it more slower same for vehicle traffic. I do have Airport add ons flew to one of them with the flight I did, no problems at that thus far. I was amazed no sound packs outside hjg was affected by this problem in the first place. As I have many TSS sound packs for other aircraft outside hjg. Also drivers and hardware were updated less than a month ago. Thanks very much for the help.
|
|
|
Post by Nathan Ford - HJG on Jul 14, 2021 20:35:52 GMT
Aaah, sound fading during ATC, that’s something different. Windows had an update earlier in the year and I know it reset some sound settings for me (I was getting no sounds in FSX at all).
Can you check and do the following for me,
Go to Control Panel>hardware and sound>sound Reselect your speakers (for me, it stoped reading them as the default even though they where showing as default) Click on the communications tab under sound management In the section “Windows Detects Communications Activity” click on Do Nothing Apply and restart your computer.
That should fix the sound issue 😉
Pleased to know you didn’t get a CTD on the last flight.
Let me know how you go,
Nathan
p.s. I just noticed a typo in a previous post it should read: HIGHMEMFIX=1 sorry, can you double check that it’s correct in your FSX.cfg 😉
|
|
|
Post by dl1011 on Jul 15, 2021 6:42:27 GMT
Aaah, sound fading during ATC, that’s something different. Windows had an update earlier in the year and I know it reset some sound settings for me (I was getting no sounds in FSX at all). Can you check and do the following for me, Go to Control Panel>hardware and sound>sound Reselect your speakers (for me, it stoped reading them as the default even though they where showing as default) Click on the communications tab under sound management In the section “Windows Detects Communications Activity” click on Do NothingApply and restart your computer. That should fix the sound issue 😉 Pleased to know you didn’t get a CTD on the last flight. Let me know how you go, Nathan p.s. I just noticed a typo in a previous post it should read: HIGHMEMFIX=1 sorry, can you double check that it’s correct in your FSX.cfg 😉 I'll definitely update the next time I get on. But the help was appreciated. and yes since I didnt get ctd on the last one. Not sure what can accur if I get a repeated one as I've done all you listed. But will definitely update.
|
|