Hello, sorry for the lack of updates. I have been out of office for a couple weeks so haven't really used the computer much and it has been left in sleep mode. It did BSOD once or twice when I tried and remote in. Attached the files. Running it currently in safe mode so will see if that does anything.
In the event viewer there is windows operating system file corruption.
Earlier in the thread BSODHunter had you check the operating system and the dism commands were not completed.
"MemCompression and memory_corruption going in hand with NTFS.sys all over the place are present in your dumps. I say there something wrong with SSD, Sata Cable, Sata Port or Windows filesystem."
An in place upgrade repair allows you to keep files and applications and repairs the operating system and registry.
Please perform an in place upgrade repair with a bootable windows 10 iso: Download Windows 10
Before performing the in place upgrade repair make a new restore point and make an image using Macrium: Macrium Software | Your image is everything
Typically the in place upgrade repair fixes underlying problems not fixed by scannow and restorehealth.
Steps for in place upgrade repair:
1) find a flash drive that you can format
2) create a bootable windows 10 iso: Download Windows 10
3) power on the computer and open file explorer > this PC > local disk
4) insert the windows 10 iso into any USB port
5) identify the windows 10 iso drive within file explorer
6) click on the windows 10 iso drive and identify setup or setup.exe
7) launch setup or setup.exe
8) choose language, time, currency, and keyboard
9) do not click on install as that is the method for a clean install which will delete partitions, format the drive and make an unallocated drive.
10) look in the left lower corner for repair your computer
11) follow the text and images in this link for an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials
Code:Event[3028]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2017-07-27T11:16:22.876 Event ID: 1002 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-2UMU17L Description: Startup Repair failed.Code:Event[3029]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2017-07-27T11:16:22.876 Event ID: 1121 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-2UMU17L Description: The following file necessary for Windows startup was corrupt: e:\windows\system32\drivers\acpi.sys
Ive done 3 - 5 clean install of windows 10 on this computer with the last about 2 months ago and the problem still comes back. Could my SSD have memory issues even though I ran the check on it?
If you have your files backed up a clean install is a better starting point.
The thread has been active a little more than 2 months and within the thread you had performed studies on the RAM, GPU, and drive SMART. All of those studies passed.
Chkdsk was in the posts but there was no report.
Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
This may take many hours so plan to run overnight.
When the chkdsk has completed post the results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Chkdsk ran in less than 20 minutes. I don't know if that means somethign or not. Here is the output
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure ...
662272 file records processed. File verification completed.
6827 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
789858 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 171 unused index entries from index $SII of file 0x9.
Cleaning up 171 unused index entries from index $SDH of file 0x9.
Cleaning up 171 unused security descriptors.
Security descriptor verification completed.
63794 data files processed. CHKDSK is verifying Usn Journal...
37641152 USN bytes processed. Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
662256 files processed. File data verification completed.
Stage 5: Looking for bad, free clusters ...
43582761 free clusters processed. Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
233916415 KB total disk space.
58542508 KB in 564093 files.
267352 KB in 63795 indexes.
0 KB in bad sectors.
775511 KB in use by the system.
65536 KB occupied by the log file.
174331044 KB available on disk.
4096 bytes in each allocation unit.
58479103 total allocation units on disk.
43582761 allocation units available on disk.
Internal Info:
00 1b 0a 00 8b 94 09 00 1b 9b 11 00 00 00 00 00 ................
b0 00 00 00 5e 00 00 00 00 00 00 00 00 00 00 00 ....^...........
Windows has finished checking your disk.
Please wait while your computer restarts.
It's a SSD.
Hardware and drive problems have been ruled out for CPU, GPU, RAM, SSD based on the most recent tests.
If you can perform a clean install please do not install any drivers or application other than bluescreenview and whocrashed.
Blue screen of death (STOP error) information in dump files.
http://www.resplendence.com/whocrashed
At this time you will have only a clean install of windows 10 version 1703 with updates and only windows installed default drivers and two software programs. There will have been no other drivers or applications installed.
Then you will activate windows driver verifier and stimulate drivers to find any misbehaving drivers.
To turn off windows driver verifer you will open windows recovery or windows advanced troubleshooting options and navigate to startup options. In startup options (not startup repair) you will select #6 safe mode with command prompt and type verifier /reset
If this command fails to turn off windows driver verifier you will navigate in the windows advanced troubleshooting menu to command prompt or administrator X: \windows\system32\cmd.exe and type: verifier /bootmode resetonbootfail
In case these two methods fail to turn off windows driver verifier you will navigate within the windows advanced troubleshooting menu to restore. This should restore but unfortunately you will likely loose the bsod mini dump file and little progress will be made in the troubleshooting.
Each time you turn off windows driver verifier you will return to the desktop and run each bluescreenview and whocrashed. Then post the results into the thread along with an updated version of the zip: BSOD - Posting Instructions - Windows 10 Forums
We will debugg the mini dump file and make suggestions.
Device manager will be viewed and drivers will then be installed from the computer manufacture's web site or from the hardware component websites.
Windows driver verifier will then be used to test the new drivers. When there are no more bsod windows driver verifier will be run for 36 hours while the computer is under typical use. If there are no more bsod the troubleshooting will be completed.
When a bsod occurs with windows driver verifier there will be a stop code. Typically it is driver verifier detected violation. Sometimes it will also display the misbehaving driver: *.sys If you see the driver on the bsod please record it. The system settings need to be modified to not automatically restart so that you have ample time to view the bsod window. Follow the settings in this link: BSOD Finding and fixing them - Microsoft Community
Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure uncheck automatically restart
To practice navigating the windows advanced troubleshooting menu you can open administrative command prompt and type: shutdown /r /o /f /t 00 On reboot you will be in the windows recovery or advanced troubleshooting menu.
Please see the links below to understand how to turn on, customize, and turn off windows driver verifier.
Before starting windows driver verifier please create a brand new restore point.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
BSOD - Posting Instructions - Windows 10 Forums
Turned on verifer and it BSOD right on startup. Using who crashed it says it was an intel driver so I found instructions here. After uninstalling that intel smart connect I turned verifier back on and am currently running it. Will let you know if I BSOD again. Oddly the commonly linked driver verifier tutorial on this forum selects much fewer options than the one you gave, so i wonder if that is why verifer was ineffective in the past.
Frequent BSOD's, ntoskrnl and usb drivers - Page 3 - Windows 7 Help Forums
This driver can be uninstalled.
Code:BugCheck C4, {2000, fffff809bf9b9154, 0, 54435349}*** WARNING: Unable to verify timestamp for ISCTD64.sys*** ERROR: Module load completed but symbols could not be loaded for ISCTD64.sysProbably caused by : ISCTD64.sys ( ISCTD64+9154 )
ISCTD64.sys Intel Smart Connect Technology Driver Info here: http://www.intel.com/p/en_US/support...prod/smrt_cnct
Check w/OEM - Also available at Intel Download Center:https://downloadcenter.intel.com/Sea...mart%20Connect
Features and Requirements for Intel® Smart Connect TechnologyCode:ISCT Intel(R) Smart Connect Intel(R) Smart Connect Kernel Manual Running OK TRUE FALSE 20,480 16,384 0 11/27/2012 1:52:34 PM C:\Windows\system32\drivers\ISCTD64.sys 8,192
Uninstalled that program and the computer sat for 2 days with driver verifier running. I remoted into it last night and started google drive and then the computer BSOD (don't know if drive caused it). Since I was out of office I didn't see the error on the screen and when I got in this morning the computer screen was blank, so I just rebooted. Whocrashed says a microsoft driver, but not which. Attached the dumps.
There was 1 bsod mini dump file debugged and it displayed the misbehaving driver: rt640x64.sys (Realtek RT640 NT Driver)
The reference table that we use has different information about this driver than what is displayed about the driver within the msinfo32. The reference table displays: Realtek NICDRV 8169 PCIe GBE Family Controller driver
So when you open device manager make sure that you click properties then driver details and confirm that it is the Realtek driver rt640x64.sys
Then report into the thread the name used for this driver on device manager.
When you see this driver within device manager > right click properties > driver > update driver
Code:BugCheck C4, {9200d, fffff806264705f0, ffff9d0396c44d80, ffff9d0396c44df8}*** WARNING: Unable to verify timestamp for rt640x64.sys*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys Probably caused by : rt640x64.sys ( rt640x64+1b66a )
rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver http://www.realtek.com.tw/downloads/...&GetDown=false
Code:rt640x64 Realtek RT640 NT Drive Realtek RT640 NT Drive Kernel Manual Running OK TRUE FALSE 4,096 897,024 0 10/7/2016 4:24:19 AM C:\Windows\system32\drivers\rt640x64.sys 8,192
Quote