Possible RAM issue?

[connorb389]

About a week ago, I cleaned my pc out, when I put it back together, the RAM was half unplugged on one side, I booted it up like this, PC did not boot to windows, I found the problem and pushed the RAM back in, and now I am getting lots of blue screens for reasons like: POOL_CORRUPTION_IN_FILE_AREA, and MEMORY_MANAGEMENT, they are the main 2 stop codes, I used memory diagnostic and it came back and said I had a hardware issue (RAM Issue). Did I break my RAM by leaving it half unplugged and turning pc on? or is this an error with windows/faulty RAM? Also I have wiped my hard drive incase it was a virus and I am reinstalling windows 10 fresh. That way if it bluescreens again it is a Broken RAM, I just need to know if I broke it or if it was faulty.

 

[Darkbreeze]

If you did not have ANY similar error issues prior to starting the system with the memory halfway installed, but did after, then of course it stands to reason, and there is much precedent to support this as we see this happen here and there, that you've in some fashion either damaged the memory or the motherboard. Even the CPU is vulnerable since the memory controller is IN the CPU, and can be damaged by the memory circuit if there is a short or other issue.

My main question would be whether or not you had the CPU and CPU cooler, or any other hardware besides the memory, removed at the time you did the "cleaning"?

First thing I'd do is make sure ALL electrical connections are completely seated, remove the RAM again, make sure you have the population rules correct with the memory in the RIGHT slots for how many modules you have installed based on the motherboard manual population rules (YES, this makes a difference. Most systems CAN run without following the population rules but with varying results including lack of dual channel operation OR errors.) and then reinstall the memory, making sure they are in the correct slots. Every board is different so check the manual.

If all of that is good, try running only a single stick in the slot intended for single module operation to see if there are still errors. Then try the other stick by itself. Let us know what if any changes you notice or if it's the same regardless of whether or not you use either module or both/all, IF you have more than one memory module that is.

 

[connorb389]

If you did not have ANY similar error issues prior to starting the system with the memory halfway installed, but did after, then of course it stands to reason, and there is much precedent to support this as we see this happen here and there, that you've in some fashion either damaged the memory or the motherboard. Even the CPU is vulnerable since the memory controller is IN the CPU, and can be damaged by the memory circuit if there is a short or other issue.

My main question would be whether or not you had the CPU and CPU cooler, or any other hardware besides the memory, removed at the time you did the "cleaning"?

First thing I'd do is make sure ALL electrical connections are completely seated, remove the RAM again, make sure you have the population rules correct with the memory in the RIGHT slots for how many modules you have installed based on the motherboard manual population rules (YES, this makes a difference. Most systems CAN run without following the population rules but with varying results including lack of dual channel operation OR errors.) and then reinstall the memory, making sure they are in the correct slots. Every board is different so check the manual.

If all of that is good, try running only a single stick in the slot intended for single module operation to see if there are still errors. Then try the other stick by itself. Let us know what if any changes you notice or if it's the same regardless of whether or not you use either module or both/all, IF you have more than one memory module that is.

I Literally only took RAM out to clean just the RAM. I have only got one stick of RAM. I am trying to reinstall windows but every time I go to install it from a USB it says a file is missing or corrupted, and the latest try it bluescreened i forgot to stop code but something wasn't _HANDLED

 

[Darkbreeze]

Let me ask you this. Since you say the machine will not "boot to Windows", does it at least POST?

Are you able to access the bios, and if so, if you leave it in the bios or browse around in there for a while without actually making any changes, does the system continue to run or will it crash/reset even if you are not attempting to actually boot into windows?

Try one of the Linux distros.

Also, download and run Seatools for DOS and test the storage drive. Probably it's a good idea as well, if you have multiple drives attached, to disconnect ALL of them except for the drive you are actually trying to install Windows on.

Run Seatools on the primary drive you want to use, or have been attempting to install on. Run the Short DST and Long generic. The Long generic will take a long time to complete. Probably you will want to let it run overnight.

https://www.seagate.com/support/downloads/seatools/