none
Failed on testing "DP WLK - Hot-Add - Device Test - Verify driver support for Hot-Add CPU" and "DF - Concurrent Hardware And Operating System (CHAOS) Test (Certification)" RRS feed

  • Question

  • Hello,

    Currently I am running the HCK perview for Win 8.1 and testing Storage device on the Windows 2012 R2 9431. I had met two problems on test cases "DP WLK - Hot-Add - Device Test - Verify driver support for Hot-Add CPU" and "DF - Concurrent Hardware And Operating System (CHAOS) Test (Certification)". Those test cases are failed and the system has crashed and reboot during the two test cases. The Windows system logs said "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

    After the system came back, I opend the memory dump files and paste at below. Dose anyone met those problems at before?

    #############################################################################

    MEMORY.DMP for “DF - Concurrent Hardware And Operating System (CHAOS) Test (Certification)” 2013/07/10


    Microsoft (R) Windows Debugger Version 6.3.9431.0 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    OK                                             C:\Symbols
    Symbol search path is: C:\Symbols
    Executable search path is:
    Windows 8 Kernel Version 9431 MP (4 procs) Free x64
    Product: Server, suite: TerminalServer DataCenter SingleUserTS
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    Machine Name:
    Kernel base = 0xfffff802`86c76000 PsLoadedModuleList = 0xfffff802`86f40990
    Debug session time: Tue Jul  9 19:28:08.066 2013 (UTC - 7:00)
    System Uptime: 0 days 0:03:13.092
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols

    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 18, {0, ffffe000030bb2e0, 10, ffffe00003691db1}

    Probably caused by : partmgr.sys ( partmgr!PmPnp+2755 )

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

    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    REFERENCE_BY_POINTER (18)
    Arguments:
    Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
    Arg2: ffffe000030bb2e0, Object whose reference count is being lowered
    Arg3: 0000000000000010, Reserved
    Arg4: ffffe00003691db1, Reserved
     The reference count of an object is illegal for the current state of the object.
     Each time a driver uses a pointer to an object the driver calls a kernel routine
     to increment the reference count of the object. When the driver is done with the
     pointer the driver calls another kernel routine to decrement the reference count.
     Drivers must match calls to the increment and decrement routines. This bugcheck
     can occur because an object's reference count goes to zero while there are still
     open handles to the object, in which case the fourth parameter indicates the number
     of opened handles. It may also occur when the object?s reference count drops below zero
     whether or not there are open handles to the object, and in that case the fourth parameter
     contains the actual value of the pointer references count.

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


    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x18

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre

    LOCK_ADDRESS:  fffff80286f4afe0 -- (!locks fffff80286f4afe0)

    Resource @ nt!PiEngineLock (0xfffff80286f4afe0)    Exclusively owned
        Contention Count = 13
         Threads: ffffe0000142f140-01<*>
    1 total locks, 1 locks currently held

    PNP_TRIAGE:
     Lock address  : 0xfffff80286f4afe0
     Thread Count  : 1
     Thread address: 0xffffe0000142f140
     Thread wait   : 0x3045

    LAST_CONTROL_TRANSFER:  from fffff80286de9f87 to fffff80286dc6da0

    STACK_TEXT: 
    ffffd000`20d077d8 fffff802`86de9f87 : 00000000`00000018 00000000`00000000 ffffe000`030bb2e0 00000000`00000010 : nt!KeBugCheckEx
    ffffd000`20d077e0 fffff802`872f421e : 00000000`00000000 ffffd000`00001f80 ffffd000`20d08250 ffffc000`01e548f0 : nt! ?? ::FNODOBFM::`string'+0x12947
    ffffd000`20d07820 fffff802`872f4473 : ffffe000`02573420 ffffcf80`01b0ef28 00000000`00000000 00000000`00000000 : nt!IovUtilGetBottomDeviceObject+0x3a
    ffffd000`20d07850 fffff802`872fda2e : ffffd000`20d082c8 fffff802`871b302e ffff0000`0000027f 00000000`00000000 : nt!IovUtilIsWdmStack+0xb
    ffffd000`20d07880 fffff802`872f4b04 : ffffe000`030bb2a0 00000000`00000260 00000000`00000000 00000000`00000026 : nt!VfPnpVerifyIrpStackUpward+0x42
    ffffd000`20d07b00 fffff802`872eb344 : ffffcf80`01b0ec60 ffffd000`20d07da0 00000000`00000000 ffffe000`00e83b10 : nt!VfMajorVerifyIrpStackUpward+0x74
    ffffd000`20d07b40 fffff802`872e6201 : fffff802`00000000 00000000`00000000 00000000`00000000 fffff800`0023cb65 : nt!IovpCompleteRequest2+0xec
    ffffd000`20d07c30 fffff802`86cde9b4 : ffffcf80`01b0ec60 ffffe000`00000000 ffffd000`20d07d09 ffffe000`025733a8 : nt!IovpLocalCompletionRoutine+0x99
    ffffd000`20d07c90 fffff802`872e5b2b : ffffe000`030bb2e0 ffffcf80`01b0ec00 00000000`00000000 fffff802`8702fe0c : nt!IopfCompleteRequest+0x4c4
    ffffd000`20d07d70 fffff802`873034d2 : ffffe000`0316d5f0 00000000`00000000 ffffe000`0316d5f0 ffffcf80`01b0ec60 : nt!IovCompleteRequest+0x1d7
    ffffd000`20d07e40 fffff802`872e58c1 : ffffe000`030bb430 ffffcf80`01b0ec60 ffffe000`030bb2e0 00000000`00000002 : nt!ViFilterDispatchPnp+0x1b2
    ffffd000`20d07e80 fffff800`002fdf29 : ffffcf80`01b0ec60 fffff800`0023cb65 fffff802`86d8fdf0 ffffe000`0245ee40 : nt!IovCallDriver+0x3cd
    ffffd000`20d07ed0 fffff800`0023cb65 : ffffcf80`01b0ec60 ffffcf80`01b0ef28 00000000`00000000 ffffe000`0365f040 : VerifierExt!IofCallDriver_internal_wrapper+0x71
    ffffd000`20d07f10 fffff800`003057be : ffffe000`0365f040 ffffd000`20d07f90 ffffcf80`01b0ec60 fffff800`0022e010 : partmgr!PmPnp+0x2755
    ffffd000`20d07f60 fffff802`872e58c1 : ffffcf80`01b0ec60 00000000`00000002 ffffe000`01ee5030 ffffe000`00000000 : VerifierExt!xdv_IRP_MJ_PNP_wrapper+0xfe
    ffffd000`20d07fc0 fffff802`87303490 : ffffe000`0365f040 ffffe000`0365b530 ffffe000`0365b530 ffffe000`00e6bf40 : nt!IovCallDriver+0x3cd
    ffffd000`20d08010 fffff802`872e58c1 : ffffe000`0365b680 ffffcf80`01b0ec60 ffffe000`0365b530 00000000`00000002 : nt!ViFilterDispatchPnp+0x170
    ffffd000`20d08050 fffff802`87020856 : ffffe000`0365b530 00000000`00000000 ffffd000`20d08150 ffffe000`0246f5d0 : nt!IovCallDriver+0x3cd
    ffffd000`20d080a0 fffff802`8700e84b : 00000000`00000002 ffffd000`20d08169 ffffe000`0315a010 ffffe000`023db060 : nt!IopSynchronousCall+0xfe
    ffffd000`20d08110 fffff802`87255a4a : ffffc000`01e56760 ffffc000`01e548f0 ffffe000`0315a010 ffffc000`01e548f0 : nt!IopRemoveDevice+0xd7
    ffffd000`20d081d0 fffff802`871b302e : 00000000`00000000 ffffc000`01e548f0 ffffcf80`00354fc0 ffffffff`80000f50 : nt!PnpDisableDevice+0x5e
    ffffd000`20d08200 fffff802`870127d8 : ffffffff`80000f4c 00000000`00000007 ffffffff`80000f58 ffffe000`00000001 : nt! ?? ::NNGAKEGL::`string'+0xc98e
    ffffd000`20d08290 fffff802`870125c3 : 00000000`00000010 ffffffff`80000f5c ffffffff`80000f4c ffffffff`80000f4c : nt!PnpIsAnyDeviceInstanceEnabled+0xc0
    ffffd000`20d08310 fffff802`870e0760 : ffffe000`03767e60 ffffe000`0234d000 00000000`00000000 00000000`20206f49 : nt!PnpDriverStarted+0x2b
    ffffd000`20d08340 fffff802`87025a83 : 00000000`00000000 00000000`00000000 ffffd000`20d08858 00000000`00000000 : nt!IopLoadDriver+0x8a0
    ffffd000`20d08600 fffff802`8702539b : 00000000`0000000c 00000000`00000000 ffffd000`20d08890 fffff802`87024af6 : nt!PipCallDriverAddDeviceQueryRoutine+0x25f
    ffffd000`20d08720 fffff802`87023e0f : 00000000`00000000 00000000`00000002 00000000`00000000 ffffe000`01cf25a0 : nt!PnpCallDriverQueryServiceHelper+0x11f
    ffffd000`20d08790 fffff802`87023462 : ffffe000`01cf25a0 ffffd000`20d08a30 ffffe000`01cf25a0 00000000`00000000 : nt!PipCallDriverAddDevice+0x36f
    ffffd000`20d08930 fffff802`8710e26f : ffffe000`01cf25a0 00000000`00000001 00000000`00000000 fffff802`8702fd72 : nt!PipProcessDevNodeTree+0x1aa
    ffffd000`20d08bb0 fffff802`86d5e5af : 00000001`00000003 00000000`00000000 fffff802`86f49a80 00000000`00000001 : nt!PiRestartDevice+0xaf
    ffffd000`20d08c00 fffff802`86cb6efd : ffffe000`0142f140 00000000`00000000 fffff802`86f49a80 fffff802`59706e50 : nt!PnpDeviceActionWorker+0x3c7
    ffffd000`20d08cb0 fffff802`86d57968 : 00000000`00000000 ffffe000`0142f140 00000000`00000080 ffffe000`0142f140 : nt!ExpWorkerThread+0x129
    ffffd000`20d08d40 fffff802`86dcd3c6 : ffffd000`20881180 ffffe000`0142f140 ffffe000`002fa700 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`20d08da0 00000000`00000000 : ffffd000`20d09000 ffffd000`20d03000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    partmgr!PmPnp+2755
    fffff800`0023cb65 8bf8            mov     edi,eax

    SYMBOL_STACK_INDEX:  d

    SYMBOL_NAME:  partmgr!PmPnp+2755

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: partmgr

    IMAGE_NAME:  partmgr.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  51bd0881

    BUCKET_ID_FUNC_OFFSET:  2755

    FAILURE_BUCKET_ID:  0x18_VRF_partmgr!PmPnp

    BUCKET_ID:  0x18_VRF_partmgr!PmPnp

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x18_vrf_partmgr!pmpnp

    FAILURE_ID_HASH:  {91c8c7e7-4243-3920-c666-e966cb83746a}

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

    3: kd> lmvm partmgr
    start             end                 module name
    fffff800`0022d000 fffff800`00245000   partmgr    (pdb symbols)          c:\symbols\partmgr.pdb\9A515F456AD143CEA9DCE1FB57D2CB7E2\partmgr.pdb
        Loaded symbol image file: partmgr.sys
        Image path: \SystemRoot\System32\drivers\partmgr.sys
        Image name: partmgr.sys
        Timestamp:        Sat Jun 15 17:36:17 2013 (51BD0881)
        CheckSum:         0001FFAA
        ImageSize:        00018000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    #############################################################################

    #############################################################################

    MEMORY.DMP for “DP WLK - Hot-Add - Device Test - Verify driver support for Hot-Add CPU” 2013/07/10

    Microsoft (R) Windows Debugger Version 6.3.9431.0 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    OK                                             C:\Symbols
    Symbol search path is: C:\Symbols
    Executable search path is:
    Windows 8 Kernel Version 9431 MP (2 procs) Free x64
    Product: Server, suite: TerminalServer DataCenter SingleUserTS
    Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
    Machine Name:
    Kernel base = 0xfffff800`d2800000 PsLoadedModuleList = 0xfffff800`d2aca990
    Debug session time: Tue Jul  9 18:05:36.745 2013 (UTC - 7:00)
    System Uptime: 0 days 0:06:56.768
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols

    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffff80000739260, 2, 8, fffff80000739260}

    *** ERROR: Module load completed but symbols could not be loaded for pnpcpu.sys
    Probably caused by : pnpcpu.sys ( pnpcpu+7ac1 )

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

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff80000739260, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff80000739260, address which referenced memory

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


    READ_ADDRESS:  fffff80000739260

    CURRENT_IRQL:  2

    FAULTING_IP:
    NDIS!ndisCreateThread+0
    fffff800`00739260 488bc4          mov     rax,rsp

    IP_IN_PAGED_CODE:
    NDIS!ndisCreateThread+0
    fffff800`00739260 488bc4          mov     rax,rsp

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  AV

    PROCESS_NAME:  System

    ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre

    TRAP_FRAME:  ffffd000209e1ad0 -- (.trap 0xffffd000209e1ad0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe000019fed10 rbx=0000000000000000 rcx=fffff800006a2dd0
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80000739260 rsp=ffffd000209e1c68 rbp=0000000000000000
     r8=0000000000000008  r9=ffffe000019fed18 r10=ffffe00001bdccc0
    r11=00000000ffffffff r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    NDIS!ndisCreateThread:
    fffff800`00739260 488bc4          mov     rax,rsp
    Resetting default scope

    LOCK_ADDRESS:  fffff800d2ad4fe0 -- (!locks fffff800d2ad4fe0)

    Resource @ nt!PiEngineLock (0xfffff800d2ad4fe0)    Exclusively owned
        Contention Count = 7
         Threads: ffffe000003ff040-01<*>
    1 total locks, 1 locks currently held

    PNP_TRIAGE:
     Lock address  : 0xfffff800d2ad4fe0
     Thread Count  : 1
     Thread address: 0xffffe000003ff040
     Thread wait   : 0x6830

    LAST_CONTROL_TRANSFER:  from fffff800d295c9e9 to fffff800d2950da0

    FAILED_INSTRUCTION_ADDRESS:
    NDIS!ndisCreateThread+0
    fffff800`00739260 488bc4          mov     rax,rsp

    STACK_TEXT: 
    ffffd000`209e1988 fffff800`d295c9e9 : 00000000`0000000a fffff800`00739260 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    ffffd000`209e1990 fffff800`d295b23a : 00000000`00000008 00000000`00000080 ffffd000`209e1c00 ffffd000`209e1ad0 : nt!KiBugCheckDispatch+0x69
    ffffd000`209e1ad0 fffff800`00739260 : fffff800`006db5b8 00000000`00000080 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x23a
    ffffd000`209e1c68 fffff800`006db5b8 : 00000000`00000080 00000000`00000000 00000000`00000001 ffffe000`0025c390 : NDIS!ndisCreateThread
    ffffd000`209e1c70 fffff800`007537a4 : ffffd000`00000300 ffffe000`00010000 ffffd000`209e1d58 ffffe000`0025c390 : NDIS!ndisPeriodicReceivesAddCpu+0x94
    ffffd000`209e1cb0 fffff800`d28387c7 : ffffe000`0025b358 fffff800`d2cf620b ffffd000`209e1e90 fffff800`d28e171f : NDIS!ndisCpuHotAddHandler+0x6c
    ffffd000`209e1ce0 fffff800`d29dd751 : 00000000`00000000 ffffd000`209e1d80 fffff800`d2aa5040 ffffd000`21f41180 : nt!ExNotifyWithProcessing+0xdb
    ffffd000`209e1d30 fffff800`d2df2a9c : 00000000`00000000 ffffd000`209e1e90 fffff800`d2aa5040 ffffd000`21f41180 : nt!KiDynamicProcessorAddNotification+0x51
    ffffd000`209e1d90 fffff800`d2df3414 : 00000000`00000000 ffffd000`209e2619 ffffcf80`00c88e50 00000000`00000002 : nt!KiStartDynamicProcessor+0x3a0
    ffffd000`209e2570 fffff800`02253ac1 : ffffcf80`00c88e50 ffffd000`209e2619 00000000`00000002 ffffe000`02f54630 : nt!KeStartDynamicProcessor+0xc8
    ffffd000`209e25b0 fffff800`02253558 : ffffcf80`00c88e50 fffff800`02254960 ffffcf80`00c88e50 00000000`00000001 : pnpcpu+0x7ac1
    ffffd000`209e2680 fffff800`d2e6f8c1 : ffffcf80`00c88e50 ffffe000`02f544e0 00000000`00000002 ffffe000`0165df40 : pnpcpu+0x7558
    ffffd000`209e26c0 fffff800`d2ba7d16 : ffffcf80`00c88e50 ffffe000`0382c190 ffffe000`02f544e0 ffffe000`0165df40 : nt!IovCallDriver+0x3cd
    ffffd000`209e2710 fffff800`d28e7ac6 : ffffe000`03036b70 ffffd000`209e27b9 00000000`00000000 fffff800`d2bb5ec0 : nt!PnpAsynchronousCall+0x102
    ffffd000`209e2750 fffff800`d2c91d97 : ffffe000`03817c30 ffffe000`03817c30 ffffe000`0382c190 00000000`00000000 : nt!PnpStartDevice+0xc2
    ffffd000`209e2820 fffff800`d2c91c13 : ffffe000`03817c30 ffffe000`03817c30 00000000`00000000 ffffe000`03817c30 : nt!PnpStartDeviceNode+0x147
    ffffd000`209e28f0 fffff800`d2bad6a2 : ffffe000`03817c30 00000000`00000001 00000000`00000001 ffffe000`0031a830 : nt!PipProcessStartPhase1+0x53
    ffffd000`209e2930 fffff800`d2c950e9 : ffffe000`038157c0 00000000`00000001 00000000`00000000 fffff800`d2bb9d72 : nt!PipProcessDevNodeTree+0x3ea
    ffffd000`209e2bb0 fffff800`d28e8350 : 00000001`00000003 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PiProcessReenumeration+0x91
    ffffd000`209e2c00 fffff800`d2840efd : ffffe000`003ff040 00000000`00000000 fffff800`d2ad3a80 fffff800`00698328 : nt!PnpDeviceActionWorker+0x168
    ffffd000`209e2cb0 fffff800`d28e1968 : 00000000`00000000 ffffe000`003ff040 00000000`00000080 ffffe000`003ff040 : nt!ExpWorkerThread+0x129
    ffffd000`209e2d40 fffff800`d29573c6 : fffff800`d2af4180 ffffe000`003ff040 ffffe000`00239040 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`209e2da0 00000000`00000000 : ffffd000`209e3000 ffffd000`209dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    pnpcpu+7ac1
    fffff800`02253ac1 eb3a            jmp     pnpcpu+0x7afd (fffff800`02253afd)

    SYMBOL_STACK_INDEX:  a

    SYMBOL_NAME:  pnpcpu+7ac1

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: pnpcpu

    IMAGE_NAME:  pnpcpu.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  51bd4d15

    FAILURE_BUCKET_ID:  AV_VRF_CODE_AV_PAGED_IP_pnpcpu+7ac1

    BUCKET_ID:  AV_VRF_CODE_AV_PAGED_IP_pnpcpu+7ac1

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:av_vrf_code_av_paged_ip_pnpcpu+7ac1

    FAILURE_ID_HASH:  {879b3578-2ada-e2a0-2eaf-a0b76bdab745}

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

    1: kd> lmvm pnpcpu
    start             end                 module name
    fffff800`0224c000 fffff800`02258000   pnpcpu     (no symbols)          
        Loaded symbol image file: pnpcpu.sys
        Image path: \SystemRoot\System32\drivers\pnpcpu.sys
        Image name: pnpcpu.sys
        Timestamp:        Sat Jun 15 22:28:53 2013 (51BD4D15)
        CheckSum:         0001A5C9
        ImageSize:        0000C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Wednesday, July 10, 2013 6:13 AM

