Windows 10: BSoD's after 10 minutes idle

This has been going on for about a month. After ten minutes idle, I get a random blue screen. 8 passes of memtest yielded no errors. How many of the 42 .dmp files should I send and how should I send them?

Thanks in advance

:)

 

Windows 10 x64 BSOD irql not less or equal

Hi there!

I have Lenovo T460s UltraBook with Windows 10 x64 onboard and the same problem but...

BSOD's shows up in very random times. All my drivers are up to date (updated today from official Lenovo site).

Computer starts normally works fine and... BSOD. Last one was few minutes ago. Computer was idle. I've started Windows after BSOD, logged in and did nothing. After 3 or 4 minutes Windows crashed with BSOD.

All factory diagnostics passed.

Memory dump is here:

https://1drv.ms/u/s!An3BHu_b5TxXiP1kZ9m_ZWe-rJdRaQ

I hope that someone can help me.

Regards

SK

 

BlueScreen (system_service_exception) happening everytime my computer is idle

Everytime my computer is idle it gets a BSOD after a few minutes. It is running Windows 10. I don't think it is releated to sleep beacuse sleep is set to 'Never'. I have updated my NVIDIA drivers.

I uploaded a minidump file: https://db.tt/l00o3Xyo

Thanks for any help with this issue.

Bengt

 

Hello and welcome to TenForums *Smile

Just follow the BSOD Posting Instructions. This will send everything!

 

The folder was empty.
BSOD - Posting Instructions - Windows 10 Forums

 

I tried repeating the process and now it's not outputting a zipped folder at all.

 

Check the operating system:
Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

 

Here it is:

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[===========================96.6%======================== ]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 MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>

 

1) What history if any is there of:
a) hardware problems
b) software problems
c) malware
2) Open administrative command prompt and type: chkdsk /scan
Please post the results of this scan into the thread.
3) make a back up image with Macrium:
Macrium Software | Macrium Reflect Free
4) back up your files
5) create a restore point
6) find a flash drive that you can format
7) create a bootable windows 10 iso: Download Windows 10
8) Plan to perform an in place upgrade repair. You should be able to save files and applications.
Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials

 

It should create a folder called: "%USERPROFILE%\Desktop\TFdebugFiles. It's then supposed to write all the generated log files there then zip that folder to the desktop.

Run it again, but don't press Enter when it's done. Instead, look on your Desktop for a TFdebugFiles folder. See if you can find the files that way and zip them yourself.

 

I built this computer in December. There have been no major hardware, malware, or outstanding software issues as far as I can tell (well, my ram might not be able to clock at the speed it says it can, but it seems stable running below 2133mhz currently). Also, the first time trying the posting tool again just yielded two empty folders before nothing at all on consecutive tries.

Here are the results of the disk check:

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 277504 file records processed.File verification completed. 5875 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 339468 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. 30983 data files processed.CHKDSK is verifying Usn Journal... 43835096 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 243618815 KB total disk space. 53122480 KB in 157852 files. 107328 KB in 30984 indexes. 0 KB in bad sectors. 398199 KB in use by the system. 65536 KB occupied by the log file. 189990808 KB available on disk. 4096 bytes in each allocation unit. 60904703 total allocation units on disk. 47497702 allocation units available on disk.C:\WINDOWS\system32>

 

Upon startup, my desktop yielded two files from the tool. I don't know if they're what you need, but they're in the attached zipped folder.

 

Hi idespisebsods,

Those files are not what is needed.

Please wait until the tool tells it is finished *Smile

 

Okay, for whatever reason, pressing a key to finish and exit out of the script formatted both the folders it outputs? So I just avoided doing that as was suggested a few posts ago.
I'm not illiterate with computers, I swear... :'(

I had to remove a few .dmp files in order to post it, but there are still pleeeenty. I'm also gonna hold off from doing an in place upgrade until I have nothing else to turn to.

 

Hi idespisebsods ,

In the log there were 39 bsod. The most recent 10 were debugged.
In the event log there were many dump file creation failed events so you likely had more than 50 bsod in the past 23 days.
With this many bsod it could be related to memory/MB problems so there will be tests performed to rule in /rule out hardware problems.
The event logs indicated file corruptions especially multiple drivers.
Antivirus software drivers were identified as misbehaving drivers and the software needs to be uninstalled.
Hardware drivers were identified as misbehaving drivers and should be uninstalled and reinstalled.

The results of sfc scannow and dism restore health will be important in consideration of starting the troubleshooting with a windows 10 1703 repair installation. Please post these results early in the troubleshooting.



Open administrative command prompt and type or copy and paste:

1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

2) sfc /scannow

