Windows 10: BSOD while playing or idle

Hello,

i build this PC in december, and everything was runing fine until like 2 months ago. Getting random BSOD while playing some of them happend even when idle. The most recent ones are from today playing Diablo 3, got 3 BSOD in a span of an hour. Getting about 3-4 different stop codes. My suspicion was something GPU driver related by the looks of it. Tried completly uninstall GPU drivers using DDU, tried reseating GPU, tried reinstaling MB drivers. Nothing helped.

Thanks for help.

PC spec:
CPU: Intel Core i5-6600K OC to 4,4GHz
GPU: EVGA GeForce GTX 1070 SC GAMING ACX 3.0, 8GB GDDR5
RAM: Corsair Vengeance LPX Black 16GB (2x8GB) DDR4 3000
MB: GIGABYTE GA-Z170-HD3 - Intel Z170
PSU: EVGA SuperNOVA 550 G2 550W
SSD: Samsung EVO 840 120gb - only old part, about 3y old
HDD: WD black 2tb
OS: W10 home 64bit

:)

 

System restarts after sometime without user interaction.

I started the computer in safe mode , and computer ran with a BSOD .

now how am i going to find what's responsible for the BSOD while computer is idle?

 

Surface BSOD while idle

Thanks Rob. I'll try what is suggested an see if that resolves my problem.

Due to the randomness of the error I'll wait a week before posting a result.

Regards

Matt

 

Hi Odyn,

The logs are in a foreign language. If possible please repost the logs using English so that we can troubleshoot the contents.


Code: BugCheck D1, {fffff8036cfcff14, ff, 10, fffff8036cfcff14}Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+23d )[/quote] Code: BugCheck 7F, {8, fffff8026e466e70, 1, fffff8026c6f511a}Probably caused by : memory_corruption[/quote] Code: BugCheck D1, {41, 2, 1, fffff800f60727fe}Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpCopyInputReportToUser+e )[/quote] HIDCLASS.SYS Hid Class Library Windows Update
Code: BugCheck A, {8, 2, 0, fffff80288674a13}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote]
Code: BugCheck F7, {3000cceb8e21eb35, cceb8e21eb35, ffff331471de14ca, 0}Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )[/quote]
Code: BugCheck A, {40, d, 0, fffff8005f2efcc4}Probably caused by : ntkrnlmp.exe ( nt!KeClockInterruptNotify+4a4 )[/quote] Code: BugCheck 3B, {c0000005, ffff8115f485c046, ffff8280b239cee0, 0}Probably caused by : win32kbase.sys ( win32kbase!DirectComposition::CConnection::KeepOrDeferBatches+85ff6 )[/quote] Code: BugCheck D1, {fffffffffffffff1, 2, 0, fffff803f99e1265}*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption[/quote] Code: BugCheck A, {aa, ff, 0, fffff802be2ee686}Probably caused by : ntkrnlmp.exe ( nt!KiFindNextTimerDueTime+296 )[/quote] Code: BugCheck 3B, {c000001d, ffff993028060d07, ffffa000c0579550, 0}*** WARNING: Unable to verify checksum for win32kfull.sysProbably caused by : memory_corruption[/quote]

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

 

well yea, im using Czech version of W10, so i guess they generated in czech, can i somehow generate them in english ?

 

There may be language choices on windows 10 that you can use to produce event logs in English.

 

okay, switched to english, hope it help

version 1703, Build 15063.447

Code: Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. 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> C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\WINDOWS\system32>chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 496384 file records processed. File verification completed. 16579 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 749642 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. 126630 data files processed. CHKDSK is verifying Usn Journal... 37424712 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 116639743 KB total disk space. 57600736 KB in 295004 files. 203652 KB in 126631 indexes. 0 KB in bad sectors. 615003 KB in use by the system. 65536 KB occupied by the log file. 58220352 KB available on disk. 4096 bytes in each allocation unit. 29159935 total allocation units on disk. 14555088 allocation units available on disk. C:\WINDOWS\system32>[/quote]

 

1) Run memtest86+ version 5.01 for at least 8 runs. This may take many hours so plan to run it overnight.

Memtest86+ - Advanced Memory Diagnostic Tool

Memory problems. - Microsoft Community
When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.


