Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Generic User Avatar

System that worked fine for years suddenly refuses to boot with RAM set to XMP


  • Please log in to reply
9 replies to this topic

#1 Cyber_Akuma

Cyber_Akuma

  •  Avatar image
  • Members
  • 22 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:10 AM

Posted 25 June 2024 - 12:43 AM

I am pulling my hair out trying to solve this, I tried asking elsewhere but nobody could help.

 

 
If you just want the important parts:
CPU: 11700K
Motherboard: Gigabyte Z490 Aorus Pro AX
RAM: G.Skill Ripjaws V 64 GB (F4-3600C18D-64GVK)
 
I have been basically building this system since early 2021, budget constraints have prevented me from fully finishing it but it's at least been in a functional state for a while now.
 
Recently after it had been running fine for months I tried to finish some more work on it, which involved re-wiring the drives, installing a sound card, and re-installing a RAID card that had been disconnected for a while but was originally on it. I also updated the BIOS.
 
I then started getting errors from the BIOS that a boot error was detected and that it would not let me continue trying to boot without either entering the BIOS and fixing it or just completely resetting my BIOS settings:
 
 
I tried checking my wires, removing the sound card, and other tests and eventually have narrowed it down to the RAM, specifically, when it's operating past the JEDEC standard of 2666.
 
Sometimes it will boot fine with XMP enabled, but about 95% of the time it will not. When it does boot it can run for literally months just fine, but every reboot after is a gamble if it will complain about a boot error or not.
 
I tried setting the CAS latency from it's XMP speed of 18 to it's JEDEC speed of 19 to see if that was it, didn't work. I tried manually adjusting the voltage from the XMP default of 1.35 in increments of 0.01 up to 1.4 (I didn't want to risk going higher) and nothing. I even tried manually adjusting the memory speed but ANY speed above 2666, even at just a mere 2700, it refuses to boot with the same error.
 
This utter strict adherence to the memory speed being at 2666 and not even being able to handle 2700, while other times it can randomly do the XMP profile of 3600 and stay rock solid for months even with all the stability tests I throw at it makes me worry that it's the motherboard rather than the RAM. Very odd that it can randomly boot fine at 3600 and stay fine, but then claim anything over 2666 is causing it to fail to boot. I really really hope it's not the motherboard, this thing would be a mess to completely take apart and rebuild and I doubt I can find another of the same board for any reasonable price.
 
Does anyone have any idea what this could be? Or what I can try? I really want to get the RAM running at XMP speeds again, it was fine from 2021 until just a few weeks ago. At this rate this thing has me pulling my hair out so much I wish I could just disable whatever blasted boot error detection it has and spend days running my own stability tests just to make sure the motherboard's boot error detection isn't just garbage.
 
I had someone try to suggest it was my OS install, which makes no sense to me since this is the motherboard complaining about this well before it tries to boot an OS, even if I try to bypass the OS by pressing F12 to select a different boot device it will bring up the error before bringing up the boot menu. Still, just to make sure I tried disconnecting my OS drive with the system set to JEDEC speeds to make sure. After the motherboard logo instead of seeing the spinning circles from when Windows loads (Or the error message if it had a boot error) I saw a cursor keep jumping up and down, pretty sure that's the board searching each drive for a bootloader, and then loading me into the CMOS settings. Expected behavior, that's generally what happens when the hardware is working fine but the board did not find anything to boot. I didn't get an error message.
 
So I tried setting it back to XMP on expecting to get the error message, but like I said before sometimes it will rarely decide to work, and it did (still dumped me into the CMOS, but again with no error) so before it flakes out again I quickly booted up Memtest86+ 7.0 to see if I can catch anything wrong with the RAM. I couldn't get Ventoy to boot it in UEFO mode so I was forced to use CSM/Legacy mode.
 
It didn't find anything wrong but I did notice something odd. Unless this is a bug in Memtest86+ itself, it's claiming my IMC is reporting an insane speed and laughably high timings:
 
 
I don't know if this is an indicator of what might be wrong or just a bug in Memtest86+. I then tried a MEmtest86 boot USB and it found no errors in the 4 passes I an allowed to do for the free version, reported correct speeds/timings too. I decided to just create a memtest86+ boot USB to try to in UEFI mode and now it was reporting correct speeds/timings. However, it still behaves oddly. The test seems to go normal at first, but then it gets to the last test "bit fade" or something like that the systems slows down considerably. I thought it was frozen at first until I noticed the animated cursor just barely moves every half minute or so. Even the timer was effected. Currently it's sitting at 10 passes and it thinks two hours have gone by.... it's actually been about 40 hours...
 
