BSOD when away from computer

erwhat · 10 Sep 2015

Hey all, I am getting random crashes caused by ntoskrnl.exe when I am away from my computer. Not everytime I am away either. Haven't found another thread with the address I'm getting, so any help would be appreciated.

PS in the logs there is another crash for applecharger.sys, caused by my gigabyte on/off charging option. If anyone know how to leave that gigabyte feature on without the BSOD, that information would be appreciated also.

Thanks

blueelvis · 14 Sep 2015

Hi Erwhat ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
[hr]
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000

So, the DPC Watchdog found that an ISR which is also known as Interrupt Service Routine (As per the Bucket ID) was not serviced at the appropriate time. Let's check the stack and see if we can find the culprit -

Code:

0: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff803`2806b8a8 fffff803`265e6e7a nt!KeBugCheckEx
01 fffff803`2806b8b0 fffff803`26489c26 nt! ?? ::FNODOBFM::`string'+0xa07a
02 fffff803`2806b940 fffff803`2648a66d nt!KiUpdateRunTime+0x56
03 fffff803`2806b9a0 fffff803`26411aa6 nt!KeClockInterruptNotify+0x53d
04 fffff803`2806bbd0 fffff803`26551257 hal!HalpTimerClockInterrupt+0x56
05 fffff803`2806bc00 fffff803`265cf60a nt!KiCallInterruptServiceRoutine+0x87
06 fffff803`2806bc40 fffff803`265cfa37 nt!KiInterruptSubDispatchNoLockNoEtw+0xea
07 fffff803`2806bc90 fffff800`76346f9e nt!KiInterruptDispatchNoLockNoEtw+0x37
08 fffff803`2806be20 ffffe000`0fa9b458 amdsata+0x6f9e
09 fffff803`2806be28 00000000`00000200 0xffffe000`0fa9b458
0a fffff803`2806be30 00000000`00000000 0x200

There we have it. The culprit is the AMD's SATA Driver.
Below is a list of 3rd party drivers present on your system -

Code:

**************************Thu Sep 10 22:19:20.802 2015 (UTC + 5:30)**************************
GVTDrv64.sys                Tue Sep  5 12:40:02 2006 (44FD22CA)
SiLib.sys                   Wed Feb  7 04:43:54 2007 (45C90BB2)
AseUSBCC.sys                Wed Feb  7 04:45:34 2007 (45C90C16)
teamviewervpn.sys           Thu Dec 13 14:52:09 2007 (4760F9C1)
wdcsam64.sys                Wed Apr 16 14:09:08 2008 (4805BB2C)
gdrv.sys                    Fri Mar 13 08:52:29 2009 (49B9D175)
amdsata.sys                 Thu Oct  8 01:43:09 2009 (4ACCF655)
amdxata.sys                 Thu Oct  8 01:43:10 2009 (4ACCF656)
usbfilter.sys               Tue Dec 22 13:56:22 2009 (4B3082AE)
AODDriver.sys               Thu Mar  4 16:28:24 2010 (4B8F9250)
mvxxmm.sys                  Mon Mar  7 07:43:21 2011 (4D743F41)
mvs91xx.sys                 Mon Mar  7 07:43:40 2011 (4D743F54)
SCDEmu.SYS                  Wed Jun 15 13:59:27 2011 (4DF86D67)
GEARAspiWDM.sys             Fri May  4 01:26:17 2012 (4FA2E2E1)
000.fcl                     Fri Oct 18 12:46:31 2013 (5260E04F)
RzDxgk.sys                  Thu Apr  3 21:09:50 2014 (533D80C6)
rzpmgrk.sys                 Fri Apr 18 01:06:12 2014 (53502D2C)
rzpnk.sys                   Sat Oct 18 01:08:10 2014 (54417022)
ElbyCDIO.sys                Thu Dec 18 05:00:51 2014 (5492122B)
rzendpt.sys                 Tue Dec 30 15:02:47 2014 (54A2713F)
rzudd.sys                   Tue Dec 30 15:02:50 2014 (54A27142)
rt640x64.sys                Wed Apr  1 20:04:31 2015 (551C01F7)
nvhda64v.sys                Fri Apr 17 00:33:16 2015 (55300774)
AnyDVD.sys                  Tue Apr 28 00:35:44 2015 (553E8888)
usbaapl64.sys               Thu Jun 11 11:38:10 2015 (557925CA)
RTKVHD64.sys                Tue Jun 16 16:25:05 2015 (55800089)
NvStreamKms.sys             Sat Jul 25 14:52:15 2015 (55B35547)
nvvad64v.sys                Mon Aug 10 13:21:42 2015 (55C8580E)
nvlddmkm.sys                Tue Aug 25 19:11:50 2015 (55DC709E)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 10 04:05:00.130 2015 (UTC + 5:30)**************************
AppleCharger.sys            Wed Nov  2 08:16:00 2011 (4EB0AEE8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep  9 20:02:06.224 2015 (UTC + 5:30)**************************
DirectIo64.sys              Mon Aug 13 10:00:24 2012 (502882E0)

Please update your AMD SATA driver since it is very old (Dates back to 2009) and is most likely not compatible with Windows 10.
Please remove Teamviewer, any Western Digital software since they are also very old.

Regarding your query about the AppleCharger.sys, it is a known problem that this driver causes BSOD on certain system. Your best bet would be to turn off and uninstall Gigabyte Software which bundles this.

Let me know how it goes ^_^

-Pranav