-
Posts
54 -
Joined
-
Last visited
Nexus Mods Profile
About voldoman
voldoman's Achievements
-
Link? He's saying it's overheating, don't bother.
-
Do you have a MSI card? I don't run a laptop and also have a good PSU (Antec EA 650, rated 9.0 on JonnyGURU) I'm telling you, give it a try. Disabling the 2D clocks won't hurt your GPU if you have decent cooling. It's not energy efficient but not really harmful either. I've felt your pain, frustration, anger, and like you tried every fix in this thread to no avail. This fixed it 100% for me, and it's a huge relief off my shoulders despite my GPU having to idle at 49 degrees.
-
Did you try my recent solution and turn off your 2D clocks? Like you, nothing worked for me until I did that. Try it if you can.
-
Your method didn't work for me. I just did a fresh install of Windows for other related reasons last week and only loaded the latest driver, no CCC or any of the other crap. I figured while I had a new install I might as well test Skyrim and it still hard crashed. However, I did just find a new solution that worked for me, I posted this in the big thread as well. I had tried every fix in that thread to no avail, maybe this will work for some. Like a lot of people, I tried every solution listed here and nothing worked. I have plenty of posts itt from way back when lol. Anyway, much to my amazement after nearly a year, I FINALLY FOUND A SOLUTION!!! I bought SR3 during the Steam summer sale and it was doing the same s***, but these are the only two games that crash my system. So I start more hours and hours of research. I still refused to believe it was a hardware problem, and it turns out it is and isn't. Well, it could be either one, but I'm still leaning towards the code in these games or something screwy with the GPU drivers, maybe a combo of both. Either way, here's how I fixed it and have been playing both games without system crashes for 2 days now, before it was 5 minutes or less. It's simple, DISABLE 2D CLOCKS ON YOUR GPU. After all this time it was that easy, and I don't recall ever seeing this solution posted to fix it. For some reason my card was slipping into 2D clock speeds during gameplay which was causing the crashes, as it should at those low speeds trying to handle demanding graphics. So everyone who has lost all hope should give it a whirl, especially if you have a 6870 like me, which seems to still be the biggest offender. If the option isn't there or isn't working in CCC try downloading your card manufacturer's specific GPU tool, which in my case was HIS iTurbo. (Afterburner for MSI, Trixx for Saphire, etc) I never tried in CCC tbqh, but iTurbo does the trick for me. I hope this works for some desperate folks out there, good luck! Edit: Just a small warning, disabling your 2D clocks will make your GPU idle at higher temps. Make sure you have good cooling.
-
Like a lot of people, I tried every solution listed here and nothing worked. I have plenty of posts itt from way back when lol. Anyway, much to my amazement after nearly a year, I FINALLY FOUND A SOLUTION!!! I bought SR3 during the Steam summer sale and it was doing the same s***, but these are the only two games that crash my system. So I start more hours and hours of research. I still refused to believe it was a hardware problem, and it turns out it is and isn't. Well, it could be either one, but I'm still leaning towards the code in these games or something screwy with the GPU drivers, maybe a combo of both. Either way, here's how I fixed it and have been playing both games without system crashes for 2 days now, before it was 5 minutes or less. It's simple, DISABLE 2D CLOCKS ON YOUR GPU. After all this time it was that easy, and I don't recall ever seeing this solution posted to fix it. For some reason my card was slipping into 2D clock speeds during gameplay which was causing the crashes, as it should at those low speeds trying to handle demanding graphics. So everyone who has lost all hope should give it a whirl, especially if you have a 6870 like me, which seems to still be the biggest offender. If the option isn't there or isn't working in CCC try downloading your card manufacturer's specific GPU tool, which in my case was HIS iTurbo. (Afterburner for MSI, Trixx for Saphire, etc) I never tried in CCC tbqh, but iTurbo does the trick for me. I hope this works for some desperate folks out there, good luck! Edit: Just a small warning, disabling your 2D clocks will make your GPU idle at higher temps. Make sure you have good cooling.
-
It happens with Nvidia cards as well, it just seems more common with ATI.
-
I'll reply to my own post. I was right, the HIS 6870 IceQ X 1GB GDDR5 video card causes the game to crash and my my XFX Radeon HD 4870 ATI-Design 1GB GDDR5 plays Skyrim just fine. I was able to play with the HIS card for about 10-15 minutes and then it did the infamous black screen crash with Skyrim only. There must be something about the faster cards causing the issue since the older cards work fine. Could it be DX11 since the HIS card is DX11 compatible and the XFX card is only 10.1? That is where I would look if I were a developer for Bethesda, but there could be something else. Most likely a driver issue. The game is DX9 so it really wouldn't matter if the 6870 supports DX11 while the 4870 doesn't. Have you tried increasing the voltage a notch or two on the 6870 with MSI Afterburner? Try that and see if it alleviates the crashes. If not I'd use drive sweeper to completely uninstall the video drivers and would install the latest beta drivers. I'd also delete the ini files located in ../my games/skyrim/ folder before starting up the game. Here is what worked for me using so that I can play Skyrim. That only took about 15-20 hours of headaches. First of all, here is what I found perplexing from your statement - Increase the voltage of my 6870 a few notches...means nothing because that is subjective. That was counter productive to me since the 4870 worked fine and the 6870 did not. Anyhow, I did download the MSI Afterburner v2.1.0 and installed it. I did do what you stated by increasing the voltage, and it failed, like I thought it would. However, I took what was working for the 4870 and applied it to the 9870 and it worked just fine. The 4870 has a 750Mhz Core Clock and a 900Mhz Memory Clock. I applied those settings ONLY to the 6870 using the MSI Afterburner. I just finished playing over 2 hours without any issues. I tried using AMD Vision Control, but the setting could not go as low as I needed for both the Core Clock and Memory Clock. I tried the lowest settings using the AMD tool and it crashed after 25 minutes or so...I knew I was headed in the right direction. Therefore, I used the MSI Afterburner to set the lower settings into a Profile that can be saved with the tool. Definitely the lower Mhz on the Core Clock and the Memory Clock worked. I bet it will work for anyone else as well. Don't remove and INI files, or try some other file hack. That just ends up screwing up the integrity of the directory structure. See attachment. Cheers! Have some ale. Brad I did this and was able to play again without random crashes 10 seconds-5 minutes after starting, but it still crashes when I open the world map >_< Oh well, at least it's semi playable again, but this is the last Bethesda game I ever buy.
-
you logout and "jay0510" logs in again i wonder if you agree with yourself in the next reply ;) just pick another thread to derail,this ones for grown ups. :rolleyes: You seem really irritated and salty by the fact my posts have helped people going as far as saying they are me. :laugh: I ain't going no where salty. Stay tuned for my next post. Your process of unplugging/replugging your video card(s) and reinstalling drivers? And helping who, your alt account? Yeah, go back to the Bethesda forums and continue your "it can't be Skyrim it must be hardware" propaganda there.
-
It doesn't crash the entire PC, just video and sound which can't be fixed without a hard reset. You say it isn't, can't be Skyrim? Then why is it only this game in my case? BF3, BC2, TF2, Metro, Rage, not to mention every single other game I have runs fine without incident. Furmark and Heavenly can run for hours, Memtest and Prime 95 pass with flying colors. So why does only Skyrim do this? You and some others say it has to be hardware yet logic dictates the complete opposite, all signs point to Skyrim and Bethesda's barely tested POS code as the culprit. If it looks like, smells like, and tastes like chicken then it's probably f***ing chicken. Sorry, I'm just sick and tired of some people trying to blame hardware. In some select cases that might be, but for the vast majority of users having this problem it's highly doubtful.
-
The good news is that mod tools will be out soon, I bet the mod community will probably have this fixed soon after that.
-
Very interesting. Since you just fresh installed it shouldn't be much trouble to do it again. After that don't install Skyrim and see how your other games run. It is possible you got a bad card, but that's how you can tell if it's Skyrim or not. Quite messed up if it is. Also, what kind of PSU are you using?
-
Just keep choosing the install option, after 20-30 tries it will work. Sadly those audio drivers didn't work for me though, good luck.
-
Sorry, I meant what amd drivers are you using. Im using 11.11 Well, did not work for me.
-
Sorry, I meant what amd drivers are you using.
-
This worked for me. I went to realtek's website and got the newest ac97 drivers. Skyrim hasn't killed my video drivers since. Its been a few days and probably 15+ hours of play. I even got to play long enough to see my first CTD. At first i thought it was the black screen again but when i saw the desktop I was super happy. I am running vanilla skyrim no mods, no dll or patches. Im running win7 64 bit. asus mobo amd processor ati raedon 6900 series. I'll try this, the realtek drivers I installed were the HD audio ones and that didn't help. They aren't signed and I had to hit install anyway about 25 times. It was annoying but well worth it. Same issue lol, had to hit install about 30 times. Anyway, before I test this I'm curious, what driver versions are you using, the most recent ones? 12.1 preview is what I have.