Still though, despite all this, no errors found in the RAM. I have NO idea what to do now. When the system decides to work at XMP speeds I can't find anything wrong and will stay working until the nest reboot where then it may or might not work, when it doesn't absolutely NO setting above 2666 will work no matter what other settings I tweak, and it will refuse to boot anything in that state. How can I even try to figure out what's wrong when it doesn't even consistently give me the error?


BC AdBot (Login to Remove)

 


#2 Pkshadow

Pkshadow

  •  Avatar image
  • BC Advisor
  • 13,821 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:On the Brow of the Hill, West Coast, Canada
  • Local time:07:10 AM

Posted 25 June 2024 - 02:25 AM

Hi, nothing unusual about it not deciding to boot up.

 

Your i7 - 11700K Supports Ram speed to DDR4-3200MHz  

https://ark.intel.com/content/www/us/en/ark/products/212047/intel-core-i7-11700k-processor-16m-cache-up-to-5-00-ghz.html

While the installed Ram is : DDR4-3600 ( CL18-22-22-42 1.35V ) to use XMP Ram Speed needs to be below 3200  ===  Suggest lock the timings in.

 

The Ram : G.Skill Ripjaws V 64 GB (F4-3600C18D-64GVK)  is not on the Motherboards QVL List

https://download.gigabyte.com/FileList/Memory/mb_memory_z490-aorus-pro-ax_201023.pdf?v=13e6c67e08b2c32ec74973f5a19300f3

 

Anything that Speeds up the Boot such as Example : ASUS Fast Boot needs to be turned off for the same reasons as below.

MS Fast Start Needs to be turned off : (Will take it you are running Win10)  https://www.windowscentral.com/how-disable-windows-10-fast-startup and WHY !!!

As well your Power settings need to be on Balanced.  Using anything higher is a form of Overclocking.

 

Gigabyte is a strange company and names their Boards differently. please always use the proper name in case release another.

Proper name is : Gigabyte Z490 Aorus Pro AX (Rev 1.0) 

If you are running Win10/11 you should have BIOS Release : F23 installed  https://www.gigabyte.com/Motherboard/Z490-AORUS-PRO-AX-rev-1x/support#support-dl-driver

Your board does Support Windows 11 so please always state your OS.

 

So there you have it.   It has decided to play.  Once this happens will only get it right be doing the above.  Ram speed down and lock the timings in / Buy new ram that is on the QVL List & under compatible speed for the Chip.

 

Nothing can do about it though would suggest if have not done so pull the CMOS Battery out for a few while unplugged from the wall and hold down the power button to bleed the PSU and return the Board to Stock Factory Settings.

again when leaving BIOS make sure have not turned on anything that speeds up the Boot.

 

G'luck.


" mosquitoes really wake up everyday and choose violence "   — dalia (@_dalia7)
www.cnn.com/2020/07/23/health/mosquitoes-attraction-humans-future-wellness-scn/index.html

Ticks - Lyme disease & anaplasmosis - https://www.ctvnews.ca/health/what-you-should-know-about-the-tick-borne-disease-anaplasmosis-1.6942217
 

I-7 ASUS ROG Rampage II Extreme  / ASUS TUF Gaming F17 / I-7 4770K ASUS ROG Maximus VI Extreme


#3 Cyber_Akuma

Cyber_Akuma
  • Topic Starter

  •  Avatar image
  • Members
  • 22 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:10 AM

Posted 25 June 2024 - 03:03 AM

Even back when I had a 10700K installed in this system I had no problem running the RAM at it's XMP setting of 3600, it was running for years at 3600 just fine. And like I mentioned, when this happens it does not accept ANY speed above 2666, not even 2700 which is well below 3200. If Intel's specs of the CPU were a hard limit then literally no CPU would ever be able to operate above 3200 in this board.

 

And very similar RAM kits are on the QVL list, even the 4-stick 128GB version of that same kit (F4-3600C18Q-128GVK), which is quite literally my kit but with four sticks instead of two.

 