All replies

  • I also have a failure "DP WLK - Hot-Add - Device Test - Verify driver support for Hot-Add CPU" on server 2012 R2 ,

    i have found the same failure in the filter :227 ,but now it do't suppurt Server 2012 R2 , so i still have a failure ,and

    i have try three systems .

    Wednesday, July 10, 2013 7:23 AM
  • I have this same issue

    The error is:

    TaskResult Errors 
    # Message Time Source Machine Name Root Cause 
    1 9/16/2013 6:46:10 PM Execution Agent WIN-JADM1IIBUSF CExecutionTask::Cleanup Machine got Rebooted while Task "Run IO Stress" Was running....Failing the Task

     
    Resolution 
    This computer is found to have had an unexpected reboot. None of the tasks that were running before the reboot requested a reboot. 
    The job will be cancelled as a result.  
    # Message Time Source Machine Name Root Cause 
    2 9/16/2013 6:43:41 PM Execution Agent WIN-JADM1IIBUSF Task Cancelled Because of an Unexpected Reboot

    Machine Rebooted Unexpectedly when Task "Run IO Stress" was running

     
    Resolution 
    This computer is found to have had an unexpected reboot. None of the tasks that were running before the reboot requested a reboot. 
    The job will be cancelled as a result.  

    Any suggestions?

    Tuesday, September 17, 2013 3:39 AM
  • Hi,

    This error ususally comes when there is a issue with the display adapter driver. see whether system supports sleep states or not.

    Tuesday, September 17, 2013 9:11 AM
  • Hello Garg9,

    I got a bluescreen while running this test.

    Bluescreen is about NDIS.SYS.

    Tuesday, September 17, 2013 9:56 AM
  • Hello,

    i got it running with the new RTM Build of Server 2012R2.

    You can download it from MSDN since 10/09/2013

    So it will work now.

    Tuesday, September 17, 2013 1:27 PM
  • Hello Szillat,

    Can you give me the link for Windows Server 2012 R2 RTM, I can't seem to find it.

    Thanks!

    Wednesday, September 18, 2013 3:16 AM