My PC won't start until I remove and reinsert my RAM

iON_C

Commendable
Apr 27, 2016
3
0
1,510
BOTH RESPONSES COULD HELP IN THE PROBLEM

As the title said, my PC won't start until I remove and reinsert my RAM. My motherboard's BIOS is the most recent version. I built my PC from scratch 6 months ago and there were apparently no incompatibility problems.

Everything was working fine until I decided to start my OS in safe mode, and the PC started with an infinite start loop (apparently a common problem with WIN 10) I needed to reset the BIOS so I could avoid the fast-boot setup and change the order of my devices and use my installation CD.

After that I started to have problems and got a black screen every time I restart or turn on my PC, then after checking my hardware discovered that the PC will only start if I remove and reinsert my RAM (I didn't have the problem before). I've already made memory diagnostic tests and they say I don't have memory errors.

Just to make it clear, I've never overclocked either my RAM or my CPU. The only variation I've made from the factory setup was the fast-boot. I've already rebooted my BIOS and removed the motherboard's battery. I don't know if my RAM has the problem or my motherboard is the one with the problem. When I enter windows my PC recognize both RAM sticks and apparently they work normally.

Any thoughts, of how could I resolve my problem?

These are my PC specs:

Operating System: Windows 10 Pro 64-bit
CPU: Intel Core i7 4790K @ 4.00GHz
Haswell 22nm Technology
RAM: 16.0GB Dual-Channel DDR3 @ 798MHz (10-10-10-30)
Motherboard: Gigabyte Technology Co. Ltd. Z97X-Gaming 5 (SOCKET 0)
Graphics:
Intel HD Graphics 4600 (Gigabyte)
2047MB NVIDIA GeForce GTX 750 Ti (ASUStek Computer Inc)
ForceWare version: 364.72
SLI Disabled
Storage: 931GB Western Digital WDC WD10EZEX-00BN5A0 (SATA)
Optical Drives: STcorp CD/DVDW TS-H653L
Audio: Realtek High Definition Audio

(English isn't my first language so I hope I've explained my problem in a clear way)

Thanks in advance.

BOTH RESPONSES COULD HELP IN THE PROBLEM
 
Solution
That's a good looking rig you have there.

So the title basically says what the issue is with your PC, it won't start until you reseat your RAM. Which means the OS is not properly shutting down/turning off, so it's not dumping data correctly. This indicates one of two issues, Win10 (which is what it most likely is) or the RAM itself. However, if the RAM itself had issues, you would probably be getting blue screens and things.

My advice would be to reinstall Windows 10, or downgrade if you can. Windows 10 has ALOT of bugs to work out, so there's no harm in reverting back to something older.

thejackal85

Reputable
Jan 18, 2016
1,181
0
5,960
That's a good looking rig you have there.

So the title basically says what the issue is with your PC, it won't start until you reseat your RAM. Which means the OS is not properly shutting down/turning off, so it's not dumping data correctly. This indicates one of two issues, Win10 (which is what it most likely is) or the RAM itself. However, if the RAM itself had issues, you would probably be getting blue screens and things.

My advice would be to reinstall Windows 10, or downgrade if you can. Windows 10 has ALOT of bugs to work out, so there's no harm in reverting back to something older.
 
Solution

iON_C

Commendable
Apr 27, 2016
3
0
1,510


 

iON_C

Commendable
Apr 27, 2016
3
0
1,510
Thanks for the quick response. I've finally solved the problem. It wasn't windows after all, in the end was a false contact in the RAM slots.

When I started with the problem I removed and checked the components and cleaned the dust with canned air. So, I thought that everything was "clean" and that wasn't the problem. In my last try removing and reinserting the RAM I decided to clean the RAM slots again and that did the trick. It seems that it was a false contact or something. Kind of strange since I didn't have the BOSD or beeps when the PC booted and when I entered Windows my RAM seemed to work fine, both memories were detected.

In the end after breaking my head thinking It was a defective motherboard, apparently was a little particle in the memory slots. I don't know if it's the final solution but It seems that everything is fine now and even my booting times improved.