2

Has RAM quality just fallen off the deep end? I swear I remember a BSOD could mean just about anything, now it seems to be failing RAM every time.

Also, why am I troubleshooting it? I know a few programming languages, so suddenly I can fix anything plugged into a wall?

Comments
  • 1
    So you read the first error code and you conclude it's faulty RAM stick?
  • 0
    @pyjong ... No, either by replacing with known good part or running memtest it ends up being replacing the ram that fixes it.
  • 1
    @Ratpack309 ah i see. I thought that be the case because you mentioned BSOD and programming languages. I guess that was just to spice it up then.
  • 1
    @pyjong No, it just also drives me nuts that as a 'programmer' somehow I should also know how to fix hardware issues as my company sees it. Just the 'it's not my job' feeling.
  • 1
    @Ratpack309 ahhh ok, now I get it.
  • 0
    Usually computers have some kind of warranty
  • 0
    @electrineer True, but these are 3-4 years old.

    Perhaps I'm just getting old enough that I'm starting to say things like, 'back in my day ram used to last 10 years'. Clearly not true. Just rose colored glasses, I guess.
  • 1
    Well.. it's definitely not going to help you solve anything but if you have windbg installed. You can use it to open up file in c windows minidump. Then type analyze -v and check the error struct. Then you might wanna google microsoft docs bug check codes and with that you should be able to put together why it bsoded. Maybe.. for some bug checks one just has to know kernel
  • 0
    @Pyjong if it fails memtest you should just change the ram. On linux you can disable some ram addresses but it's not really worth the hassle
  • 0
    @Pyjong Thanks for the tip, anyway. Maybe next time it's not as simple as ram, it will help me out.
  • 0
    @electrineer if some banana dev misconfigures say pam registers you can run memtest on as many ram sticks as you want and it will tell you all of them are faulty. You are proly right but it might be worth it to at least check what the os says the problem is. Cuz treating symptoms wont solve your problems.
  • 0
    @Pyjong do you even memtest?
  • 0
    @electrineer I realize it runs in preboot. But there are two other things that run before that.
  • 0
    @electrineer ah I see: PAMs are processor registers, not a path in Windows registry
Add Comment