Windows 10: BSOD errors galore - should I get a new CPU?

I have a company computer that uses a hefty amount of RAM. I recently upgraded my ram to 128 GB (4 x 32 GB) and 6 TB storage (3 x 2T SSD). It originally came with 16 GB RAM ( 2 x 8 GB) and one 500 GB SSD. I have a Dell Precision 7530. All the parts were double checked online and with my IT professional that they are compatible parts.

Two weeks after upgrading and paying a professional my computer starts a series of BSODs. I tried updating windows and updating drivers. I call a tech professional and he thinks it’s the RAM but ram tests show up fine. It would BSOD before he could do a thorough test on the dell website. He decides it is most likely hardware failure. He takes two RAM chips out so now I have 64 GB. On average I use 25-35 GB of ram so I didn’t want to go smaller.

It’s been two weeks and I am now in BSOD hell again. I end up restarting windows from my PC while keeping my personal files so I can back them up to a hard drive. It would BSOD in safe mode. I’m trying to figure out what is wrecking my computer. It could be faulty ram but could it ALL be faulty? I got from crucial on their amazon site. I can return but would need to wait weeks for a replacement. BSODs vary but most common is CRITICAL_PROCESS_FAILURE and WHEA_UNCORRECTABLE_ERROR.

I’m at the end of my rope and want to just see if I can get a new computer or if this is fixable. But I had to justify spending all this money on upgrading (I needed 1 TB and 32 GB of RAM minimum but my bosses just said to max it out) so I feel very embarrassed asking them for a new cpu a month after upgrading. I know it’s not my fault but it’s not a good feeling. I’m also hesitant to upgrade a new cpu with the ram and SSD from this one. Thoughts?

Edit: I can’t return the RAM as it’s past the return window but I can get replacements from crucial.

submitted by /u/honeywings
[link] [comments]

:)

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?

 

BSOD - Registry Error

Your BSOD code is 0X000000051

Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

+1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

Run a Diskchk /R (I know you already ran one, so you can skip this)

Run SFC /SCANNOW

Report back.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.