December 26, 201213 yr Hey Guys. My FSX is recently crashing to desktop usually After Pushingback, or sometimes just before entering the runway, the CTD never showed up before i merged the WILCO A340-600 panel with SMS A340-500 Model, when i turned on my Event Log, The Crash Log showed the Followoing : Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: USER32.dll Fault Module Version: 6.1.7600.16385 Fault Module Timestamp: 4a5bdb2f Exception Code: c0000005 Exception Offset: 0001862b OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 2a60 Additional Information 2: 2a6011d1df54fee9b664699c28dcfc5b Additional Information 3: 11cd Additional Information 4: 11cd06e655a3fd99fecd0883ee0f91e5 i never made it to the runway because of that crash ! :( any help?? My FSX and PC Specs are detailed in my profile. and really sorry fir my bad english Thanks in advance
December 27, 201213 yr The user32.dll caused your crash and that is a Windows 7 file. Windows stores instructions for graphical elements such as dialog boxes and windows in the User32.dll file. The User32.dll file is necessary to the operation of Windows. If this file is damaged, deleted, or removed, the system will no longer work correctly. If a program or a service accesses User32.dll incorrectly, the program or the service will not work correctly. You can try a system restore before merging the Wilco panel with the A340 model and see if that fixes the problem. You can uninstall or remove the merged Wilco and SMS models too. Windows 7 probably didn't like the merger. Run a system scan to find and repair corrupted system files. Click on the start button, type run, then look up in the menu and click on Run. In the run box type sfc \scannow. If that doesn't work, set up a new user account and see if the problem still exists - http://windows.microsoft.com/en-us/Windows7/Create-a-user-account. If it does then follow the instructions for fixing a corrupted User Account (so you can keep your old settings, desktop, etc.). Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
December 27, 201213 yr Author Unfortunately, i don't have a restore point before the merge i've done :( but, i'll try a system scan as you mentioned above and it'll be followed by a test flight to see what will happen. i hope everything goes well i'll keep you updated. Thank You, Muhammad.
December 27, 201213 yr Author Hello Jim i ran through a system Scan, and here's what i found in the CBS.log : 2012-12-27 10:05:55, Info CSI 00000009 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:05:55, Info CSI 0000000a [sR] Beginning Verify and Repair transaction 2012-12-27 10:05:58, Info CSI 0000000c [sR] Verify complete 2012-12-27 10:05:58, Info CSI 0000000d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:05:58, Info CSI 0000000e [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:00, Info CSI 00000010 [sR] Verify complete 2012-12-27 10:06:00, Info CSI 00000011 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:00, Info CSI 00000012 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:03, Info CSI 00000014 [sR] Verify complete 2012-12-27 10:06:03, Info CSI 00000015 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:03, Info CSI 00000016 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:05, Info CSI 00000018 [sR] Verify complete 2012-12-27 10:06:06, Info CSI 00000019 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:06, Info CSI 0000001a [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:08, Info CSI 0000001c [sR] Verify complete 2012-12-27 10:06:08, Info CSI 0000001d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:08, Info CSI 0000001e [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:11, Info CSI 00000020 [sR] Verify complete 2012-12-27 10:06:11, Info CSI 00000021 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:11, Info CSI 00000022 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:17, Info CSI 00000024 [sR] Verify complete 2012-12-27 10:06:18, Info CSI 00000025 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:18, Info CSI 00000026 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:20, Info CSI 00000028 [sR] Verify complete 2012-12-27 10:06:21, Info CSI 00000029 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:21, Info CSI 0000002a [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:23, Info CSI 0000002c [sR] Verify complete 2012-12-27 10:06:23, Info CSI 0000002d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:23, Info CSI 0000002e [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:26, Info CSI 00000030 [sR] Verify complete 2012-12-27 10:06:26, Info CSI 00000031 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:26, Info CSI 00000032 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:28, Info CSI 00000034 [sR] Verify complete 2012-12-27 10:06:29, Info CSI 00000035 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:29, Info CSI 00000036 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:30, Info CSI 00000038 [sR] Verify complete 2012-12-27 10:06:30, Info CSI 00000039 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:30, Info CSI 0000003a [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:33, Info CSI 0000003c [sR] Verify complete 2012-12-27 10:06:33, Info CSI 0000003d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:33, Info CSI 0000003e [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:37, Info CSI 00000040 [sR] Verify complete 2012-12-27 10:06:38, Info CSI 00000041 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:38, Info CSI 00000042 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:41, Info CSI 00000046 [sR] Verify complete 2012-12-27 10:06:41, Info CSI 00000047 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:41, Info CSI 00000048 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:44, Info CSI 0000004c [sR] Verify complete 2012-12-27 10:06:44, Info CSI 0000004d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:44, Info CSI 0000004e [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:48, Info CSI 00000050 [sR] Verify complete 2012-12-27 10:06:48, Info CSI 00000051 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:48, Info CSI 00000052 [sR] Beginning Verify and Repair transaction 2012-12-27 10:06:54, Info CSI 0000005c [sR] Verify complete 2012-12-27 10:06:55, Info CSI 0000005d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:06:55, Info CSI 0000005e [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:00, Info CSI 00000062 [sR] Verify complete 2012-12-27 10:07:00, Info CSI 00000063 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:00, Info CSI 00000064 [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:04, Info CSI 00000066 [sR] Verify complete 2012-12-27 10:07:04, Info CSI 00000067 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:04, Info CSI 00000068 [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:08, Info CSI 0000006a [sR] Verify complete 2012-12-27 10:07:08, Info CSI 0000006b [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:08, Info CSI 0000006c [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:12, Info CSI 0000006e [sR] Verify complete 2012-12-27 10:07:12, Info CSI 0000006f [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:12, Info CSI 00000070 [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:15, Info CSI 00000072 [sR] Verify complete 2012-12-27 10:07:15, Info CSI 00000073 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:15, Info CSI 00000074 [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:21, Info CSI 00000076 [sR] Verify complete 2012-12-27 10:07:21, Info CSI 00000077 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:21, Info CSI 00000078 [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:29, Info CSI 0000007c [sR] Verify complete 2012-12-27 10:07:29, Info CSI 0000007d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:29, Info CSI 0000007e [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:36, Info CSI 00000080 [sR] Verify complete 2012-12-27 10:07:36, Info CSI 00000081 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:36, Info CSI 00000082 [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:50, Info CSI 00000084 [sR] Verify complete 2012-12-27 10:07:50, Info CSI 00000085 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:50, Info CSI 00000086 [sR] Beginning Verify and Repair transaction 2012-12-27 10:07:59, Info CSI 00000088 [sR] Verify complete 2012-12-27 10:07:59, Info CSI 00000089 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:07:59, Info CSI 0000008a [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:01, Info CSI 0000008c [sR] Verify complete 2012-12-27 10:08:02, Info CSI 0000008d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:02, Info CSI 0000008e [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:03, Info CSI 00000090 [sR] Verify complete 2012-12-27 10:08:03, Info CSI 00000091 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:03, Info CSI 00000092 [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:05, Info CSI 00000094 [sR] Verify complete 2012-12-27 10:08:06, Info CSI 00000095 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:06, Info CSI 00000096 [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:16, Info CSI 000000b4 [sR] Verify complete 2012-12-27 10:08:16, Info CSI 000000b5 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:16, Info CSI 000000b6 [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:20, Info CSI 000000b8 [sR] Verify complete 2012-12-27 10:08:21, Info CSI 000000b9 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:21, Info CSI 000000ba [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:24, Info CSI 000000bc [sR] Verify complete 2012-12-27 10:08:25, Info CSI 000000bd [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:25, Info CSI 000000be [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:27, Info CSI 000000c0 [sR] Verify complete 2012-12-27 10:08:27, Info CSI 000000c1 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:27, Info CSI 000000c2 [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:32, Info CSI 000000c4 [sR] Verify complete 2012-12-27 10:08:32, Info CSI 000000c5 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:32, Info CSI 000000c6 [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:41, Info CSI 000000c9 [sR] Verify complete 2012-12-27 10:08:42, Info CSI 000000ca [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:42, Info CSI 000000cb [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:44, Info CSI 000000cd [sR] Verify complete 2012-12-27 10:08:44, Info CSI 000000ce [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:44, Info CSI 000000cf [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:45, Info CSI 000000d1 [sR] Verify complete 2012-12-27 10:08:46, Info CSI 000000d2 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:46, Info CSI 000000d3 [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:51, Info CSI 000000d5 [sR] Verify complete 2012-12-27 10:08:51, Info CSI 000000d6 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:51, Info CSI 000000d7 [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:55, Info CSI 000000d9 [sR] Verify complete 2012-12-27 10:08:55, Info CSI 000000da [sR] Verifying 100 (0x00000064) components 2012-12-27 10:08:55, Info CSI 000000db [sR] Beginning Verify and Repair transaction 2012-12-27 10:08:59, Info CSI 000000dd [sR] Verify complete 2012-12-27 10:09:00, Info CSI 000000de [sR] Verifying 100 (0x00000064) components 2012-12-27 10:09:00, Info CSI 000000df [sR] Beginning Verify and Repair transaction 2012-12-27 10:09:08, Info CSI 000000e2 [sR] Verify complete 2012-12-27 10:09:08, Info CSI 000000e3 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:09:08, Info CSI 000000e4 [sR] Beginning Verify and Repair transaction 2012-12-27 10:09:16, Info CSI 00000109 [sR] Verify complete 2012-12-27 10:09:16, Info CSI 0000010a [sR] Verifying 100 (0x00000064) components 2012-12-27 10:09:16, Info CSI 0000010b [sR] Beginning Verify and Repair transaction 2012-12-27 10:09:22, Info CSI 0000010d [sR] Verify complete 2012-12-27 10:09:22, Info CSI 0000010e [sR] Verifying 100 (0x00000064) components 2012-12-27 10:09:22, Info CSI 0000010f [sR] Beginning Verify and Repair transaction 2012-12-27 10:09:38, Info CSI 00000111 [sR] Verify complete 2012-12-27 10:09:38, Info CSI 00000112 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:09:38, Info CSI 00000113 [sR] Beginning Verify and Repair transaction 2012-12-27 10:09:52, Info CSI 00000116 [sR] Verify complete 2012-12-27 10:09:53, Info CSI 00000117 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:09:53, Info CSI 00000118 [sR] Beginning Verify and Repair transaction 2012-12-27 10:09:58, Info CSI 0000011a [sR] Verify complete 2012-12-27 10:09:58, Info CSI 0000011b [sR] Verifying 100 (0x00000064) components 2012-12-27 10:09:58, Info CSI 0000011c [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:04, Info CSI 0000011e [sR] Verify complete 2012-12-27 10:10:04, Info CSI 0000011f [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:04, Info CSI 00000120 [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:08, Info CSI 00000122 [sR] Verify complete 2012-12-27 10:10:08, Info CSI 00000123 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:08, Info CSI 00000124 [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:11, Info CSI 00000126 [sR] Verify complete 2012-12-27 10:10:12, Info CSI 00000127 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:12, Info CSI 00000128 [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:16, Info CSI 0000012b [sR] Verify complete 2012-12-27 10:10:16, Info CSI 0000012c [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:16, Info CSI 0000012d [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:18, Info CSI 0000012f [sR] Verify complete 2012-12-27 10:10:18, Info CSI 00000130 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:18, Info CSI 00000131 [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:32, Info CSI 00000133 [sR] Verify complete 2012-12-27 10:10:32, Info CSI 00000134 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:32, Info CSI 00000135 [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:40, Info CSI 00000138 [sR] Verify complete 2012-12-27 10:10:40, Info CSI 00000139 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:40, Info CSI 0000013a [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:43, Info CSI 0000013c [sR] Verify complete 2012-12-27 10:10:44, Info CSI 0000013d [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:44, Info CSI 0000013e [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:49, Info CSI 00000140 [sR] Verify complete 2012-12-27 10:10:49, Info CSI 00000141 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:49, Info CSI 00000142 [sR] Beginning Verify and Repair transaction 2012-12-27 10:10:58, Info CSI 00000145 [sR] Verify complete 2012-12-27 10:10:58, Info CSI 00000146 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:10:58, Info CSI 00000147 [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:03, Info CSI 00000149 [sR] Verify complete 2012-12-27 10:11:03, Info CSI 0000014a [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:03, Info CSI 0000014b [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:08, Info CSI 0000014d [sR] Verify complete 2012-12-27 10:11:08, Info CSI 0000014e [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:08, Info CSI 0000014f [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:12, Info CSI 00000151 [sR] Verify complete 2012-12-27 10:11:12, Info CSI 00000152 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:12, Info CSI 00000153 [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:16, Info CSI 00000156 [sR] Verify complete 2012-12-27 10:11:16, Info CSI 00000157 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:16, Info CSI 00000158 [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:22, Info CSI 0000015a [sR] Verify complete 2012-12-27 10:11:23, Info CSI 0000015b [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:23, Info CSI 0000015c [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:27, Info CSI 0000015e [sR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:40{20}]"UIAutomationCore.dll" from store 2012-12-27 10:11:27, Info CSI 00000160 [sR] Verify complete 2012-12-27 10:11:28, Info CSI 00000161 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:28, Info CSI 00000162 [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:36, Info CSI 00000164 [sR] Verify complete 2012-12-27 10:11:36, Info CSI 00000165 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:36, Info CSI 00000166 [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:42, Info CSI 00000169 [sR] Verify complete 2012-12-27 10:11:42, Info CSI 0000016a [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:42, Info CSI 0000016b [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:46, Info CSI 0000016d [sR] Verify complete 2012-12-27 10:11:46, Info CSI 0000016e [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:46, Info CSI 0000016f [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:53, Info CSI 00000171 [sR] Verify complete 2012-12-27 10:11:53, Info CSI 00000172 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:53, Info CSI 00000173 [sR] Beginning Verify and Repair transaction 2012-12-27 10:11:59, Info CSI 00000175 [sR] Verify complete 2012-12-27 10:11:59, Info CSI 00000176 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:11:59, Info CSI 00000177 [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:11, Info CSI 00000179 [sR] Verify complete 2012-12-27 10:12:11, Info CSI 0000017a [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:11, Info CSI 0000017b [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:12, Info CSI 0000017d [sR] Verify complete 2012-12-27 10:12:13, Info CSI 0000017e [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:13, Info CSI 0000017f [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:17, Info CSI 00000181 [sR] Verify complete 2012-12-27 10:12:17, Info CSI 00000182 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:17, Info CSI 00000183 [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:21, Info CSI 00000185 [sR] Verify complete 2012-12-27 10:12:21, Info CSI 00000186 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:21, Info CSI 00000187 [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:24, Info CSI 00000189 [sR] Verify complete 2012-12-27 10:12:24, Info CSI 0000018a [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:24, Info CSI 0000018b [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:26, Info CSI 0000018d [sR] Verify complete 2012-12-27 10:12:27, Info CSI 0000018e [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:27, Info CSI 0000018f [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:30, Info CSI 00000191 [sR] Verify complete 2012-12-27 10:12:31, Info CSI 00000192 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:31, Info CSI 00000193 [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:44, Info CSI 00000195 [sR] Verify complete 2012-12-27 10:12:44, Info CSI 00000196 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:44, Info CSI 00000197 [sR] Beginning Verify and Repair transaction 2012-12-27 10:12:55, Info CSI 00000199 [sR] Verify complete 2012-12-27 10:12:55, Info CSI 0000019a [sR] Verifying 100 (0x00000064) components 2012-12-27 10:12:55, Info CSI 0000019b [sR] Beginning Verify and Repair transaction 2012-12-27 10:13:00, Info CSI 0000019d [sR] Verify complete 2012-12-27 10:13:00, Info CSI 0000019e [sR] Verifying 100 (0x00000064) components 2012-12-27 10:13:00, Info CSI 0000019f [sR] Beginning Verify and Repair transaction 2012-12-27 10:13:03, Info CSI 000001a1 [sR] Verify complete 2012-12-27 10:13:03, Info CSI 000001a2 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:13:03, Info CSI 000001a3 [sR] Beginning Verify and Repair transaction 2012-12-27 10:13:06, Info CSI 000001a5 [sR] Verify complete 2012-12-27 10:13:06, Info CSI 000001a6 [sR] Verifying 100 (0x00000064) components 2012-12-27 10:13:06, Info CSI 000001a7 [sR] Beginning Verify and Repair transaction 2012-12-27 10:13:10, Info CSI 000001a9 [sR] Verify complete 2012-12-27 10:13:10, Info CSI 000001aa [sR] Verifying 100 (0x00000064) components 2012-12-27 10:13:10, Info CSI 000001ab [sR] Beginning Verify and Repair transaction 2012-12-27 10:13:15, Info CSI 000001ad [sR] Verify complete 2012-12-27 10:13:16, Info CSI 000001ae [sR] Verifying 88 (0x00000058) components 2012-12-27 10:13:16, Info CSI 000001af [sR] Beginning Verify and Repair transaction 2012-12-27 10:13:18, Info CSI 000001b1 [sR] Verify complete 2012-12-27 10:13:18, Info CSI 000001b2 [sR] Repairing 1 components 2012-12-27 10:13:18, Info CSI 000001b3 [sR] Beginning Verify and Repair transaction 2012-12-27 10:13:18, Info CSI 000001b5 [sR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:40{20}]"UIAutomationCore.dll" from store 2012-12-27 10:13:19, Info CSI 000001b7 [sR] Repair complete 2012-12-27 10:13:19, Info CSI 000001b8 [sR] Committing transaction 2012-12-27 10:13:19, Info CSI 000001bc [sR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired what i can confirm is, that the "uiautomationcore.dll" has been removed and repaired, But, that file didn't need to be repaired as it IS the Correct file for me, Also, the log never showed any of "USER32.dll" :( should i go and try a new user? Thanks, Muhammad.
December 27, 201213 yr The uiautomationcore.dll file that was corrupted was your system uiautomationcore.dll not the one you placed in your FSX main folder. Like I have been saying a lot, putting another version of the uiautomationcore.dll in your FSX directory may cause problems as it could be trumping out the uiautomationcore.dll used by Windows 7 (the one that got corrupted). Did you run FSX and see if the problem is fixed? If you don't get another crash then that was the fix. If you get another User32.dll crash, then you'll have to go through the procedure of setting up a new User as I described above. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
December 27, 201213 yr Author uhaaaa now i get it, but my uiatuomationcore.dll file version is always the same everywhere. and i'll Test FSX to see if it works, and will update you with anything new Thank You, Muhammad.
December 27, 201213 yr Author the problem still exists :( going to make a new User and will see what will happen.
December 27, 201213 yr Just because USER32 shows as the faulting module in a crash does NOT mean your Windows install is borked. It simply means that an instruction from that kernel module was what was running when the fault occurred. The C0000005 exception code means that something attempted an out-of-range memory access and DEP was tripped. Lots of things can cause this...given your description of the problem, I'd suspect a problem with a texture on your merge. Bad textures on acft, AI, and scenery are a common cause of user crashes, and they can show up with ntdll, user32, etc as the faulting module. If the problem is only occurring with your new merge, it makes sense to look hard there for a cause. And make sure your merge isn't set up as your default flight with this going on. W/r/t uiautomationcore.dll, if you are using the Vista version on a Win 7 install to cure menu problems, place the Vista version of the DLL in your FSX root folder ONLY. Do not replace the Win 7 version of this dll in the system32 or syswow64 directories. Regards Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
December 27, 201213 yr W/r/t uiautomationcore.dll, if you are using the Vista version on a Win 7 install to cure menu problems, place the Vista version of the DLL in your FSX root folder ONLY. Do not replace the Win 7 version of this dll in the system32 or syswow64 directories. That may be exactly what he did (placed the Vista version in the system32 folder) as the one in the system32 folder was found to be corrupted. However, can one put old versions of a dll in a system folder? I hope the OP placed the Vista version of the uiautomationcore.dll in the main FSX folder. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
December 28, 201213 yr However, can one put old versions of a dll in a system folder? One can, but one would not be happy with the results. It'll cause other (newer) programs properly written for the newer UI to crash. BTW, I lived in Woodbridge for a few years back when I was imprisoned working at the Pentagon. Cheers Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
December 29, 201213 yr Author The problem DOES still exist even after making a whole new user :( any helo? the crash log shows the same : Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: USER32.dll Fault Module Version: 6.1.7601.17514 Fault Module Timestamp: 4ce7ba26 Exception Code: c0000005 Exception Offset: 0001c44b OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 2a60 Additional Information 2: 2a6011d1df54fee9b664699c28dcfc5b Additional Information 3: 1c76 Additional Information 4: 1c76b9c6b81d9b74b4b19c5d65048191 :( and sorry for being late, my internet connection was out :(
December 30, 201213 yr One can, but one would not be happy with the results. It'll cause other (newer) programs properly written for the newer UI to crash. BTW, I lived in Woodbridge for a few years back when I was imprisoned working at the Pentagon. Cheers I disagree. As experiment, I did replace the old vista version in my System/32 and Wow/64 quite a bit ago. Keeping the updated version dll ready at hand if needed, I have been playing FSX with every single newest addon out there on the market. (Flytampa Dubai, Airbus X Extended, NGX), and have experienced no crashes whatsoever.
December 30, 201213 yr I disagree. As experiment, I did replace the old vista version in my System/32 and Wow/64 quite a bit ago. Keeping the updated version dll ready at hand if needed, I have been playing FSX with every single newest addon out there on the market. (Flytampa Dubai, Airbus X Extended, NGX), and have experienced no crashes whatsoever. By "other programs" I was not referring to other FS add-ons. I mean other software that doesn't run as part of FS. Adobe Photoshop was one in particular that yakked with the Vista UIAutomationcore.dll on Win7. It's generally safer to keep the original system dll in place and to put the older version in the program directory so that it doesn't affect other software. Regards Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
December 30, 201213 yr By "other programs" I was not referring to other FS add-ons. I mean other software that doesn't run as part of FS. Adobe Photoshop was one in particular that yakked with the Vista UIAutomationcore.dll on Win7. It's generally safer to keep the original system dll in place and to put the older version in the program directory so that it doesn't affect other software. Regards Bob, I would agree with you, however my computer is strictly FSX. I am curious to see if the file will ever corrupt or cause a uiautomationcore.dll crash. Or even prevent crashes. I hardly ever get crashes, but I do occasionally. But never from uiautomationcore.dll, or ntdll.dll.. etc.
December 31, 201213 yr Author the problem seems to be solved, after i killed the "explorer.exe" process, is it a solution? it's funny how i fly without the desktop and just ALT+TAPING between windows LOL Edited December 31, 201213 yr by Muhammad Essam96
Create an account or sign in to comment