Reporting on new system running FSX after replacing motherboard.

[annber]

:mad::confused:Hi all, I got my computer back on Saturday but just got to gingerly start testing it with FSX yesterday afternoon. I was very nervous, waiting for it to shut down unexpectedly again.

I first did a few very short flights on Carenado's PC12 from PHNL to Dillingham with FSDT PHNL installed and LOD17 photoreal scenery for the whole island. There is no overclocking done yet on the new system. Frames were locked at 30 with everything maxed out and some tweaks applied to the cfg. Frame rates were holding steady at 30.

Yesterday evening I went a step further and installed FTX Global, FTX NorCal, Orbx Monterey, and Orbx San Carlos along with LOD photoreal blend of Northern California's coastline from Point Reyes to Big Sur. Last night flew from San Carlos to Monterey with frame rates at take off around 24 and maintaining a steady 30 all the way to Monterey.

This morning I did the opposite, took of from KMRY with frame rates oscillating between 27 to 30.1 everything beautifully clear and smooth on Carenado's Hawker.

Then something weird happen, first I got a message about either a windows update or something about meeting to register windows for me to use all features. I clicked off the message.

Two minutes later FSX stopped and I got a grey screen. 5 seconds later FSX was back on and there was a error message saying something about the display driver stopped responding and had recovered.:mad:

I am besides myself now. WTF???? What is going on here, I am not expecting the best flightsim performance, but I certainly was never expecting this nightmare.

I have a doctors appt at 11am my time, so I can't respond to you guys for the next three hours or so, but I am now afraid to open FSX, and have no idea what end is up anymore.

[mrzippy]

It sounds like it updated your graphics driver. Be Careful using 3 letter abbreviations!;)

[E-Buzz]

Hi Annber,

I think mrzippy might be on the right track here.

I had the exact same problem when I updated my vid card drivers, but my card is AMD and with the newer drivers, it's a known issue that most of them aren't ideal for FSX - AMD (as opposed to Nvidia) doesn't seem to give much thought about FSX (although maybe that will change with FSXSE).

Hopefully someone will know and post which driver version should be used for your card, although I imagine all Nvidia drivers are fine. I can't comment on that as I don't have Nvidia.

You might be able to just roll back to the previous version driver (since it was working fine before) IF indeed the driver was updated. I always set my preferences in Windows/CCC to either prompt me and ask permission before downloading any updates, or at least ask for permission BEFORE installing.

I feel your pain - I know it's disappointing right now. But, you have access to the collective mind of this forum - someone, or more than one, will be able to help figure this out and get you back to flying shortly! And mrzippy might have already done just that!

Hang in there!

 

E-Buzz :pilot:

[W2DR]

I would offer three things:

 

Uninstall/reinstall everything related to FSX, and

 

roll back your video drivers, and

 

never, ever let Windows automatically install anything (especially drivers).

 

As always, YMMV.....

 

Doug

[mallcott]

The only reason updates will automatically install on a Windows-based rig is if the owner gives it permission. No graphic card driver update can be carried out without such permission so you are already barking up the wrong tree. A Windows update, while you are in the middle of a gaming session? The only way that happens is if you allowed it.

 

YOU are the owner so take some responsibility. Stop trying to rush into things like an FSX installation - With all that you've thrown back in already there is no way for anyone - not even YOU - to know what the problem is, what caused it, and how you might solve it and prevent it in the future.

 

What you NOW need to do is start reporting the issues properly.

 

Get us the error message, or simply reinstall Windows, wait three or four days while the updates are offered and accepted (Windows does NOT offer you all historic updates at once, this happens over a few days as many can be conditional on previous updates.

 

ONLY once you have a stable OS can you even contemplate installing FsX, and then do so systematically.

[il88pp]

..... Then something weird happen, first I got a message about either a windows update or something about meeting to register windows for me to use all features. I clicked off the message.

Two minutes later FSX stopped and I got a grey screen. ........

 

allways take screenshots of messages you don't understand.

then type the tekst in google and look it up.

 

take a picture with your Phone if you can't take a screenshot at that moment.

 

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

Sounds like windows is not activated. That's serious. But the precise message would help.

 

Did you reinstall windows when you got the pc back?

[annber]

Guys, thanks for the responses. I am still not home in front of the computer, but I did stop on my way out at the computer shop. The guy there said that he thinks that because they replaced the motherboard, Windows is treating it like a new installation of Windows 7 and therefore I need to right click on Windows 7 and enter the code #.

BTW, the Windows message was about validation. I did try to capture the image, but was a second too late.

Supposedly by registering Windows again it will be solved. Does this make sense?

[E-Buzz]

Guys, thanks for the responses. I am still not home in front of the computer, but I did stop on my way out at the computer shop. The guy there said that he thinks that because they replaced the motherboard, Windows is treating it like a new installation of Windows 7 and therefore I need to right click on Windows 7 and enter the code #.

BTW, the Windows message was about validation. I did try to capture the image, but was a second too late.

Supposedly by registering Windows again it will be solved. Does this make sense?

 

Yes.

If your version of Windows is not OEM (as in, not from a store-bought computer - the OEM versions tend to be tied to the original motherboard), entering your code should work.

Let us know how it goes.

 

E-Buzz :pilot:

[il88pp]

....they think .... and therefore I need to right click on Windows 7 and enter the code #.

 

Yes, and no.

Yes you need to Activate, but no, Activation may not be that simple.

 

There are many versions of each windows.

 

There is windows 7 basic, Home, Home premium, Pro, and black edition. For example.

 

But of each one, there is also: A full version and an O.E.M. version.

OEM stands for Original Equipment Manufacturer.

The Full version costs around 400 dollars, The OEM version around 100.

The main difference: The full version you can take with you if you get a new computer. You can remove it from the old one and install it on the new one.

 

The OEM version is tied to the first computer it is installed on.

 

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

Now what is "the computer" here?? It is the mainboard.

You can get a new cpu, graphics card, harddisk, ram, whatever you want. Windows does not care.

But you can't get a new mainboard.

If you do, you have to buy a new copy of windows, and install afresh.

 

One exception: If the mainboard was fauty ( :) this is you!! ) You can get the mainboard replaced and get windows activated again. But you will need permission from Microsoft. You will probably need to call them.

