Hello again ... posted up above, a while back.

 

New problem that I hope someone can help with.

 

My computer hard drive had to be replaced ... in the process the computer guy installed AMD CCC version 14.0417.2226.38446 and Driver Packaging Version 14.10.1006-140417a-171099C, Catalyst Version 14.4.

 

My computer spec are above in a previous post. Couldn't figure out how to copy it.

 

The new install of FSX has some issues which are annoying; such as , when exiting FSX, it gives a fatal fault error message and then reboots....  the CH yoke button mapped to VC view does not work after changing to some aircraft.... an instrument view window when opened in VC view works fine but if I leave that VC view and then come back to the VC view the instrument view is closed again, forcing me to re open it every time I return to the VC view. More small bugs like the above not worth mentioning because the problem is clear.

 

Should FSX be working with this newer CCC version?

 

If so, what could be the cause with this new install?

 

Which version of CCC should I roll back to if that is a cure?

 

Thanks

 

J35

I remember when the problem occurred with 13.9.
Well, I'm using 14.4 without problems in FSX, P3DV 1.4 and P3DV 2.3.
My card is ATI 6950 2gb.

I can not say, but maybe the problem is not CCC.
Maybe you'll find something here:

http://forum.avsim.net/files/file/65-avsim-crash-to-desktop-guide-for-fsx-p3d-fs9/

 

 

João Alfredo

I have version 11.11, 12.1, 12.2,12.3,12.4,12.6,12.8,12.10,13.1,13.4,13.12, 14.4.
I've tried all, none had problems.

 

João Alfredo

Thanks for the reply Joao. I have had no luck with my set up. I will take a look at your link.

Here is a Windows Event Viewer summary which means nothing to me ...limited knowledge with such things.

 

Log Name:      Application
Source:        Application Error
Date:          9/27/2014 9:31:43 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Jack-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0xc0000002
Fault offset: 0x0000c42d
Faulting process id: 0x33c
Faulting application start time: 0x01cfdab319b61a35
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: d1c4e949-46a6-11e4-9af4-50e549ced655
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-28T00:31:43.000000000Z" />
    <EventRecordID>3881</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Jack-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61637.0</Data>
    <Data>46fadb14</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.18409</Data>
    <Data>53159a86</Data>
    <Data>c0000002</Data>
    <Data>0000c42d</Data>
    <Data>33c</Data>
    <Data>01cfdab319b61a35</Data>
    <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
    <Data>d1c4e949-46a6-11e4-9af4-50e549ced655</Data>
  </EventData>
</Event>

I was told this is a DX9 issue and AMD's Catalyst's new drivers do not support this. I hope the help us old school simmers out.

Not much help but I have the same problem after reinstalling win7 and updating drivers I also have blue screen issues. Have this problem for the last 48 hours. Keep us informed if you find an answer and ill do the same.

Best of luck..

----------------------------------------------------

 

If you have recently downloaded all the KB files of the last Download Tuesday, and this has been happening (if you think back...) since you downloaded, or your just installed W7 downloaded the latest security KB's... then the Windows Update borked your Windows. I warned people about this, two days ago. Some, said that they 'had no problems' in downloading the files. There is one KB, that even if it seems to load in properly...will bork your system, if not in the next reboot..it will show up...and corrupt. It is about BitLocker coding, and not possibly your video drivers. I would suggest, a roll back with the System Restore point made at the time you downloaded and installed all files in the Tuesday release. This might get you back to a stable system. A Mod moved my warning from Hangar Chat, to the W7 forum. This has been reported also on W8 setups as well. This might be your issue...and that others have/will have, or not. Try the latest Restore Point date...and see if that clears things up.

----------------------------------------------------

If you have recently downloaded all the KB files of the last Download Tuesday, and this has been happening (if you think back...) since you downloaded, or your just installed W7 downloaded the latest security KB's... then the Windows Update borked your Windows. I warned people about this, two days ago. Some, said that they 'had no problems' in downloading the files. There is one KB, that even if it seems to load in properly...will bork your system, if not in the next reboot..it will show up...and corrupt. It is about BitLocker coding, and not possibly your video drivers. I would suggest, a roll back with the System Restore point made at the time you downloaded and installed all files in the Tuesday release. This might get you back to a stable system. A Mod moved my warning from Hangar Chat, to the W7 forum. This has been reported also on W8 setups as well. This might be your issue...and that others have/will have, or not. Try the latest Restore Point date...and see if that clears things up.

Thanks for the info but my post is over 13 months ago, new card and running p3d2.4 now haven't had any problems with it since .

Thanks for the info but my post is over 13 months ago, new card and running p3d2.4 now haven't had any problems with it since .

Great to read...didn't look at the date...

 

Someone else must have resurrected your thread...