• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

Kernel power 41 just means the system lost power. Flick the switch at back of pc for example will show this error.

Could be a power delivery issue, i.e. a problem with the PSU.

Yeah that was my initial thought too after googling around, PSU is relatively new, about a year old, EVGA supernova G2 750W.

It is so random though, it could be fine for months and then I could get 1-5 of those system crashes in the space of a week or 2 :confused:
 
I see il look there then, it's takin some getting used to, I also had a problem with these drivers powered up cold boot and just got a black screen with the fan on my top card spinning 100%, no matter how many times I switched off and on again it would not boot and just do a black screen and fan at 100%. In the end I had to boot in safe mode uninstall driver and reinstall again, has anybody else had this problem?
 
Hmm, could be the 290 then....

Will just make do with it till the next gen lot of GPU's. Should have a good idea of where we stand with regards to DX 12, drivers and g/free sync monitors by then too....
 
I had the kernel power crash a few times when using my 290x's, never had it using the 980's.

It's a wierd one.

If you had this with 290 and not 980 the 290 was damaged.. This error is a dead give away the system lost power.. So the 290x must have been loosing power..

Or you get this error if you crash say bsod and don't let the pc restart instead you force shut down..

In short they is a lot that can trigger this event error.
 
If you had this with 290 and not 980 the 290 was damaged.. This error is a dead give away the system lost power.. So the 290x must have been loosing power..

Or you get this error if you crash say bsod and don't let the pc restart instead you force shut down..

In short they is a lot that can trigger this event error.

Could Well have been Shanks, never crashed in games with the error though, normally on desktop or while browsing the web.
 
Same, mine could happen no matter what I was doing, gaming, browsing or even just idle.... Saying that I don't think any system crashes have happened other in just gaming for quite a while now... *touch wood*
 
In the new Crimson drivers where is it that you can disable xfire, I can't find it anywhere.

- Click on Gaming
- Find the game in the list (or click Add in the top right corner if it's not there)
- On the default tab (Profile Graphics) for that game select the AMD CrossFire Mode.

There's no default "all on" (or all off, for that matter) that I can find.
 
I cannot get Skyrim to work properly on my 280X at all. All sorts of corruption going on. Quitting and re-launching fixes it temporarily. Not overclocked.

A combination of psychedelic colours like this:

And polygons jutting out all over the shop like this:

Now I hate to say it, but I've only had problems with Skyrim with AMD cards. The 460 I had previously didn't give me any problems at all.

Also this 280X plays Metro, etc, with no corruption, so I'm confident it's not the card.
 
^ I've got over 4000+ hours in Skyrim with HD 7950, R9 290 (two in fact) and currently a R9 390 and I can honestly say I've had no consistent trouble like that with any of them.

The top issue you have there with purple is missing textures and thats typically a mod issue the armour meshes can't find their texture, the other time I've known it happen is running out of Vram the textures start disappearing followed not long after by a CTD. That was incidently on a 1gb Nvidia card.

The second issue is either driver or hardware related - the severely stretched meshes I've only had when I've either overclocked too hard or undervolted it - the latter especially.

Personally I'd say you have a faulty card or PSU and if it was me I'd be RMA'ing it or looking at my PSU output voltages closely.
 
Last edited:
- Click on Gaming
- Find the game in the list (or click Add in the top right corner if it's not there)
- On the default tab (Profile Graphics) for that game select the AMD CrossFire Mode.

There's no default "all on" (or all off, for that matter) that I can find.

There is, but it's somewhere stupid. Go to display settings then click the little arrow in the top-right (additional settings) you'll see an old friend ;)
 
There is, but it's somewhere stupid. Go to display settings then click the little arrow in the top-right (additional settings) you'll see an old friend ;)

Oh yeah, I meant the "in the new Radeon settings window". I've never turned crossfire on globally though, always did it by game only ... turning it on globally is probably not going to give good results unless all that you play supports CF ... which is not likely.
 
There is, but it's somewhere stupid. Go to display settings then click the little arrow in the top-right (additional settings) you'll see an old friend ;)

To get the old crossfire settings you can also click on preferences at the bottom and then 'radeon additional settings'.
 
Thank you AMD.. thanks for taking away my ability to change the gamma. How you did this from the first to the latest Crimson driver is beyond me.. GG.

I dont usually have driver problems but THIS is something that will make me move to the other side.
 
Thank you AMD.. thanks for taking away my ability to change the gamma. How you did this from the first to the latest Crimson driver is beyond me.. GG.

I dont usually have driver problems but THIS is something that will make me move to the other side.

To each their own I guess? My monitors are hardware calibrated, and I don't need or want anything else changing my gamma.
 
Back
Top Bottom