I think the RAM is bad in this machine. Opinions?

Slaters Kustum Machines

Well-Known Member
Reaction score
2,498
Location
Iowa
I have a Lenovo Yoga 710-14ikb on the bench that is getting constant BSOD's of various errors. (most of the time the machine doesn't get to the lock screen) Most seem to be RAM related such as "Cache Manager", "IRQ_NOT_LESS_OR_EQUAL", etc.

I have tried a known good M.2 drive as a replacement that will not install Windows due to BSOD. I have tested the RAM with Memtest with no errors. However this machine takes DDR4 RAM and I don't have any to test with nor another machine to put this RAM into. The machine only has one slot so 1 stick of RAM so I can't try different slots/sticks at this point.

Even though the RAM passed the tests I think it's bad since the only other option I can think of would be the system board, but I have never seen a system board act like this. Typically they work or they don't or there is an issue with a port.

Testing Linux next.
 
Last edited:
Have you checked the ram slot for dust, lint etc. I use an artists brush to gently brush out the slot the blast with some canned air.
Try gently rubbing an eraser along the contact pins on the ram (both sides).
Ive had similar issues and found a cat/dog/human hair in the ram slot that was breaking the contacts.
Just a thought.
 
Have you checked the ram slot for dust, lint etc. I use an artists brush to gently brush out the slot the blast with some canned air.
Try gently rubbing an eraser along the contact pins on the ram (both sides).
Ive had similar issues and found a cat/dog/human hair in the ram slot that was breaking the contacts.
Just a thought.
I'll give it a whir. I did re-seat the RAM. The RAM is actually under a metal cover so not much can get in there, but cleaning the contacts can't hurt.
 
Trying to boot to Linux I get an error "BUG: soft lockup CPU#2 stuck for 22s!" I wonder if it's actually a processor issue.
No, this error could be because your linux distro is looking for a network computer or network/internet connection that doesn't exist. Are you using an updated "live" distro?
Use one of the latest distro's and it shouldn't happen.
 
No, this error could be because your linux distro is looking for a network computer or network/internet connection that doesn't exist. Are you using an updated "live" distro?
Use one of the latest distro's and it shouldn't happen.
I tried Mint 17.2 and Ubuntu Gnome 14.04 and 12.04. I'll grab a copy of Ubuntu 17.04.
 
  • Like
Reactions: GTP
It likely has 2 RAM sticks. One is under a plate and can be removed, the other is probably soldered onto the motherboard. Try to boot it without the removable stick in it and run Memtest. Hopefully the only thing that's bad is the removable stick and it can be safely discarded and you can run it on the soldered stick alone. If it's the soldered stick that's gone bad, you're SOL.
 
According to service manual DIMM slot is the only memory.

See https://download.lenovo.com/consumer/mobiles_pub/yoga_710-14isk_14ikb_15isk_15ikb_hmm_201605.pdf

On a side note, from the manual:

Important notes:

• Only certified trained personnel can service the computer.
• Before replacing any FRU, read the entire page on removing and replacing FRUs.
• Carefully remove screws for reuse when replacing FRUs.
• Be extremely careful during such write operations as copying, saving, or formatting. Drives in the computer that you are servicing sequence might have been altered. If you select an incorrect drive, data or programs might be overwritten.
• Replace an FRU only with another FRU of the correct model. When you replace an FRU, make sure that the machine model and the FRU part number are correct by referring to the FRU parts list.
• An FRU should not be replaced just because of a single, unreproducible failure. Single failures can occur for a variety of reasons that have nothing to do with a hardware defect, such as cosmic radiation, electrostatic discharge, or software errors. Consider replacing an FRU only when a problem recurs. If you suspect that an FRU is defective, clear the error logs and run the test again. If the error does not recur, do not replace the FRU. • Be careful not to replace a nondefective FRU.

You haven't been exposing it to cosmic radiation have you?
 
MemTests just runs a parity and response test for the most part and doesn't catch much. Run Prime95 overnight if you really want to check/stress the memory.
 
It likely has 2 RAM sticks. One is under a plate and can be removed, the other is probably soldered onto the motherboard. Try to boot it without the removable stick in it and run Memtest. Hopefully the only thing that's bad is the removable stick and it can be safely discarded and you can run it on the soldered stick alone. If it's the soldered stick that's gone bad, you're SOL.
If I take the 1 stick out the machine won't even boot to the BIOS. If I leave the stick in I can get into the BIOS and it recognizes just the 1 stick. I don't think this model has any on board RAM.
 
What does the BSOD log say that reported the error?

These are all of the BSOD errors listed:

SYSTEM_SERVICE_EXCEPTION
MEMORY_MANAGEMENT
CRITICAL_PROCESS_DIED
BAD_POOL_HEADER
KMODE_EXCEPTION_NOT_HANDLED
BAD_POOL_COUNTER
REFERENCE_BY_POINTER
PAGE_FAULT_IN_NONPAGED_AREA
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Now that the system is running I pulled these from Bluescreenview. Never thought to run BSV with the drive slaved to another machine, D'oh.
 
  • Like
Reactions: GTP
Back
Top