New
#11
My windows 10 version are 1703 (Build 15063.413). I attached the new zipped in this post.
BSOD Caused by ntoskrnl.exe and hal.dll
-
-
New #12
[CODE]Code:BugCheck 74, {2, ffffe10032d86a70, 1, ffffffffc000014c}Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+a3ce7 )
The memory test had 20 runs and zero errors. That number of runs is sufficient to rule out RAM/DIMM problems.
So far you have removed the Realtek driver and updated the AMD driver.
The bsod tonight did not give sufficient information to determine the misbehaving driver or application.
To recover the operating system you performed a registry backup and it was successful.
Open administrative command prompt and run these commands:
1) sfc /scannow
2) dism /online /cleanup -image /restorehealth
3) chkdsk /scan
Post the results into the thread.
The next step is using Windows driver verifier to stimulate drivers and find the misbehaving drivers. Windows driver verifer will repetitively produce bsod until there are no more malfunctioning drivers or until it is turned off.
You must know how to turn it off. That is accomplished by opening the windows recovery or windows advanced troubleshooting menu and navigating to startup options (not startup repair). Once startup options is chosen there is a restart and after restart you will select #6 safe mode with command prompt and type verifier /reset
The command verifier /reset most of the time turns off windows driver verifier. When it is off you will reboot to the desktop. On the desktop you will use two software applications to analyze the dump files. They are Bluescreenview and Whocrashed and they each may add something to the analysis. If you have a driver or application that is identified and can be uninstalled with device manager or control panel you will uninstall it. Then you can either attempt to reinstall another driver or continue finding misbehaving drivers and uninstalling them. It's a personal choice as to which method you prefer. The end result should be the same. All of the misbehaving drivers or applications will be uninstalled and some will be reinstalled and tested again with windows driver verifier to make sure that the new drivers don't misbehave.
To practice navigating the advanced troubleshooting menu open administrative command prompt and copy and paste:
shutdown /r /o /f /t 00
When the windows recovery opens you will navigate to startup repair. If the startup repair stop code fails you will navigate to command prompt with Administrator: X:\windows\system32/cmd.exe and enter
verifier /bootmode resetonbootfail to turn off windows driver verifer. If that fails to turn windows driver verifier off you will navigate to restore and perform a restore to the most recent valid restore point. You will make a brand new restore point before using windows driver verifier.
When there is a bsod you will want time to view the window. It typically will display a stop code driver verifier detected violation and sometimes it may display the misbehaving driver in the form *.sys. If you see a driver named please record it.
There are settings to view to make sure you are ready to record bsod and to turn off automatic restart so that you have time to view the bsod window:
Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure un-check automatically restart
BSOD Finding and fixing them - Microsoft Community
This is information on how to start windwos verifier and the customized settings for the tests and the drivers.
Please make sure that you have files backed up, have made and image using Macrium, and have made a fresh restore point before starting Windows driver verifier.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Once all misbehaving drivers or applications have been fixed you will use windows driver verifier for 36 hours of typical computer use. If there are no more bsod the testing will be completed. The misbehaving drivers/applications will be fixed and preventative maintenance will be accomplished.
During the use of windows driver verifier you may notice that performance is diminished. This is normal while using windows driver verifier.Last edited by zbook; 03 Jul 2017 at 01:11.
-
New #13
Here are the result of sfc /scannow
dism /online /cleanup-image /restorehealth
chkdsk /scan
Code:Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>winverC:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online/cleanup-image/restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Error: 87The online/cleanup-image/restorehealth option is unknown.For more information, refer to the help by running DISM.exe /?.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Windows\system32> dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================]Error: 0x800f081fThe source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Windows\system32> chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... Found corrupt basic file structure for "\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db-shm <0x7,0x30aa3>" ... repaired online. File "\Windows\System32\LogFiles\Srt\SrtTrail.log <0x2b,0x547c>" and file "\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db-shm <0x7,0x30aa3>" both own logical cluster 0x219cb ... queued for offline repair. 702208 file records processed. File verification completed. 21434 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 917142 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 107469 data files processed.CHKDSK is verifying Usn Journal...Usn Journal verification completed.Windows has found problems and some were fixed online;the remaining problems must be fixed offline.Please run "chkdsk /spotfix" to fix the issues. 102562598 KB total disk space. 91610848 KB in 463335 files. 258804 KB in 107469 indexes. 0 KB in bad sectors. 792686 KB in use by the system. 65536 KB occupied by the log file. 9900260 KB available on disk. 4096 bytes in each allocation unit. 25640649 total allocation units on disk. 2475065 allocation units available on disk.C:\Windows\system32>
-
New #14
Please use Macrium to make a backup image of your drive and please make a fresh restore point.
Please reboot and have it do the offline repair.
Then run overnight chkdsk /x /r
1) run one of the SMART tests on your drives:
CrystalDiskInfo - Software - Crystal Dew World: CrystalDiskMark - Software - Crystal Dew World
HD Tune: http://www.hdtune.com/
Hard Disk Sentinel - HDD health and temperature monitoring: Hard Disk Sentinel - HDD health and temperature monitoring
When the SMART test has completed open the Microsoft snipping tool and make images of the results to post into the thread.
11) Run Sea tools for windows on your drive using SMART, short and long generic tests:
How to use SeaTools for Windows
How to use SeaTools for Windows
-
New #15
Attachment 142253
Here are the result of the SMART test.
-
New #16
Here are the screenshoot of SeaTools test.
Short Generic
Attachment 142272
Long Generic
Attachment 142273
-
New #17
Please post output of:
dism /Online /NoRestart /Cleanup-Image /RestoreHealth
-
New #18
After the chkdsk /x /r has completed please post the result into the thread:
How to find chkdsk results in Windows 10 - Winaero uses 26226 find
Pending the results of this command you can plan to use windows driver verifier when you have time to process the bsod.
Before starting windows driver verifier make sure you have made an image with macrium, and created a brand new restore point.
As the bsod occur you will use:
Bluescreenview: Blue screen of death (STOP error) information in dump files.
Whocrashed: http://www.resplendence.com/whocrashed
to provide immediate analysis of the bsod created minidmp files.
Please update the zip file or post a new one into the thread for the bsod:
BSOD - Posting Instructions - Windows 10 Forums
And we can help guide you through the debugging, the uninstall and the reinstall.
-
-
New #19
here are result of
dism /Online /NoRestart /Cleanup-Image /RestoreHealth
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Windows\system32>dism /Online /NoRestart /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[===========================97.1%======================== ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\system32>
-
New #20
Tip
Until May 19th 2017, there was a problem in the Creators Update (version 1703, build 15063) with DISM reporting corruption and unable to repair it. This was fixed by Microsoft updating something on their servers that was causing DISM to fail with 'source not found' when it tried to refer to it.
See: KB4016871 Fixes Spurious Win10 DISM Issue - Windows Enterprise Desktop
Quote
Related Discussions