I highly doubt it's a compatibility problem considering this started happening about a month ago when it had been stable since 2021, plus the fact that it didn't even accept a speed of 2700 when it happened.

 

Disabling MS's nonsense like Fast Startup is one of the first things I do when setting up a new Windows system for myself. But like I said, this is happening even before the motherboard will try to boot an OS, it refuses to boot anything at all when it gives that error and kicks me into the CMOS settings page. And yes, it's Windows 10... for now, I sadly won't have a choice by next October despite how much I hate 11.

 

The CMOS has been reset multiple times considering I have upgraded and downgraded the BIOS several times during this mess, which completely wipes it every time.



#4 ranchhand_

ranchhand_

  •  Avatar image
  • Members
  • 5,329 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Midwest
  • Local time:08:10 AM

Posted 25 June 2024 - 11:19 AM

 

Recently after it had been running fine for months I tried to finish some more work on it, which involved re-wiring the drives, installing a sound card, and re-installing a RAID card that had been disconnected for a while but was originally on it. I also updated the BIOS.

Start there. Everything was good until you made hardware changes. Reverse everything and return any system settings to pre-problem date. Then start from there; something in what you did is the problem.

My first suspicion is your RAID card; RAID was great years ago, but for a regular work-computer it's not necessary, and the drivers can create problems. If you aren't going to use RAID, why have it installed? If you were getting good sound from the Windows default sound utility, remove the sound card and any drivers you installed for it. Double-check your "re-wiring" of the drives. Are you sure the new cables (I assume that is what you mean) are good?

If no joy:

Start with the basics: run Memtest 86 on your memory one stick at a time, not all at once.

Run. Seatools for Windows on each drive you have. If you can't install it, then run Seatools for DOS which will run virtual from your DVD drive or USB thumb drive. Another good one is Gsmart Control

Check your power supply; fluctuating line voltages will cause what you are experiencing. A cheap dedicated power supply tester will do it. If you order it, read the users' reviews for hints on usage. OR if you have access to an alternate PS you know is good, you can swap to test.

If everything tests as good and you still have the same problems, then try to boot into safe mode and see if the problems disappear.


If there are no responses to my post for 3 days I remove it from my answer list. If you wish to continue the thread after 3 days please PM me.


#5 Cyber_Akuma

Cyber_Akuma
  • Topic Starter

  •  Avatar image
  • Members
  • 22 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:10 AM

Posted 25 June 2024 - 11:37 AM

The only hardware I added was the sound card, which I tried removing to no effect. The Raid card was in the system for a while, it was temporarily removed but just got re-added, it's not new. And I am using a RAID, my main storage array is using it, so I am actually making use of the card. The new cables also came with my PSU and were still new, had not been used before, so the cables should be good. I also tried force-downgrading the BIOS (The BIOS download page says once it's on version F21 it will not let you downgrade below it, but I can still force that by using the Q-Flash Plus feature) back to what I originally had at version F20, the same error still happened.

 

Even more annoyingly, for the last two days it hasn't been giving me problems so I can try to test further, but that hardly means the problem is gone since it's done this before where it's been stable for a while and then suddenly one day decides to fail to boot again.

 

I don't understand the point of testing my drives when it's my motherboard refusing to boot before it even tries to check for a bootloader on any of my drives though. Safe mode is something I can't even get to when it happens since again, before it even tries to boot the OS the motherboard itself is complaining and refusing to boot anything, the OS itself is not failing to boot, it never even gets to try to boot. Windows can't do it's "I see your system failed to boot several times, go into safe mode?" thing because it never even gets to try to boot so it can fail at it. If the motherboard manages to get past POST and starts loading the bootloader, then the system will actually work fine from then on until potentially the next reboot.

 

I know I had a PSU tester from before, will have to see if I can find it. Since I got the PSU new in 2021 though I am skeptical that's the issue. Disconnecting all the wires would be a total mess since I have used most of the PSU's ports by now. If it was the PSU though then wouldn't I also suffer from issues after the system has booted, not just at boot time?


Edited by Cyber_Akuma, 25 June 2024 - 11:38 AM.


#6 mjd420nova

mjd420nova

  •  Avatar image
  • Members
  • 3,259 posts
  • ONLINE
  •  
  • Gender:Male
  • Local time:07:10 AM

Posted 25 June 2024 - 12:11 PM

