Announcement

Collapse
No announcement yet.

BSOD from "bad" memory?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • BSOD from "bad" memory?

    Hi there,

    When using one set of RAM sticks in my Ryzen 5 3600 build with an ASRock B550 PRO4 mother board, things are working fine. However when I switch to identical set of RAM from the same manufacturer into the same system, I get periodic BSOD with the failer reason of "MEMORY_MANAGEMENT" or "IRQ_NOT_LESS_THAN". If I switch back to the "good" sticks then it is fine and I can't reproduce the BSOD, and when I again switch back to the bad sticks and the problems occur. I am using DDR4 4GB sticks x2 for 8GB total.

    I'm running 8.4 of MemTest Free and letting it run with all the default tests (11?) and 4 passes and it finds no errors. However from my BSOD per the above, it seems clear that something is wrong with one set of RAM sticks. Would you agree?

    I have several pairs of this RAM from. Some pairs do not have the problem but most due. For instance out of a pack of 20 pairs, most pairs are having this issue. I think this is too many errors to suggest that the RAM sticks are bad, unless there was a bad batch. But then again, MemTest is not picking up any errors after all 4 tests so I'm not sure what to make of this.

    So one question is whether it is possible to have some issue with these bad pairs of RAM sticks even tho MemTest 86 doesn't detect any issues (100% pass on all 4 passes). And also if you have any ideas of how to solve it in general or how to collect more troubleshooting data? I'd appreciate any suggestions you guys may. Thanks so much in advance!

  • #2

    [Crash dump from from EMail]

    Crash dump 020621-7250-01.dmp occurred in the code amdppm.sys
    inside a function called PerfReadWrappingCounter

    This other person had a similar sounding problem and it wasn't RAM in the end.
    https://www.tenforums.com/bsod-crash...h-install.html

    Another another on here
    https://www.tenforums.com/bsod-crash...om-bsod-6.html
    Which also wasn't a RAM fault.

    The 2nd crash dump happened in nt.dll in the function MiInsertPageInList.
    Which is similar to this problem.
    https://answers.microsoft.com/en-us/...fdbe0df?page=1
    Which also wasn't a RAM fault.

    While MemTest86 should you you a high degree of confidence, it doesn't pick up all faults. So none of this is conclusive.
    Do the "faulty" sticks continue to come up as faulty in another motherboard with another CPU?

    Comment

    Working...
    X