don't click here

PC is cursed, pls help

Discussion in 'Technical Discussion' started by JaredAFX, May 31, 2017.

  1. JaredAFX

    JaredAFX

    You telling me a shrimp fried this rice? Member
    909
    70
    28
    Florida
    Downloading megahertz
    I'm sorry for bringing up all my computer nightmare issues to you guys, but you're all very knowledgeable around here and I need help. So for the past several days I've been getting blue screens--this one, in fact. It tends to happen when the computer hasn't been on for that long or not long after I open it from sleep mode. Also, when I plug it in to charge, I tend to get this message. I've been removing some things that I've installed recently, including a bunch of different revisions of Visual C++ and reinstalling only the 2015 versions of the x64 and x68, and I still have the same problems. I've gone into Device Manager and updated things like video card drivers. I also ran dskchk and let it do its thing for a few hours, and still, I get the same problems. I'm really at a loss right now.
     
  2. NyaNyaLily

    NyaNyaLily

    Member
    88
    29
    18
    Open CMD with admin rights and type "sfc /scannow". Maybe that will work

    If the problem still occurs, try opening CMD again (with admin rights of course) and type "Dism /Online /Cleanup-Image /RestoreHealth".
     
  3. Covarr

    Covarr

    Sentient Cash Register Member
    4,233
    3
    18
    Trapped in my own thoughts.
    Two stageplays, a screenplay, and an album
    Is it always reader_sl.exe? If so, you should be uninstalling Acrobat and/or Acrobat Reader first and foremost.

    It does very much seem like some data on your drive has been corrupted. Whether that's from a damaged disk or something else, I don't know. Worst case scenario you'll need a new HDD, but it's worth additional investigation first; a Windows reinstall might be enough. Uninstalling the right application might even be enough, hopefully.
     
  4. JaredAFX

    JaredAFX

    You telling me a shrimp fried this rice? Member
    909
    70
    28
    Florida
    Downloading megahertz
    Thank you, you two. Really. I've gone ahead and done all of those suggestions (I don't need Adobe Reader anyway, I prefer using Chrome for PDFs) and if it keeps happening I'll do a reinstallation of Windows. The only thing about buying a new drive is that I also want to get some sort of tablet/smaller laptop to take around to my classes, because this 15" thing hurts my back, and my Early 2011 MacBook Pro isn't what it used to be (it takes two percent just to turn on). I'm trying to not spend so much money on computer stuff, but if that's what needs to happen, then it'll happen.
     
  5. NyaNyaLily

    NyaNyaLily

    Member
    88
    29
    18
    I just did another Google search, turns out you have to uninstall any existing Microsoft Visual C++ Redistributable Package and install the latest one.

    Be sure to install the right version though (x86 version if you have a 32 bit machine, x64 version if you have a 64 bit machine).
     
  6. GerbilSoft

    GerbilSoft

    RickRotate'd. Administrator
    2,972
    85
    28
    USA
    rom-properties
    MSVCP120.dll is specifically the Visual Studio 2013 runtime. Uninstall all instances of the 2013 runtime (both x86 and x64), then reinstall these:
    http://download.microsoft.com/download/0/5/6/056dcda9-d667-4e27-8001-8a0c6971d6b1/vcredist_x64.exe
    http://download.microsoft.com/download/0/5/6/056dcda9-d667-4e27-8001-8a0c6971d6b1/vcredist_x86.exe

    For the blue screen issue, you'll need to check the Event Viewer to see what driver's actually crashing. Alternatively, check the memory dump (usually C:\Windows\memory.dmp) using WINDBG to see where it's failing.
     
  7. You-Are-Pwned

    You-Are-Pwned

    Member
    76
    8
    8
    Error 0xC000012F means corrupted executable file. Which means the DLL is corrupted, so you should most definitely reinstall the Visual Studio runtimes. For the blue screen try using http://www.nirsoft.net/utils/blue_screen_view.html
    It should tell which service exactly had failed.