Windows 10: I keep getting CTDs and BSoDs on my new-ish PC. Can anyone make sense of my DxDiag or...

Hi,As the title says, I've been having some serious issues with many games and occasionally the same errors outside of games, causing frustration, loss of progress, and a lot of time wasted by trying to fix these errors myself. Usually, I'll be in a game most often this happens in more demanding games and suddenly it'll crash to desktop. I'll reopen the game, and this same thing will happen a few more times and eventually I'll get a bluescreen with an error code usually related to a memory error. This mainly happens in games like Warframe, GTA 5 unmodded, in case that matters, Star Citiz

:)

 

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?

 

Miracast Windows 10 dxDiag "not Available"

Let me suggest you to contact the manufacturer of Miracast. To contact the manufacturer, please follow the steps below:

• The name of the OEM + “contact information”
• The name of the OEM + “PC support”

Regards.

 

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.