Windows 10: Tracking down Memory BSOD

Hello,


I could really use some help in tracking down some memory based BSOD's I've been getting. I tracked some issues down to an ASUS driver in an earlier post, and was able to clean it off the system. I've now been having some slightly different issues.


I've still been getting some Memory Management BSOD, as well as an issue where the PC doesn't wake up the video card properly from sleep. PC wakes from sleep, but no display is outputted, and PC no longer responds to power/sleep button, requiring force restart. Upon reboot, memory BSOD usually presents itself.


Upon running the driver verifier, I got into a BSOD loop with the message "DRIVER_VERIFIER_DETECTED_VIOLATION".


Here are my latest minidump files.

https://www.dropbox.com/s/gu6jtken6t4e5nl/Minidump3.zip?dl=0


Any help would really be appreciated.

:)

 

IRQ memory BSODS, device manager, memory range?

The only time I've seen that type of BSOD for myself is when I fried the PCI-e slots on my Striker 2 board... There wasn't anything that I could do, try and rma and go on.. I would suggest the steps that MilkyWay has said.. But, if you really don't know much about Bios's... I wouldn't play with Irq's... That can mess up everything on your board. USB, ethernet, ram, chip... But, that's just me on playing with irq's... To much of a hassle IMHO..

 

Overclocking / Undervolting guide for Vega 56 or 64?

Here's a quick laundry list:

List of software to use for overclocking and testing
Examples:
Wattman (and how to find and use it, like an overview, including profiles)
Unigine Valley or Heaven (use this for quick testing while changing settings in Wattman and checking for stability / artifacts) ...just suggesting this
How to monitor cores / mem speeds and temps during testing (I've seen screen overlays, and others using GPUz)

Step-by step overclocking in Wattman
Fan speeds
Power limit
Temp limit
Voltages
Core speeds
Memory speeds

 

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.