Does this line in a log mean that I have a bad RAM sector or chip?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
-1
down vote

favorite












Aug 4 15:11:09 LiquidNZXT kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -16M


Does this line in a log mean I have a bad RAM sector or chip?










share|improve this question





















  • Have you tried running a RAM test?
    – Stephen Rauch
    Aug 7 at 1:50










  • @Crash Could you post output of the command: journalctl -k -b somewhere at pastebin.ubuntu.com
    – Bob
    Aug 7 at 3:35






  • 1




    Please calm down; I cleared all the comments that don't have anything to do with the actual question. I don't know where you got the impression that you can't answer comments like "have you tried running a RAM test", but you can and it'd be a good start to diagnosing the problem
    – Michael Mrozek♦
    Aug 7 at 5:00














up vote
-1
down vote

favorite












Aug 4 15:11:09 LiquidNZXT kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -16M


Does this line in a log mean I have a bad RAM sector or chip?










share|improve this question





















  • Have you tried running a RAM test?
    – Stephen Rauch
    Aug 7 at 1:50










  • @Crash Could you post output of the command: journalctl -k -b somewhere at pastebin.ubuntu.com
    – Bob
    Aug 7 at 3:35






  • 1




    Please calm down; I cleared all the comments that don't have anything to do with the actual question. I don't know where you got the impression that you can't answer comments like "have you tried running a RAM test", but you can and it'd be a good start to diagnosing the problem
    – Michael Mrozek♦
    Aug 7 at 5:00












up vote
-1
down vote

favorite









up vote
-1
down vote

favorite











Aug 4 15:11:09 LiquidNZXT kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -16M


Does this line in a log mean I have a bad RAM sector or chip?










share|improve this question













Aug 4 15:11:09 LiquidNZXT kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -16M


Does this line in a log mean I have a bad RAM sector or chip?







logs ram






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 7 at 1:49







user289380


















  • Have you tried running a RAM test?
    – Stephen Rauch
    Aug 7 at 1:50










  • @Crash Could you post output of the command: journalctl -k -b somewhere at pastebin.ubuntu.com
    – Bob
    Aug 7 at 3:35






  • 1




    Please calm down; I cleared all the comments that don't have anything to do with the actual question. I don't know where you got the impression that you can't answer comments like "have you tried running a RAM test", but you can and it'd be a good start to diagnosing the problem
    – Michael Mrozek♦
    Aug 7 at 5:00
















  • Have you tried running a RAM test?
    – Stephen Rauch
    Aug 7 at 1:50










  • @Crash Could you post output of the command: journalctl -k -b somewhere at pastebin.ubuntu.com
    – Bob
    Aug 7 at 3:35






  • 1




    Please calm down; I cleared all the comments that don't have anything to do with the actual question. I don't know where you got the impression that you can't answer comments like "have you tried running a RAM test", but you can and it'd be a good start to diagnosing the problem
    – Michael Mrozek♦
    Aug 7 at 5:00















Have you tried running a RAM test?
– Stephen Rauch
Aug 7 at 1:50




Have you tried running a RAM test?
– Stephen Rauch
Aug 7 at 1:50












@Crash Could you post output of the command: journalctl -k -b somewhere at pastebin.ubuntu.com
– Bob
Aug 7 at 3:35




@Crash Could you post output of the command: journalctl -k -b somewhere at pastebin.ubuntu.com
– Bob
Aug 7 at 3:35




1




1




Please calm down; I cleared all the comments that don't have anything to do with the actual question. I don't know where you got the impression that you can't answer comments like "have you tried running a RAM test", but you can and it'd be a good start to diagnosing the problem
– Michael Mrozek♦
Aug 7 at 5:00




Please calm down; I cleared all the comments that don't have anything to do with the actual question. I don't know where you got the impression that you can't answer comments like "have you tried running a RAM test", but you can and it'd be a good start to diagnosing the problem
– Michael Mrozek♦
Aug 7 at 5:00










1 Answer
1






active

oldest

votes

















up vote
2
down vote













Six years ago I had similar problem with my Fedora server. The kernel messages:



*BAD*gran_size...


can have three basic reasons:



  • corrupted physical memory

  • corrupted BIOS

  • wrong MTRR size

I have solved the problem by enabling MTRR sanitizer, read my post (I'm melal on Fedora forum) and another post below it.



Additionally read this, to understand what the messages *BAD*gran_size... mean.






share|improve this answer






















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f460934%2fdoes-this-line-in-a-log-mean-that-i-have-a-bad-ram-sector-or-chip%23new-answer', 'question_page');

    );

    Post as a guest





























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    Six years ago I had similar problem with my Fedora server. The kernel messages:



    *BAD*gran_size...


    can have three basic reasons:



    • corrupted physical memory

    • corrupted BIOS

    • wrong MTRR size

    I have solved the problem by enabling MTRR sanitizer, read my post (I'm melal on Fedora forum) and another post below it.



    Additionally read this, to understand what the messages *BAD*gran_size... mean.






    share|improve this answer


























      up vote
      2
      down vote













      Six years ago I had similar problem with my Fedora server. The kernel messages:



      *BAD*gran_size...


      can have three basic reasons:



      • corrupted physical memory

      • corrupted BIOS

      • wrong MTRR size

      I have solved the problem by enabling MTRR sanitizer, read my post (I'm melal on Fedora forum) and another post below it.



      Additionally read this, to understand what the messages *BAD*gran_size... mean.






      share|improve this answer
























        up vote
        2
        down vote










        up vote
        2
        down vote









        Six years ago I had similar problem with my Fedora server. The kernel messages:



        *BAD*gran_size...


        can have three basic reasons:



        • corrupted physical memory

        • corrupted BIOS

        • wrong MTRR size

        I have solved the problem by enabling MTRR sanitizer, read my post (I'm melal on Fedora forum) and another post below it.



        Additionally read this, to understand what the messages *BAD*gran_size... mean.






        share|improve this answer














        Six years ago I had similar problem with my Fedora server. The kernel messages:



        *BAD*gran_size...


        can have three basic reasons:



        • corrupted physical memory

        • corrupted BIOS

        • wrong MTRR size

        I have solved the problem by enabling MTRR sanitizer, read my post (I'm melal on Fedora forum) and another post below it.



        Additionally read this, to understand what the messages *BAD*gran_size... mean.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Aug 7 at 4:53

























        answered Aug 7 at 4:39









        Bob

        72017




        72017



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f460934%2fdoes-this-line-in-a-log-mean-that-i-have-a-bad-ram-sector-or-chip%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?