RAM broke? :: Help and Tips

All Discussions > Steam Forums > Help and Tips > Topic Details

This topic has been locked

Kanye Quest Nov 20, 2018 @ 9:10am

RAM broke?

Hello guys,

I overclocked my ryzen 3 2200g and became a bluescreen after 30mins.
I reset my bios so my ryzen isnt overclocked anymore...
The problem: The bluescreen isnt gone...

I dont know if my RAM is broken or something else, because in memTest86 it shows 1 Error by testing it... I tried to use only 1 of the 2 sticks but both dont work...

I get an bluescreen every 30-120mins or when I start csgo...

It says: win32kfull.sys or win32kbase.sys

ty for help

< >

Showing 1-13 of 13 comments

Cathulhu Nov 20, 2018 @ 9:17am

https://steamcommunity.com/discussions/forum/1/3374780959395943174/
https://steamcommunity.com/discussions/forum/1/3374780959395879426/
https://steamcommunity.com/discussions/forum/11/3374780959389264210/

This is now your fourth thread about this topic. What was wrong with the first three?

Kanye Quest Nov 20, 2018 @ 9:18am

Originally posted by Cathulhu:
https://steamcommunity.com/discussions/forum/1/3374780959395943174/
https://steamcommunity.com/discussions/forum/1/3374780959395879426/
https://steamcommunity.com/discussions/forum/11/3374780959389264210/

This is now your fourth thread about this topic. What was wrong with the first three?

I dont, I have multiple problems with my PC :C
And I cant fix them

JPMcMillen Nov 20, 2018 @ 9:20am

Have you tried running MemTest86 to test each stick by itself? I had a problem a year or so ago, and MemTest86 showed errors no matter which stick of ram I was testing. The only thing I could do was use the stick that showed the error towards the end of the test, and buy new ram. Didn't try playing anything till the replacements came in.

Kanye Quest Nov 20, 2018 @ 9:34am

Originally posted by JPMcMillen:
Have you tried running MemTest86 to test each stick by itself? I had a problem a year or so ago, and MemTest86 showed errors no matter which stick of ram I was testing. The only thing I could do was use the stick that showed the error towards the end of the test, and buy new ram. Didn't try playing anything till the replacements came in.

I just dont know if my ram or something else is broke... I overclocked my CPU but how does the Ram get damaged by it?

Kanye Quest Nov 20, 2018 @ 9:57am

Originally posted by JPMcMillen:
Have you tried running MemTest86 to test each stick by itself? I had a problem a year or so ago, and MemTest86 showed errors no matter which stick of ram I was testing. The only thing I could do was use the stick that showed the error towards the end of the test, and buy new ram. Didn't try playing anything till the replacements came in.

Was also after oc?

JPMcMillen Nov 20, 2018 @ 10:03am

Originally posted by wet like rain♛:
Originally posted by JPMcMillen:
Have you tried running MemTest86 to test each stick by itself? I had a problem a year or so ago, and MemTest86 showed errors no matter which stick of ram I was testing. The only thing I could do was use the stick that showed the error towards the end of the test, and buy new ram. Didn't try playing anything till the replacements came in.
I just dont know if my ram or something else is broke... I overclocked my CPU but how does the Ram get damaged by it?

There's no telling. But if you are constantly getting a BSOD, you have to assume anything could be the problem and eliminate things one at a time by thoroughly testing them.

If you can run the full battery of MemTest86 tests on a single stick and there are no errors, than that stick should be good. If there is an error, note all details, shut the machine off and do it again. If you get an error in the exact same spot, odds are something caused a problem with the ram. All it takes is one bad byte in a commonly used memory location to cause the system to keep crashing. I know one of those tests takes a long time, but that's the one that kept giving me the exact same error whenever I would test a particular stick of ram.

Kanye Quest Nov 20, 2018 @ 10:08am

Originally posted by JPMcMillen:
Originally posted by wet like rain♛:
I just dont know if my ram or something else is broke... I overclocked my CPU but how does the Ram get damaged by it?
There's no telling. But if you are constantly getting a BSOD, you have to assume anything could be the problem and eliminate things one at a time by thoroughly testing them.

If you can run the full battery of MemTest86 tests on a single stick and there are no errors, than that stick should be good. If there is an error, note all details, shut the machine off and do it again. If you get an error in the exact same spot, odds are something caused a problem with the ram. All it takes is one bad byte in a commonly used memory location to cause the system to keep crashing. I know one of those tests takes a long time, but that's the one that kept giving me the exact same error whenever I would test a particular stick of ram.

I have done the test 2 times with both sticks in it... The first time it had no errors, but the second time had 1 error... In the 1st test Ive only done 1 pass in the second test i have 1,5pass...

JPMcMillen Nov 20, 2018 @ 10:19am

Originally posted by wet like rain♛:
Originally posted by JPMcMillen:
There's no telling. But if you are constantly getting a BSOD, you have to assume anything could be the problem and eliminate things one at a time by thoroughly testing them.

If you can run the full battery of MemTest86 tests on a single stick and there are no errors, than that stick should be good. If there is an error, note all details, shut the machine off and do it again. If you get an error in the exact same spot, odds are something caused a problem with the ram. All it takes is one bad byte in a commonly used memory location to cause the system to keep crashing. I know one of those tests takes a long time, but that's the one that kept giving me the exact same error whenever I would test a particular stick of ram.
I have done the test 2 times with both sticks in it... The first time it had no errors, but the second time had 1 error... In the 1st test Ive only done 1 pass in the second test i have 1,5pass...

I'm pretty sure it's MemTest86 test #7 that was consistantly finding errors in the RAM that I had. That test puts the RAM through an exhaustive workout and is really good at finding really subtle errors, but the test takes a really long time.

Kanye Quest Nov 20, 2018 @ 10:24am

Originally posted by JPMcMillen:
Originally posted by wet like rain♛:
I have done the test 2 times with both sticks in it... The first time it had no errors, but the second time had 1 error... In the 1st test Ive only done 1 pass in the second test i have 1,5pass...

I'm pretty sure it's MemTest86 test #7 that was consistantly finding errors in the RAM that I had. That test puts the RAM through an exhaustive workout and is really good at finding really subtle errors, but the test takes a really long time.

So Im pretty sure that my RAM is broke, did u do the test via usb or how? Im gonna do that now

Kanye Quest Nov 20, 2018 @ 10:25am

Originally posted by JPMcMillen:
Originally posted by wet like rain♛:
I have done the test 2 times with both sticks in it... The first time it had no errors, but the second time had 1 error... In the 1st test Ive only done 1 pass in the second test i have 1,5pass...

I'm pretty sure it's MemTest86 test #7 that was consistantly finding errors in the RAM that I had. That test puts the RAM through an exhaustive workout and is really good at finding really subtle errors, but the test takes a really long time.

Ive done memTest86 7,5 is it the same?

#10

JPMcMillen Nov 20, 2018 @ 10:35am

Originally posted by wet like rain♛:
Originally posted by JPMcMillen:

I'm pretty sure it's MemTest86 test #7 that was consistantly finding errors in the RAM that I had. That test puts the RAM through an exhaustive workout and is really good at finding really subtle errors, but the test takes a really long time.
Ive done memTest86 7,5 is it the same?

Each test runs different routines of reads and writes. Test 7 essentially tests each 32 bit address 32 times. That's why it takes so long.

As for how to run the test, I followed the instructions to create a bootable USB and booted from that to run the tests.

#11