bios or board issue?

MCFC_ANDY

MCFC_ANDY

MCFC_ANDY

Soldato
Joined
9 Aug 2013
Posts
3,310
Location
S. Wales
werid things going on lately, i thought i sorted it but i hadnt, but every time i change anything in bios, like an overclock, i click save and reboot, but i get a tile saying save and reset, so basically i cant change anything as its resetting it all the time, i cant get out of bios without resetting it, so in pic i o/c'ed to 3.7ghz mwhen i return to bios its reset to 3ghz and same for the memory its defaulting to 2666mhz, yet still showing the figures i had put in,
ps ignore ram timmings selected wrong one, doh

B450 tomahawk

any ideas
1605088982077.jpg
 
MCFC_ANDY said:
Yep, I have even reinstalled it to check, but no difference, so I'm going back to original bios and will work up from there, if not then I'm stumped
Click to expand...
Seems so strange you can't save and exit only save and reset.

F4 on the keyboard is save and exit then hit enter

Long shot but it mite be worth changing the cmos battery.
 
I've just gone back to one of the pre click bios and even though can F10 and will save config it tries to boot multiple times, then after about 5 tries gets back into bios and same issue hasn't saved any overclock settings but figures are still there, it's so werid, even if try a tiny 100mhz oc it does same. I try new CMOS, otherwise does look like a board issue

IMG-20201111-115512.jpg
 
so strangely I can oc using Ryzen master weridly enough but not the memory so I thinking a memory issue?
IMG-20201111-173448.jpg
 
Last edited:
It seems like it could be a memory issue. I'm just guessing that the "memory try it" function is trying to boot the board with the faster ram settings you enabled (going by your first screenshot) before reverting back to pre modified settings.
 
EsxPaul said:
It seems like it could be a memory issue. I'm just guessing that the "memory try it" function is trying to boot the board with the faster ram settings you enabled (going by your first screenshot) before reverting back to pre modified settings.
Click to expand...
Could be I guess, I'm at 3.8ghz CPU and holding fine but memory just defaults everytime even in Ryzen master
 
ive just run memtest and all im getting is "memory locking failed" and tests stop, does that mean 100% its a memory issue or could it still be the board?
 
MCFC_ANDY said:
ive just run memtest and all im getting is "memory locking failed" and tests stop, does that mean 100% its a memory issue or could it still be the board?
Click to expand...

That could be a false alarm where memtest cannot access the full memory allocation due to it being taken up by another process if you are running it from within Windows (if you are)

Have you tried running the test directly from a bootable USB drive so that you don't have to boot into Windows?
 
EsxPaul said:
That could be a false alarm where memtest cannot access the full memory allocation due to it being taken up by another process if you are running it from within Windows (if you are)

Have you tried running the test directly from a bootable USB drive so that you don't have to boot into Windows?
Click to expand...
funnily enough have just used the windows memory diag, and detected no errors, so guess im back to square one lol.

i just dont get what could cause the issue.
to sum up:
unable to oc in bios, if i do if oc in bios,then the bios will reset but leaves the oc figues i put in there:confused:
can oc cpu using ryzen master, though pc takes mauliple attempts to reboot, finally after around 3-4mins it finally reboots and has held the oc.
cant set my memory to its 3000mhz as always defaults to 2666mhz
have reinstalled latest bios and rolled nack to previous bios

if i scratch my head anymore i have no hair left:D think i need a large drink:D
 
I'm not clued up at all on what can expected in terms of memory speed on the first gen Ryzen CPUs but I thought they had a reputation for being quite finicky with certain ram kits.

I wonder what the result would be if you set the cpu back to stock and tried to OC the memory then? After you've had that large drink of course :)
 
EsxPaul said:
I'm not clued up at all on what can expected in terms of memory speed on the first gen Ryzen CPUs but I thought they had a reputation for being quite finicky with certain ram kits.

I wonder what the result would be if you set the cpu back to stock and tried to OC the memory then? After you've had that large drink of course :)
Click to expand...
the memory oc, well not really overclock as its 3000mhz memory, but its just resetting to 2666mhz, ive never had an issue,had it running at 3200mhz, thats the weird part, was yesterday i thought i maybe try oc the memory a little more to try improve my fps in RDR2, but all hell broke loose as above, i been watching the debug Leds on boot up after a oc, first twice it fails to reboots it stays on cpu led, then next 2 attempts at reboot it stays on dram, then 5th attempt it finally boots,so i thinking i do a full tear down tomorrow with a reinstall of windows and take it from there,as im completely stumped
 
That is a weird one for sure, especially if you've had it running reliably in the past and never changed any parts :confused:

I think I'd do the same thing as you have planned. A completely fresh start just might reveal something. Good luck and let us know how it all turns out :)
 
ok finaly its sorted, managed to tear down today, found nothing out of ordinary, but i removed a fan splitter coming off the cryorig h7+. and now is is fine back to 3200mhz and 3.8ghz. so its looks like it was the the spliter that was the issue, maybe shorting. anyway cheers:)
 
MCFC_ANDY said:
ok finaly its sorted, managed to tear down today, found nothing out of ordinary, but i removed a fan splitter coming off the cryorig h7+. and now is is fine back to 3200mhz and 3.8ghz. so its looks like it was the the spliter that was the issue, maybe shorting. anyway cheers:)
Click to expand...
How strange it was a fan splitter, glad you sorted it.
 
Good news mate. Well done!

That's crazy that a fan splitter could cause such a problem but just goes to show that you can never discount anything that's connected to the board. I'll bear that in mind if I run into similar issues. Thanks for coming back with an update :)
 
was very strange one, i checked the usual stuff pins etcs, possible shorts, couldnt find anything so just decided to strip it back and the only take off was the splitter, but thats been on there well over a year with no issues. i thought the board was toast, but a little thing like a splitter causing that issue is a new one on me.
 
Tons of years ago I was handling a Supermicro server that was giving me hell. It turns out that, at the end, the problem was a fan in the chassis causing all short of strange issues in the mobo. This story just reminded me that :).
 
You must log in or register to reply here.
Back
Top Bottom