3) dism /online /cleanup-image /restorehealth

4) chkdsk /scan

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread

5) perform windows updates and post any failed KB# with error code into the thead

6) Make sure that there is no over clocking while troubleshooting.

Sometimes there are problems in the bios that produce bsod.

7) To ensure that there are no improper bios settings please reset the bios.

Sometimes there can be failure to boot after resetting the bios.

8) So please make sure your files are backed up.

9) Please make a backup image with Macrium: Macrium Software | Macrium Reflect Free:
Macrium Software | Your image is everything

10) And please create a restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:

How to Clear Your Computers CMOS to Reset BIOS Settings

3 Ways to Reset Your BIOS - wikiHow:3 Ways to Reset Your BIOS - wikiHow

11) Run memtest86+ version 5.01 for at least 8 runs.

This may take many hours so plan to run it overnight.

http://www.memtest.org/When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.

Memory problems. - Microsoft Community

Windows 10 Forums)

12) run one of the SMART tests on your drives:CrystalDiskInfo - Software - Crystal Dew World:
CrystalDiskMark - Software - Crystal Dew World

Software - Crystal Dew World

HD Tune: HD Tune website

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.

13) Uninstall all Nvidia drivers/software

The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your from the NVidia website.
When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download

14) Uninstall: Webroot antivirus using the control panel
Then use the Webroot uninstall tool: Installation Support
Do not reinstall this antivirus software during the troubleshooting
Instead turn on Microsoft Windows defender

15) Uninstall: Intel rapid storage technology using the control panel
reinstall: Downloads for Intel® Rapid Storage Technology (Intel® RST)

16) Uninstall: Intel Pro/1000 Network Adapter driver using device manager
reinstall: Software and Drivers for the Intel® PRO/100 Adapter

17) Uninstall: all Focusrite software FocusriteUSB.sys using device manager
reinstall: USB Audio Interfaces | Focusrite

18) turn off windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials


Code: BugCheck 139, {3, ffff8001e6d0f3d0, ffff8001e6d0f328, 0}Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )[/quote] Code: fffff803`a7985778 fffff809`32ca08d2Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for iaStorA.sys*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys iaStorA+0xa08d2[/quote] Code: iaStorA Intel Chipset SATA RAI Intel Chipset SATA RAI Kernel Boot Running OK TRUE FALSE 4,096 782,336 0 3/17/2017 10:32:24 AM C:\WINDOWS\system32\drivers\iaStorA.sys 4,096[/quote] iaStorA.sys Intel RST (Rapid Storage Technology) driver Drivers & Software XP
Code: BugCheck A, {40, 2, 1, fffff803a4f05c41}Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+31 )[/quote] Code: BugCheck A, {34, 2, 0, fffff8025ff2ac29}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: ffffac00`4a118128 fffff80e`6954ac5cUnable to load image \SystemRoot\System32\drivers\WRkrn.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for WRkrn.sys*** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys WRkrn+0xac5c[/quote] Code: WRkrn WRkrn WRkrn Kernel Boot Running OK TRUE FALSE 8,192 65,536 0 5/25/2017 12:49:29 PM C:\WINDOWS\system32\drivers\WRkrn.sys 8,192[/quote] WRkrn.sys Webroot SecureAnywhere Essentials driver
Webroot SecureAnywhere Anti-virus driver http://www.webroot.com/En_US/consumer.html