They do not always allow this, but sometimes they do.

 

I would suggestkeep proof the mainboard was faulty. Talk to the shop. See if they can help too.

 

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

If you have the full version of windows, there are no such issues. You can just enter the activation code again.

 

All this is just how I understood the differences.

Look up the full info for your Windows version on the Microsoft Website.

[il88pp]

the reason this happened togethre with the vid update was pure chance.

 

well, not really.

 

Wehn windows update connects to www.microsoft.com to get the updates there is a check to see if you have the right to download updates, so there is a check to see if windows is activated.

 

So it would have happened with any update you got.

[loki]

Yes.

If your version of Windows is not OEM (as in, not from a store-bought computer - the OEM versions tend to be tied to the original motherboard), entering your code should work.

Let us know how it goes.

 

E-Buzz :pilot:

 

Microsoft is pretty lenient about reactivating with the same product key if you had to replace a faulty motherboard. You will likely have use the phone activation method though.

[napamule2]

Off come the gloves. You are now going to get it good. First off, you got nobody to blame but yourself. (1). Did you go get the latest CHIP SET drivers for your NEW Motherboard? (2). Did you do a clean install of Windows after formating your hard drive (ie: singular drive and not having the 2nd drive plugged in as Windows will install and run best with only 1 hdrive during installation). (3). Did you do DEFRAG after Windows installation? MUST do this!! And do restart of PC. (4). Did you download the latest (NOT BETA) drivers for your video card? Must remove all prior video driver files from hard drive, but since you FORMATED the hard drive they would not be there and you would be using the on-board video (at 800 x 600 res-LEAVE IT there-your Monitor SHOULD self-set for 'ok' display) while you finished the Windows 'clean' installation. Right? Right! (5). Call Microsoft to get registration 'issue' squared away. You DO need to have your PC turned on and be online. It's painless and they SHOULD say 'Yes' since you had to replace a bad MB (ie: there is no 'fault' involved). Restart your PC when finished with MS. (6). Run the Video card drivers exe. When 'finish' is done RESTART your PC. THEN set monitor res to what you want (but 'native' res is best for everyone concerned, especially Windows. FSX has to 'adopt' to whatever Windows chooses-that's the best way to do things-go with what Windows 'says'-for now anyway). Everything look good? Good, now restart your PC to 'prove it' and while it is rebooting press 'Del' (of whatever key) to go into BIOS and set boot drive. After you SAVE changes and reboot is finished THEN you can go look at Process Manager, set your Virtual memory, give preference to Programs, etc. Restart PC. Let it run for 24 hrs. If stable and no errors THEN consider doing a 'vanilla' installation (with NO mods or tweaks) of FSX (if Gold (acceleration) install Deluxe, restart PC, fly for 1 or 2 minutes, exit FSX and restart your PC. THEN install Accel, restart PC, start FSX Accel, fly Accel for 1 or 2 minutes, exit Accel and restart your PC. Do the FSX tweaks to fsx cfg and do SAVE. Start FSX and fly 1 or 2 min. All look 'normal'? Then you are done. Take a breather (take a walk, or go Disney Land?). Now you can install FSX add ons ONE AT A TIME with restart of PC before you fire up FSX to test IT (one program per restart). It's best to take your time and not have to re-do things. Piling garbage on top of garbage is not the way to 'fly' (pun intended).

Chuck B

[darryl737]

Annber, nice to have you back. Ok don't panic the driver update will be fine and will work fine with FSX. You do need to change the settings so that the OS needs permission to install updates though. You will find over the next few days that windows will be wanting to do a number of updates to your rig.

As far as windows goes the comments are right and windows is tied to a motherboard so you will need to reactivate windows, this should be no drama and it is something that you should do straight away. You shouldn't have to uninstall FSX or the add-ons at all.

What you experienced with the driver update is normal other than it doing it mid game which other than being a pain in the you know what, wont of effected anything at all.

 

Just take a couple of deep breaths and dive right in to setting up your rig how you want it and most of all ENJOY yourself.

Darryl

[annber]

Well, it seems that the activation was a success. Did get a scare though thinking my wife had thrown out my Windows 7 Pro disk and cover, but it's here. Anyway, I did pay somewhere around $120 plus from Newegg for Windows 7 Pro, on sale.

So far no new messages or errors:rolleyes:, will keep testing gingerly and reading your advice for guidance.

[darryl737]

Looking good Annber.

[il88pp]

The specs and speed of the Vcard are listed in the fsx.cfg file. Probably a good idea to refresh the windows experience index and the fsx.cfg file now you have all the new hardware.

To save your keyboard shortcuts when refreshing the fsx.cfg file, in the same folder it is in find folder "controls". In there is "standard.xml" file, save a copy to the desktop.

Then rename fsx.cfg and start fsx.

Accept key mappings.

Close fsx again.

A new fsx.cfg and controls.xml are created.

Replace the new controls.xml with the one on your desktop.

Then start fsx again.

All key presets are back.