The Mysterious Case of Code 55: A Troubleshooting Journey

I've been dealing with an intermittent issue that's left me scratching my head, and I'm hoping that by sharing my experience, I can provide some valuable insights to you, dear reader. It started when I noticed that my system was crashing repeatedly, often at the most inopportune moments. At first, I suspected a driver issue or a problem with the graphics card, but after conducting a series of tests, I realized that it was something more complex.

The issue seemed to be memory-related, as indicated by Code 55, which appeared on my screen whenever the problem occurred. I tried reseeding my RAM, thinking that might resolve the issue, but unfortunately, it didn't. I also checked the BIOS settings and ensured that all cables were securely connected. Still, the problem persisted. As a last resort, I decided to power cycle my system, which often helps in resolving issues related to faulty components or overheating.

After some tinkering, I loosened up my CPU cooler, making sure it wasn't too tight, as that can sometimes cause problems with the motherboard's pins. To my surprise, this simple change resolved the issue entirely. It was as if I had " rebooted" my system, and everything worked fine once again. But why? What could have caused such a seemingly unrelated problem to resolve so quickly?

I decided to investigate further by running a Cinebench test, which is known for its reliability in stress-testing computer hardware. To my delight, the system passed with flying colors, indicating that it was indeed not a memory issue or a hardware failure. However, I couldn't shake off the feeling that there might be something more complex at play.

As I dug deeper, I discovered that Intel's 12th Gen processors are designed with larger substrates than their predecessors. This design change can sometimes lead to issues related to component stress and heat dissipation. Moreover, the retention system of these newer processors is designed to prevent the CPU from lifting off the socket pins, which can cause problems like Code 55.

One particular instance where my system locked up during shutdown caught my attention. It was an unexpected behavior that made me wonder if it might be related to a driver issue or some sort of software conflict. However, after further investigation, I realized that this wasn't the case either. It seemed that there must have been something more fundamental at play.

I tried to recreate the conditions under which Code 55 appeared, but unfortunately, the postcode error didn't manifest again during my testing. This lack of recurrence made it difficult for me to pinpoint the exact cause of the issue. However, I did discover that sometimes, the simplest solutions can resolve complex problems.

In this case, loosening up my CPU cooler and re-tightening it in a specific way seemed to have resolved the issue entirely. It was almost as if I had "reset" my system's behavior, allowing me to start fresh with a clean slate. While this solution might seem obvious now, it took some trial and error to figure out that adjusting the tension on my cooler could make such a significant difference.

As I reflect on this experience, I'm reminded of the importance of basic troubleshooting techniques. Sometimes, all it takes is a fresh perspective or a new approach to resolve seemingly intractable issues. By sharing my journey with you, dear reader, I hope that I can inspire others to think creatively and outside the box when faced with similar problems.

So, if you're watching this video right now and you're struggling with an unstable computer system, I would encourage you to consider the following: double-check your RAM installation, ensure that your cooler is properly secured, and don't be afraid to try something unconventional. You never know what might work until you try it!

