Ati Radeon Hd 2400 Xt Driver Windows 10 64-bit

[Athina Dollison]

Irecently bought this APU called Ryzen 5 2400g about 3 weeks ago and saw so many post about ryzen 5 2400g users that are not satisfied enough because of some stability issues. So i am here trying to share my experience with AMD community what kind of problem i got and how to fix it in a certain ways and also share some tips about this APU.

Problem: a thing called TDR checker monitors the computers hardware, particularly the GPU, is say the GPU stops responding with the computer for 2 seconds TDR checker restarts the driver. The TDR checker was good on paper but did not work in the real world. as a gpu can stop responding when it is working hard.

Close the registry editor and then restart your computer for the changes to take affect. This puts a delay on the tdr checker of 8 seconds thus the gpu can stop responding for 10 seconds, usually this fixes the problem.

If you are still suffering from this issue (after updates or a reinstall your drivers) then you can follow this step, do the same thing as i mentioned before but instead of typing "TdrDelay" you can now type "TdrLevel" enter the data value as 0 then delete the TdrDelay ones, restart your PC. This method completely turns off Tdr checker, so now your windows 7/vista/8/10 now works more like windows XP without any TDR Checker anymore.

First of all i DO NOT recommend any corsair ddr4 RAM on any b350 series motherboard (idk for other series due to lack of experiment), i've been using the Vengeance RGB 3200 kit for more than 2 weeks and IT'S NOT STABLE even at loose timing. So i changed my RAM to V-GeN Tsunami DDR4 LED 3200kit, stable at cl 14 timing and it runs great untill now. I ussually OC that ram into 3533MHz with 16-18-18-18-36 timing and subtiming tweaked a lil bit when iam in need for AAA Gaming to boost my performance even better.

The reason why is because if the GPU card get "Stuck" on a process and the screen freezes up, you would probably need to reboot the computer each time it happens. But with TDR active, if the GPU card get "Stuck" on a process and freezes up, TDR will automatically make Windows aware that the GPU Card is frozen. Windows will then "Reset" the GPU to unfreeze the GPU card instead of you having to reboot the computer.

The best bet is to find out what is causing the TDR to be activated rather than turning it off permanently. As stated, some times extending the TDR to 8 seconds solves many GPU issues with resetting.This can be a permanent solution if it stops the TDR issue. But if you continue to have TDR related issues afterwards, then you need to start troubleshooting to find out why the TDR is be activated so much.

FYI: Wagnardsoft has a TDR Tool that does everything you want to the TDR in registry automatically including turning it off. Here is the thread I opened concerning this useful tool if interested: Wagnardsoft "TDR Manipulator v.1.2" - small program to change TDR in Registry

Please note that Ryzen 5 2400g performance will scale with your ram speed, if you wanna improve the performance then you should probably increase your ram speed, not to decrease it back to default (2133MHz). I think 3200MHz is recommended to achieve the excellence performance level but you can still run at higher speed like me if you have decent ram that "overclockable" to more than 3200MHz.

I also do not recommend to run at higher than 3333MHz if you're new to ram overclocking because it's not easy to get that ryzen APU stable beyond that speed and it requires you to tweak the advance timing module for that, which is quite frustrating to learn (buying higher ram speed module higher than that may or may not help you to get more performance due to ryzen memory controller issues which is not solved yet while iam posting this reply, maybe after some bios or driver update it will be fixed but idk when it comes).

As i mentioned in my guide above, I've been testing my rig with corsair vengeance LPX and vengeance RGB 3200kit module, they're both unstable even at loose timing module, maybe i just got a bad silicon lottery on that "memory B-die" or something but some of my friends also having the same problem with corsair ram module so again i personally do not recommending that brand for ryzen 5 2400g.

Firstly I apologize for any mistake, as English is not my native language. Well, I was also having problems with RAM at 3200mhz, BSOD and freezing. After some time testing several things just increasing the DRAM to 1.350v solved everything. Even though the RAM manufacturer and XMP profile indicate 1,200v it didn't work for me.

I think that many of the ideas here are correct. I believe, that the 2400G using DDR4 for its memory map is a major part of the instability issues we're experiencing. There seems to be a consistent inconsistency with Radeon driver packages, as well as the drivers performance with DRAM based memory maps using Raven Ridge. In my case, the system performs completely differently from version to version, sometimes crashing, sometimes BSOD, sometimes bootloops.

Sometimes, if I adjust the UMA for the APU to be 2GB, the crashing/BSODs go up. Sometimes, if I run the DDR4 at 2133, it never crashes, but if I run it at 3000, it will randomly BSOD. Certainly 18.10.1 driver packaging is crashing for me over and over again. Had to roll back to 18.9.3

