Ram

It's not a big deal r-right?

Attached: 20190122_230402.jpg (3264x1836, 1.33M)

I don't think a single bit being wrong some of the time is acceptable since you have no idea what that bank is going to be responsible for.

It's just a single bit what can it do

Replace the hardware.
You could flag the range as dead using whatever convention your OS uses, but if something is faulty I wouldn't trust it.

My old socket 754 mobo would do this when I plugged two ram sticks in.
Turns out my new socket 754 mobo did the same too, so I who knows what the fuck was going on.

Did you consider it's probably the ram and not the board? Or even the slots.

Bought new ram and it did the same, so it wasn't that either.

dude, your ram is fucked
return that shit

>run memtest
>reports 20% of my ram is borked
>run a memory test in windows
>everything fine here, goy!
Who the fuck do I trust?

nvm i figured it out

>>run a memory test in windows
Memtest. Windows' memory test is garbage

This is why your bios has a memory tester written into it. You can trust that

CPU with bad memory controller?

>2,246 errors
>t=0:06:44

I doubt it, I tried both my athlon 64 3100+ and an athlon 64 3200+ on it, still the same problem

If you get even one red line you throw out the RAM.

Forgot to mention, so if it's some weird crap like this, try running a single and testing the different sticks slot to see if it works and changing up slots.

Pull the RAM out and test them one at a time. Make sure they are seated properly.

Try microwaving the RAM

it's fucking dead

>>has a quad core cpu
"Do i have enough ram??"
>>Goes to mommy for crucial ballistix 64gb
Shitposts on Jow Forums without reading the sticky