1: You don't really seem to know what you are doing, and I'm getting the feeling you are guessing at almost all of this. I'm coming to that conclusion based on the absolutely nonsensical "fan curve" you "invented". That fan curve is bizarre, to say the least, and is only SLIGHTLY better than moronic ones defaulted to by card manufacturers. 2: Editing the registry is ⚠ *⚠ * ⚠* ⚠DANGEROUS ⚠* ⚠* ⚠* ⚠. You can TOTALLY F@$% UP YOUR SYSTEM if you don't know what you are doing. 3: Unless YOU are willing to take full and complete responsibility for any damage you do, you shouldn't be telling people to mess with their registry. 4: The registry doesn't have a "save" button, or an "apply" button- Everything you do is in real-time, and there is no "undo" button. Accidentally hitting "delete" could remove huge sections of the registry, and that is not recoverable without a full reinstall of Windows.
Ive been strugling with my amd card for 2 years now and this isnt a solution, its temporal, eventually the crashes will happen again and its fuckinh frustating, do you have any advice since you seem to know better than all of the stupid tutorials that say the exact same shit
@@timerunesout Talk to me, Goose. I make no promises, but I will do anything I can to help. I, too, struggled for years with AMD and my GPU, but thankfully, I am past that now. Gimme FULL system deets, full problem deets, and I will do my best.
@@NegativeROG 2 years ago i bought a new asrock rx 570 with 8 gb vram, since day one i had the same problem, my screen would fragment it self in tiny squares, just like a chess board pattern, but instead of each square being black and white they where composed of a multicolor texture and of whatever frame the screen was on when the crash happened, after a couple of seconds amd would show me a sign with the message "we detected a driver timeout has occurred in your system", after that a couple of things could happen, the most common one would be that i just had to restart whatever task i was doing before the crash (99% of the time playing videogames), but sometimes the crash would cause my gpu drivers to be uninstaled or paused(forcing me to restart my pc or reinstall amd drivers once again), Another issue (yes, it doesnt stop i fucking hate amd) is that everytime i turn on my pc theres a big chance of it not showing any video in my monitor unless i change the hdmi cable from my card to my motherboard directly, using my cpu's integrated graphic card (vega 8) So i guess that somehow sometimes my pc just doesnt recognize my rx 570 drivers and it wont start working unless i restart it manually over and over again. , thats my issue, heres my pc specs: Cpu: ryzen 3 3200g (with vega 8 graphincs integrated in it) Ram: hyperx 3000mhz 8gb x2 working on dual channel Motherboard: asrock b450m hdv r4.0 Storage: 1tb hard disk GPU: RX 570 8GB ASROCK Power supply: cylon 80 plus bronze 500w System version: windows 10 pro (up to the latest version of it) Here's some details that happened before i got my rx 570: I used to have no dedicated gpu so i used my ryzen 3 with its vega 8, at that time i dealt with a blue screen with the code "thread stuck in device driver" for almost 2 years aswell, luckily i solved it by changing my motherboards bios version to a previous version much more stable, apparently since my cpu was so new at the time my motherboard wasnt updated properly for it, but a previous version than what i was using was much more stable, i havent had a blue screen with that code ever since ( i really dont know if my bios version has anything to do with it but just in case im letting you know) Heres what ive tried to do: When the crashes started i found a solution pretty quick, i saw in a video that apparently amd does a tiny bit of overclock on its gpus so they reach higher numbers and sell more, i noticed that in my software my gpus mhz reached up to 1250 mhz(without OC), but in its official amd page it said that it reached 1244mhz, i thought 6 stupid mhz wouldnt make a difference but they did, i started using a profile config in amd software that limited my gpus mhz from 1250 to 1244, and it worked for a lot of time, but somehow it came back, believe me, ive tried every fucking thing(including what this video does) but it just doesnt dissapear, i dunno if i just wasnt lucky and was given a broken gpu, its to late to get a refund anyway. I really dont know what else to tell you but whatever info you need let me know cuz i need this thing to work, thanks and i hope i didnt make too many redaction mistakes, english isnt my first language
@@timerunesout I got your message, and I have a response for you. I'm travelling today and tomorrow, hopefully I can sit down tomorrow night and type out a full-length answer. I know exactly what you are talking about, though. Rest assured, I will do everything I can to help. I'll get back on here tomorrow night (Wednesday night) when I can use my PC and not my phone. Hang on!!!
![Путин и ПЕСКОВ ждут звонка от ТРАМПА 😁 [Пародия]](/img/n.gif)
Hope this helped with any AMD crash you have had
unfortunately not
I will try this.
Is my value being different in MinDxgKrnlVersion a problem?
1: You don't really seem to know what you are doing, and I'm getting the feeling you are guessing at almost all of this.
I'm coming to that conclusion based on the absolutely nonsensical "fan curve" you "invented".
That fan curve is bizarre, to say the least, and is only SLIGHTLY better than moronic ones defaulted to by card manufacturers.
2: Editing the registry is ⚠ *⚠ * ⚠* ⚠DANGEROUS ⚠* ⚠* ⚠* ⚠.
You can TOTALLY F@$% UP YOUR SYSTEM if you don't know what you are doing.
3: Unless YOU are willing to take full and complete responsibility for any damage you do, you shouldn't be telling people to mess with their registry.
4: The registry doesn't have a "save" button, or an "apply" button- Everything you do is in real-time, and there is no "undo" button.
Accidentally hitting "delete" could remove huge sections of the registry, and that is not recoverable without a full reinstall of Windows.
Ive been strugling with my amd card for 2 years now and this isnt a solution, its temporal, eventually the crashes will happen again and its fuckinh frustating, do you have any advice since you seem to know better than all of the stupid tutorials that say the exact same shit
@@timerunesout Talk to me, Goose. I make no promises, but I will do anything I can to help. I, too, struggled for years with AMD and my GPU, but thankfully, I am past that now. Gimme FULL system deets, full problem deets, and I will do my best.
@@NegativeROG 2 years ago i bought a new asrock rx 570 with 8 gb vram, since day one i had the same problem, my screen would fragment it self in tiny squares, just like a chess board pattern, but instead of each square being black and white they where composed of a multicolor texture and of whatever frame the screen was on when the crash happened, after a couple of seconds amd would show me a sign with the message "we detected a driver timeout has occurred in your system", after that a couple of things could happen, the most common one would be that i just had to restart whatever task i was doing before the crash (99% of the time playing videogames), but sometimes the crash would cause my gpu drivers to be uninstaled or paused(forcing me to restart my pc or reinstall amd drivers once again),
Another issue (yes, it doesnt stop i fucking hate amd) is that everytime i turn on my pc theres a big chance of it not showing any video in my monitor unless i change the hdmi cable from my card to my motherboard directly, using my cpu's integrated graphic card (vega 8)
So i guess that somehow sometimes my pc just doesnt recognize my rx 570 drivers and it wont start working unless i restart it manually over and over again.
, thats my issue, heres my pc specs:
Cpu: ryzen 3 3200g (with vega 8 graphincs integrated in it)
Ram: hyperx 3000mhz 8gb x2 working on dual channel
Motherboard: asrock b450m hdv r4.0
Storage: 1tb hard disk
GPU: RX 570 8GB ASROCK
Power supply: cylon 80 plus bronze 500w
System version: windows 10 pro (up to the latest version of it)
Here's some details that happened before i got my rx 570:
I used to have no dedicated gpu so i used my ryzen 3 with its vega 8, at that time i dealt with a blue screen with the code "thread stuck in device driver" for almost 2 years aswell, luckily i solved it by changing my motherboards bios version to a previous version much more stable, apparently since my cpu was so new at the time my motherboard wasnt updated properly for it, but a previous version than what i was using was much more stable, i havent had a blue screen with that code ever since ( i really dont know if my bios version has anything to do with it but just in case im letting you know)
Heres what ive tried to do:
When the crashes started i found a solution pretty quick, i saw in a video that apparently amd does a tiny bit of overclock on its gpus so they reach higher numbers and sell more, i noticed that in my software my gpus mhz reached up to 1250 mhz(without OC), but in its official amd page it said that it reached 1244mhz, i thought 6 stupid mhz wouldnt make a difference but they did, i started using a profile config in amd software that limited my gpus mhz from 1250 to 1244, and it worked for a lot of time, but somehow it came back, believe me, ive tried every fucking thing(including what this video does) but it just doesnt dissapear, i dunno if i just wasnt lucky and was given a broken gpu, its to late to get a refund anyway. I really dont know what else to tell you but whatever info you need let me know cuz i need this thing to work, thanks and i hope i didnt make too many redaction mistakes, english isnt my first language
@@timerunesout I got your message, and I have a response for you. I'm travelling today and tomorrow, hopefully I can sit down tomorrow night and type out a full-length answer. I know exactly what you are talking about, though. Rest assured, I will do everything I can to help. I'll get back on here tomorrow night (Wednesday night) when I can use my PC and not my phone. Hang on!!!
@@NegativeROG tysm