F5F Stay Refreshed Hardware Desktop Device fails to start unless the CMOS is reset each time by taking out and reinserting the MB battery.

Device fails to start unless the CMOS is reset each time by taking out and reinserting the MB battery.

Device fails to start unless the CMOS is reset each time by taking out and reinserting the MB battery.

S
StanleyRules
Junior Member
31
04-22-2016, 08:52 PM
#1
Hi everyone, welcome! I’m new here and hope you’re all doing well. I’m facing an unusual issue with my computer, just like the problem described in the forum. My motherboard is a Gigabyte H170M-D3H, and it worked perfectly for about three years. Suddenly, it stopped functioning last month. I tried everything—replaced the CMOS battery, put it back, waited a bit, and it started working again. After about two weeks, the issue returned. Now it won’t power on unless I remove and reinsert the CMOS battery each time I try to start it. Once it boots up, everything works fine, except for games like GERAS OF WAR 5. I also changed the power supply, but the problem persists. It seems to happen only when I shut down and restart after a few hours. I’m not sure what’s causing it, any advice would be greatly appreciated. Thanks for your help! Asif
S
StanleyRules
04-22-2016, 08:52 PM #1

Hi everyone, welcome! I’m new here and hope you’re all doing well. I’m facing an unusual issue with my computer, just like the problem described in the forum. My motherboard is a Gigabyte H170M-D3H, and it worked perfectly for about three years. Suddenly, it stopped functioning last month. I tried everything—replaced the CMOS battery, put it back, waited a bit, and it started working again. After about two weeks, the issue returned. Now it won’t power on unless I remove and reinsert the CMOS battery each time I try to start it. Once it boots up, everything works fine, except for games like GERAS OF WAR 5. I also changed the power supply, but the problem persists. It seems to happen only when I shut down and restart after a few hours. I’m not sure what’s causing it, any advice would be greatly appreciated. Thanks for your help! Asif

R
RulwenJr
Posting Freak
786
04-28-2016, 03:05 PM
#2
Just keep it ON, right? Do you have a case speaker? Can you get a POST? It could be many things, but I’d try removing one stick of RAM and resetting the CMOS again, then attempt to duplicate the issue. If it doesn’t work, test the other RAM stick after resetting again—if it fails, it’s faulty. You can also run Memtest64 to check for errors, which is a simple test.
R
RulwenJr
04-28-2016, 03:05 PM #2

Just keep it ON, right? Do you have a case speaker? Can you get a POST? It could be many things, but I’d try removing one stick of RAM and resetting the CMOS again, then attempt to duplicate the issue. If it doesn’t work, test the other RAM stick after resetting again—if it fails, it’s faulty. You can also run Memtest64 to check for errors, which is a simple test.

X
XaLoRoX
Junior Member
39
04-28-2016, 08:18 PM
#3
hi thanks for your reply well its nothing to do with the rams i try to boot them without the ram too no pwer at all but as i said if i reomve the battry and put it baack it power on any way i tested the rams with the osftwear you sugested this is the result looks like rams are fine Module 0: DDR4, 8192 MB, 64-bit, 2133 MHz ChannelA-DIMM0 BANK 0 Kingston 9905678-065.A00G Module 1: DDR4, 8192 MB, 64-bit, 2133 MHz ChannelA-DIMM1 BANK 1 04CB Module 2: Empty Module 3: Empty 0.000: Detecting usable memory (16269 MB theoretical max)... 13.078: 10560 MB Test starting on 4 CPUs... 13.078: Allocating memory... 22.641: Memory locking failed (might be reserved by other apps/kernel) 26.766: Test finished with no errors detected
X
XaLoRoX
04-28-2016, 08:18 PM #3

hi thanks for your reply well its nothing to do with the rams i try to boot them without the ram too no pwer at all but as i said if i reomve the battry and put it baack it power on any way i tested the rams with the osftwear you sugested this is the result looks like rams are fine Module 0: DDR4, 8192 MB, 64-bit, 2133 MHz ChannelA-DIMM0 BANK 0 Kingston 9905678-065.A00G Module 1: DDR4, 8192 MB, 64-bit, 2133 MHz ChannelA-DIMM1 BANK 1 04CB Module 2: Empty Module 3: Empty 0.000: Detecting usable memory (16269 MB theoretical max)... 13.078: 10560 MB Test starting on 4 CPUs... 13.078: Allocating memory... 22.641: Memory locking failed (might be reserved by other apps/kernel) 26.766: Test finished with no errors detected

S
sydneyyyyyy
Senior Member
396
05-05-2016, 10:21 PM
#4
Memory locking issue indicates some applications are altering RAM capacity. Pause briefly and try again. It seems you have two different RAM models, which may affect performance. Take out the second stick, insert the first one (the rightmost one) into the slot, reset CMOS, and attempt to boot. Once on desktop, wait a few minutes until the CPU is idle, then run Memtest64. If the error persists, retry until it starts. Never boot a PC without any RAM in the first slot, typically Channel 1 dimming 0.
S
sydneyyyyyy
05-05-2016, 10:21 PM #4

Memory locking issue indicates some applications are altering RAM capacity. Pause briefly and try again. It seems you have two different RAM models, which may affect performance. Take out the second stick, insert the first one (the rightmost one) into the slot, reset CMOS, and attempt to boot. Once on desktop, wait a few minutes until the CPU is idle, then run Memtest64. If the error persists, retry until it starts. Never boot a PC without any RAM in the first slot, typically Channel 1 dimming 0.