So, before you go any further it's important to note a few things about the issues I'm currently having.
1.) It does not pertain to just a mod pack, but rather the program as a whole (FTB Client included.)
2.) It seems to have some issue with the card's overclocking, but it's always been overclocked however mildly.
3.) I've not changed anything pertaining to the program other than how much memory it allocates. (Which has been in effect for a few weeks now.)
Okay, so a few days ago I decided I'd try and overclock my desktop's graphics cards. Keep in mind that all has been running just fine on FTB for awhile under a milder overclock, but overclocked none the less. It's previous overclock was running +40 MHz to the Core clock module, and +273 MHz to the Memory module. This brought the totals up to about mid 800's for core clock frequency and mid to low 3000's for memory clock frequency. All games I own run great here, not qualms or anything.
A few days ago, though, I over doubled the core clock frequency boost to +100, and added about the same to memory. Again, no qualms, all my games run great, except for the FTB client. I'm not sure what's the matter with it. The executable takes forever to boot up, but the jar starts up instantly. Things start to get ugly when I enter in game. It'll instantly freeze within seconds of getting in -- forcing the closing of Java. I've noticed some strange symptoms regarding rendering. It seems to do fine in my void age, where there's not much to render in the way of blocks (Maybe a few thousand or so). However, it's most recently crashed when I either put it into developer mode (F3, shows FPS among other stats), or when I load the Over world.
I've got a hunch that it's got something to do with Java that's interfering with the program and my cards. However that still wouldn't adequately explain why the client runs so rocky after a somewhat modest overclock tweak.
Relevant Desktop Specs:
Processor : Intel Core i7 4770K @ 4.0 GHz / Core
Graphics : MSI N660 Twin Frozr III OC -- x2 in SLI
SLI probably isn't all that relevant as Minecraft can't even be coerced into SLI rendering, but it's there in case someone has a revelation as to how it may be the problem.
Thanks all in advance I look forward to reading your suggestions, and solutions. I'll do my best to respond in a timely manner so we can clear this up, with or without a solution -- I may just setup an OC profile for FTB, so I can de-clock when I choose to play. I'd rather not de-clock but if that's what it resorts to, I'll oblige begrudgingly.
UPDATE: So I've been playing around with it the past few hours, and have narrowed down the symptoms somewhat. It appears that when I put it into "Max FPS" mode under video settings, it crashes the driver. All drivers have been updated and should be running just fine. My cards can certainly handle the usage as every other game does so easily.
1.) It does not pertain to just a mod pack, but rather the program as a whole (FTB Client included.)
2.) It seems to have some issue with the card's overclocking, but it's always been overclocked however mildly.
3.) I've not changed anything pertaining to the program other than how much memory it allocates. (Which has been in effect for a few weeks now.)
Okay, so a few days ago I decided I'd try and overclock my desktop's graphics cards. Keep in mind that all has been running just fine on FTB for awhile under a milder overclock, but overclocked none the less. It's previous overclock was running +40 MHz to the Core clock module, and +273 MHz to the Memory module. This brought the totals up to about mid 800's for core clock frequency and mid to low 3000's for memory clock frequency. All games I own run great here, not qualms or anything.
A few days ago, though, I over doubled the core clock frequency boost to +100, and added about the same to memory. Again, no qualms, all my games run great, except for the FTB client. I'm not sure what's the matter with it. The executable takes forever to boot up, but the jar starts up instantly. Things start to get ugly when I enter in game. It'll instantly freeze within seconds of getting in -- forcing the closing of Java. I've noticed some strange symptoms regarding rendering. It seems to do fine in my void age, where there's not much to render in the way of blocks (Maybe a few thousand or so). However, it's most recently crashed when I either put it into developer mode (F3, shows FPS among other stats), or when I load the Over world.
I've got a hunch that it's got something to do with Java that's interfering with the program and my cards. However that still wouldn't adequately explain why the client runs so rocky after a somewhat modest overclock tweak.
Relevant Desktop Specs:
Processor : Intel Core i7 4770K @ 4.0 GHz / Core
Graphics : MSI N660 Twin Frozr III OC -- x2 in SLI
SLI probably isn't all that relevant as Minecraft can't even be coerced into SLI rendering, but it's there in case someone has a revelation as to how it may be the problem.
Thanks all in advance I look forward to reading your suggestions, and solutions. I'll do my best to respond in a timely manner so we can clear this up, with or without a solution -- I may just setup an OC profile for FTB, so I can de-clock when I choose to play. I'd rather not de-clock but if that's what it resorts to, I'll oblige begrudgingly.
UPDATE: So I've been playing around with it the past few hours, and have narrowed down the symptoms somewhat. It appears that when I put it into "Max FPS" mode under video settings, it crashes the driver. All drivers have been updated and should be running just fine. My cards can certainly handle the usage as every other game does so easily.
Last edited: