-
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
New build for 1440p gaming
- Thread starter johnnypiper
- Start date
OP
- Joined
- Apr 13, 2020
- Location
- New York
- Thread Starter
- #90
When I went to go into BIOS it had reset. I cleared CMOS and I'm back in Windows again. Do I have to go into legacy mode to boot memtest? It keeps telling me to insert a boot drive when I try to boot from the USB.
Rebooted manually and it reset the BIOS again when I went into it...bad board? I'm confused now
Rebooted manually and it reset the BIOS again when I went into it...bad board? I'm confused now
Last edited:
- Joined
- Dec 27, 2008
If your bios is configured to legacy mode then you would need to run memtest86 in legacy mode. If your bios is configured for UEFI then you should run memtest86 in UEFI mode but if the latter it may still read the USB drive even if the USB is in legacy.
Is your system disk partition scheme MBR or GPT? Do you know? You can check that out in Disk Management. If there is an EFI partition in the system drive then your bios is in UEFI mode and your system disk is using UEFI (aka, EFI).
Is your system disk partition scheme MBR or GPT? Do you know? You can check that out in Disk Management. If there is an EFI partition in the system drive then your bios is in UEFI mode and your system disk is using UEFI (aka, EFI).
Attachments
OP
- Joined
- Apr 13, 2020
- Location
- New York
- Thread Starter
- #92
It's EFI. I'm not exactly sure of the format. Disk Management says it's NTFS. I went back to the BIOS I had before. The newer BIOS kept resetting itself and was crashing the system. I still can't get the system to boot to memtest.... not sure what I'm doing wrong. I let the memtest program do it's thing but when I try to boot from the USB it keeps asking for a bootable device. I'm wondering if I am supposed to have the flash drive formatted to NTFS? It's currently FAT32....
Last edited:
- Joined
- Dec 27, 2008
The newer bios kept resetting itself? You mean it wouldn't hold custom values?
If you have an optical disk drive, try creating creating a memtest86 boot disk with a CD or DVD. That bypasses UEFI/legacy issues.
NTFS is the file system format the partition is using. MBR or GPT (aka, GUID) is the partiton scheme the disk is using. Two different things entirely. MBR is another disk partition scheme that was used for years before we had GPT. MBR limits the usable size of a disk partition to 2TB. There are some other advantages to GPT as well. For instance, a system boot disk with a MBR partition scheme cannot work with a UEFI bios.
It's easy to confuse file systems with partition scheme.
If you have an optical disk drive, try creating creating a memtest86 boot disk with a CD or DVD. That bypasses UEFI/legacy issues.
NTFS is the file system format the partition is using. MBR or GPT (aka, GUID) is the partiton scheme the disk is using. Two different things entirely. MBR is another disk partition scheme that was used for years before we had GPT. MBR limits the usable size of a disk partition to 2TB. There are some other advantages to GPT as well. For instance, a system boot disk with a MBR partition scheme cannot work with a UEFI bios.
It's easy to confuse file systems with partition scheme.
Last edited:
OP
- Joined
- Apr 13, 2020
- Location
- New York
- Thread Starter
- #94
Yeah, when I entered BIOS it said that all values had been reset. Unfortunately, I don't have an optical drive and I must have a GPT for the hard drive seeming how I have UEFI BIOS. I was also getting hard crashes with the other BIOS while playing Doom. I checked it again with the original BIOS and it doesn't crash at all... Still not sure if I'm going to be able to run memtest with USB... The restarting isn't too inconvenient but still bothers me and makes me wonder what needs to be replaced. I don't want it to end up damaging anything
- Joined
- Dec 27, 2008
Find the image file in the memtest86 folder and convert it from .img to .iso using this: http://www.imgtoiso.com/
Then build the bootable memtest86 USB stick with Rufus: https://rufus.ie/
Then build the bootable memtest86 USB stick with Rufus: https://rufus.ie/
- Joined
- Dec 27, 2008
Most likely. Or as I said earlier, the bios may be assigning a non load vcore that is just a little too low. We see this now and then on some boards. You might try a fixed voltage as an experiment, say 1.35?
Do you have another GPU you could stick in there for awhile to test if it is a driver issue? Remove existing drivers before you try a different card.
Do you have another GPU you could stick in there for awhile to test if it is a driver issue? Remove existing drivers before you try a different card.
OP
- Joined
- Apr 13, 2020
- Location
- New York
- Thread Starter
- #99
I don't have another GPU until I decide to upgrade which won't be for a while. I can put fixed voltage on the CPU. Isn't 1.35v supposed to be the maximum safe voltage for the 3000 series? Should I use the 100Mhz clock with 36x multiplier or shoot for something like a 40x multiplier at 1.35v? I've heard of people getting 4.2GHz at 1.2v...
- Joined
- Dec 27, 2008
Yes, 1.35 is generally considered max safe 24/7 long term voltage. Understand that in suggesting this dx step I was intending it not to be a long term solution. So 36x sounds like a good starting point but I would go as high as you can get and be stable on 1.35 volts. You may be able to get more out of it than 36x. If you set the multiplier to 36x manually, see what the bios gives you for voltage when the voltage is left on auto. That might be helful.
