Windows 10: BSODs playing Overwatch, multiple codes

9/16 dump caused by ISCTD64.SYS:
Code: BugCheck C9, {6, 103, ffffaa848cf62d80, 0} Unable to load image \SystemRoot\System32\drivers\ISCTD64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ISCTD64.sys *** ERROR: Module load completed but symbols could not be loaded for ISCTD64.sys[/quote] It's another old driver, one of many left on your PC:
Code: 2008/09/24 01:28:20 PM C:\WINDOWS\system32\drivers\SiSRaid2.sys 2008/10/01 04:56:04 PM C:\WINDOWS\system32\drivers\sisraid4.sys 2009/11/18 11:39:04 AM C:\WINDOWS\system32\drivers\jnprvamgr.sys 2011/04/11 01:48:16 PM C:\WINDOWS\system32\drivers\iaStorV.sys 2011/05/18 03:07:24 AM C:\WINDOWS\system32\drivers\dc3d.sys 2011/09/21 04:42:57 AM C:\WINDOWS\system32\drivers\asahci64.sys 2012/02/27 04:58:49 AM C:\WINDOWS\system32\drivers\iusb3hcs.sys 2012/05/03 02:56:17 PM C:\WINDOWS\system32\DRIVERS\GEARAspiWDM.sys 2012/07/02 05:14:58 PM C:\WINDOWS\system32\drivers\HECIx64.sys 2012/07/03 09:59:39 PM C:\WINDOWS\system32\drivers\libusbK.sys 2012/10/18 05:19:45 AM C:\WINDOWS\system32\drivers\jnprva.sys 2012/11/26 06:02:51 PM C:\WINDOWS\system32\drivers\stexstor.sys 2012/11/27 01:52:34 PM C:\WINDOWS\system32\drivers\ISCTD64.sys 2012/12/11 03:21:44 PM C:\WINDOWS\system32\drivers\amdsbs.sys 2013/01/21 01:00:28 PM C:\WINDOWS\system32\drivers\vstxraid.sys 2013/03/15 06:39:38 PM C:\WINDOWS\system32\drivers\lsi_sss.sys 2013/03/26 04:36:54 PM C:\WINDOWS\system32\drivers\HpSAMD.sys 2013/05/05 04:31:26 PM C:\WINDOWS\system32\drivers\ScpVBus.sys 2013/06/03 05:02:39 PM C:\WINDOWS\system32\drivers\megasr.sys 2014/03/16 05:07:36 AM C:\WINDOWS\system32\drivers\bcmfn2.sys 2014/03/18 07:20:53 PM C:\WINDOWS\system32\DRIVERS\LHidEqd.Sys 2014/03/18 07:20:55 PM C:\WINDOWS\system32\DRIVERS\LEqdUsb.Sys 2014/03/18 07:21:03 PM C:\WINDOWS\system32\DRIVERS\LHidFilt.Sys 2014/03/18 07:21:03 PM C:\WINDOWS\system32\DRIVERS\LMouFilt.Sys 2014/04/21 01:28:42 PM C:\WINDOWS\system32\drivers\nvraid.sys 2014/04/21 01:34:03 PM C:\WINDOWS\system32\drivers\nvstor.sys 2014/04/22 02:21:41 PM C:\WINDOWS\system32\drivers\vsmraid.sys 2014/05/23 03:39:04 PM C:\WINDOWS\system32\drivers\mvumis.sys 2014/09/09 07:13:01 AM C:\WINDOWS\system32\DRIVERS\IntcDAud.sys 2014/10/30 01:38:20 PM C:\WINDOWS\system32\DRIVERS\jnprns.sys[/quote] At this point I recommend you backing up all your data then doing a Clean Install of Windows 10. I think there is too much old stuff left from when you upgraded.

Follow this tutorial: Windows 10 - Clean Install

After the install, repeatedly run Windows Update until all updates are downloaded and installed.

 

Hi Ztruker,

Sorry for the lag in communications; I cleanly reinstalled Windows 10 this past Sunday, and I've played a couple games since then. So far, no BSODs, though Overwatch itself did crash once (that might be an Overwatch problem, I'm not sure). I'll keep testing it over the next week or two, and if there are no issues, I'll mark the thread as solved.

Thanks!

 

Okay, thanks for letting me know.

 

Looks like I spoke too soon; I just got a BSOD again. I assume this will be another one of those uninformative ones, since I didn't have driver verifier running, but here's the dump. Should I switch driver verifier on again?

 

Ths only problem indicated is for your Nvidia card:
Code: ffff9901`37c85168 fffff80f`f89136b8Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d3851cb7c8216f9e\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+0x7d36b8[/quote] Looks like you have the latest one available, 372.90.

