Hi,

I recently got new hardware for my computer. It is the I5-2500k togeather with the MSI P67A-GD53A mainboard. Since I installed my new hardware I'm running into strange problems. Of cause I have already installed the drivers for the mainboard, but that did not help.

Now the problem is that I'm getting a bluescreen when I'm not using FSX togeather with a complex addon, respective my NGX and the other PMDG products I have (actually most of the time works with some other complex addons too, but they don't work always to keep my computer running. Only PMDG products do it reliable!).

To give you some examples of situations I had:

1) Starting my computer just to surf on the internet is not possible. It'll get a bluescreen within 30 minutes. Sometimes immediatly (even before I can start FSX) and sometimes in 30 mins. I can't find any order in it.

2) I've made my first flight with the default Cessna or a Carenado aircraft. I'll again get a bluescreen within those 30 minutes.

3) If I make a flight with any of your products and then turn the sim off and continue doing other things I am not experiencing any bluescreens.

 

The Bluescreenmessage itself says "critical system code or new hardware detected."

 

I have no real idea why this happens. The only things I know is that it happens since I installed the new hardware and that the only reliable way to prevent it is by using PMDG aircraft.

I have already run a virus scanner through my system to make sure it is not a virus, but it didn't find anything.

 

Does anybody have an idea what went wrong?

 

Regards

Emi

When you got this new mobo, did you then do a clean installation of the OS or was it it just shuffled underneath your last instance? If your device manager shows all devices properly installed and on current versions, I would next do a thorough memory test with memtest86+. Are you getting proper cooling? Does your system log offer any additional clues? Did it start happpening after a particular software package was installed?

When installing a new hardware like a mobo, it is essential to do a clean install of your entire system including the OS. Except you have a software that allows a baremetal restore. I guess you didn't do so, when reading this: "...new hardware detected".

If you did, did you try to do a safe boot?

I might add that your power supply might also not be up to specs to run your new equipment. Low wattage power supplies or defective power supplies have been a good source of blue screens in my experience.

When you got this new mobo, did you then do a clean installation of the OS or was it it just shuffled underneath your last instance? If your device manager shows all devices properly installed and on current versions, I would next do a thorough memory test with memtest86+. Are you getting proper cooling? Does your system log offer any additional clues? Did it start happpening after a particular software package was installed?

 

I did not reinstall my OS, as I've lost the CD sadly. My devices are all propably installed. I'll try the memorytest soon.

Cooling shouldn't be the problem as the bluescreens also appear in situations without a high CPU workload. Also the tempratures are in normal range so that should be ok.

The systemlog doesn't offer any clue. It doesn't even show what went wrong.

No, the only things I installed were the mobo and the CPU.

 

When installing a new hardware like a mobo, it is essential to do a clean install of your entire system including the OS. Except you have a software that allows a baremetal restore. I guess you didn't do so, when reading this: "...new hardware detected".

If you did, did you try to do a safe boot?

 

As written above I can't do a reinstall. Can you suggest any other way to make such a baremetal restore?

What exactly am I supposed to do in the safe mode?

 

I might add that your power supply might also not be up to specs to run your new equipment. Low wattage power supplies or defective power supplies have been a good source of blue screens in my experience.

 

the power supply is most propably not the problem. As said, the system even crashes when not on high workload (and therefore not high demand for electricity).

 

 

 

 

 

As I've said in my first post, using a PMDG product will prevent the system from getting a bluescreen. So there must be some connection with the use of FSX and the crashes. FSX must somehow activate a file or something which keeps the system running. Any ideas?

So this is bad luck when you do not have a windows CD. I wonder how this could happen, loosing a CD????

In this case I strongly recommend you to buy a new copy of windows. There are 2 ways:

- as a student

- or a systembuilder version here

price is about the same.

 

Everything else doesn't make sense, regardless what other might say! Sorry to say that.

 

And that it doesn't happen when using FSX, is simply luck. As in this case Windows might not use those components that are needed during surfing or during other tasks.

Just download the .iso of W7 , and use the key stuck to the side of your computer.

Just download the .iso of W7 , and use the key stuck to the side of your computer.

Doesn't make much sense as he gets a BSD after a while. Works only if he got a 2nd pc to download and burn a DVD.

So this is bad luck when you do not have a windows CD. I wonder how this could happen, loosing a CD????

Everything else doesn't make sense, regardless what other might say! Sorry to say that.

 

And that it doesn't happen when using FSX, is simply luck. As in this case Windows might not use those components that are needed during surfing or during other tasks.

 

If you got a mother who throws away all the papers you have on your desk loosing a CD is quite easy...

 

I don't beleave that it is just luck that it doesn't crash while using FSX as I'm still surfing on the web and do everything I'd do when it crashes while flying on my second screen. So it must have something do with FSX.

 

 

Just download the .iso of W7 , and use the key stuck to the side of your computer.

 

Allright, will try that.

In my past experience with the good old blue screen it's either been recently installed software that causes it, minidump files or hardware.

 

If there's anything in here - C:\Windows\Minidump - Delete them, or just run disk cleanup.

 

I bought some Anti-virus and it totally messed up my laptop. Made my Wi-Fi receiver mess up, gave me blue screens so I uninstalled and everything worked perfect.

 

PMDG's products have never caused a problem for me personally.

check virtual memory, I didn't have any after a new install. check all partitions.

This is a hardware issue so I am sending it to those people on the hardware forum who could best help you.

 

Kind regards,

 

<strong class='bbc'>This is an automatic message.</strong><br /><br /><br />This topic has been moved from "PMDG General Forum" to "MOBO, RAM, CPU's & Other Hardware". This move has been done for a number of possible reasons.<br /><ul class='bbc'><br /><li>The most likely reason is that the post was off topic.<br /></li><li>The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.<br /></li><li>The images might not have been "illustrative" or "explanatory" in nature.<br /></li><li>The topic could have been moved because we deemed it to be more appropriately placed elsewhere.<br /></li></ul><br /><br />Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.<br /><br />Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Instability problem jumped at me.

 

Make sure you have enough CPU voltage, raise the CPU voltage a little just to see if you still get BSOD.

 

Before testing your memory make sure you entered the spec. (cas) in bios by hand (not on auto), also make sure they work at their rated voltage, 1.55v / 1.65v?

 

Good luck.

Sometimes the cause is quite simple. You have an I5 2500 K, so I guess that you have overclocked it a little too much. A decent cooler is a must. A friend of mine had lots of BSD due to poor cooling and OC. A BSD is in most cases an

 

hardware issue.

Crash at "idle" when overclocked is usually due to having C states and other power saving features enabled in the BIOS. Turning them off will likely solve the issue and is an easy thing to test.