New
#1
Random BSOD on Surveillance PC
This PC has randomly been blue screening. Obviously that doesn't make it of much use in surveillance. The appropriate logs are attached.
This PC has randomly been blue screening. Obviously that doesn't make it of much use in surveillance. The appropriate logs are attached.
Security Software:Code:msmpeng.exe c:\program files\microsoft security client\antimalware\msmpeng.exe 808 8 200 1380 3/22/2012 4:20 PM 3.0.8107.0 12.48 KB (12,784 bytes) 11/11/2010 2:36 PM nissrv.exe c:\program files\microsoft security client\antimalware\nissrv.exe 1916 8 200 1380 3/22/2012 4:20 PM 3.0.8107.0 275.99 KB (282,616 bytes) 11/11/2010 2:36 PM msseces.exe c:\program files\microsoft security client\msseces.exe 1516 8 200 1380 3/22/2012 4:22 PM 2.0.657.0 1.37 MB (1,436,224 bytes) 11/30/2010 1:26 PM
Possible out of date driver:ADIHdAud.sysCode:ADIHdAud fffff880`04000000 fffff880`04080000 Mon Jun 22 13:01:24 2009 (4a3fd504) 00081e59 ADIHdAud.sys
This is a TDR Crash:Code:Loading Dump File [D:\Kingston\BSODDmpFiles\raf051888\Bluescreens\Windows_NT6_BSOD_jcgriff2\032012-10966-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`0281b000 PsLoadedModuleList = 0xfffff800`02a5f650 Debug session time: Tue Mar 20 18:38:36.184 2012 (UTC - 6:00) System Uptime: 1 days 3:01:38.432 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800cdd3010, fffff88004a71000, 0, 2} *** 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+1d000 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800cdd3010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88004a71000, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: igdkmd64+1d000 fffff880`04a71000 4889542410 mov qword ptr [rsp+10h],rdx DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`04462988 fffff880`054ce000 : 00000000`00000116 fffffa80`0cdd3010 fffff880`04a71000 00000000`00000000 : nt!KeBugCheckEx fffff880`04462990 fffff880`054cdd0a : fffff880`04a71000 fffffa80`0cdd3010 fffffa80`0f25c910 fffffa80`0ec8a410 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`044629d0 fffff880`05574f07 : fffffa80`0cdd3010 00000000`00000000 fffffa80`0f25c910 fffffa80`0ec8a410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`04462a00 fffff880`0559eb75 : 00000000`ffffffff 00000000`005f2aa9 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`04462ae0 fffff880`0559d2bb : 00000000`00000102 00000000`00000000 00000000`005f2aa9 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`04462b10 fffff880`055702c6 : ffffffff`ff676980 fffffa80`0ec8a410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`04462bb0 fffff880`0559ce7a : 00000000`00000000 fffffa80`0f2e2900 00000000`00000080 fffffa80`0ec8a410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`04462cc0 fffff800`02b31f7a : 00000000`fffffc32 fffffa80`0f268a10 fffffa80`0c109740 fffffa80`0f268a10 : dxgmms1!VidSchiWorkerThread+0xba fffff880`04462d00 fffff800`028889c6 : fffff800`02a0ce80 fffffa80`0f268a10 fffff800`02a1acc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a fffff880`04462d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: igdkmd64+1d000 fffff880`04a71000 4889542410 mov qword ptr [rsp+10h],rdx SYMBOL_NAME: igdkmd64+1d000 FOLLOWUP_NAME: MachineOwner MODULE_NAME: igdkmd64 IMAGE_NAME: igdkmd64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c44e97b FAILURE_BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys Followup: MachineOwner ---------
- The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.
I also see some hard disk file system corruption:
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
at cmd typr chkdsk /r and you will get a thorough check of all sectors, for just files, type chkdsk /f quicker, but the r flag will look for any bad sectors you might have, a very good idea with older hard drives. i would update the drivers through the device manager, too :)