MSI afterburner + noob = fried GPU?

G

Guest

Guest
Hi guys,

First off: yes, I am a noob, and an idiot, and this is my own fault… now that that’s out of the way, let me tell you about my problem..!

I recently bought a new Asus N550JV notebook with Intel integrated graphics and an Nvidia 750M card. Everything worked ok, but my FPS were a bit low so I searched for some tweaks and read about MSI Afterburner. So I install it, start Microsoft Flight Simulator and monitor the GPU temp and GPU load for a while, no problems. But then I noticed those neat looking sliders and I decided to fool around with them… big mistake, as it turned out… As I was moving the sliders, nothing happened, which makes sense because I failed to notice the little “Apply” button at the bottom. So I am moving them back and forth and nothing changes. Then I finally did notice the “Apply” button but I failed to notice that I had inadvertently moved one of the sliders (memory clock, I think) to the far right. So when I hit the “Apply” button, GPU load spikes to 100%, FSX crashes immediately and Windows tells me the driver crashed or something. Now when I start FSX, it always uses to the Intel integrated graphics, even when I tell Windows to use the Nvidia 750M.

- Resetting MSI afterburner, unistalling it and reinstalling the Nvidia drivers did nothing. Did I fry the Nvidia GPU? Is there a way to test the card and verify that it is broken?

- Do you think I can send it in for repairs under warranty and pretend like the GPU died for no apparent reason? If the damage is your own fault and you choose not to repair it, Asus will still charge you €75, I guess it’s worth a try considering it's a 3-week old €1100 notebook… what do you guys think?

Thanks!
 
G

Guest

Guest


I'll give it a try when I get home tonight, but if the old profile were still active, wouldn't the drivers crash every time I try to run a game because Windows is attempting to use the Nvidia GPU with the incorrect settings? That's not what's happening, it seems like Windows either ignores the Nvidia GPU, or attempts to use it in the background but switches to the integrated GPU because of an error.

Perhaps I should check the Windows event log, that might show me something useful.