Welcome to Inkbunny...
Allowed ratings
To view member-only content, create an account. ( Hide )
Bachri

Issue is (partially) resolved, returning to Leaktober right away!

by
So... a LOT has happened since my last journal...

TL;DR I've gotten my PC working again at 1/4 its capacity, getting back to work on art.

Basically, like I said in the last journal, I had a new storage drive, an M.2, to replace what I thought was a dying SSD. When the replacement came, I installed it only to find that it was listing only half of its storage space as being available for use. It turned out that the manufacturers had incorrectly given it an MBR partition format, which has a maximum partition size of 2GB, instead of a GPT format. I was able to reformat it and get the Windows OS loaded onto it, however this made the drive unrecognizable as a bootable device. I was able to load up to the desktop, but only with the SSD attached to boot the PC into the OS that was loaded on the M.2.

This made the purchase of the M.2 completely pointless, as the entire reason for buying it was to replace the SSD. However, it also revealed something vital: The SSD was not causing the crashing and seizing that my computer was experiencing. It was still suffering these issues even with the M.2 installed and running everything, which meant that the drive I had gotten it to replace was perfectly fine. And so, I began testing. Everything.

I tested the drives. I tested the RAM. I ran memory tests, I updated the drivers, I messed with BIOS, I ran everything on UEFI, I did virus scans, I pulled out the RAM sticks and put them back in one by one, I cleaned the dust out of the tower, I formatted, reformatted and deformatted, I did a factory reset, I defragged everything, I uninstalled over 100GB of inconsequential things, I turned Windows Update back on... I did everything I could think of to do to find the culprit to this issue. I didn't stop for anything but to sleep, and this went on for a week straight.

Finally, at long last, I found the source of the issue. Well... somewhat. I now know for certain that the issue was in the RAM, however I don't yet know the exact nature of the issue. I know that if I have all four of my RAM sticks inserted, the scanner system I used to check them throws out enough errors that the scan force-halts, but if I only have one RAM stick then it produces zero errors.

And honestly, that's enough for me. I'm so FUCKING tired of testing and burnt out on trying to fix it that I'm willing to just work with one out of four RAM sticks installed and work on sorting the others out later. That just leaves me with returning to work on the arts that I need to do, which I really need to catch up on, so I'll be getting back to that now that I know the data is safe.
Viewed: 92 times
Added: 7 months, 3 weeks ago
 
Liquid123
7 months, 3 weeks ago
Glad you could kind of find the cause..
Does the issue persist on with 2 RAM sticks? Or did you test a single stick on every port on the mainboard? Maybe one port is broken and the mb is causing the issue.
Bachri
7 months, 3 weeks ago
This is one of the theories I have, but as I said, I'm just too tired to test it further right now. I've already tested every RAM stick individually on a single port, and one stick in particular SEEMED to be more temperamental than the others, but I never tested a RAM stick that I know is working on each port, so honestly it could be some combination of two different issues. Meh, I'll figure it out after some rest.
Bachri
7 months, 3 weeks ago
Bit of an update, I just finished testing each individual RAM stick and each individual port. The ports all checked out on the memory test without errors, so I'm fairly certain the motherboard is fine, but one RAM stick in particular started throwing thousands of read errors so I'm tossing it. I think I've finally got the issue handled, I just need a replacement RAM unit now.
Liquid123
7 months, 3 weeks ago
Good job finding the issue! At least you can use 2 RAM sticks until the new one comes.
New Comment:
Move reply box to top
Log in or create an account to comment.