2) Windows driver verifier is a tool which stimulates drivers to find misbehaving drivers. The misbehaving drivers produce bsod's. The windows driver verifier will repetitively produce bsod until it is turned off or until all misbehaving drivers are fixed.

Turning on windows driver verifier is easy as it is part of windows 10. In the left lower corner search typing verifier will produce a pop up for windows driver verifier that needs to be customized.

Turning off windows driver verifier is a lot harder as you must be able to open the windows recovery or advanced troubleshooting menu and navigate to startup options (not startup repair). Once in startup options, click restart, and select #6 safe mode with command prompt. Then type: verifier /reset
That should enable you to turn off windows driver verifier and reboot to the desk top.

Once you are back on the desk top you will process the bsod mini dump files with two software programs: Bluescreenview (Blue screen of death (STOP error) information in dump files. )and Whocrashed ( Resplendence Software - WhoCrashed, automatic crash dump analyzer). They each may have information that adds value to deciphering the minidump files. After the driver is identified the driver is uninstalled and a new one is downloaded from the computer manufacturers web site.

There are two main methods in using windows driver verifier: Choice 1) after a driver is uninstalled a new one is immediately installed and windows driver verifier is restarted to test the new driver. Choice 2) windows driver is run to find all of the misbehaving drivers before any are reinstalled. The choice 1 versus 2 is personal preference. The end result should be the same. All misbehaving drivers should be identified and then uninstalled and reinstalled.

Once there are no more bsod, windows driver verifier is run for an additional 36 hours. If no bsod occurs then windows driver verifier is turned off and the troubleshooting and preventative maintenance has been completed.

Whenever there is a bsod you will update the zip file or create a new one so that we can process the minidumps and guide you in the troubleshooting.

Sometimes software applications and hardware are producing bsod and the misbehaving software sometimes can be completely removed and an alternative software can be installed. For example using VLC player instead of Cyberlink or using WIndows defender instead of bitdefender.

To practice navigating the windows advanced troubleshooting menu:
1) click win + r keys simultaneously
2) type or copy and paste: shutdown /r /o /f /t 00
3) the computer will reboot to the windows recovery or advanced troubleshooting menu.

Before using windows driver verifier all files must be backed up. Use Macrium (Macrium Software | Macrium Reflect Free) to create an image. A new restore point will be created. And you must be comfortable navigating the windows advanced troubleshooting menu.

For the Memtest86+ at least 8 runs are needed as lower runs may produce false negatives. It sometimes takes run into the teens to find ram/dim problems.
Once the memtest has completed plan to use windows driver verifier to find misbehaving drivers.

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

To setup and start using Windows driver verifier use the settings in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

 

Hello, memtest completed fine

Attachment 141758

with verifier i was unable to even boot, fist culprit was ScpVbus.sys, i thik its because of use DS4windows for my dualshock 4 controller, tryed reinstall scp virtual bus driver to no avail, so i let it uninstaled , next was dukems.sys, which is driver for my mouse corsair M95, after removing that i was able to boot, only to get another BSOD when to try run speedfan, ill let verifier run till morning to see what happen, now i go to sleep

 

The attachment displayed: Invalid Attachment specified.
Please find another method to post the memtest image.

Code: Probably caused by : ScpVBus.sys ( ScpVBus+b048 )[/quote]

ScpVBus.sys Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver http://forums.pcsx2.net/Thread-XInpu...6161#pid186161
Code: eamonm.sys[/quote]

eamonm.sys ESET Amon driver Support: ESET Knowledgebase
Downloads: Downloads for Home
Code: BugCheck D1, {fffff8036cfcff14, ff, 10, fffff8036cfcff14}Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+23d )[/quote]

ntkrnlmp.exe see ntoskrnl.exe Windows Update
Code: intelppm[/quote]

intelppm.sys Intel Processor driver Drivers & Software also at
Code: em018_64.dll[/quote]

em018_64.dat ESET Smart Security Support: ESET Knowledgebase
Downloads: Downloads for Home
Code: epfw+0x170f[/quote]

epfw.sys ESET Support: ESET Knowledgebase
Downloads: Downloads for Home
Code: ehdrv.sys[/quote]

ehdrv.sys ESET Support: ESET Knowledgebase
Downloads: http://www.eset.com/int/download/home/
Code: epfw.sys[/quote]