I noticed ISCTD64.sys is still at the same old date as before. I see a 2015 version on their web site, might want to give that a try:

Intel® Smart Connect Technology

Code: Drivers and Downloads

• Intel® Smart Connect Technology
  • Date: 25-Aug-2014
  • Version: 5.0.10.2850 (Latest)
  • OS: Windows 7*, Windows 8*, Windows 8.1*

[/quote]

 

Strange, when I follow that link, it only shows me the one from August 2014. I also did some searching online, and it seems like support for Smart Connect Technology has been discontinued for Windows 10. Also, when I check my list of programs and features, Intel Smart Connect Technology isn't listed (and I never installed it myself in the first place, though Windows may have tried to install it on its own). Is it hiding somewhere, and if so, do you know how I could see it?

 

Yes, support dropped as of some time in 2015 and no Win 10 driver.

All searches I've done indicate using Control Panel, Programs and Features to remove it, but if it's not listed then that won't work.

It is being loaded though: Code: fffff801`08fd0000 fffff801`08fe1000 ISCTD64 \SystemRoot\System32\drivers\ISCTD64.sys[/quote] You could try searching the registry via regedit for ISCTD64.sys. If it's found, delete it.
Make sure you do a registry backup first. or at least export the key before deleting it.

 

I removed the registry key, which didn't seem to cause any instabilities. A couple days later, though, I got a BSOD trying to shut my system down (attached).

Unrelated, but I just found that I have a Windows.old folder on my drive for some reason. Isn't that a folder that data from an old Windows installation is moved to? I know for a fact that this was a clean install because this is an entirely new hard drive; where could this folder have come from?

 

Another one today, playing a game, attached. This one had the error "page fault in a non-paged area".

 

Same as some of the other dumps. memory_corruption_large and nvida

Code: MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: LARGE FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE BUCKET_ID: MEMORY_CORRUPTION_LARGE PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE[/quote] Code: ffff9c01`ecc0c6f8 fffff80c`8e7478f7Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_674733509ab83d72\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+0x1c78f7[/quote] I just noticed you have memory modules in slot 2 and 3 (starting with 0) but the manual says for 2 memory modules you should use 0 and 2 or 1 and 3 (A1 and B1 or A2 and B2). Might want to change that and see what happens.
Code: 1. If you want to install two memory modules, for optimal compatibility and reliability, it is recommended to install them in the slots: DDR3_ A1 and DDR3_B1, or DDR3_A2 and DDR3_B2. 2. If only one memory module or three memory modules are installed in the DDR3 DIMM slots on this motherboard, it is unable to activate Dual Channel Memory Technology. 3. If a pair of memory modules is NOT installed in the same Dual Channel, for example, installing a pair of memory modules in DDR3_A1 and DDR3_A2, it is unable to activate Dual Channel Memory Technology. 4. It is not allowed to install a DDR or DDR2 memory module into DDR3 slot; otherwise, this motherboard and DIMM may be damaged. 5. Some DDR3 1GB double-sided DIMMs with 16 chips may not work on this motherboard. It is not recommended to install them on this motherboard. 6. For optimal compatibility and stability while overclocking memory frequency, it is recommended to install one memory module on DDR3_B2 slot or two memory modules on DDR3_A2 and DDR3_ B2 slots.[/quote]

 

Ah, that's interesting. I think I had them in slots 0 and 1 at first, then switched to slots 2 and 3 to see if it would solve the BSOD problem. I'll set them in slots 1 and 3 and report back.

 

Looks like I'm still getting BSODs, this time while watching a video online. Here's the set of dumps, but it's another Memory management code.

 

Yup, another Bugcheck 1A Memory_Management.

Let's give verifier one more shot. If othing after 24 ours we'll try GPU and CPU stress tests.

 

Here's a BSOD that just happened when I put the computer to sleep (driver verifier should have been running at this time). I didn't realize that it happened, so I didn't see the bugcheck code.

 

That one is different, ISCTD64.sys:
Code: BugCheck C9, {6, 103, ffff858fbf510010, 0} Unable to load image \SystemRoot\System32\drivers\ISCTD64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ISCTD64.sys *** ERROR: Module load completed but symbols could not be loaded for ISCTD64.sys Probably caused by : ISCTD64.sys[/quote] That belongs to Intel(R) Smart Connect which is very old: Tue Nov 27 14:52:34 2012

There is one from 2015 available on the web site:
10/15/2015
Windows® 10 64bit
1.11MB Intel Smart Connect Utility ver:1.0.7
ASRock > Z77 Extreme4

You could also just disable ot uninstall it as it's not required.