Msi Afterburner 0 Everything

[Lorri Dent]

HelloFor some time after effects was working badly for me, the picture was freezing, I could hear the sound, but nothing else happened. The combination of Photosop and After was terrible. In a word, it was impossible to work. It turned out that after uninstalling another MSI afterburner program to measure computer temperature, everything in After Effect started working. Why am I writing about this? I guess a lot of users might have a problem with this and won't even know what After Effects is all about. Some users may have uploaded msi afterburner to their computer first and then After Effects and won't know what influences it at all.

Not quite unexpected, as such tools could intercept critical function calls and/ or meddle with clock speed and memory mapping. not to diminish your efforts, but generally the assumption for professional users has to be that such tools aren't used to ensure a "standardized" working environment. Anyway, thanks for sharing your insights.

I've had a problem several times where if I fly any thing without AB for a few hours, then switch to something with AB, the burners will not light no matter what switch is turned on. The only option is to reload with the afterburning plane.

I have noticed this too, i contacted Austin, he asked if the throttle was really at 100% and asked me re-check with the throttle statistics being shown by data out, haven't managed to make it fail again since

One thing that I noticed in the v8 run was that if you flew a normal non afterburning jet powered aircraft and then switched to something with a little more umph, the burners would never light. If you opened the sim with an afterburning aircraft, it generally worked every time. I haven't noticed the issue in 9 however, but I seldom fly anything that requires afterburner If it exhibits the same behavior as in 8, then the issue can be more easily identified. Mention that in a bug report and Austin should be able to fix it.

I'm also having afterburner problems. However, I only get the problems if I start with all systems off. If I load the aircraft I want with everything running it's fine, but after starting with everything off then when I try to go full throttle only engine 1 goes 100% N1, the rest hang at about 97% so I only get one afterburner going, which is a nightmare considering my design is for the space shuttle replacement comp. I'll try Voidhawk9's suggestion of turning FADEC off to see if that helps.

If you have the throttles only going up to about 97%, but need the last 3%, there's always the option of rolling the mouse scroll-wheel forward a notch. I also remember the V8 problem (I seem to recall crashing into the back/stern/transom of the Nimitz a couple of times having been unable to light the afterburners at the end of what turned into a singularly bad approach...)

Yesterday i bought the premium deluxe version. Since then i used standard, everything fine. today after finishing installing everything i get the message. thats a bit lazy. i use only the win defender. + msi afterburner, riva tuner, simlink, ghub (for mouse), icue (for keyboard), samsung magican software, navdata center,

I've never overclocked a GPU before, and I'm not looking to squeeze out every last bit of life from my 290 (Sapphire VaporX), I just want to give it a push to hopefully get a few more frames in Skyrim (because 1440p with texture mods and a fairly lightweight ENB is bringing me down to 29-32 fps).

I used Afterburner to change the core clock from 1030 to 1080, and that seemed ok.

At which point do you need to start increasing core voltage? Or can I just keep pushing the core clock up to maybe 1100?

I recommend not touching voltages until you really know what your doing, just adjust your memory and core clocks individually and back off 20mhz from what you find the maximums to be on both. As long as your temps stay in check, have fun with it!

But just bumb up the core in increments of 10MHz until you think you hit the threshold and same with the memory. Be ready to quickly change it back to the lower clock because it can often lead to some odd displaying and won't go away until you restart and reset the memory clock or boot into safe mode and Uninstaller the driver to restore to default clocks.

2. The R9 200/300 series of cards have their memory clock tide to the core voltage. So if you want to stabilize memory overclocks you must increase core voltage until artifact-ing stops. I increase clocks by 10Mhz, I recommend doing the same.

Aux Voltage is not for the Memory. It's power delivery for everything else in the card beside the GPU Chip and Memory. Sometimes the core chip and memory will siphon too much power, and the rest of the components in the PCB will be starve for power. Tweaking Aux Voltage will help with this.

The VRAM on Hawaii cards is very different from previous cards. ALL Hawaii cards have a golden ratio of

