Jump to content

My friend was complaining about Random BSODS, so after looking at the minidump in WinDBG, I noticed that Avira's Scanning Component was causing the system to sometimes crash.

Looking in the Event Log, I noticed an irregular pattern of crashes and decided that I would run the system file checker and run Memtest86 to be thorough.

I received the following errors after running memtest:

57aSqx7.jpg

 

I get the same errors using both the original DIMM and a known good DIMM in both slots on the motherboard.

More details can be provided if requested, but I am currently at work so if you would like the exact motherboard model, I will provide it some point later on today.

Thanks for any help provided!

Link to comment
https://linustechtips.com/topic/498791-memtest86-same-errors-different-dimms/
Share on other sites

Link to post
Share on other sites

I actually had problems with errors in memtest earlier this year as well. Problem with memtest is that errors in this test may be related to faulty RAM-slots, or faulty RAM or a faulty CPU. However I was unfortunately not able to find any info on how to distinguish the different errors and find out the right component. I would highly suggest testing the RAM on a different board and other RAM (tested and well working) on the initial board. Really this is the easiest way to go about it I would say.

Actually for me (which was a bummer) both the slots as well as the ram ended up being faulty.

PC: AMD Ryzen 7 7700 || Noctua NH-U12S SE2 || 32GB DDR5 6000 CL32  || 
|| Powercolor RX 9070 Reaper || Asus B650E-I
  || WD 850X 2TB ||  Corsair SF600 || Intertech IM 1 |||
Peripherals: Sennheiser PC  360 G4ME || AOC CQ27G2U || Viewsonic PX701HD || Keychron V1 || Logitech G303 Shroud Edition||| Laptop: XPS 13 2in1 7390 || Steam Deck 256 GB (64GB Version) ||| Cameras: Fujifilm XH-1 || Fujifilm X100T

 

 

Elite 110 build log (update:05/15/2018)

Link to post
Share on other sites

Could be the ram settings, it might not be picking up xmp correctly so disabling it and going down to the standard speed with default cas/ras/etc might resolve it for both sticks. If it doesn't then there is a decent chance the motherboard is suffering a weirs failure (of is never the CPU)

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×