[SOLVED] Memory errors with working RAM

Scufrie

Honorable
Oct 19, 2015
6
0
10,510
I’m getting various errors across various different things that all seem to point to ram, but I know that my ram is working on another device. Tried all 4 slots as well but still the same errors
I’m getting 0x0000007a when I try to boot into a windows 7 image, “Critical process died” BSOD on windows 10, and when loading Linux to memory I get a load of kernel panic errors

any ideas? Trial and error?
 
Solution
Motherboard:


CPU: i7 8700K
RAM: 8GB DDR4 Corsair vengeance (although I have 3 other sticks not plugged in)
Graphics Card: GTX 970
Power Supply: Corsair 850
Storage: 1tb Samsung nvme
Case:
OS: Win10 64
Yes, as said above, those BSODs across different OSs (Windows , Linux) and varting scenarios can have various reasons. In order to make sure if the RAM is faulty or not so you can move on and check other components and/or possible causes you can use MemTest86.

Having issues in Windows and linux might point to a hardware issue, RAM or otherwise.

Which motherboard? Is this RAM (single stick 8GB Corsair?) installed in the slot the motherboard manufacturer recommends for single stick operation?
Motherboard:
Please list your full system specifications including make and model of:
Motherboard:
CPU:
RAM:
Graphics Card:
Power Supply:
Storage:
Case:
OS:

You can check RAM (one stick at a time) with a bootable USB of MemTest86 from here.

You should get 0 errors.

CPU: i7 8700K
RAM: 8GB DDR4 Corsair vengeance (although I have 3 other sticks not plugged in)
Graphics Card: GTX 970
Power Supply: Corsair 850
Storage: 1tb Samsung nvme
Case:
OS: Win10 64
 
Motherboard:


CPU: i7 8700K
RAM: 8GB DDR4 Corsair vengeance (although I have 3 other sticks not plugged in)
Graphics Card: GTX 970
Power Supply: Corsair 850
Storage: 1tb Samsung nvme
Case:
OS: Win10 64
Yes, as said above, those BSODs across different OSs (Windows , Linux) and varting scenarios can have various reasons. In order to make sure if the RAM is faulty or not so you can move on and check other components and/or possible causes you can use MemTest86.

Having issues in Windows and linux might point to a hardware issue, RAM or otherwise.

Which motherboard? Is this RAM (single stick 8GB Corsair?) installed in the slot the motherboard manufacturer recommends for single stick operation?
 
Solution
Yes, as said above, those BSODs across different Windows can have various reasons. In order to make sure if the RAM is faulty or not so you can move on and check other components and/or possible causes you can use MemTest86.

Which motherboard? Is this RAM (single stick 8GB Corsair?) installed in the slot the motherboard manufacturer recommends for single stick operation?
Apologies I missed that info,

motherboard is asus rog z370

the single 8GB ram is installed as per the manual for single stick and also same outcomes when it is dual stick

I had a read of that article earlier and deduced that is was either the disk or memory - i know the memory works as it works fine in another machine and I’m currently 93% of the wait through the memory test with 0 errors currently - although I will update once finished

I figured it wouldn’t be the disk as this is when i boot to Linux from a usb or to windows 7 installer from usb
 
critical process died is an error that only happens to Microsoft files. can be storage drive instead of ram, as some of the files are boot related. Others that cause it are related to your user, and to general system operation. Any of them crash, windows has to follow.

kernel panic errors can be CPU related.

could run prime 95 as it checks CPU & Ram

Prime 95 bootable - https://www.infopackets.com/news/10113/how-fix-bootable-prime95-stress-test-hardware
Prime 95 how to Guide: http://www.playtool.com/pages/prime95/prime95.html

have latest bios for motherboard?
 
  • Like
Reactions: Scufrie
Apologies I missed that info,

motherboard is asus rog z370

the single 8GB ram is installed as per the manual for single stick and also same outcomes when it is dual stick

I had a read of that article earlier and deduced that is was either the disk or memory - i know the memory works as it works fine in another machine and I’m currently 93% of the wait through the memory test with 0 errors currently - although I will update once finished

I figured it wouldn’t be the disk as this is when i boot to Linux from a usb or to windows 7 installer from usb
Yes, as said above, I would update BIOS too. Linux live session errors would point towards RAM and CPU and kernel panic errors as colif said can be CPU related too.

One other thing you can do is, if available, test system with current setup and even before BIOS update with other known good RAM and see if this still happens.

From your title "Memory errors with working RAM" and “Critical process died BSOD on windows 10" I assumed you had Win 10 already installed and running and that this RAM was used before in other system/PC? Or the system just started throwing BSODs? Is this a new build?

Have you tried other USB port with the Win 7 or linux images?
 
Yes, as said above, I would update BIOS too. Linux live session errors would point towards RAM and CPU and kernel panic errors as colif said can be CPU related too.

One other thing you can do is, if available, test system with current setup and even before BIOS update with other known good RAM and see if this still happens.

From your title "Memory errors with working RAM" and “Critical process died BSOD on windows 10" I assumed you had Win 10 already installed and running and that this RAM was used before in other system/PC? Or the system just started throwing BSODs? Is this a new build?

Have you tried other USB port with the Win 7 or linux images?
Correct, this is my normal build with my normal ram running windows 10. I took my ram out one by one and still got errors so I checked my ram in another pc I have lying around and no issues whatsoever. Also did the memory test and showed 0 errors with 2 sticks in

also I have tried with a different USB port and still the exact same sadly

going to do a bios update then test the cpu

appreciate all the help
 
Correct, this is my normal build with my normal ram running windows 10. I took my ram out one by one and still got errors so I checked my ram in another pc I have lying around and no issues whatsoever. Also did the memory test and showed 0 errors with 2 sticks in

also I have tried with a different USB port and still the exact same sadly

going to do a bios update then test the cpu

appreciate all the help
Any minidumps dropped after BSODs? Look in C:\Windows\Minidump any *.dmp files? You can check if Windows is set to drop them in Advanced system settings.

Type sysdm.cpl in Windows search box. In windows that opens go to Advanced Tab and then click Settings in Startup and Recovery section. Then enable:
Write an event to the system log
Automatically restart
Writing debugging information -> Small memory dump (256kb).
Like this:


If there are any minidumps you can upload them somewhere and share links here so we can have a look.
 
Yes, I actually mentioned possible hardware issues in post #5 as it's hapenning across two major Windows releases/editions and linux.
windows doesn't create minidumps until you set it up. It defaults to memory.dmp

That's right. Maybe I should have worded that better as I thought the OP (or possible other user on the PC?) might have already set Windows to drop minidumps and if otherwise how to set it up.
 
maybe you need a word document where you can save things you write out a lot... like

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

but i don't know how many times I have done this...