Blue screen "memory management" and corrupt windows files.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Retromer
    PCHF Member
    • Feb 2020
    • 17

    #1

    Blue screen "memory management" and corrupt windows files.

    Hi, I am having issues with my windows 10 and have had multiple blue screens with different error codes. After using the sfc/scannow command the scan found corrupt files but was unable to fix some of them. The corrupt files was succesfully removed with the chkdsk /f /r /x scan, and no corrupt files was found with the sfc scan. After the next restart of my computer the sfc scan again found corrupt files.

    I recently did a hardware change of my motherboard, ram and cpu, aswell as installing a new M.2 SSD. The issues started a short period after installing COD, Modern Warfare.
    After the hardware change my activation key for windows was lost, so I dont have an activated version of Windows 10.

    All innsight is much appreciated.
  • jmarket
    PCHF Owner
    • Jan 2015
    • 7634

    #2
    Hi @Retromer and welcome to PCHF

    When you registered Windows 10 before, did you link it to your Microsoft account?

    Comment

    • Retromer
      PCHF Member
      • Feb 2020
      • 17

      #3
      Thank you jmarket, yes I did link it to my microsoft account. I bought the computer used, and my guess is that the version of windows 10 that I had was from a Windows 8 in the free upgrade period. I dont know if it was a valid windows 8 product thou.

      Comment

      • phillpower2
        PCHF Administrator
        • Sep 2016
        • 15209

        #4
        Just a cautionary note, unless your present product key is the full retail version you cannot use it with a new MB as an OEM product key is tied to the original MB it was paired with, to use an OEM key with a new MB is detected by the Microsoft servers as software piracy and therefore you get on screen warnings etc..

        Exceptions to the above are 1: If your MB is replaced under warranty and 2: If your MB is replaced out of warranty with an alternative type but same brand due to the original model no longer being available, an upgraded MB however will require the purchase of a new OS licence.

        If you have a full retail disk and a product key that is not in use on another computer the OEM restriction/s is/are not the same.

        Comment

        • Retromer
          PCHF Member
          • Feb 2020
          • 17

          #5
          That makes sense, which is why I dont have an activated OS right now. Still, I think all the features and the windows 10 OS should still work even though it is not activated. Or do you think my issues with the corrupt files might be from the fact that the OS is not activated?@phillpower2

          Comment

          • phillpower2
            PCHF Administrator
            • Sep 2016
            • 15209

            #6
            If you don`t have a legitimately activated version of Windows you are denied updates and many of these updates are fixes for known problems, there is also the matter of driver updates, with the exception of the chipset drivers for the MB which you must get from the board manufacturer most drivers are obtained via Windows updates these days.

            Comment

            • Retromer
              PCHF Member
              • Feb 2020
              • 17

              #7
              I see. After doing some research I found that my student organisation has windows 10 activation keys, so now my windows 10 is activated. I just now tried the command DISM /Online /Cleanup-Image /RestoreHealth, and then did sfc scan and it said that the corrupt files was succesfully removed . I will post again if the issues continue to come back! Thanks @phillpower2 and jmarket for the response.

              Comment

              • phillpower2
                PCHF Administrator
                • Sep 2016
                • 15209

                #8
                You are welcome Retromer and thank you for letting us know that you no longer required assistance with this (y)

                Comment

                Working...