BSOD's still after replacing RAM.

[Cavi]

Hi guys! I have a problem... again...

Back in December I started this thread: 

As you can see, after my PC woke up from sleep mode one day, I kept getting memory related BSOD's. People here and on other multple forums said that it was most probably RAM, which was my original thought as well. I decided to replace my RAM in the store I bought it from. It took a while because of the holidays and also I'm busy so I didn't have much time to get to it, but when I finally received my new set of G.SKILL Ripjaws RAM and installed Windows 10 again just to have a fresh install... I realized nothings changed. When Windows installed without problems I immediatelly thought it was going to be ok, but when installation was completed and it was time for the first configuration of Win 10... I received a BSOD again. I don't remember which one was it, but most likely PFN_LIST_CORRUPT. I was shaking. It was so bad that It took me some time (I know I'm an idiot for not approaching the problem immediatelly) to even try and do something about it, but I won't wait anymore. I need your advice. I think every detail is in my old thread, but feel free to ask me anything. I just want to enjoy my new PC again as for now I'm stuck with my old (REALLY OLD) E2200 GT220 PC and I can't handle it anymore. Is it likely that some files on my SSD are still corrupted? (I still have original recovery partitions in Windows installer, I haven't touched them, however I installed a fresh Win 10 on the "main" part of the drive) Is it the fault of RAM slots? Or am I so unlucky that I got bad RAM... twice? Any help will be appreciated as I'm so scared and don't know what to do. 

 

[kelvinhall05]

Have you tried doing the simplest thing, which is just Googling the error message?

[Cavi]

1 minute ago, kelvinhall05 said:

Have you tried doing the simplest thing, which is just Googling the error message?

Yes, I believe I did back when my problem originally showed up. From what I've read and been told, it all pointed out to a problem with memory. PFN_LIST_CORRUPT and MEMORY_MANAGEMENT were 2 BSOD's I've seen countless times trying to boot up my PC. 

[Mooshi]

Any in page errors related bsods? 

[Cavi]

2 minutes ago, Mooshi said:

Any in page errors related bsods? 

Sorry but could you expand a little on that? I'm not really knowledgeable when it comes to errors and BSOD's. 

[Mooshi]

2 minutes ago, Cavi said:

Sorry but could you expand a little on that? I'm not really knowledgeable when it comes to errors and BSOD's. 

It was an error my Gfs pc was getting before resulting in BSODs. That particular one could be either ram or storage and replacing the ssd resolved that. Was curious if you may have also had a BSOD that mentioned in page error. 

[Cavi]

1 minute ago, Mooshi said:

It was an error my Gfs pc was getting before resulting in BSODs. That particular one could be either ram or storage and replacing the ssd resolved that. Wad curious if you may have also had a BSOD that mentioned in page error. 

Actually, there might've been an error like that, but I'm not entirely sure. However I'll try to see if it will run on another drive when I have time (It's 00:40 PM for me right now so I'll be going to sleep soon). Did that error come up on bootup for you? Because in my case when Windows tries to boot up I imediatelly see a BSOD, but in BIOS it's stable. 

[Cavi]

I'll try to mess with the drive soon, maybe it's the cause, but I'm not sure about that. Even if that error popped up on my BSOD's, it was 1%, because 99% of these BSOD's were MEMORY_MANAGEMENT and PFN_LIST_CORRUPT. 

also, refreshing thread. 

[Cavi]

Hello. Sorry for multiposting again... but I wanted to report on something that might be a clue or something for a person more experienced than me that could help me. I had some limited time at home when I could try to do some stuff. I decided to stick my Windows 10 USB into the PC again and try to install it once more. I wiped the SSD, and installed Windows. No problems during the install (before replacing ram it would freeze etc even at install stage). But when I got to the first bootup to configure windows, my heart was beating like crazy. It went for a little longer than usual. Before it would BSOD me as fast as the spinning loading wheel appeared, but now it actually went for a few seconds longer, I even saw some percentage of first configuration before I've experienced a BSOD, but this time it was unlike any other I've seen before replacing my RAM. SYSTEM_SERVICE_EXCEPTION (I think, I'm writing it from memory). was the messeage on the BSOD, I've never seen it before replacing my RAM, at least I do not recall it appearing. I will try to google it's meaning, but I've found microsoft sites to describe these errors in a pretty cryptic way (English is not my first language), so your help would be appreciated as well. I want to thank everyone who contributed so far, @Mooshi made me check my drives and I'm thankful. I thought it was unlikely, but maybe that's it. The problem is not fully solved though, and I do not know what to do next, so I would be very happy if someone could look into it. I can provide any info you need. 

[stconquest]

18 minutes ago, Cavi said:

Hello. Sorry for multiposting again... but I wanted to report on something that might be a clue or something for a person more experienced than me that could help me. I had some limited time at home when I could try to do some stuff. I decided to stick my Windows 10 USB into the PC again and try to install it once more. I wiped the SSD, and installed Windows. No problems during the install (before replacing ram it would freeze etc even at install stage). But when I got to the first bootup to configure windows, my heart was beating like crazy. It went for a little longer than usual. Before it would BSOD me as fast as the spinning loading wheel appeared, but now it actually went for a few seconds longer, I even saw some percentage of first configuration before I've experienced a BSOD, but this time it was unlike any other I've seen before replacing my RAM. SYSTEM_SERVICE_EXCEPTION (I think, I'm writing it from memory). was the messeage on the BSOD, I've never seen it before replacing my RAM, at least I do not recall it appearing. I will try to google it's meaning, but I've found microsoft sites to describe these errors in a pretty cryptic way (English is not my first language), so your help would be appreciated as well. I want to thank everyone who contributed so far, @Mooshi made me check my drives and I'm thankful. I thought it was unlikely, but maybe that's it. The problem is not fully solved though, and I do not know what to do next, so I would be very happy if someone could look into it. I can provide any info you need. 

Have you tried running the PC with a single stick of RAM... in each of the DIMM slots... one by one, moving to different slots?

[Cavi]

25 minutes ago, stconquest said:

Have you tried running the PC with a single stick of RAM... in each of the DIMM slots... one by one, moving to different slots?

I believe I've tried that before replacing my RAM, but not with the new sticks. Thanks, I'll give it a try! I was so in shock when it didn't work with the new RAM that I didn't think of the simplest solutions, sorry for my stupidity. Slot 1 is covered up by my be quiet! cooler, but 2/3/4 are OK so I'll check that. 

[stconquest]

5 minutes ago, Cavi said:

I believe I've tried that before replacing my RAM, but not with the new sticks. Thanks, I'll give it a try! I was so in shock when it didn't work with the new RAM that I didn't think of the simplest solutions, sorry for my stupidity. Slot 1 is covered up by my be quiet! cooler, but 2/3/4 are OK so I'll check that. 

Just one stick at a time though.

 

Have you tried removing everything that is not needed, the GPU or a storage drive/etc... and run the PC with the bare minimum components.

[Mooshi]

BSOD's are so dreadful when it could be anythiiiing.  Ram, storage or the mobo itself could all be culrpits. I wish you much luck! 

[Cavi]

21 hours ago, stconquest said:

Just one stick at a time though.

 

Have you tried removing everything that is not needed, the GPU or a storage drive/etc... and run the PC with the bare minimum components.

I have not tried this. Thanks for the idea. I will try to do what you recommended me to do yesterday with the RAM and also with running the PC with minimum components now and I will report back later.

 

@Mooshi Thank you! 

[Cavi]

21 hours ago, stconquest said:

Just one stick at a time though.

 

Have you tried removing everything that is not needed, the GPU or a storage drive/etc... and run the PC with the bare minimum components.

Report #1

Normally I have a standard slot2/slot4 setup with my RAM. I took slot4 out leaving only slot2 and tried to reinstall windows again. This time it didn't even complete the instalation, it crashed during the process with a "PAGE FOUND IN NON PAGED AREA" BSOD (from my memory, messeage may look a little different actually). It never happened a few times I've tried reinstalling  after getting new RAM. Should I be concerned about my board/slots? Needs more testing in different slots that I'll do, but just wanted to share that first report. 

[stconquest]

16 minutes ago, Cavi said:

Report #1

Normally I have a standard slot2/slot4 setup with my RAM. I took slot4 out leaving only slot2 and tried to reinstall windows again. This time it didn't even complete the instalation, it crashed during the process with a "PAGE FOUND IN NON PAGED AREA" BSOD (from my memory, messeage may look a little different actually). It never happened a few times I've tried reinstalling  after getting new RAM. Should I be concerned about my board/slots? Needs more testing in different slots that I'll do, but just wanted to share that first report. 

I am concerned that it might be the motherboard, yes.  That is a big problem if it is the mobo.  Keep testing different slots.

[JoostinOnline]

Download the free edition of Passmark's MemTest86 (the original and memtest86+ are very out of date) and run it overnight.  Check if there were any errors in the morning.

[Cavi]

2 hours ago, stconquest said:

I am concerned that it might be the motherboard, yes.  That is a big problem if it is the mobo.  Keep testing different slots.

I will test them and report tomorrow (almost 1AM for me right now). The good thing in the sea of all the problem is the fact that I still have warranty for everything. RAM was actually replaced with the help of warranty. 

1 hour ago, JoostinOnline said:

Download the free edition of Passmark's MemTest86 (the original and memtest86+ are very out of date) and run it overnight.  Check if there were any errors in the morning.

I remember doing it before I had my RAM replaced. I had like a few hundred thousand errors and it froze on test 7 (I stated that in the original thread I linked, I believe). Haven't tried running it with the new memory for some reason. I was scared and shocked and didn't think of the most important things. I will try to run it and see. 

[Cavi]

On 13.02.2017 at 10:24 PM, stconquest said:

I am concerned that it might be the motherboard, yes.  That is a big problem if it is the mobo.  Keep testing different slots.

Sorry for lack of updates past few days. Like I said before, I'm really busy at times, and I don't even get to go into my room and see my PC some days. Anyway, I tried using different slots for RAM. I had time to try and put the RAM (one stick) into a slot that wasn't used at the moment my PC broke. Slot 3. I put the stick in, pop my Windows USB... And nothing. Another MEMORY_MANAGEMENT error before windows even installed. Tomorrow I will be able to take my PC to some sort of a specialist in the nearest town so he can test it more than I do. I'm really angry at myself that I don't have enough time to solve my big problem. They should be able to locate the problem and I will be then able to return that certain part using warranty and get it replaced. Thanks for every advice so far, I'm really thankful. If someone wants to add anything, I'll be glad to read your advices. 

[TetraSky]

At the point you are at, seeing a PC specialist does indeed sound like the only solution. Don't do the same mistake I did before and just buy hardware after hardware trying to fix an issue that simply doesn't want to be fixed no matter what...

 

There's a chance the new RAM was also faulty, but I'm gonna go and guess it's either the memory controller of the CPU itself or the motherboard whose ram slots are all dead for some reason.

Is it possible that you have an extra standoff in the back of the motherboard that caused a short?

[Cavi]

2 hours ago, TetraSky said:

At the point you are at, seeing a PC specialist does indeed sound like the only solution. Don't do the same mistake I did before and just buy hardware after hardware trying to fix an issue that simply doesn't want to be fixed no matter what...

 

There's a chance the new RAM was also faulty, but I'm gonna go and guess it's either the memory controller of the CPU itself or the motherboard whose ram slots are all dead for some reason.

Is it possible that you have an extra standoff in the back of the motherboard that caused a short?

I also think that it might be a problem related to MOBO/CPU. And for the standoff - I don't think that's the case, I don't remember any standoffs that would not fit with my mobo. I'll see the manual to find out though, but it's unlikely.