PC Crashes When Bumped

[orangeandblack5]

Hi all,

 

Been dealing with this issue for about a year now, but I don't have excess money or access to spare parts, so it's been pretty hard to diagnose in that time. Basically, whenever my computer is bumped, it will often crash, either via BSOD or just straight to black and then rebooting. Adjusting all of my wires has never helped, but re-seating my memory has often temporarily fixed the issue (it'll go a few days before coming back) and, given the BSODs I do get often involve messages such as "Attempted write to read-only memory" I've been under the impression it was probably just faulty RAM.

 

Well, I finally managed to get my hands on some other sticks, and although the first few days had me certain that I had indeed found the issue, it's looking like that was just the usual "re-seating the RAM fixes the issue for a few days" thing I mentioned before, because bumping the table my PC lives on just now did in fact cause it to throw the above error and BSOD. Without the ability to purchase or even borrow any spare parts, and with a constant need for computer uptime for my work, I'm really at a loss as to how I can figure out what the problem is and address it.

 

If anybody has seen this before, or has any tips for things I could do to help figure out what the heck is wrong here, I'd really appreciate it.

 

Full Specs:

 

MOBO: MSI MAG X570 TOMAHAWK WIFI

CPU: AMD Ryzen 9 5900X

GPU: ASUS RTX 3070 KO OC

RAM: 2x16 GB G.Skill Ripjaws V 3600 CL16

PSU: Super Flower Leadex Platinum 850

Boot Drive: WD Black SN_850 500GB

SSD: WD Black SN_850 2TB

HDD: Toshiba X300 7200RPM 4TB

OS: Windows 10

[IkeaGnome]

Nothing is wrong here. The hard drive would destroy it’s self if it tried to write when the platter was off access so it shuts down. 

[orangeandblack5]

I'm not so sure about that - I don't mean it happens when it's hammered, I mean "standing up from my chair sends a very slight shockwave through the floor into the table legs and the PC hard restarts because of it." This is not my first HDD-based system, and I've never seen anything this touchy before; furthermore, it did not do this in the past (for at least the first year of ownership I never once had this issue), and nothing I use with any regularity is actually stored on the hard drive, just for holding onto photos/videos/other miscellaneous old files.

 

Still, if you're convinced that's the issue, I could try running with the hard drive unplugged for a bit.

[AbydosOne]

4 minutes ago, IkeaGnome said:

Nothing is wrong here. The hard drive would destroy it’s self if it tried to write when the platter was off access so it shuts down. 

HDDs spinning down don't cause memory bugs. Besides, 3.5" HDDs don't have accelerometers (that I'm aware of) like 2.5" drives.

 

11 minutes ago, orangeandblack5 said:

2x16 GB G.Skill Ripjaws V 3600 CL16

What happens if you leave DOCP/XMP off?

[orangeandblack5]

I had turned off XMP on my original set, and didn't really notice a difference - at absolute best, it might have slightly decreased the frequency of crashes, but I'm not convinced that's an actual effect and not just my brain trying to be hopeful about having made headway. At the end of the day, it was certainly not a fix.

[kitnoman]

That's actually kind of dangerous. At least in my opinion. You can try to reseat the CPU. Check if there's bend pins or it's too tight. But what worries me is that you might be grounded. So I would suggest to disassemble everything and build it out of the case first. Like just on top of the motherboard box. Then try to bump on your table or directly use percussive fix/test on the motherboard itself(within reason of course). You can also just try to use a single stick of ram while testing.

[191x7]

Faulty pci-e slot or faulty ram slots.

[orangeandblack5]

That's unfortunate if true - don't have easy access to another motherboard, and RMAing mine seems like it could take a fair bit of time.

[orangeandblack5]

Just disassembled and re-assembled the whole thing - will update here if issue returns. Otherwise, hopefully something was just loose somewhere deep in the system and that will now be taken care of?

[orangeandblack5]

Issue has returned