I've experience random 5-10s hangs with nvidia-drivers-430. I can't tell if they're just input or more, my music doesn't hang. This sounds similar to: https://webcache.googleusercontent.com/search?q=cache:qRKQ10mWCTIJ:https://bbs.archlinux.org/viewtopic.php%3Fid%3D246568+&cd=4&hl=en&ct=clnk&gl=us&client=firefox-b-1-e
I tried a lot of things like messing with kernel parameters (turned of ring buffer stress testing, trace messages, etc unrelated to video). Then I finally masked and downgraded to 418.74 and everything is better.
A small note on this problem, it seems to start only after the computer's been on for a while 30min-1hour ish. It also seems to get worse with time to the point where it's almost unbearable after a day or so.
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems.
I have had very good experience on the gentoo IRC  with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels .
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.
My apologies, I didn't clearly state what I was suggesting. I believe this version of nividia-drivers is flawed and as such needs to be masked. From what I have seen no one else has come up for a solution to the problem other than downgrading nvidia-drivers. I'll go post something on the forums, but I would suggest this version be masked for others' user experience (I've already masked it myself).
Nobody has responded on the forums and 430.26 works where 430.14 doesn't. This is clearly a bug with the 430.14 drivers, please stop blaming it on me and just keyword 430.14 as ~amd64 and stabilize 430.26.
(In reply to Alex Orange from comment #3)
> This is clearly a bug with the 430.14 drivers, please stop blaming it on me
> and just keyword 430.14 as ~amd64 and stabilize 430.26.
Since 430.14 is gone from the tree, I guess this is obsolete.