I have reverted all the way back to crimson 16.2.1 which I hope is pre vulkan and the newer power management changes for the new 300 series cards. I guess for an older card likes yours and mine the older drivers should be good. I read many still use the old catalyst drivers 15.11.x or 15.12.
I would grab DDU off guru3d and run that to clean out the old drivers. Grab an older driver first and save ready to install it before running ddu. Maybe try 16.2.1 which I think is pre vulkan. Check if it offers it as an option on install, I can't recall.
I have been having lots of issues on my R9 270 since about Crimson 16.3.2 and all versions up to 16.6.x
In particular Company of Heroes 2 MP would crash either to desktop, blue screen or more often just plain hard lock the pc needing a complete power off; after about 30 minutes in game with sound glitching in a loop. I don't use the amd hdmi audio and its disabled in the drivers .
Tested my RAM using Linux grub memtest and stress tested the cpu using intel burn test all ok, no smart issues and SFC scan is ok. Linux and windows 7 run fine and my other all be it simpler games like RCT3, this war of mine etc run fine. Just some game seem to cause these kind of locks. There are others having crashes and lock-ups on the 16.7.x drivers here...
Was vulkan support introduced at 16.3.x ? Can someone confirm this ?
thank you for your fast answer.
I already tried to install the 16.2.1 driver (no Vulkan there) but the error is still appearing. Furthermore I tried to play Flight Simulator and there was no problem. As a result I guess that only a few games are affected. After that I made a Benchmark with FurMark and the system crashed again.
I really don´t know what I can do to solve the issue.
Do you or someone else have other ideas? I´m just a bit confused because my system worked perfectly before (played 3 hours Overwatch before). The issue appeared abruptly.
I am finding 16.2.1 more stable. Did you use ddu to clean out the old drivers ?
The only difference is I am on windows 7 64 bit. Seem to be more issues with win10.
If other games are fine then unlikely to be hardware but you can do some basic hardware tests if you want to rule everything out.
if you have linux on a live CD or usb drive(use Universal USB Installer – Easy as 1 2 3 | USB Pen Drive Linux ) you can make a live linux usb to boot off and do a memtest from the boot menu (memtest86). You could also run the intel burn test tool Download IntelBurnTest - MajorGeeks to check the cpu and main board system stability. This one runs under windows so an easy test tool.
Does win10 have the sfc scan feature ?
I already did a Memtest 86, no error.
I will test my CPU and Mainboard with the tool.
Yes, Win 10 has an sfc /scannow feature. No error message aswell.
I used DDU to uninstall the driver. But i got this error message while using it: "A problem occured in one of the module, send your ddu logs to the developer"
I have Direct x12 installed. Does my GPU support it?
DDU is fine know. Just the wrong version. The issue is still there. No error while testing CPU and Mainboard
I suspect if MS flight sim works then its a similar issue to mine. I had coh2 crashing and locking up but other games run fine. I take it you have run the verify cache for each of the 'problem' games from your steam library. Sometimes the games come with a redist folder which has vc++ and directx folders so you can find those and re-run those installers for the problem game. W
Be aware that mods from the steam workshop can break some games and sometimes they don't get removed clean. These usually are stored in C:\Program Files (x86)\Steam\userdata. (close steam, backup the folder and remove the contents). On steam re-start it will resync. If you have local save games only these can be lost though if the game saves them in this userdata folder and does not cloud save on steam, (mostly old games).
I doubt its hardware. I guess you could try the 15.11.1 Windows 10 catalyst branch which is the 'driver era' for your card as a last resort. Use ddu and remove the driver then reboot and let windows install its own generic amd driver first before installing the amd ones.
Be aware that 15.12 and 16.xxx are all the newer crimson drivers.
I have no end of problems after 16.2.1. It seems the newer drivers development is focused on new hardware R300 series and testing on older cards feels like it becomes secondary if at all so I am sure there must be a sweet spot for the most stable driver for each card as it ages. Just find 1 that works stable that you can always go back to.
I´ll try to repeat the installation of 16.2.1 and if this doesn´t help again I will try 15.11.1.
I think it´s my GPU. Maybe the VRam
buying a 300€+ graphicard should be including a decent driver support.
everyone was complaining about the driver issue and problems someone got with a amd/ati gpu. i didnt had one (had a hd4870)
now i bought a r9 290 years ago and someday the drivers are **up. really?
where i can get the older driver version?
Does anyone have an idea how to fix that?
The error is really annoying.
Is that event id44 correct (did you web search it).
What is the exact error message (windows reliability history will show it).
Critical error: Kernel-Power ID 41 (63). The system shut down unexpected
Sorry,I wrote down the wrong the number.
I got the exact issue. Random system crash and Display corruption all over the place. AMD please DO FIX THIS ASAP.
I have gotten three hard freezes with this driver. While this does fix one issue that has really been bothering me (VSR on HDTVs), I can't have my PC crashing three times a day, I would be upset if it would crash once a month. I'm back to 16.7.2 and all seems well.
1 of 1 people found this helpful
On my R9 380 card I had to roll back to 15.11 I am still running crimson software but I just rolled back the driver version and my pc has been stable since. 16.7 was causing a lot of crashes for me too in windows 10 'Blue Screen Of Death' and memory addressing errors during gaming (where all the gpu memory was used up instantly which most games shouldn't be the case at all) made quite a few games unplayable, and unstable. I hope they address these issues soon to support the R9 series cards in the newer drivers because the crashes are quite unbearable during gaming, and I suspect a lot of people own R9 cards still.
Just added a reply that could interest you.
Glad to know that I am not alone, but sad to read all this. Here is what is happening with me and my "lovely" Radeon HD 7970 3GB OC from Gigabyte plus Windows 10 64bits and 16GB of RAM:
Company of Heroes 2 restarts the computer. After trying several graphic configurations this is one that I was able to finish the Theater of War > Case Blue > Assault on Voronezh (I have finished the mission but at the end the movie shows a building collapsing and the computer restarted):
On AMD Radeon Settings: everything off or use application settings. only opengl triple buffering on.
In the game: image quality low, anti-aliasing and v-sync off. the other settings left as is after pressing auto-detect button.
This configuration was the closest one I could set up to play CoH2 in a stable way, but even so not 100% stable.
Other "funny" things:
Starcraft 2 was restarting the computer, but after turning off v-sync and anti-aliasing, and setting the refresh rate as default, SC2 became stable again.
Diablo III : the same as SC2 but selecting 1920x1080 60hz as the resolution and refresh rate, with both monitor and driver set @ 60hz of refresh rate.
Battlefield 3: the same.
Older games that I've repeated the set up from CoH2 to test and it seems that they are stable:
Rise of Nations
Aliens Colonial Marines
Other STEAM games I did not have time to test but I have now 2 types of set up: for newer games I am following the SC2 configuration and for older games the CoH2 configuration.
As I am using the 16.8.3 driver hotfix pack over 16.7.3 core, I will keep the core at 16.7.3 and remove the driver pack and install the 15.11 version to see what happens.
I was able to finish the CoH2 scenario I've mentioned before with the following: entire AMD pack in 15.11 version (removed everything before the installation) and the following graphics settings in the CoH2:
* auto-detected button pressed, changed to off anit-aliasing and v-sync.
* gameplay resolution set to 50% instead of 100%
And in the AMD Radeon Settings:
* Global graphics profile: Balanced
* In CoH2 profile: all off or use application settings, texture filtering standard, anti-aliasing method multisampling (but it does nothing as in the game is switched off)
After CoH2 match I've jumped to Diablo III to verify the behavior and I felt that 15.11 is more stable than the newer drivers. In Diablo III both v-sync and anti-aliasing were off and resolution was 1920x1080 @ 60hz
Hope this can be used to help others with the same issue.
1 of 1 people found this helpful
I found a solution for the power crashes caused by 16.7.3 driver:
1. I unistalled all AMD software
2. Turn off PC and open the tower
2. REMOVE the graphic card from motherboard
3. Reset the power supply
4. I removed the motherboard battery for a few seconds to achieve a complete reset
5. I turned on my computer (without the graphic card) and I installed the software of integrated graphics (intel hd 4600 in my case)
6. I reboot after instalation and the problem was SOLVED
7. Then I just placed the graphic card to its place (with the previous driver) and it worked completely normal
Notes. first sorry for my english. It seems that 16.7.3 changes something at respect of power supply managment causing surges and hard crashes. Restore system is not necessary.
This is hot news !
I've removed the card from the system and inserted again, but I didn't try to reset the powers (mobo batt. and power supply)
Can I kindly ask you to try to play Company of Heroes 2, any map, and observe if the hard crash happen ?