Help Figure Out Why System Crashing (windows 10)

Occasionally my system will crash without a blue screen or any other information. It will simply reboot.

The latest time was 3/4 at 6:43 AM after pulling the computer out of sleep.

Given that there is no BSOD information to go off, I would like your help in figuring out how to get the right information and fix this issue

Thanks!

 

Download this program.
WhoCrashed Free - http://www.majorgeeks.com/files/details/whocrashed_free_home_edition.html
Save the log and upload it.

 

Attaching the file - it didn't log the ones from 3/4 though

 

From the log...

Intel Driver Update Utility.
http://www.majorgeeks.com/files/details/intel_driver_update_utility.html

DriverEasy.
http://www.majorgeeks.com/files/details/drivereasy.html

 

Turn off W10's ability to install hardware drivers, it's still less than perfect.

Are you really using the CPU graphics (on a 'gaming' motherboard)? If so, use the Intel updater already linked by Eldon. If not, disable the Intel gfx from within the BIOS/UEFI and Windows Device Manager and use the add-in card.

Driver updater software is also variable, I wouldn't use any.

Take a read of an article by HTG and the comments.

If you want a deeper dig into the crashes, copy the crash dumps to your Desktop then zip and attach them here. For even more clues and a better chance to find out what's going on, carefully read and follow the info here, again, zip and attach the files to a reply here.

 

I have disabled W10 hardware drivers update.

I disabled the intel graphics card in BIOS; no longer present in windows device manager.

I've attached the SysnativeFileCollection report; PERFMON still running, will update post tomorrow

· OS - Windows 10, insider build 11099
· x64
· Windows 10
· full retail version
· ~1 year hardware
· ~ half a year old OS install

· i5-4690
· GTX 970
· MB GIGABYTE|GA-H97-GAMING 3 H97 ATX
· PSU EVGA|750W 120-G1-0750-XR RT

 

The only 'missing' BSOD/bugcheck I can find any reference to is of a LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys
The best troubleshooting for this that I know of is here. It's possible that the cause was other drivers/modules hogging CPU time, maybe at a higher CPU priority as well, that triggered a delay in data transfer to the GPU.

Now that you've successfully removed the Intel gfx from the equation, the only dump file is probably irrelevant, other than useful for listing drivers that were running at the time. The inability of the debugger to verify the Intel graphics driver might point to *something* (likely a 'bad' driver) causing memory corruption (corruption within memory space, rather than any physical memory fault).

Code:

Debug session time: Thu Feb 25 04:22:54.898 2016 (UTC + 0:00)
Loading Dump File [C:\Users\Me\SysnativeBSODApps\022416-10187-01.dmp]
Built by: 11099.1000.amd64fre.rs1_release.160109-1156
System Uptime: 5 days 14:27:35.688
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+3c90d )
BugCheck A, {ffffe000274b8290, f, 0, fffff801b4126dc5}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Bugcheck code 0000000A
Arguments:
Arg1: ffffe000274b8290, memory referenced
Arg2: 000000000000000f, IRQL
Arg3: 0000000000000000, bitfield :
   bit 0 : value 0 = read operation, 1 = write operation
   bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801b4126dc5, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  AV_igdkmd64!Unknown_Function
MaxSpeed:  3500
CurrentSpeed: 3500
BiosVersion = F5
BiosReleaseDate = 06/28/2014
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H97-Gaming 3

*** 3rd PARTY DRIVER LIST (for info only at this stage) ***

Code:

IntcDAud.sys  Mon Nov 16 09:12:19 2015 (56499DF3)
MBfilt64.sys  Fri Jul 31 04:40:32 2009 (4A7267B0)
NEOFLTR_808_33771.SYS  Wed Dec 24 21:01:17 2014 (549B299D)
Netwbw02.sys  Tue Jan 28 18:59:26 2014 (52E7FE0E)
NvStreamKms.sys  Wed Dec  9 01:23:38 2015 (5667829A)
RTKVHD64.sys  Wed Jul 29 12:59:49 2015 (55B8C035)
ScpVBus.sys  Sun May  5 22:31:26 2013 (5186CFAE)
TeeDriverW8x64.sys  Tue Jul  7 18:43:32 2015 (559C0FC4)
apmwin.sys  Fri Nov  7 12:16:57 2014 (545CB839)
ctxusbm.sys  Fri Jun 12 07:28:15 2015 (557A7BFF)
gpt_loader.sys  Fri Nov  7 12:17:23 2014 (545CB853)
gzflt.sys  Mon Apr 22 11:21:00 2013 (51750F0C)
hfsplus.sys  Fri Nov  7 12:15:15 2014 (545CB7D3)
hfsplusrec.sys  Fri Nov  7 12:16:01 2014 (545CB801)
ibtusb.sys  Thu Nov 12 19:47:13 2015 (5644ECC1)
igdkmd64.sys  Wed Feb  3 02:18:16 2016 (56B16368)
intelppm.sys  Sat Jan  9 22:31:25 2016 (56918A3D)
lvrs64.sys  Wed Oct  7 09:27:59 2009 (4ACC510F)
lvuvc64.sys  Wed Oct  7 09:28:44 2009 (4ACC513C)
mbam.sys  Wed Sep  3 18:50:25 2014 (540754E1)
mounthlp.sys  Fri Nov  7 12:17:32 2014 (545CB85C)
nvhda64v.sys  Mon Sep 21 10:44:17 2015 (55FFD171)
nvlddmkm.sys  Wed Dec 16 14:03:30 2015 (56716F32)
nvvad64v.sys  Mon Aug 10 08:51:42 2015 (55C8580E)

