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

I´ve 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 won´t 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.
I´ve 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.

:)

 

BSOD error 0x00000139

Hi
SpiritX MS MVP

Thank you for your reply!

I finally found a solution (I hope ) in
NVIDIA forums, as you recommended. The problem is with Nvidia driver, with a new version 361.43 realized on 21.12.2015. So I just uninstalled manually 361.43 version and installed a previous version
359.06, downloaded
here. I couldn´t use roll back option in device manager because I upgraded the system to 10586 and I lost previous version of the driver.

I had 3 BSOD crashes yesterday , when I tried to launch Adobe Photoshop CS6, since I reinstalled the driver I haven´t got any errors.

I hope Nvidia fix this issue soon.

Regards

Noff

 

BSOD error 0x00000139

Hi guys,

I have a problem with my pc, almost every week restarted with Kernel Security Check failure. It is the third time now, here is the link for a MEMORY.DMP and for a MsInfo file from the last error.

Link for Google Drive

It seems something wrong with ntkrnlmp.exe. When I got the error first time, I ran
scf /scannow and chkdsk without any errors, after this I tryed to update drivers but each driver was up to date.

Really appreciate your help in advance.

Thanks

Noff

PS: sorry for my poor English

 

Hi Lih147,

What exactly is this for in the hosts file?
Code: 127.0.0.1 validation.sls.microsoft.com[/quote]

 

[/quote] I don't know. Wasn't me who put it there.

 

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 don´t 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.

 

It doesn't exactly have to be related, it could though.
The reason is following

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.

 

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[/quote]

 

[/quote] So, I uninstalled nod 32, restart the computer and... another BSOD, 2 of them actually.

The new file is attached.

Thanks.

 

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[/quote] 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[/quote]




Diagnostics Test

HDD TEST


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



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.