Jump to content

CommonCurt

Honorary Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by CommonCurt

  1. 20 hours ago, AdvancedSetup said:

    I don't see a specific reason why it would not run. That leads me to believe that something odd is going on. I see errors in the Event Logs but was hoping a clean install might correct it.

    You could also try using the Google Public DNS temporarily to see if that helps correct the issue. If neither of those options correct the issue then I can write a generic clean up and maintenance script to see if that corrects it.

    https://developers.google.com/speed/public-dns/docs/using

    If neither of those corrects the issue let me know and I'll write a script for you to run

    Thanks @CommonCurt

     

    I have tried, both of those things.   I'll probably try them one more time just in case.

    I'm all for trying that clean up maintenance script to see if it helps.  Please go ahead and send it to me.

  2. 20 minutes ago, AdvancedSetup said:

    If you copy/paste the entry it will automatically answer yes for you.

    Did the disk check run?

     

    Press the Windows + R keys to open the Run dialog, type powershell.exe, and press Enter.

    In PowerShell, copy and paste the command below, and press Enter

    get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

    CHKDSKResults.txt file will be created on your desktop, that is the log file of your chkdsk scan results from Event Viewer.

    Please upload that file on your next reply

     

    Okay got it.

     

     

    CHKDSKResults.txt

  3. 39 minutes ago, AdvancedSetup said:

    Hello @CommonCurt

    The logs show multiple different issues in the Event Logs. Let's do a bit of clean up and see if that corrects the issue.

    Please open an elevated admin command prompt and type in or copy paste the following.

    
    ECHO Y|CHKDSK C: /F

    Then restart the computer.

    Then open another elevated admin command prompt and type in the following

    
    sfc  /scannow

    Let me know what the message says from the SFC command

    Thanks

     

    Thanks.

     

    After trying the first command it said: cannot run disk in use, would you like to run on next restart Y/N.   When I typed in Y and pressed enter it said not a valid command.

    I then restarted the computer, and ran sfc /scannow, and it says: Did not find any integrity violations.

  4. On 12/12/2017 at 8:46 AM, usasma said:

    I can't recall - have you tried a clean boot on either of the systems?
    Perform a Clean Boot:  http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows

    If that stops the problem, then re-enable things a few at a time until you figure out what's causing it.
    Then uninstall the problem program (from Start...Settings...Apps...Apps & Features - if you don't find it there, check the right sidebar for Programs and Features and see if you can remove it from there).
     

    Beyond that, this memdory dump is basically the same as the others.
    We're at a point now where there's not much else we can do here.
    Further analysis by an expert who is more skilled with WinDbg than I am might reveal something.
    Try posting on the BSOD forums at http://www.sysnative.com  , I haven't been active there in years so I'm unsure of who's still working there.
    Beyond that, you're looking at a live debugging session to do this - and that can get very, very expensive very quickly.  For more info on that, I'd talk with the people at https://www.osr.com/

     

    Hey,

    Not sure if you saw my last post above due to the holidays, but I managed to find the first BSOD (when all this started), and it looks like the very first one might say something a little different.  

  5. I haven't tried doing a clean boot on either system because of how long it takes for the BSODs to show up (this system around 5 days, and on the other system 7-10 days).

    It never happens right after a restart.  After I try uninstalling somethings if that doesn't flush out what's causing it I might consider trying clean boot, but it would take a long time with how long in between the BSODs are.

    I also will look into the other forum that you mentioned.  Then, as a last resort, I might go back and start installing the Monthly roll up Updates starting with the Month when my problem started.

    Just for the sake of it I attached the first two BSODs I received on this system when all of this started.  Maybe one of them can give some information that we haven't gotten from the current ones.

    071317-7956-01.zip

    071317-8782-01.zip

  6. Sorry it has taken me so long to reply.  Been dealing with Holiday stuff.

    Should I keep Malwarebytes Ransomware & Exploit Protection turned off after I turn Driver Verifier back on, or is it okay to turn those back on?

    Also, I notice in the Event Viewer almost every time right before a BSOD there is an Event ID: 3 "Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D""

    Not sure if that helps anything, but I thought i'd mention it.

    Lastly,  in that list you posted above.  The second driver "cpuz136_x64.sys".  If it belongs to a program called CPUID CPU-Z I can uninstall the program.  I don't use it that often.

  7. Okay, finally had a BSOD on this system when I woke up this morning.  It looks like it's saying that it's  iaStor.sys again just like the other system.

    I went ahead and turned off Driver Verifier on this one now, but I didn't get another BSOD like on the other system during the restart.

    The funny thing is that I had already deleted the RealTemp folder from this system about 2 days ago.

    Guess I'll start disabling the Malwarebytes live protections now.

    111717-13993-01.zip

  8. I turned RansomWare protection off before I left the house.  When I get home I'll see what else I can turn off.

    I really don't want to have to uninstall MalwareBytes.  I have two lifetime licenses, and I do really like the program.

    The thing that sucks is that like I said before.  BSOD's usually take 3 -5 days.

    I never get BSOD's when shutting down. or restarting the system.  So I'm guessing Driver Verifier is the reason the last one happened when I restarted after turning turning Driver Verifier off?

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.