Note that the Logitech camera drivers (lvrs64.sys/lvuvc64.sys) date back to 2009, these really need to be updated.


http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
NEOFLTR_808_33771.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed = Secure Application Manager, Juniper Networks, Inc.
http://www.carrona.org/drivers/driver.php?id=Netwbw02.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=ScpVBus.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=apmwin.sys
http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
http://www.carrona.org/drivers/driver.php?id=gpt_loader.sys
http://www.carrona.org/drivers/driver.php?id=gzflt.sys
http://www.carrona.org/drivers/driver.php?id=hfsplus.sys
http://www.carrona.org/drivers/driver.php?id=hfsplusrec.sys
http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys.

Other notes/advice:

BitDefender Free is not based on the same driver set/engine as the pay version of BitDefender, it's not been upgraded, as far as I can tell, since it was first released. Drivers date back almost 3 years in some cases. I'd advise removing it and re-enabling Defender + Smart Screen, these should give at least as good protection, with the bonus of being written for W10 = stability.

Samsung Magician isn't needed at startup (parts of it are pretty poor anyway ime), start the software and set it to not run at boot.

The full Nvidia install package contains 'extras' that many people don't need or use, uninstall those parts (Streamer, 3D,... ?) that you don't need.

Similar with Steam (and other game software), disable it from running at startup, prevent it from loading everything, use only what is actually required. Some parts (overlays, etc.) can cause issues with certain games - and don't run the Steam Beta - we're trying to get some stability here

Check through those other Startups, many really aren't needed until you need them to run!

 

The restart on 3/4 didn't happen with a BSOD. Is it at all worthwhile to pull data from Event Viewer as there are some errors associated with that date and time?

Do you have any data to back up the claim about BitDefender Free - I tried Googling this but couldn't find anything to support that the definitions in the free version are old?

Thanks for suggestions on startup programs - I will keep them in the meantime as they are not causing any delays in boot time (unless of course any of them are associated with the crashes)

Thanks

 

From Bitdefender Technical Support:

Read the complete post at: https://forum.bitdefender.com/index.php?showtopic=59225&st=0&p=234570&#entry234570

Note: Bitdefender Free was last updated in April 2015, well before the above referenced post.

 

For BitDefender Free, you could check the driver dates for yourself (Modified Date column) using DriverView. As far as I can tell, it's still at version 1.0, no upgrades have been made since release, only relatively minor updates. Definitions are regularly updated but I don't think it's on a daily basis. Drivers date from Summer of 2013 > Spring 2015, from what I recall from my previous test installs (last one was ~Nov. last). Most other free AV makers upgrade the engine yearly, though some filter drivers, etc. are often older because they don't need updating frequently.

The below log entry might be indicative of BD Free and W10 not getting along, the bdfwfpf.sys driver not loading is a BitDefender filter driver, maybe a firewall remnant left over from whichever BD pay version the Free one was built from.

Yes, it would be a good idea to export the relevant parts of the App and System sections from Event Viewer in the default .EVTX ? format, they'll be much easier to deal with than the text files I have from the Sysnative collection app.

Another couple of oddities I just dug up from those logs:

Juniper Networks driver plus a Russian phonetic keyboard file?

 

Noted on BitDefender - will reactivate windows defender.

Juniper Networks: used to establish secure connection to work resources
Russian phonetic keyboard file: 3rd party Russian phonetic keyboard that I use.

Attached are events from event viewer labeled in sequence as they appeared around 6:43AM. Most of these are system events, the only one that is an application event is the one that begins with a 10

Thanks!

 

The shutdown errors can be ignored, they contain no useful data, the GPT error is directly linked to the shutdown as well. The Netlogon, I think, can be ignored or you can disable the Netlogon Service if the machine never needs to connect to a Domain, the DistributedCom and SecuritySPP errors are more worrying, Run SFC /SCANNOW and allow it to reboot to check System files.

The Juniper Networks and keyboard software, try to find updated versions or reinstall the current versions of both.

It's possible that some of these bugs are down to the recent (~5 days ago?) minor upgrade to a new Build version of W10, if SFC doesn't fix everything it finds, you may need to do a Repair Install of Windows.

See if you can track down the BitDefender uninstall tool to ensure all remnants are removed, try these: http://www.bitdefender.com/uninstall/

 

The build of W10 I currently have is a few builds old. I have turned off insider previews due to instability issues I was having, but cannot revert back to the latest released stable build unfortunately.

Results:
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.