Code: ffffac00`4a117338 fffff80e`6a58c565Unable to load image \SystemRoot\system32\DRIVERS\e1d65x64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for e1d65x64.sys*** ERROR: Module load completed but symbols could not be loaded for e1d65x64.sys e1d65x64+0x1c565[/quote] Code: e1dexpress Intel(R) PRO/1000 PCI Intel(R) PRO/1000 PCI Kernel Manual Running OK TRUE FALSE 4,096 421,888 0 8/13/2015 5:14:29 AM C:\WINDOWS\system32\DRIVERS\e1d65x64.sys 4,096[/quote] e1d65x64.sys Intel Pro/1000 Network Adapter driver Drivers & Software

Code: BugCheck 3B, {c0000005, fffff802834b7cd7, ffffac004a117cf0, 0}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: BugCheck 4E, {99, 10a393, 2, e0001a0001a8948}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: BugCheck 1A, {41792, ffff860000004118, 1000, 0}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: ffffc281`51a6b830 fffff808`a0b94c00Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for iaStorA.sys*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys iaStorA+0x84c00[/quote] Code: BugCheck 1000007E, {ffffffffc0000005, fffff8031ad136a6, ffffc28151a6c5a8, ffffc28151a6bdf0}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: fffff800`59b85628 fffff80c`ddde6ce3Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2386fda73b467ac8\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+0x1c6ce3[/quote] nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops


Code: fffff800`59b85158 fffff80c`dbeb6ae1Unable to load image \SystemRoot\System32\drivers\FocusriteUSB.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSB.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSB.sys FocusriteUSB+0x6ae1[/quote] Code: FocusriteUSB Focusrite USB Focusrite USB Kernel Manual Running OK TRUE FALSE 4,096 61,440 0 6/8/2017 7:58:59 AM C:\WINDOWS\system32\drivers\FocusriteUSB.sys 4,096 FocusriteUSB Focusrite USB Audio Focusrite USB Audio Kernel Manual Running OK TRUE FALSE 0 24,576 0 6/8/2017 7:58:42 AM C:\WINDOWS\system32\drivers\FocusriteUSBAudio.sy 4,096 FocusriteUSB Focusrite USB MIDI Focusrite USB MIDI Kernel Manual Running OK TRUE FALSE 0 20,480 0 6/8/2017 7:58:45 AM C:\WINDOWS\system32\drivers\FocusriteUSBMidi.sys 4,096 FocusriteUSB USB Audio Root USB Audio Root Kernel Manual Running OK TRUE FALSE 4,096 65,536 0 6/8/2017 7:58:52 AM C:\WINDOWS\system32\drivers\FocusriteUSBSwRoot.s 4,096[/quote]

Code: BugCheck A, {c0, 2, 0, fffff800570843ae}Probably caused by : afd.sys ( afd!AfdCompletePollIrp+8b )[/quote] Code: ffff9180`75286a48 fffff808`abf5da01Unable to load image \SystemRoot\System32\drivers\WRkrn.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for WRkrn.sys*** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys WRkrn+0xda01[/quote] WRkrn.sys Webroot SecureAnywhere Essentials driver
Webroot SecureAnywhere Anti-virus driver Virus Protection Software Programs for All of Your Devices | Webroot

Code: BugCheck 3B, {c0000005, fffff8014b987154, ffff918075284fc0, 0}Probably caused by : memory_corruption[/quote] Code: BugCheck 3B, {c0000005, fffff800194b20ff, ffff9901a57cead0, 0}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\config\DRIVERS' was corrupted and it has been recovered. Some data might have been lost.[/quote] Code: The following file necessary for Windows startup was corrupt: d:\windows\system32\ntoskrnl.exe[/quote] Code: The following file necessary for Windows startup was corrupt: d:\windows\system32\drivers\wrkrn.sys[/quote] Code: The following file necessary for Windows startup was corrupt: D:\TDI.SYS[/quote] Code: The following file necessary for Windows startup was corrupt: D:\NDIS.SY[/quote] Code: The following file necessary for Windows startup was corrupt: d:\werkernel.sys[/quote] Code: The following file necessary for Windows startup was corrupt: d:\windows\system32\drivers\partmgr.sys[/quote] Code: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Dump file creation failed due to error during dump creation.[/quote]