epfw.sys ESET Support: http://kb.eset.com/
Downloads: http://www.eset.com/int/download/home/
Code: BugCheck D1, {41, 2, 1, fffff800f60727fe}Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpCopyInputReportToUser+e )[/quote]

HIDCLASS.SYS Hid Class Library Windows Update
Code: USBXHCI[/quote]

USBXHCI.sys USB XHCI Driver
Info - http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx Windows Update
Code: dxgmms2[/quote]

dxgmms2.sys DirectX Graphics MMS
OS: Win10TP Windows Update
Code: hidusb[/quote]

hidusb.sys USB Miniport Driver for Input Devices Windows Update
Code: HIDCLASS[/quote]

HIDCLASS.SYS Hid Class Library Windows Update
Code: storahci[/quote]

storahci.sys MS AHCI Storport Min Windows Update
Code: BugCheck C4, {2000, fffff80151381435, 0, 30444653}*** WARNING: Unable to verify timestamp for speedfan.sys*** ERROR: Module load completed but symbols could not be loaded for speedfan.sysProbably caused by : memory_corruption[/quote] speedfan.sys SpeedFan http://www.almico.com/sfdownload.php
Code: speedfan[/quote] Code: BugCheck C4, {2000, fffff80c3b43b048, 0, 56706353}*** WARNING: Unable to verify timestamp for ScpVBus.sys*** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sysProbably caused by : ScpVBus.sys ( ScpVBus+b048 )[/quote] ScpVBus.sys Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver http://forums.pcsx2.net/Thread-XInpu...6161#pid186161
Code: eamonm.sys[/quote] eamonm.sys ESET Amon driver Support: http://kb.eset.com/
Downloads: http://www.eset.com/int/download/home/
Code: BugCheck C4, {2000, fffff8013381a568, 0, 62527050}*** WARNING: Unable to verify timestamp for DUKEMS.sys*** ERROR: Module load completed but symbols could not be loaded for DUKEMS.sysProbably caused by : memory_corruption[/quote] DUKEMS.sys Corsair M95 Gaming Mouse http://www.corsair.com/en/gaming-per...lack.html#tab8
Code: rt640x64.sys[/quote] rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver http://www.realtek.com.tw/downloads/...&GetDown=false
Code: hidusb[/quote] hidusb.sys USB Miniport Driver for Input Devices Windows Update
Code: DUKEMS[/quote] Code: RTKVHD64.sys[/quote] RTKVHD64.sys Realtek High Definition Audio Function Driver http://www.realtek.com.tw/downloads/...Level=3&Conn=2

In the event log there was a startup repair.
Please indicate if you are having any difficulty using windows driver verfier.
Is the verifier /reset command turning off windows driver verifier?

When were you using Eset antivirus?

1) Uninstall: SCVPBUS.sys
reinstall: XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller


2) Uninstall: ESET antivirus using the uninstall tool: Uninstall ESET manually using the ESET uninstaller toolESET Knowledgebase

Do not reinstall: Only use Windows defender during the troubleshooting


3) Uninstall the Intel driver using the control panel: INTELPPM.sys
reinstall: Drivers & Software


4) Uninstall: USBXHCI.sys
Click Start, and then click Run.
In the Open box, type devmgmt.msc, and then click OK. Device Manager opens.
Expand Universal Serial Bus controllers.
Note You might have to scroll down the list to find this item.
Right-click the affected USB Root Hub, and then click Uninstall to remove it.
Restart the computer. After the computer starts, Windows will automatically scan for hardware changes and reinstall all the USB root hubs that you uninstalled.




5) Uninstall: DUKEMS.sys
If you plan to continue using this gaming mouse Reinstall: Vengeance® M95 Performance MMO and RTS Laser Gaming Mouse — Gunmetal Black



6) Uninstall: SPEEDFAN.sys by uninstall the software
reinstall: during the troubleshooting do not reinstall
consider other temperature monitoring software:
Speccy - Free Download - Piriform: Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID


7) Uninstall: all Realtek software and drivers incuding rt640x64.sys and RTKVHD64.sys
Reinstall: Realtek

8) Please post using a different method the memtest86+ version 5.01 results.