Problem with the newly installed PC causing BSODs.
Problem with the newly installed PC causing BSODs.
Hi, i just built my first pc and I don’t understand why it keeps
The specs are:
RTX6800xt
Ryzen 7700x
Gigabyte b650 eagle ax
16x2 xpg ddr5 5200mhz
Cooler master cpu cooler
Deepcool case
1tb ssd
3 tb hdd
I built everything following a guide, i downloaded all the drivers and updates i updated the bios
At first i thought i was the ram that made the pc bsod but after testing with one stick of ram and changing the sticks to see if one of them is faulty in the hopes of it working with just one but no.
While searching for the reason i removed my 3tb hdd since i heard it do a scraching sound and i know that means it has some problems, after removing it i still got bsod but less, the thing is it gives me a different error message every time, sometimes is the ram one or the drivers one or other stuff but i can’t understand the reason why it doesn’t work, is there a website where i can find the right drivers since in know that amd is a pain in the <
Expletive removed by moderator
> when i comes to drivers but i have the amd adrenaline and the gigabyte app for updates and i did the on both, can yall help me?
If Windows was installed while a problematic drive was connected, my advice would be to perform a CLEAN install of Windows without linking that device to the system. Also, I strongly advise against reinstalling the Gigabyte app after installing Windows. It’s unnecessary for any system to have it installed in order to function properly or receive the latest drivers. In fact, many motherboard manufacturers’ software—such as Gigabyte App/Control Center or ASUS Armory Crate—are unreliable. More often than not, simply removing those utilities has resolved issues that were previously unsolvable, including BSODs. Regarding drivers and other matters, what Windows version are you using and is it a properly licensed installation? Has it been activated and linked to your Microsoft account?
Visit the Passmark website to obtain the free USB Memtest86 version. Alternatively, you may opt for the optical disk method if a bootable USB isn't feasible.
Generate a bootable media using the Memtest86 files you've received. After that, access your BIOS settings and set the system to start from the USB containing Memtest86 or the optical drive when applicable.
You're welcome to use Memtest86+, since they recently refreshed the software after years without updates. However, for this guide I suggest sticking with the Passmark version, as it has proven reliable over time. The latest 86+ release hasn't been thoroughly tested against Memtest86, so the older version remains a solid choice. You might view Memtest86+ as a supplementary check alongside Memtest86.
Follow these steps to create a bootable USB:
1. Obtain the Windows MemTest86 USB image.
2. Right-click the file and choose "Extract to Here," placing both the image and tool in your current directory.
3. Launch the included imageUSB utility; it should already have the file selected. Select the USB drive you wish to make bootable, noting that this will erase all data on it.
For optimal results, ensure no memory fails during testing. Start with four full passes of all 11 tests at the default configuration. This is recommended before applying XMP profiles. The paid version includes 13 tests, while the free one covers only tests 1–10 and test 13. Always use the most recent Memtest86 version available.
If you encounter any failures, it may indicate instability in your memory setup. You could either slightly increase the DRAM voltage or adjust primary timings. Few secondary or tertiary settings require modification. I can elaborate on those if you need deeper guidance.
Should you fail with the default XMP configuration, consider reverting to the standard JEDEC SPD (1333/2133mhz) and run another Memtest86 pass. If that succeeds, proceed to Prime95 testing.
If it still doesn't pass after a voltage adjustment, attempt further increases within your board's limits. Persistent failure suggests a hardware issue—consider testing each memory module individually with Memtest86. Replacing faulty modules is essential to avoid compatibility problems.
Remember to perform all tests under the default non-XMP settings initially. This helps distinguish whether the issue lies in configuration or in the physical memory itself.