Great post OP, thanks. Ive been searching this for days after building a new system in an Asrock A300 and running into exactly this issue. I had a BSOD within minutes of starting any game. Oddly FurMark and Prime95 worked without issue, but CSGO would crash after a couple of rounds. Ive re-downloaded and re-installed windows with no effect. Finally found this thread.

Adding the TdrDelay didnt fix my issue, but TdrLevel=0 totally stopped the BSOD...at the expense of major artifacts and screen tearing when there would normally be a BSOD. Then game crashed to desktop.

Next I upped the RAM voltage from 1.2V to 1.35V (desktop system but uses SODIMM with default voltage of 1.2, no finer control than those 2 options). That extended duration before crashes, but didnt fix it.

Next I upped SOC voltage from auto to 1.4V. This fixed EVERYTHING. I suspect there were some voltage or power draw spikes or something going on that caused instability. Next Ill try re-upping the RAM speed and lowering CAS latency back to optimal but if I have to leave them here Ill still be happy.

Looking around that seems to be the consensus, but I couldn't figure out what the default voltage was so guessed (BIOS goes up to 1.6V!). It was stable and didn't get above 70oC under synthetic load so not sure >1.2V is really unsafe. Anyway, after a (finally) a day of crash-free games I started backing off the voltage. Currently at 1.2V without crashes.

I've been having a really hard time to stabilize my 2400G iGPU to run at 1500 without giving more than 1.2v on soc. LLC came to rescue. It was set on auto and I set that on high. now the voltage doesn't go above 1.2 and it's stable.

Hi, I don't think you have experienced all of the problems with this processor, I have purchased a brand new Ryzen 5 2400G and an ASUS ROG STRIX X570-I Gaming Motherboard and this CPU does not even get to the bios stage - the motherboard is reporting a CPU problem, the memory modules are 2 x 8Gb G.Skill DDR4-3200 and a 1Tb Samsung 970EVOPlus chip, and a new 600W PSU - was hoping for a blistering fast setup and got a brick of a PC, has anyone else had any issues where the fans spin and that's about it? any help is gratefully appreciated.

I had what I think is a similar problem-- I use MSI B450 tomahawk as MB, had an ADATA spectrix d41 8GB 2666 1.2 V working fine. Then, I tried to upgrade to a 16GB (2 x 8GB) RipJaws V 3200 1.35 V instead-- in the standard dual channel slots. The cpu red led will go off and that it; no booting, or BIOS. I removed the second stick, and the gpu led went off, but the screen showed an error message asking if I want to choose the default setting (can't remember the exact phrase), when I prompt that it worked fine (at 2133 though, not the full 3200). I tried two sticks with one RipJaws and the Adata spectrix, and the same took place-- cpu red led on, nothing is working.

I don't know if the problem is the MB or the APU or both, but I gave up, and went back to my 2666 old ram out of desperation!

The Ryzen APUs are only spec'd to run at 3000 (2933 to be precise), not 3200. I'm sure some people have had luck based on the silicon lottery of their particular APU. In my case, it runs perfectly fine with 16GB @ 3000. Its been running fine 24x7 for almost a year and half. Its likely why it runs fine at 2133 for you, rather than at 3200, which its not set up to run.

I guess the moral of the story is that because the APU uses standard DRAM memory for its GPU memory address space, its finicky ultimately with how that memory is controlled, allocated, and managed. Candidly, the speed difference is basically infinitesimal, and not worth the anxiety over trying to get it to run much faster.

I was able to install and run Haiku, setting up the SSD with 2 partitions (GPT), one for Haiku, one for Data, with just by setting some Safe Mode options, which I found after unchecking one by one. The safe mode options are:

(Edited) Most likely, and just thinking about this right now, the issue with the 4GB Ram might be related to the fact that Ryzen 5 2400G has integrated Radeon Vega graphics, and in the BIOS, if I recall correctly, I had the video memory set to auto. 4GB of ram is the maximum RAM that can be assigned to video, so I presume that this is why the 4GB limit. I will try with fixed RAM assigned to video.

(Edited 2018.09.06) - well, the 4GB issue has nothing to do with the VRAM, and besides, today, none of the images are capable of booting the box, no matter what safe mode options are set. Therefore, I will keep testing and posting. For now, installing on Ryzen is more a matter of witchcraft than technology

I messed things up later by being stupid and installing bootmanager. Before I was running Xubuntu on this box with Haiku inside Virtualbox, which were wiped out while the Haiku install. Therefore, there was Grub2 there. Installing Boot Manager Removed Grub and then Boot Manager did not show any menu and stayed there in the Boot Manager window forever. Will fix that tomorrow.

3a8082e126