September 11, 201114 yr After clearing my CMOS BIOS by the clear RAM jumper and removing the battery from the P8P67 Asus motherboard I got all defaults loaded and my Ms7 with FSX system back. However when I want to load a PMDG 737NX I got the message to activate the NGX product which to me is odd in the first place. But entered my product key in order to activate the selected 737NGX. This plane loads partialy and the activation message is repeated again. All stock FSX planes and other payware like Level-D and Correnado run fine. Everytime I select the pMDG, the activation question box in order to fill in the product code appears - After a while 10 seconds maybe it comes back with activation succesfull message but after a few seconds the request to activate comes up again This cycle remains untill I select cancel and FSX quits. All other software like Ms-office and FSC or Active SKy runs perfectly. Peter de Bruin CPU: Intel i7 7700K MOBO: ASUS Prime Z270A RAM: Corsair 16GBGRAPICS: Gigabyte geforce GTX1060 6GB connected to two Samsung SyncMaster 24” - 1900 *1200 LCD’s HDD: two m.2 Corsair Force MP500 / 240GB and one SSD 120Gb OCZ Agility device for FSX device/SATA3 OS: Windows 10 version10.061472.0 FSIM: FSX-SP2, X Graphics, Active Sky Evolution, FSCommander10 , Ezdok camera 2.8 and 3.0 Hardware: SAITEK Trottle, SAITEK Pedals, SAITEK Flight Quadrant plus CH products SimYoke Planes: PMDG 737Ng for FSX PMDG 777 for Prepared3D also iFLY 737NG, CARENADO Baron 58, C172, C208 Grand Caravan and a Bonanza F33
September 11, 201114 yr I'd be surprised if altering your BIOS affects FSX?? Cheers, Graham McAllister - Melbourne, AustraliaPC Specs:Intel I7-2600K, Asus P8P67 Pro, 8GB PC3 17000 (DDR3-2133) XLD 9-11-9-28, GTX 980, 34" ASUS Monitor, 1TB Samsung EVO SSD, Windows 10 (64-bit), Prepar3D v3.3.5.17625, AS 2016, AivlaSoft EFB, EZDOK
September 11, 201114 yr Is your system clock (and date) set correctly after the CMOS reset? I've read somewhere here that this can be an issue with the activation process of the NGX. Regards Christian Stoff
September 11, 201114 yr Author After the reset the system clock and date are somewhere in september 2005.. instead of 2011. Meanwhile deleted all the PMDG files after removal with configuration tool, reboot and did a clean install. Before that I changed the clock and all other settings in the BIOS from default to the right ones like serial interface off and boot sequence, HT off and so on. With the new install activation worked fine. Maybe you are right that the system dat was out of sync and caused the error. Thanks for the info Peter de Bruin CPU: Intel i7 7700K MOBO: ASUS Prime Z270A RAM: Corsair 16GBGRAPICS: Gigabyte geforce GTX1060 6GB connected to two Samsung SyncMaster 24” - 1900 *1200 LCD’s HDD: two m.2 Corsair Force MP500 / 240GB and one SSD 120Gb OCZ Agility device for FSX device/SATA3 OS: Windows 10 version10.061472.0 FSIM: FSX-SP2, X Graphics, Active Sky Evolution, FSCommander10 , Ezdok camera 2.8 and 3.0 Hardware: SAITEK Trottle, SAITEK Pedals, SAITEK Flight Quadrant plus CH products SimYoke Planes: PMDG 737Ng for FSX PMDG 777 for Prepared3D also iFLY 737NG, CARENADO Baron 58, C172, C208 Grand Caravan and a Bonanza F33
September 11, 201114 yr I had the same problem while overclocking and the BIOS reset it self and my time and date to 8 years ago. Soon as you set it correctly it usually works again. When you boot up and Windows tells you it can not get updates from Microsoft anymore thats a big tip off that your clock is screwed up. Paul Deemer
Create an account or sign in to comment