Does this line in a log mean that I have a bad RAM sector or chip?
Clash 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?
logs ram
add a comment |Â
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?
logs ram
Have you tried running a RAM test?
– Stephen Rauch
Aug 7 at 1:50
@Crash Could you post output of the command:journalctl -k -bsomewhere 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
add a comment |Â
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?
logs ram
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
logs ram
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 -bsomewhere 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
add a comment |Â
Have you tried running a RAM test?
– Stephen Rauch
Aug 7 at 1:50
@Crash Could you post output of the command:journalctl -k -bsomewhere 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
add a comment |Â
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.
answered Aug 7 at 4:39
Bob
72017
add a comment |Â
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.
answered Aug 7 at 4:39
Bob
72017
add a comment |Â
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.
answered Aug 7 at 4:39
Bob
72017
add a comment |Â
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.
answered Aug 7 at 4:39
Bob
72017
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.
answered Aug 7 at 4:39
Bob
72017
edited Aug 7 at 4:53
answered Aug 7 at 4:39
Bob
72017
answered Aug 7 at 4:39
Bob
72017
answered Aug 7 at 4:39
Bob
72017
72017
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Have you tried running a RAM test?
– Stephen Rauch
Aug 7 at 1:50
@Crash Could you post output of the command:
journalctl -k -bsomewhere 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