Home > OS >  Turn to afd. Sys blue screen
Turn to afd. Sys blue screen

Time:09-30

Recent server often boot turn blue, in the morning after the restart normal, system is winserver 2008 x86, please god help
Below is Windbg analysis:
Microsoft (R) Windows Debugger Version 10.0.16299.91 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading the Dump File (C: \ Users \ nix \ Desktop \ log \ Mini051618-01 DMP]
The Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at the end of the path element
Error: the Empty Path.
WARNING: Whitespace at the end of the path element
Symbol search path is: the SRV * c: \ symbols * http://msdl.microsoft.com/download/symbols


The Executable search path is:
WARNING: Whitespace at the end of the path element
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP procs (4) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 6002.18005 x86fre. Lh_sp2rtm. 090410-1830
The Machine Name:
The Kernel base=0 x81c45000 PsLoadedModuleList=0 x81d5cc70
The Debug session time: Wed May 16 07:59:26. 523, 2018 (UTC + 8)
The System Uptime: 557
0 days 0:15:59.Loading the Kernel Symbols
.

Press CTRL - c (CDB, kd, NTSD) or CTRL - break (windbg) to abort symbol loads that take too long.
The Run! Sym noisy before the reload to track down the problems loading symbols.

...
.
.
Loading User Symbols
Loading unloaded the module list
.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
* Bugcheck Analysis *
* *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

The Use! Analyze the -v to get the detailed was debugging information.

BugCheck 1000007 e, {c0000005, 8737 c413, a1869aa0, a186979c}

Probably under caused by: afd. Sys (afd! AfdWskDispatchInternalDeviceControl + 21)

Followup: MachineOwner
-- -- -- -- -- -- -- -- --

Zero: kd> ! Analyze the -v
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
* Bugcheck Analysis *
* *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007 e)
This is a very common bugcheck. Usually the exception address pinpoints
The driver/function that under caused the problem. Always note this address
As well as the link date of the driver/image that contains this address.
Some common problems are the exception code 0 x80000003. This means a hard
Coded breakpoint or an assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
Hardcoded breakpoints in retail code, but...
If this happens, make sure a debugger gets connected, and the
The system is booted/DEBUG. This will let us see according This breakpoint is
Happening.
The Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2:8737 c413, The address that The exception occurred at
Arg3: a1869aa0, Exception Record Address
Arg4: a186979c, Context Record Address

Was Debugging Details:
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 6002.18005 x86fre. Lh_sp2rtm. 090410-1830

IBM SYSTEM_MANUFACTURER:

System SYSTEM_PRODUCT_NAME: IBM x3100 M5: - ac1 [5457] -

SYSTEM_VERSION: 05

IBM BIOS_VENDOR:

BIOS_VERSION: -/J9E120EUS - 1.20 -

BIOS_DATE: 09/24/2015

IBM BASEBOARD_MANUFACTURER:

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffff8737c413

BUGCHECK_P3: ffffffffa1869aa0

BUGCHECK_P4: ffffffffa186979c

EXCEPTION_CODE: (NTSTATUS) 0 xc0000005 - & lt; Unable to get the error code text>

FAULTING_IP:
+ 0
8737 8 b36 mov esi c413, dword PTR (esi)

EXCEPTION_RECORD: a1869aa0 -- (. Exr 0 xffffffffa1869aa0)
8737 c413 ExceptionAddress:
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
The Parameter [0] : 00000000
The Parameter [1] : 00000000
Attempt to read the from address 00000000

CONTEXT: a186979c -- (. CXR 0 xffffffffa186979c)
Eax=86 a6ea78 ebx=81 c45000 ecx=85984 a98 edx=00507308, esi=00000000 edi=a1869b8c
The eip==8737 c413 esp a1869b68 ebp=8737 c000 iopl=0 nv up ei ng nz na PE nc
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related