Recent content by nolifepleb

Yeah I actually sent them a message a few hours ago on this exact reason. Hopefully they get back to me soon. If I get an update from them I'll let you all know here in case someone here has the same board.

Well I'm back because it has happened again. It was about to be a month since the error in 2 days and it happens again. I had installed the 436.48 driver on the 27th of May when it occurred and assumed it was fixed.

That is great news to hear. I haven't had an issue since doing the 436.48 driver reinstall though it only has been about a week and a half. I will have to wait until ASRock decides to update my mobos bios to AGESA 1.0.0.5.

I have only done the 436.48 driver version fix for the time being and I haven't had a crash yet but its only been about 3 days. I really hope ASRock releases a bios update with AGESA 1.0.0.5 though since I have only heard good things related to this issue on that end.

I have been having this issue since installing my 2070 to replace an old 970. I am pretty positive there isn't an issue with any other components on my pc as I had been running the 970 with my more current setup (3600x, ASRock B450m Steel Legend, Crucial Ballistix Sport LT) for over a month...