VRAM clock/core clock. This ratio varies from card to card but is generally between 1.25 and 1.4. Once you find this ratio it will generally allow you to run a much higher memory clock than try to incrementally raise VRAM frequency. For example my R9 290X has a ratio of 1.36 and 1140/1500 is not stable on it but 1140/1550 is even though they are at the same voltage.

While the Hawaii cards do not have memory voltage controls available in any software the memory clock does scale with core voltage so if you are trying to push a high memory clock you wil need to raise the core voltage regardless of your core frequency. (more here)

4. R9 200 series are Hawaii based cards, they are hungry for power. At stock, they dissipate heat of about 275w. Increasing voltage will increase heat output. During summer, heat will be a concern unless you have an industrial class of air-conditioner.

5. The Hawaii chips are built like a tank. They can take a lot of power and heat. It's usually the rest of the components that give out if not cooled enough such as the power delivery components (VRMS and Chokes).

Nothing. I wasn't aiming for a high overclock, just a little bit of a performance push in 1 game that I play for a few hours on weekends.

So I didn't think I need to stress test if I aim for something reasonable.

I didn't touch memory clocks at all. It's 1400 on the memory by default and since I'm just aiming for a little bit smoother performance in skyrim, I wasn't sure that changing memory clocks would help.

Problem: KSP always crashes after loading. (As in, when the initial loading bar fills and then it begins to transition to the main menu with the circular loading indicator in the bottom-right, it freezes momentarily and then crashes.)

Previously, I only had ForScience! and KAC installed, and everything was working fine. Then, I decided that I wanted to install some graphics mods and some other basic tools (KER, BetterBurnTime, Trajectories). I've tried this in the past and always given up after twiddling with it for hours, but figured maybe you guys could help. Full modlist screenshot link below (please let me know if this is not the proper way to list mods):

Please feel free to ask for additional information, I'll be at my computer for a while and I'd really like to get this working. Also somewhat relatedly, Kopernicus threw a fit during one of my loadings stating that it was incompatible with 1.7.2 & to not open any save files, so I removed it from my modlist -- but if anybody knows if it should work regardless or if there is a way to get it to work, that would also be handy!

Worst case scenario, if this can't be resolved, does anybody have a working graphic mod setup for 1.7.2? I really don't mind changing around my mods! I'd really appreciate any help you guys can provide. Thanks!

Also somewhat relatedly, Kopernicus threw a fit during one of my loadings stating that it was incompatible with 1.7.2 & to not open any save files, so I removed it from my modlist -- but if anybody knows if it should work regardless or if there is a way to get it to work, that would also be handy!

Since you already use CKAN, you can "export mods" to a text file but a screenshot is perfectly fine as well. The output_log also contains a list of your mods. (Personally, I just look at the log, it is the most reliable source^^)

What's your memory usage though? When the game crashes, it should also create an "error.log" and ask you, if you want to open it and it contains some info about the RAM usage and the crash in general, do you mind to upload it as well? I cannot remember the file location but since this issue seem to be replicable, just launch the game and click on "yes" when you are asked to open the log^^

EDIT: It might be good to also note that I've previously used all of these mods (and more). I recently did a clean install of KSP and played 100% vanilla for quite some time, but I missed the aesthetics of some of these mods. I know this is kinda irrelevant though, since I don't have proof/exact memory of my previous modlist, but maybe it'll help?

I'm seeing an access violation (0xc0000005) in the error log. Some quick google-fu says I need to disable DEP for the executable, but since it's 64-bit it won't let me? (I'm not super savvy here, so forgive me if this just sounds dumb). I only use Windows Defender Firewall as well, and KSP is all good there as well

Thanks for your reply! I'm kind of panicking at this point. Here's the scoop..

I removed ALL mods, uninstalled my nvidia drivers and manually reinstalled from the website, uninstalled CKAN and removed all wonky files from the KSP directory, reinstalled KSP and validated the game files, and I'm still getting this error. With no mods? This is so weird, I didn't have this issue two days ago..

Here's the new error log:

I'm not running any sort of overclocking, just all normal stuff. I don't have MSI Afterburner installed, never heard of Riva Tuner (and can't find it when searching, to be safe), but I do have Discord, Steam and GeForce Experience overlays trying to run...

3a8082e126