Windows 10: Assorted BSODs after upgrade, last error 0x00000139.

  1.    15 Nov 2015 #1

    Assorted BSODs after upgrade, last error 0x00000139.


    Ive recently upgraded from windows 7 to windows 10. After that, I start to get BSODs mostly while using Google Chrome. When the PC restarts, it wont do anything (the monitor stays black and the cpu doesn't beep) until I take the power cord out and plug it back again, then turn the pc on.
    Ive tried some "solutions" found in the internet, like disabling fast startup, but it doesn't help.
    The zip file required for diagnose is attached.
    Thanks.
      My System SpecsSystem Spec

  2. axe0's Avatar
    Posts : 11,205
    Windows 10 Pro
       17 Nov 2015 #2

    Hi Lih147,

    What exactly is this for in the hosts file?
    Code:
    127.0.0.1 validation.sls.microsoft.com
      My System SpecsSystem Spec

  3.    19 Nov 2015 #3

    axe0 said: View Post
    Hi Lih147,

    What exactly is this for in the hosts file?
    Code:
    127.0.0.1 validation.sls.microsoft.com
    I don't know. Wasn't me who put it there.
      My System SpecsSystem Spec

  4. axe0's Avatar
    Posts : 11,205
    Windows 10 Pro
       20 Nov 2015 #4

    I assume there are more users?
    If so, ask the one who did.
      My System SpecsSystem Spec

  5.    20 Nov 2015 #5

    axe0 said: View Post
    I assume there are more users?
    If so, ask the one who did.
    No, just me, one user. It was an old windows 7 before the upgrade. I dont know what that line have to do with the BSOD, but I removed it from the hosts file, and the BSOD are still coming.

    To proove it, the new file is attached.
      My System SpecsSystem Spec

  6. axe0's Avatar
    Posts : 11,205
    Windows 10 Pro
       20 Nov 2015 #6

    It doesn't exactly have to be related, it could though.
    The reason is following
    A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
    For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
    Usually in the hosts some lines are added for cracking/bypassing software, it is like a push for the crack. It gives that little extra to complete the crack.

    I'll take a look at the files within a couple of hours, its almost 1AM a.t.m. here.
      My System SpecsSystem Spec

  7. axe0's Avatar
    Posts : 11,205
    Windows 10 Pro
       21 Nov 2015 #7

    Please uninstall ESET while troubleshooting and use Windows Defender as alternative
    How do I uninstall ESET Smart Security or ESET NOD32 Antivirus in Windows 10?ESET Knowledgebase

    Code:
    *** WARNING: Unable to verify timestamp for eamonm.sys
    *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
    
    ffffd001`afcb8158  fffff801`50660a0eUnable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for eamonm.sys
    *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
     eamonm+0x20a0e
    
    ffffd001`8f75f938  ffffe001`30372dcdUnable to load image C:\Program Files\ESET\ESET NOD32 Antivirus\em018_64.dat, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for em018_64.dat
    *** ERROR: Module load completed but symbols could not be loaded for em018_64.dat
     em018_64+0x19dcd
    
    ffffd001`8f75f4f8  fffff801`9807c78fUnable to load image \SystemRoot\system32\DRIVERS\ehdrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ehdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
     ehdrv+0x1c78f
      My System SpecsSystem Spec

  8.    21 Nov 2015 #8

    axe0 said: View Post
    Please uninstall ESET while troubleshooting and use Windows Defender as alternative
    How do I uninstall ESET Smart Security or ESET NOD32 Antivirus in Windows 10?ESET Knowledgebase

    Code:
    *** WARNING: Unable to verify timestamp for eamonm.sys
    *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
    
    ffffd001`afcb8158  fffff801`50660a0eUnable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for eamonm.sys
    *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
     eamonm+0x20a0e
    
    ffffd001`8f75f938  ffffe001`30372dcdUnable to load image C:\Program Files\ESET\ESET NOD32 Antivirus\em018_64.dat, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for em018_64.dat
    *** ERROR: Module load completed but symbols could not be loaded for em018_64.dat
     em018_64+0x19dcd
    
    ffffd001`8f75f4f8  fffff801`9807c78fUnable to load image \SystemRoot\system32\DRIVERS\ehdrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ehdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
     ehdrv+0x1c78f
    So, I uninstalled nod 32, restart the computer and... another BSOD, 2 of them actually.

    The new file is attached.

    Thanks.
      My System SpecsSystem Spec

  9. axe0's Avatar
    Posts : 11,205
    Windows 10 Pro
       22 Nov 2015 #9

    The nvidia video driver has been flagged
    Code:
    ffffd000`9fe59f88  fffff801`001b95c7Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x95c7
    But this crash is usually related to the hard drive
    Code:
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8013b11897f, The address that the exception occurred at
    Arg3: ffffd001f1054828, Exception Record Address
    Arg4: ffffd001f1054040, Context Record Address



    Assorted BSODs after upgrade, last error 0x00000139. Diagnostics Test Assorted BSODs after upgrade, last error 0x00000139.
     HDD TEST

    Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.


    Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html

    Run HDTune to scan for errors, health and benchmark.
    Let me know what the results are, prefered screenshots.
      My System SpecsSystem Spec


 

Related Threads
BSOD Bug Check Code 0x00000139 in BSOD Crashes and Debugging
Minidump:
BSODs at random times after windows upgrade in BSOD Crashes and Debugging
Hi there, I recently managed to get a cryptowall/cryptolocker virus. I wiped everything, formatted c: and reinstalled windows 7 home premium. Was getting constant, seemingly random BSODs 10+ times daily. Tried a bunch of things, didn't work, so...
I should probably preface by saying I am using a custom-built machine and never had a BSOD when I was using Windows 7. Since I took the plunge, I've been greeted by a BSOD on nearly every startup (usually around 1-3 minutes after the lock screen...
A couple of BSODs, different error-codes in BSOD Crashes and Debugging
Hi TenForums I updated my 8.1 Pro laptop to 10 Pro a couple of weeks ago, and so far I really like what I see. The only nasty bit about W10 so far has been these BSODs happening every once in a while. After the first few I decided I might need...
http://puu.sh/jj8wQ/4cad6d8add.png I have tried what I believe to be everything at this point. Clearing out the update download folder and retrying the update does not help whatsoever. Forcing the update through a command prompt just gets the...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:28.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums