Hello guys , need help !!!

 

So after reinstalling windows 8 , i'm installing FSX SP2 , first test without addon is okay , now after installing aircraft , texture , scenery , and sweetfx , if i'm trying to open the fsx , it just close itself without fatal error info , so i think it must be sweetfx problem , after trying to delete it , yeah i'm right . But i want to make the sweetfx worked , so i'm trying to fix it until the log looks okay , after the log looks okay , the fsx still close itself , so i'm trying to delete the sweetfx again , now it's getting worse , the fsx close itself without sweetfx installed , already tried to delete logbook, fsx.cfg , repair fsx .. It's like the sweetfx still there but i double-check it that there are no sweetfx data anymore.

 

Regards,

I want to try reinstall the fsx but i have to deactivate the PMDG products first , and i can't because of this problem :(

Make sure all remnants of SweetFX are removed from your main FSX folder. SweetFX installs the following files that should be moved to a temporary directory if problems occur: D3d9.dll, D3d9.fx, Dxgi.dll, Shader.fx, and the injector.ini. If any of those are in the folder, they will load when you start up FSX and FSX will crash.

 

Best regards,

Hello ,

Thanks for your response , i already check it , and those files aren't exist anymore .

And my fsx still crash...

 

Regards,

Then you should download and run AppCrashView (see AVSIM CTD Guide for link). There are many reasons for the StackHash/NTDLL crash(es) and they are listed in the AVSIM CTD Guide. One primary cause is My Traffic X 5.4c. The AVSIM CTD Guide is located to the right of this forum under Hot Spots.

 

Best regards,

Ah thank you ! Its my addon problem , after seeing the guide , i have to delete addon list in the dll.xml

 

I will try to add one-by-one to see what really the problem is ..

 

Thx for your support !!

 

Regards,

Glad you are using the guide.  We tried to make it easy for everyone to use and to investigate their particular crash, freeze, or issue.  A bad module in the dll.xml is a common problem.

 

Best regards,