When things start going whacko after extended periods of normal operation and it directs you to the BIOS.  That should be the first clue.  How old is the CMOS battery???



#7 Cyber_Akuma

Cyber_Akuma
  • Topic Starter

  •  Avatar image
  • Members
  • 22 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:10 AM

Posted 25 June 2024 - 12:18 PM

About three years. Most of this computer's core components are new and were bought in 2021. Only thing that is older/used is the GPU, the HDDs in the RAID (but not the other drives), the RAID card, and the case. The CPU, RAM, Motherboard, PSU, Cooler, Sound Card, and most of the drives are all new and were purchased in 2021... the CPU I think was in 2022 when I upgraded to a 11700K from a 10700K. Even the UPS is new and was bought after the PC parts.



#8 Pkshadow

Pkshadow

  •  Avatar image
  • BC Advisor
  • 13,821 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:On the Brow of the Hill, West Coast, Canada
  • Local time:07:10 AM

Posted 25 June 2024 - 07:16 PM

So as suggested. Ram Speed.

 

Again is not unusual for this to happen after years of working fine.     (I also ran ram faster than specs and burned out the CPU after 4yrs.)  (That is when learned ram to Chip speed.)

EDIT : https://www.intel.com/content/www/us/en/support/articles/000094585/processors.html ram speed by processor.

 

Others have mentioned and as I have turn things off, CMOS battery replace as who knows how long it sat in the store. As well when pulled will return to Stock as others have mentioned.

Turn off things as suggested that speed up the Boot and Read the Supplied URL for why turn off MS Fast Start as it relates to the BIOS as well.

 

As for other things such as Sound Card, disable in Bios.  Raid, you figure that out.  Move stuff off and format and clean install with no raid and install the Motherboard Drivers after install Windows.

As said this can go up to Win 11 so take it up.

 

Stuck in a rut when suggests have been offered as well as concrete proof has been displayed means need to do something differently.


Edited by Pkshadow, 25 June 2024 - 07:19 PM.

" mosquitoes really wake up everyday and choose violence "   — dalia (@_dalia7)
www.cnn.com/2020/07/23/health/mosquitoes-attraction-humans-future-wellness-scn/index.html

Ticks - Lyme disease & anaplasmosis - https://www.ctvnews.ca/health/what-you-should-know-about-the-tick-borne-disease-anaplasmosis-1.6942217
 

I-7 ASUS ROG Rampage II Extreme  / ASUS TUF Gaming F17 / I-7 4770K ASUS ROG Maximus VI Extreme


#9 Cyber_Akuma

Cyber_Akuma
  • Topic Starter

  •  Avatar image
  • Members
  • 22 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:10 AM

Posted 25 June 2024 - 07:59 PM

Again though, even if my CPU suddenly decided to have a hard limit of 3200 and no longer support 3600, then why did no speed under 3200 work either? When it happens, if I set the RAM speed to anything above 2666, even to just 2700, it will refuse to boot even though my CPU should support up to 3200.

 

And I did reset the CMOS, several times, I mentioned this that I upgraded and downgraded the BIOS repeatedly, which reset the CMOS every time.

 

I tried it with the RAID card unplugged too, it didn't make a difference.

 

I don't know why you are mentioning Windows when Windows does not even get a chance to try to boot when this happens.



#10 RevGAM

RevGAM

  •  Avatar image
  • Members
  • 1,555 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cincinnati, OH, USA
  • Local time:09:10 AM

Posted 26 June 2024 - 03:55 PM

A couple of things. 

 

When I have RAM problems, experience has taught me that I should also try removing the sticks, blow out any dust and debris, look for slot contacts that look off, and clean the sticks' fingers. 

 

There is no guarantee this is the problem, and you've probably already done it, so disregard if so. 

 

Please note what was previously said by our resident shadow:

 

 

(I also ran ram faster than specs and burned out the CPU after 4yrs.)

I certainly hope that this isn't the issue, but it is possible that your CPU or mobo is damaged. 


Namaste, Peace & Love,
Glenn


If I have frustrated you, then I must be a student. If I've imparted information or a skill to you, then I must be a teacher. If I've helped you, then I must be a volunteer. If I've touched your life, then I must be happy!
If you had to choose between saving just your family, or saving 10,000 GOOD people (but not your family), what would you choose?

 

My phone's auto-correct is named Otto Rong. :hysterical:





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users