New
#1
Another BSOD/freezing case -Thinkpad X390
Hello,
Hoping to get some help with a long-lasting BSOD/freezing/shut-down issue--I believe these problems started with the Win 10 update from last Fall, but I've taken all the updates since, as well as fiddled with drivers and testing, and am still having problems. I decided to do a clean install of Windows, and fairly quickly got a BSOD, so I went down the rabbit hole again (see below). My computer froze several times this morning, but did not BSOD. It occurred to me that I enabled a desktop background slideshow with a one-minute refresh interval, which makes me very suspicious of the graphics card, but it tests good, and multiple attempts at driver's haven't helped (had played with this before the re-build also). Prior to the rebuild, I would say the bigger issue over BSOD was the machine would reboot when put to sleep (with lid), with the occassionaly BSOD; the freezing up with no BSOD is much more prevalent now (I turned off the slideshow, and am able to operate, at least for now). It seems like every failure results in this error:
Kernel error 41 70368744177664, 2
In researching the error, I tried all of the following, and problem more, but these are things, roughly in order, that I tried rebuilding:
- Fresh install of Win10 (non-Lenovo)
- Set all advanced power settings (sleep, hard drive, hibernate, monitor) to never
- Turned off fast startup
- Made closing lid hibernate instead of sleep--seems to have solved the reboot on sleep problem?
- Disabled the biometric setting in bios (was already disabled); latest BIOS
- Disabled Lenovo fast start (in services)
- Turned off IPV6 in the wi-fi adapter
- Verified drivers were reasonably current, but did not replace all
- Manually updated SSD driver, but may have been okay--was looking at wrong device initially
- Manually updated wi-fi driver directly from Intel over the Lenovo one (Intel AC-9560)
- Ran hardware tests for everythiny--no issues
- Ran deeper hardware tests on memory, processor, ssd, video card, motherboard, wi-fi--no issues
- Manually ran the "tuneup" commands (scanhealth, restore health, sfc, chkdsk)
- There was a repair when running sfc /scannow at one point--no idea what it was (possibly have the CBS log)
- There were also chkdsk errors that were fixed, but only when chckdsk wouldn't run, and then ran at startup
- Ran the "tuneup" batch file recommended on this site--doesn't seem like there are any errors (will try to post below)
- Changed the "on battery" wi-fi adapter power saving mode to maximum performance
- Used Intel update tool to update the UHD 620 and bluetooth drivers (manual attempt to update UHD 620 had failed)
- Switched to 2.4G wi-fi band
Machine details:
Lenovo X390
Intel Core i5-8265U
8 GB RAM
Samsung SSD 970 Evo Plus 1TB
Intel AC 9560 wireless card
Windows 10 Pro Build 19042
Any ideas where to go from here? Thanks in advance.
- - - Updated - - -Code:########################################################### # The following commands will be run in sequence. # # The first 5 will take quite a while to run, be patient. # ########################################################### sfc /scannow dism /online /cleanup-image /scanhealth dism /online /cleanup-image /restorehealth sfc /scannow chkdsk /scan wmic recoveros get autoreboot wmic recoveros set autoreboot = false wmic recoveros get autoreboot wmic recoveros get DebugInfoType wmic recoveros set DebugInfoType = 7 wmic recoveros get DebugInfoType wmic pagefile list /format:list wmic Computersystem where name="X390" get AutomaticManagedPagefile wmic Computersystem where name="X390" set AutomaticManagedPagefile=True wmic Computersystem where name="X390" get AutomaticManagedPagefile bcdedit /enum {badmemory} C:\Windows\system32>sfc /scannow Beginning 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 /scanhealth Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19042.844 [==========================100.0%==========================] No component store corruption detected. The operation completed successfully. C:\Windows\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19042.844 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\Windows\system32>sfc /scannow Beginning 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>chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 349440 file records processed. File verification completed. Phase duration (File record verification): 4.92 seconds. 7651 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.96 milliseconds. Stage 2: Examining file name linkage ... 256 reparse records processed. 486752 index entries processed. Index verification completed. Phase duration (Index verification): 13.57 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 891.94 milliseconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 2.17 milliseconds. 256 reparse records processed. Phase duration (Reparse point and Object ID verification): 4.65 milliseconds. Stage 3: Examining security descriptors ... Security descriptor verification completed. Phase duration (Security descriptor verification): 75.46 milliseconds. 68657 data files processed. Phase duration (Data attribute verification): 1.77 milliseconds. CHKDSK is verifying Usn Journal... 38697648 USN bytes processed. Usn Journal verification completed. Phase duration (USN journal verification): 206.19 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 976129387 KB total disk space. 289920168 KB in 269814 files. 161124 KB in 68658 indexes. 0 KB in bad sectors. 487043 KB in use by the system. 65536 KB occupied by the log file. 685561052 KB available on disk. 4096 bytes in each allocation unit. 244032346 total allocation units on disk. 171390263 allocation units available on disk. Total duration: 19.68 seconds (19686 ms). C:\Windows\system32>wmic recoveros get autoreboot AutoReboot FALSE C:\Windows\system32>wmic recoveros set autoreboot = false Updating property(s) of '\\X390\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition3"' Property(s) update successful. C:\Windows\system32>wmic recoveros get autoreboot AutoReboot FALSE C:\Windows\system32>wmic recoveros get DebugInfoType DebugInfoType 7 C:\Windows\system32>wmic recoveros set DebugInfoType = 7 Updating property(s) of '\\X390\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition3"' Property(s) update successful. C:\Windows\system32>wmic recoveros get DebugInfoType DebugInfoType 7 C:\Windows\system32>wmic pagefile list /format:list AllocatedBaseSize=1920 CurrentUsage=15 Description=C:\pagefile.sys InstallDate=20210303081527.017979-480 Name=C:\pagefile.sys PeakUsage=17 Status= TempPageFile=FALSE C:\Windows\system32>wmic Computersystem where name="X390" get AutomaticManagedPagefile AutomaticManagedPagefile TRUE C:\Windows\system32>wmic Computersystem where name="X390" set AutomaticManagedPagefile=True Updating property(s) of '\\X390\ROOT\CIMV2:Win32_ComputerSystem.Name="X390"' Property(s) update successful. C:\Windows\system32>wmic Computersystem where name="X390" get AutomaticManagedPagefile AutomaticManagedPagefile TRUE C:\Windows\system32>bcdedit /enum {badmemory} RAM Defects ----------- identifier {badmemory} C:\Windows\system32>Echo off ################################################################################### # How to capture batch file data and post in your thread in the BSOD forum # # # # Batch files and instructions for use in BSOD debugging[Part Two-Four] # # # # Press [V] to visit the above web page for detailed instructions. # # Press [C] to close this window. # ###################################################################################
I just ran the "V2 log collector" if that helps--file attached.
Quote
. Attaching a screen shot of device manager.