Failure at resume from standby/hibernate: ntoskrnl.exe+14a6f0

daff · 27 Feb 2017

Hi,
sometimes i get a BSOD / Blackscreen when I resume from Hibernate/Standby. I ran Memtest and checked the temperatures. No Problems there. Also all drivers should be up to date AFAIK.

I looked at the dumps with BlueScreenView and spotted a repeating Crash Adress: ntoskrnl.exe+14a6f0
The BSOD Message is not similar most time.

I attached the output from dm_log_collector.exe
Could someone please analyse the file and give me feedback?

Thanks :)

Daff

EDIT: new output file.

BSODHunter · 28 Feb 2017

Genuine.txt seems to be valid but I see in the eventlog that there was software used to activate Windows not in the legal way.

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

daff · 28 Feb 2017

Thanks for your reply @BSODHunter. I have a legal license for my Windows 10 which was created from a Windows 7 license. The tool you found is for activating Office, but I can remove it, if it causes the failure or problems here in the forum.

Could you find any other problem?

BSODHunter · 28 Feb 2017

The Problem is, that u will not get support from this forum with not correctly licensed Software Products. Please remove all trails from "K**Aut*" and your actual Installation of Microsoft Office so that we can help you. After that please reupload a new generated zip with dm log collector

daff · 28 Feb 2017

I just uploaded a new output from dm log collector to my initial post. The event log still contains entries from the illegal tool. Hope that is not a problem...

BSODHunter · 28 Feb 2017

Code:

0x00000050:    PAGE_FAULT_IN_NONPAGED_AREA (24.02.2017 18:42:23) [Windows 10] 
 
CAUSED BY:     NTFS.sys [2.11.2016] * NT File System Driver (Windows System File) 
 
PROCESS:       svchost.exe 
 
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Code:

0x00000139:    KERNEL_SECURITY_CHECK_FAILURE (26.02.2017 23:22:05) [Windows 10] 
 
CAUSED BY:     dxgkrnl.sys [9.12.2016] * DirectX Graphics Kernel (Windows System File) 
               nvlddmkm.sys [29.12.2016] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx  
 
PROCESS:       csrss.exe

Code:

0x1000007E:    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (28.02.2017 17:44:58) [Windows 10] 
 
CAUSED BY:     memory_corruption    
 
PROCESS:       LockAppHost.ex

STEP 1:
Please update NVIDIA Driver to the newest version using DDU:

Display Driver Uninstaller: How to use
Display Driver Uninstaller (DDU) is a small software that can help the user to uninstall the display driver from the users PC. It can uninstall the driver for all the lead display chip developers, viz. Nvidia, AMD and Intel.

STEP 2:
Please remove Software Thunder Master. Its kown for causing Bluescreens.

STEP 3:
Disable or remove Kaspersky and use Defender instead to test.

STEP 4:
Please remove all Tuning Utilitys like AVG TuneUp. Its known for causing Bluescreens

STEP 5:
did u run memtest 8 passes? If not please do that again

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

daff · 03 Mar 2017

I followed the steps and uploaded the results of memtest and another run of dm log collector.
Before I tried to find other possible problematic drivers using driver verifier. I don't know if that helps but I removed VirtualBox, a Tages driver (copy protection) WinCDEmu and the driver of my Logitech mouse. The dumps I used to find the drivers are in the attached ZIP file. Maybe you can find more details about other problems in it.

BSODHunter · 07 Mar 2017

RAM seems to be okay then. Did u followed my other steps?

BSODHunter · 07 Mar 2017

Same what u wrote, these are the drivers which a blamed with verifier:

Code:

VBoxNetAdp6.sys [16.01.2017] * Oracle VirtualBox NDIS 6.0 Host-Only Network Adapter Driver * => Downloads â€“ Oracle VM VirtualBox
BazisVirtualCDBus.sys [27.09.2015] * WinCDEmu virtual CDROM driver - Bazis Inc * => WinCDEmu - the easiest way to mount an ISO. And more...
atksgt.sys [17.05.2009] * part of a Copy Protection platform developed by Tages SA * => TAGES, the AAA Copy Protection System

1.
Did u remove Thunder Master? Its known for causing Bluescreens.

2.
U have two security softwares installed at the same Time, thats not good.
U should remove Kaspersky and AVG and use Defender for testing period.

3.
U could try BIOS Version F10b for your Mainboard:
http://www.gigabyte.de/Motherboard/G...-10#support-dl

4.
Because of the older dumps which are very different corrupted hardware is not impossible.

5.
Its worth to do a filesystem check:

Repair Windows Filesystem:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /CheckHealth
dism /Online /NoRestart /Cleanup-Image /ScanHealth
dism /Online /NoRestart /Cleanup-Image /RestoreHealth

sfc /scannow

chkdsk %systemdrive% /F /R /X
fsutil dirty set %systemdrive%

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted. SFC should be able to repair the files afterwards.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...

daff · 07 Mar 2017

Yes, I did. Look at the attachment from my last post.