"WEBVTTKind: captionsLanguage: eni showed you guys in a recent video how i was you reusing the old uh intermax licktech 240 lik tech insert your own joke there there's plenty um i experienced something that i think might shed some light on some things for a lot of people when it comes to really odd errors and crashes and things so today we're going to show you guys i guess just how picky hardware can be we interrupt this video to bring you a special message from ifixit no we interrupt this interruption with this interruption about new stuff from my fitness pushing graphics card but inventory sucks fix the inventory problems with ifixit whoa don't drop it can't fix that without fixing just kidding yes you can wish you could take ifixit with you anywhere but your pockets aren't big enough introducing you more and then the new nino take them with you anywhere so can i fix it for your loved ones or just get them for yourself i interrupt this video to give you a very important message construction is fully underway out here but in the haste of getting our last video done so they can get in here and get started i forgot to give you guys a code and trust me about 50 000 of you have let me know that so i'm giving you two codes today the first code is nvidia is overpriced n v i d i a not i n people like to spell nvidia wrong n v i d i a i s o v e r p r i c d video is overpriced and if you need help spelling that i'm sorry uh the other one is jay's clickbait j-a-y-z c-l-i-c-k-b-a-i-t may now get you back to our regularly scheduled program before this mess started but you won't believe number five oh you won't believe next week's wait tomorrow the next video's code uh the intermax look tech 240 came out in i'm curious now what does the printing of the manual say because i can't remember exactly here i had a two year warranty so i think we're out of 2013. so i said it i said in that previous video that when i got it it was a couple years old like in terms of being around at that time and i got it in 2016 so clearly it already been out three years 2013 nine years old first of all this spoiler if you haven't seen that last video it cools our 10900k fantastically this sublamination didn't even happen in this setup best aio in my peer in my opinion that was ever made i don't know if they made a 360 version of it i wish i had one the 240 is able to core 100k overclocked 502 gigahertz at 1.45 volts no problem whatsoever but again as i said installing it led to some challenges so with the hardware and stuff that it comes with you know it comes with brackets and stuff for amd's am3 plus which would still work on a lot of am4 boards because they have the holes and provisions for am3 and am4 it's got the 2011 hold down stuff and then it has the hardware that's on there now which was designed for the 11 xx sockets well you know you had 11 11 50 yeah 1150 1151 1200 now we're at lga 1700. yeah 1156 i think there was uh there's there's tons there's even a socket 13 something i think i can't recall anyway it doesn't matter the point is intel every single generation like to revise the socket slightly all the way from lga 775 up until now the perimeter hole distances have stayed within a few millimeters of each other and most have brackets similar to this one that have a little sliding bob you see on the back you can see it slides in and out to expand the mounting bracket to fit with intel various intel mounts this one was listed as working all the way up to lga 2011 right i already said that amg amg amd right fm fm2 am2 am3 and then oh yeah amd am2 am2 plus am3 m2 plus fm1 fm2 fm2 plus um for intel oh lga 775 11 50 11 55 11 56 13 66 in 2011. so i was right but i said there was a 13. um no mention obviously of lga 1151 obviously 1151 1150 and 1155 are all in the same size there what this doesn't tell you is the newer sockets although they have the same basic size and perimeter the z-axis height is different amongst all of those so that's why this particular one if you look down inside here has a spring-loaded mechanism that way it's designed to always push pressure down and stop high enough so the spring is pushing it down that's proper for that era it's the same reason why if you have a modern lga 1700 12th gen intel even though the installation brackets look identical from the previous 11th gen and 10th gen cpu coolers the z-axis the z-axis on 1700 is taller so if you use the lower hardware and you go tightening it down you can put way too much socket pressure on the cpu and then you end up having a problem see this is something that amd thought of when it came to threadripper and it's the reason why they give you a torque uh clicking torque wrench with the cpu and give you a very specific order which to tighten things down if you don't use that socket or that socket wrench that torque wrench you can cause temporary or permanent damage of your cpu and or motherboard so what i experienced here and i'm just showing you this is working now with two sticks of ram and i don't know why iq turned off the ram stop lighting up but that doesn't matter it's working it's fine now if i go ahead and shut it down when i first did this video come on shut down it turned on everything was great everything's fine went took a dump 10 15 20 minutes of looking at instagram reels later i came back out and i noticed my system was locked up i completely locked up reset button did nothing i had to do the s the hard reset of holding down the power button when i powered it down and you notice i'm tightening this bracket now when i powered it back up i was getting a code 55. and code 55 is no memory detected and i thought that that was odd so now that i've tightened this down i want to see now if i can make that error come back again because what i believe happened here was because this has a slightly higher z-axis i keep saying access axis versus back then i believe that we are squeezing the socket tight and we are causing either pins to bridge and or pins to maybe lift off because of potential bending so let's see if we get a code 55 here it doesn't look like we're going to but it doesn't mean we're not going to either by letting it try and boot itself up and then see if it'll lock up in the system because what i was dealing with here this ram channel the one closest to the cpu if i took it out code 55 would no longer persist and i did the normal things clear cmos all that taking this ram stick out the code would would stop it would post and i'd be fine if i put that ram stick back in code 55 would uh would pop back up on the motherboard so that led me to think oh did i have a do you have a bad stick of ram did it somehow randomly go bad on me right now everything seems to be working of course because we're making a video that's fine memory no 32 gigs of ram it's all there thinking that the ram stick might have been bad i put the ram stick in the slot a because it's a two channel those four dimms four dim slots it's dual channel a and b i put it in slot a and it posted so i now know that that ram stick wasn't bad i put the other ram stick in the closest to the cpu slot same why'd the shutting down stop okay it's doing the thing yeah it's like weirdness right it's stuck like shutting okay perfect let me restart it now and see what happens so my point was when the cooler was tightened all the way down it's now my assumption that it is somehow causing a pin issue where the pins are now maybe one is touching maybe one is not touching here that maybe one is barely touching to where as temperature heats up in the cpu you start to have heat expansion just like anything else remember the pins lga pins or land grid array that are on the motherboard are those springy hooked looking pins and the cpu pushes down against those pins and it makes a contact right so if the cpu is in like a weird crazy angle and it's being pushed too hard the pin can also potentially touch a neighboring pin or not touch at all because it lifted up on one side and i started to say that one of the things that threadripper taught us about that was the fact that that's why they're very adamant about tightening down the socket which is a torx head in a very specific order so now i'm trying to see if i can't get this problem to come back again let's see if shutdown fails again but it got me thinking like i wonder how many people that will write me messages and go i get the weirdest randomness blue screens they're like i've changed my ram i've changed my drive i've changed everything but if they're just putting all back together with the same cooler that's maybe been repurposed and or isn't that time to shut down isn't using the right hardware and you're hulking it down are you causing yourself a problem so now i'm gonna like legitimately tighten this even more just to see if i can get the problem to persist if i were smart what i would have done is i would have stopped the video i was making and made the video about this while the error was happening just to uh be able to show you guys in real time what the code 55 was but i don't think it's going to happen right now because code 55 was popping up like nearly immediately but now it's working just fine of course it's like when your car is doing the noise you take it to the mechanic and the noise stops takes for a test drive can't figure out what's wrong he says well everything seems to be working you drive home nobody starts back you turn around go back to the mechanic and it stops right as you pull in again just like that but yeah what i ended up doing and how i ended up getting through the test uh for that previous video was i just loosened up the screws a little which to be honest too could potentially have hurt the cooling a little bit if i don't have the tension just right because the hardware is is is specked for the sockets that are specifically listed so this video is really more of a psa to let you know like if you're reusing hardware like an older thing that you've just gone through a few builds with and you're like oh hey look the brackets line up let's just use it you could very well absolutely be causing yourself a problem and look now we have no ram lighting again hey it worked look we have no mouse it's completely locked up okay now that this has happened which is basically reminiscent of what happened the last time i got nothing now reset nothing now it should come back up potentially with the code 55 error no it's posting but is it going to post in lock up again see do you understand why this could be extremely frustrating and difficult for somebody without a lot of experience with with hardware to try and figure out these types of problems when everything is working fine and then you you just can't explain why suddenly something stops working because look now it's working just fine so if i were and then the ram just turned off again in terms of the lighting oh there it goes look lock up so here's the thing if you were if you were new to computers where would you start you'd be like i don't know i don't know what's happening here would your first thought be to loosen up your aio probably not probably not you might think it's your cpu and you might swap it with another one and then you might take the cooler off put in the new cpu and then crank it back down with the force of hulk again yeah nothing so i am going to power cycle and i want to see if i can get that code 55 to come up because code55 like i said that was specifically to memory and the reason why it's giving a memory error at least it did that time see i i loosened it up and re-tightened it so it doesn't mean the same pins that were causing me a problem are going to cause a problem it could be different pins but at least the first time i did this the pins that were now it's going to do this check because it knows that it keeps crashing the pins that were causing a problem were memory related so it doesn't mean they're memory related this time does that make sense it's not always going to be and the order which i tighten them down is going to torque it in a different way so it might be completely different pins which is why i'm getting such random behavior one of the things that i had done is i left in the bios for a while to see if it would lock up there because i started thinking maybe the cooler pump was dead or something and was turning off and overheating that wasn't the case it also was not locking up in bios only in windows and that could have something to do with just the way windows accesses the memory i'm not sure but again this may not even be a memory issue on this one so this is the kind of stuff that can lead to craziness let me do a cinebench run right now i'm curious as to if we would even pass but the intermittentness that word intermittentness if it wasn't a word it is now the intermittentness is what leads to the mystery of trying to solve problems like this i want it to crash or give me a problem one more time so i can show you by loosening up my cooler they will all go away and this is a small cpu am i small i mean it's the small substrate before the 12th gen went to a much bigger one the bigger the substrate the more likelihood this can happen which is also why with the the retention system of 12th gen and the potential bending of the cpu causes the problem because then it starts lifting and not touching pins in areas where it's supposed to but you guys already saw we had a shutdown fail like a pause on shutdown it's like if someone were to tell me my system locked up when i tried to shut it down i would think you might have a driver issue something to do with like parking the driver um you know being an issue but that time it shut down just fine uh you saw we had a lock up in the middle of of our desktop interestingly enough that i cannot get a particular postcode problem which kind of even leads to the mystery of it all like if postcodes postcode 55 is what led me directly to go something's up with the memory swapping the memory out and going memory is fine let's try the cpu cooler and then that was my first thought because of my experience i knew like this cooler was not intended for this era this era obviously is years and years almost a decade newer than this so there had to be something with that it's all working at the moment but i haven't changed anything and obviously i wouldn't trust it so i can't show you guys the postcode error which i was really hoping to be able to do because it's not giving me an error again but i wanted to at least give you guys some food for thought that you know basic troubleshooting reseeding ram wouldn't have fixed the problem reseeding graphics card wouldn't have fixed the problem it really came down to cpu tension and all i did literally while i just did this loose loose loose loose and then this one wasn't that's all i did i did that still doesn't wiggle or anything it brought tension off the socket and everything worked fine so let me do another post code 55 had went away and then my both my ram 6 started working so you could see how you would inadvertently go oh man my ram is bad and you buy more ram and then you have the same problem or you go damn my cpu or my motherboard you might even think it's a bad motherboard channel or something would i like to have demonstrated that one a little bit more for you but i love to make these educational pieces where i can to give you guys some food for thought on your systems if so if you're watching this video right now and it piqued your interest because you went man i have a computer that's being super unstable i don't know what the problem is i would maybe not just give your ram a good receipt maybe double check your installation on your cooler to make sure you're not over tightened alright guys thanks for watching we'll see you in the next onei showed you guys in a recent video how i was you reusing the old uh intermax licktech 240 lik tech insert your own joke there there's plenty um i experienced something that i think might shed some light on some things for a lot of people when it comes to really odd errors and crashes and things so today we're going to show you guys i guess just how picky hardware can be we interrupt this video to bring you a special message from ifixit no we interrupt this interruption with this interruption about new stuff from my fitness pushing graphics card but inventory sucks fix the inventory problems with ifixit whoa don't drop it can't fix that without fixing just kidding yes you can wish you could take ifixit with you anywhere but your pockets aren't big enough introducing you more and then the new nino take them with you anywhere so can i fix it for your loved ones or just get them for yourself i interrupt this video to give you a very important message construction is fully underway out here but in the haste of getting our last video done so they can get in here and get started i forgot to give you guys a code and trust me about 50 000 of you have let me know that so i'm giving you two codes today the first code is nvidia is overpriced n v i d i a not i n people like to spell nvidia wrong n v i d i a i s o v e r p r i c d video is overpriced and if you need help spelling that i'm sorry uh the other one is jay's clickbait j-a-y-z c-l-i-c-k-b-a-i-t may now get you back to our regularly scheduled program before this mess started but you won't believe number five oh you won't believe next week's wait tomorrow the next video's code uh the intermax look tech 240 came out in i'm curious now what does the printing of the manual say because i can't remember exactly here i had a two year warranty so i think we're out of 2013. so i said it i said in that previous video that when i got it it was a couple years old like in terms of being around at that time and i got it in 2016 so clearly it already been out three years 2013 nine years old first of all this spoiler if you haven't seen that last video it cools our 10900k fantastically this sublamination didn't even happen in this setup best aio in my peer in my opinion that was ever made i don't know if they made a 360 version of it i wish i had one the 240 is able to core 100k overclocked 502 gigahertz at 1.45 volts no problem whatsoever but again as i said installing it led to some challenges so with the hardware and stuff that it comes with you know it comes with brackets and stuff for amd's am3 plus which would still work on a lot of am4 boards because they have the holes and provisions for am3 and am4 it's got the 2011 hold down stuff and then it has the hardware that's on there now which was designed for the 11 xx sockets well you know you had 11 11 50 yeah 1150 1151 1200 now we're at lga 1700. yeah 1156 i think there was uh there's there's tons there's even a socket 13 something i think i can't recall anyway it doesn't matter the point is intel every single generation like to revise the socket slightly all the way from lga 775 up until now the perimeter hole distances have stayed within a few millimeters of each other and most have brackets similar to this one that have a little sliding bob you see on the back you can see it slides in and out to expand the mounting bracket to fit with intel various intel mounts this one was listed as working all the way up to lga 2011 right i already said that amg amg amd right fm fm2 am2 am3 and then oh yeah amd am2 am2 plus am3 m2 plus fm1 fm2 fm2 plus um for intel oh lga 775 11 50 11 55 11 56 13 66 in 2011. so i was right but i said there was a 13. um no mention obviously of lga 1151 obviously 1151 1150 and 1155 are all in the same size there what this doesn't tell you is the newer sockets although they have the same basic size and perimeter the z-axis height is different amongst all of those so that's why this particular one if you look down inside here has a spring-loaded mechanism that way it's designed to always push pressure down and stop high enough so the spring is pushing it down that's proper for that era it's the same reason why if you have a modern lga 1700 12th gen intel even though the installation brackets look identical from the previous 11th gen and 10th gen cpu coolers the z-axis the z-axis on 1700 is taller so if you use the lower hardware and you go tightening it down you can put way too much socket pressure on the cpu and then you end up having a problem see this is something that amd thought of when it came to threadripper and it's the reason why they give you a torque uh clicking torque wrench with the cpu and give you a very specific order which to tighten things down if you don't use that socket or that socket wrench that torque wrench you can cause temporary or permanent damage of your cpu and or motherboard so what i experienced here and i'm just showing you this is working now with two sticks of ram and i don't know why iq turned off the ram stop lighting up but that doesn't matter it's working it's fine now if i go ahead and shut it down when i first did this video come on shut down it turned on everything was great everything's fine went took a dump 10 15 20 minutes of looking at instagram reels later i came back out and i noticed my system was locked up i completely locked up reset button did nothing i had to do the s the hard reset of holding down the power button when i powered it down and you notice i'm tightening this bracket now when i powered it back up i was getting a code 55. and code 55 is no memory detected and i thought that that was odd so now that i've tightened this down i want to see now if i can make that error come back again because what i believe happened here was because this has a slightly higher z-axis i keep saying access axis versus back then i believe that we are squeezing the socket tight and we are causing either pins to bridge and or pins to maybe lift off because of potential bending so let's see if we get a code 55 here it doesn't look like we're going to but it doesn't mean we're not going to either by letting it try and boot itself up and then see if it'll lock up in the system because what i was dealing with here this ram channel the one closest to the cpu if i took it out code 55 would no longer persist and i did the normal things clear cmos all that taking this ram stick out the code would would stop it would post and i'd be fine if i put that ram stick back in code 55 would uh would pop back up on the motherboard so that led me to think oh did i have a do you have a bad stick of ram did it somehow randomly go bad on me right now everything seems to be working of course because we're making a video that's fine memory no 32 gigs of ram it's all there thinking that the ram stick might have been bad i put the ram stick in the slot a because it's a two channel those four dimms four dim slots it's dual channel a and b i put it in slot a and it posted so i now know that that ram stick wasn't bad i put the other ram stick in the closest to the cpu slot same why'd the shutting down stop okay it's doing the thing yeah it's like weirdness right it's stuck like shutting okay perfect let me restart it now and see what happens so my point was when the cooler was tightened all the way down it's now my assumption that it is somehow causing a pin issue where the pins are now maybe one is touching maybe one is not touching here that maybe one is barely touching to where as temperature heats up in the cpu you start to have heat expansion just like anything else remember the pins lga pins or land grid array that are on the motherboard are those springy hooked looking pins and the cpu pushes down against those pins and it makes a contact right so if the cpu is in like a weird crazy angle and it's being pushed too hard the pin can also potentially touch a neighboring pin or not touch at all because it lifted up on one side and i started to say that one of the things that threadripper taught us about that was the fact that that's why they're very adamant about tightening down the socket which is a torx head in a very specific order so now i'm trying to see if i can't get this problem to come back again let's see if shutdown fails again but it got me thinking like i wonder how many people that will write me messages and go i get the weirdest randomness blue screens they're like i've changed my ram i've changed my drive i've changed everything but if they're just putting all back together with the same cooler that's maybe been repurposed and or isn't that time to shut down isn't using the right hardware and you're hulking it down are you causing yourself a problem so now i'm gonna like legitimately tighten this even more just to see if i can get the problem to persist if i were smart what i would have done is i would have stopped the video i was making and made the video about this while the error was happening just to uh be able to show you guys in real time what the code 55 was but i don't think it's going to happen right now because code 55 was popping up like nearly immediately but now it's working just fine of course it's like when your car is doing the noise you take it to the mechanic and the noise stops takes for a test drive can't figure out what's wrong he says well everything seems to be working you drive home nobody starts back you turn around go back to the mechanic and it stops right as you pull in again just like that but yeah what i ended up doing and how i ended up getting through the test uh for that previous video was i just loosened up the screws a little which to be honest too could potentially have hurt the cooling a little bit if i don't have the tension just right because the hardware is is is specked for the sockets that are specifically listed so this video is really more of a psa to let you know like if you're reusing hardware like an older thing that you've just gone through a few builds with and you're like oh hey look the brackets line up let's just use it you could very well absolutely be causing yourself a problem and look now we have no ram lighting again hey it worked look we have no mouse it's completely locked up okay now that this has happened which is basically reminiscent of what happened the last time i got nothing now reset nothing now it should come back up potentially with the code 55 error no it's posting but is it going to post in lock up again see do you understand why this could be extremely frustrating and difficult for somebody without a lot of experience with with hardware to try and figure out these types of problems when everything is working fine and then you you just can't explain why suddenly something stops working because look now it's working just fine so if i were and then the ram just turned off again in terms of the lighting oh there it goes look lock up so here's the thing if you were if you were new to computers where would you start you'd be like i don't know i don't know what's happening here would your first thought be to loosen up your aio probably not probably not you might think it's your cpu and you might swap it with another one and then you might take the cooler off put in the new cpu and then crank it back down with the force of hulk again yeah nothing so i am going to power cycle and i want to see if i can get that code 55 to come up because code55 like i said that was specifically to memory and the reason why it's giving a memory error at least it did that time see i i loosened it up and re-tightened it so it doesn't mean the same pins that were causing me a problem are going to cause a problem it could be different pins but at least the first time i did this the pins that were now it's going to do this check because it knows that it keeps crashing the pins that were causing a problem were memory related so it doesn't mean they're memory related this time does that make sense it's not always going to be and the order which i tighten them down is going to torque it in a different way so it might be completely different pins which is why i'm getting such random behavior one of the things that i had done is i left in the bios for a while to see if it would lock up there because i started thinking maybe the cooler pump was dead or something and was turning off and overheating that wasn't the case it also was not locking up in bios only in windows and that could have something to do with just the way windows accesses the memory i'm not sure but again this may not even be a memory issue on this one so this is the kind of stuff that can lead to craziness let me do a cinebench run right now i'm curious as to if we would even pass but the intermittentness that word intermittentness if it wasn't a word it is now the intermittentness is what leads to the mystery of trying to solve problems like this i want it to crash or give me a problem one more time so i can show you by loosening up my cooler they will all go away and this is a small cpu am i small i mean it's the small substrate before the 12th gen went to a much bigger one the bigger the substrate the more likelihood this can happen which is also why with the the retention system of 12th gen and the potential bending of the cpu causes the problem because then it starts lifting and not touching pins in areas where it's supposed to but you guys already saw we had a shutdown fail like a pause on shutdown it's like if someone were to tell me my system locked up when i tried to shut it down i would think you might have a driver issue something to do with like parking the driver um you know being an issue but that time it shut down just fine uh you saw we had a lock up in the middle of of our desktop interestingly enough that i cannot get a particular postcode problem which kind of even leads to the mystery of it all like if postcodes postcode 55 is what led me directly to go something's up with the memory swapping the memory out and going memory is fine let's try the cpu cooler and then that was my first thought because of my experience i knew like this cooler was not intended for this era this era obviously is years and years almost a decade newer than this so there had to be something with that it's all working at the moment but i haven't changed anything and obviously i wouldn't trust it so i can't show you guys the postcode error which i was really hoping to be able to do because it's not giving me an error again but i wanted to at least give you guys some food for thought that you know basic troubleshooting reseeding ram wouldn't have fixed the problem reseeding graphics card wouldn't have fixed the problem it really came down to cpu tension and all i did literally while i just did this loose loose loose loose and then this one wasn't that's all i did i did that still doesn't wiggle or anything it brought tension off the socket and everything worked fine so let me do another post code 55 had went away and then my both my ram 6 started working so you could see how you would inadvertently go oh man my ram is bad and you buy more ram and then you have the same problem or you go damn my cpu or my motherboard you might even think it's a bad motherboard channel or something would i like to have demonstrated that one a little bit more for you but i love to make these educational pieces where i can to give you guys some food for thought on your systems if so if you're watching this video right now and it piqued your interest because you went man i have a computer that's being super unstable i don't know what the problem is i would maybe not just give your ram a good receipt maybe double check your installation on your cooler to make sure you're not over tightened alright guys thanks for watching we'll see you in the next one\n"