Page 2 of 4 FirstFirst 1234 LastLast
  1.    14 Aug 2015 #11
    Join Date : Aug 2015
    Posts : 26
    Windows 10 Pro x64
    Thread Starter

    I did the second scan,
    still BSODing (as expected)
      My ComputerSystem Spec
  2.    14 Aug 2015 #12
    Join Date : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM

    It's another 0x133, this is a difficult one to determine because the problem stems from DPCs running from multiple drivers so the stack is insufficient to pinpoint the culprit.

    Code:
    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

    The only suggestion I can make at the moment is to enable DV again and see if it can weed out any more problematic drivers.
      My ComputerSystem Spec
  3.    14 Aug 2015 #13
    Join Date : Aug 2015
    Posts : 26
    Windows 10 Pro x64
    Thread Starter

    Another crash, this time it's flagging "mmcss.sys"
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc000001d, fffff801a8e416be, ffffd001c89f78c8, ffffd001c89f70e0}
    
    Probably caused by : mmcss.sys ( mmcss!CiSchedulerWait+8e )
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that 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 exception code 0x80000003.  This means a hard
    coded breakpoint or 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
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff801a8e416be, The address that the exception occurred at
    Arg3: ffffd001c89f78c8, Exception Record Address
    Arg4: ffffd001c89f70e0, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  SKU
    
    SYSTEM_VERSION:  System Version
    
    BIOS_DATE:  04/28/2015
    
    BASEBOARD_PRODUCT:  A88X-PLUS
    
    BASEBOARD_VERSION:  Rev X.0x
    
    BUGCHECK_P1: ffffffffc000001d
    
    BUGCHECK_P2: fffff801a8e416be
    
    BUGCHECK_P3: ffffd001c89f78c8
    
    BUGCHECK_P4: ffffd001c89f70e0
    
    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {AUSNAHME}  Ung ltige Anweisung  Es wurde versucht, eine ung ltige Anweisung auszuf hren.
    
    FAULTING_IP: 
    mmcss!CiSchedulerWait+8e
    fffff801`a8e416be 44382d6c5b0000  cmp     byte ptr [mmcss!CiSchedulerDisallowLazyMode (fffff801`a8e47231)],r13b
    
    EXCEPTION_RECORD:  ffffd001c89f78c8 -- (.exr 0xffffd001c89f78c8)
    ExceptionAddress: fffff801a8e416be (mmcss!CiSchedulerWait+0x000000000000008e)
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    CONTEXT:  ffffd001c89f70e0 -- (.cxr 0xffffd001c89f70e0)
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff801a8e470c0
    rdx=0000000000000000 rsi=0000000000000010 rdi=fffff801a8e47180
    rip=fffff801a8e416be rsp=ffffd001c89f7b00 rbp=00000040c38cd264
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff801a8e47170 r12=ffffd001c89f7c00 r13=0000000000000000
    r14=0000000000000010 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    mmcss!CiSchedulerWait+0x8e:
    fffff801`a8e416be 44382d6c5b0000  cmp     byte ptr [mmcss!CiSchedulerDisallowLazyMode (fffff801`a8e47231)],r13b ds:002b:fffff801`a8e47231=00
    Resetting default scope
    
    CPU_COUNT: 4
    
    CPU_MHZ: c78
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 15
    
    CPU_MODEL: 10
    
    CPU_STEPPING: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc000001d - {AUSNAHME}  Ung ltige Anweisung  Es wurde versucht, eine ung ltige Anweisung auszuf hren.
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff801a8e429c8 to fffff801a8e416be
    
    FAILED_INSTRUCTION_ADDRESS: 
    mmcss!CiSchedulerWait+8e
    fffff801`a8e416be 44382d6c5b0000  cmp     byte ptr [mmcss!CiSchedulerDisallowLazyMode (fffff801`a8e47231)],r13b
    
    STACK_TEXT:  
    ffffd001`c89f7b00 fffff801`a8e429c8 : 00000000`00000010 00000000`00000016 00000000`00000001 ffffe001`fc83a230 : mmcss!CiSchedulerWait+0x8e
    ffffd001`c89f7ba0 fffff801`34369698 : 00000000`00000010 ffffe001`fc83a230 ffffe001`fdae5040 00000000`00000000 : mmcss!CiSchedulerThreadFunction+0x1b8
    ffffd001`c89f7c00 fffff801`343d6306 : fffff801`345e7180 ffffe001`fdae5040 ffffe001`fdae8080 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd001`c89f7c60 00000000`00000000 : ffffd001`c89f8000 ffffd001`c89f2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    FOLLOWUP_IP: 
    mmcss!CiSchedulerWait+8e
    fffff801`a8e416be 44382d6c5b0000  cmp     byte ptr [mmcss!CiSchedulerDisallowLazyMode (fffff801`a8e47231)],r13b
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  mmcss!CiSchedulerWait+8e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: mmcss
    
    IMAGE_NAME:  mmcss.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  559f383c
    
    IMAGE_VERSION:  10.0.10240.16384
    
    STACK_COMMAND:  .cxr 0xffffd001c89f70e0 ; kb
    
    BUCKET_ID_FUNC_OFFSET:  8e
    
    FAILURE_BUCKET_ID:  AV_BAD_IP_mmcss!CiSchedulerWait
    
    BUCKET_ID:  AV_BAD_IP_mmcss!CiSchedulerWait
    
    PRIMARY_PROBLEM_CLASS:  AV_BAD_IP_mmcss!CiSchedulerWait
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_bad_ip_mmcss!cischedulerwait
    
    FAILURE_ID_HASH:  {0751b085-dc92-d0ca-8974-d74e14e97034}
    
    Followup:     MachineOwner
    ---------
      My ComputerSystem Spec
  4.    15 Aug 2015 #14
    Join Date : Aug 2015
    Posts : 26
    Windows 10 Pro x64
    Thread Starter

    2 new crashes, one dump file seems to be corrupt (It BSODed 2 times right after each other)
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffd7d03270144, 2, 1, fffff80335856efc}
    
    Probably caused by : memory_corruption ( nt!MiUnlinkPageFromList+3bc )
    
    Followup:     MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffd7d03270144, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80335856efc, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  SKU
    
    SYSTEM_VERSION:  System Version
    
    BIOS_DATE:  04/28/2015
    
    BASEBOARD_PRODUCT:  A88X-PLUS
    
    BASEBOARD_VERSION:  Rev X.0x
    
    BUGCHECK_P1: fffffd7d03270144
    
    BUGCHECK_P2: 2
    
    BUGCHECK_P3: 1
    
    BUGCHECK_P4: fffff80335856efc
    
    WRITE_ADDRESS: fffff80335bca500: Unable to get MiVisibleState
     fffffd7d03270144 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiUnlinkPageFromList+3bc
    fffff803`35856efc 6644895724      mov     word ptr [rdi+24h],r10w
    
    CPU_COUNT: 4
    
    CPU_MHZ: c78
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 15
    
    CPU_MODEL: 10
    
    CPU_STEPPING: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  mobsync.exe
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    TRAP_FRAME:  ffffd0002e5604b0 -- (.trap 0xffffd0002e5604b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000010000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=000000000000000f rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80335856efc rsp=ffffd0002e560640 rbp=ffffd0002e560680
     r8=ff00000fffffffff  r9=0000000ff010d006 r10=000000000010ce24
    r11=fffffa80065d0e78 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac po nc
    nt!MiUnlinkPageFromList+0x3bc:
    fffff803`35856efc 6644895724      mov     word ptr [rdi+24h],r10w ds:00000000`00000024=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8033595dba9 to fffff80335953220
    
    STACK_TEXT:  
    ffffd000`2e560368 fffff803`3595dba9 : 00000000`0000000a fffffd7d`03270144 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    ffffd000`2e560370 fffff803`3595c3c8 : fffff6fb`7dbed7f8 fffff6fb`7dbed7f8 fffff6fb`7dafffc8 fffff6fb`7dafffc8 : nt!KiBugCheckDispatch+0x69
    ffffd000`2e5604b0 fffff803`35856efc : 00000000`00000000 00000000`00000000 00000000`00000000 fffff803`00000000 : nt!KiPageFault+0x248
    ffffd000`2e560640 fffff803`3581f09b : fffffa80`03da4660 00007ffe`00000000 00000000`00000000 00000000`00000001 : nt!MiUnlinkPageFromList+0x3bc
    ffffd000`2e560720 fffff803`3582a61e : 00000000`00000000 00007ffe`391f600c 00000000`00000001 ffffe001`c7f36578 : nt!MiResolveTransitionFault+0x1db
    ffffd000`2e5607c0 fffff803`35827b13 : ffffd000`2e560a50 00007ffe`391f600c fffff6bf`ff1c8fb0 ffffe001`c7f36578 : nt!MiResolveProtoPteFault+0x49e
    ffffd000`2e560860 fffff803`35825296 : 00000000`00000100 00007ffe`391f600c ffffd000`2e560a80 ffffd000`00000000 : nt!MiDispatchFault+0x3b3
    ffffd000`2e5609b0 fffff803`3595c2bd : ffffe001`c7f28840 ffffd000`2e560b80 00000000`002f9087 ffffd000`c0000034 : nt!MmAccessFault+0x336
    ffffd000`2e560b00 00007ffe`51318ed7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13d
    000000ad`907bc980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`51318ed7
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiUnlinkPageFromList+3bc
    fffff803`35856efc 6644895724      mov     word ptr [rdi+24h],r10w
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiUnlinkPageFromList+3bc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55b99f32
    
    IMAGE_VERSION:  10.0.10240.16412
    
    IMAGE_NAME:  memory_corruption
    
    BUCKET_ID_FUNC_OFFSET:  3bc
    
    FAILURE_BUCKET_ID:  AV_VRF_nt!MiUnlinkPageFromList
    
    BUCKET_ID:  AV_VRF_nt!MiUnlinkPageFromList
    
    PRIMARY_PROBLEM_CLASS:  AV_VRF_nt!MiUnlinkPageFromList
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_vrf_nt!miunlinkpagefromlist
    
    FAILURE_ID_HASH:  {3029f02d-392f-fefd-b340-5347b39894d5}
    
    Followup:     MachineOwner
    ---------
      My ComputerSystem Spec
  5.    15 Aug 2015 #15
    Join Date : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM

    These look to me as if they're all pointing to drivers but none are showing in the last dumps. Can you enable DV again please, it's the only way we're going to dig these out.
      My ComputerSystem Spec
  6.    15 Aug 2015 #16
    Join Date : Aug 2015
    Posts : 26
    Windows 10 Pro x64
    Thread Starter

    more BSODs
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffa93f5d26ea0, 2, 0, fffff800f3aaabf5}
    
    Probably caused by : memory_corruption ( nt!MiInsertNumaStandbyPage+c5 )
    
    Followup:     MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffa93f5d26ea0, memory referenced
    Arg2: 0000000000000002, 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: fffff800f3aaabf5, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  SKU
    
    SYSTEM_VERSION:  System Version
    
    BIOS_DATE:  04/28/2015
    
    BASEBOARD_PRODUCT:  A88X-PLUS
    
    BASEBOARD_VERSION:  Rev X.0x
    
    BUGCHECK_P1: fffffa93f5d26ea0
    
    BUGCHECK_P2: 2
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: fffff800f3aaabf5
    
    READ_ADDRESS: fffff800f3c54500: Unable to get MiVisibleState
     fffffa93f5d26ea0 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiInsertNumaStandbyPage+c5
    fffff800`f3aaabf5 48330a          xor     rcx,qword ptr [rdx]
    
    CPU_COUNT: 4
    
    CPU_MHZ: c78
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 15
    
    CPU_MODEL: 10
    
    CPU_STEPPING: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  javaw.exe
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    TRAP_FRAME:  ffffd0002714f5a0 -- (.trap 0xffffd0002714f5a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000fffffffff rbx=0000000000000000 rcx=0001f36ca0000000
    rdx=fffffa93f5d26ea0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800f3aaabf5 rsp=ffffd0002714f730 rbp=ffffd0002714f7e0
     r8=000000006a74624e  r9=fffffa8005da45e0 r10=00000000001f36ca
    r11=fffffa80065d0e18 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    nt!MiInsertNumaStandbyPage+0xc5:
    fffff800`f3aaabf5 48330a          xor     rcx,qword ptr [rdx] ds:fffffa93`f5d26ea0=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800f39e7ba9 to fffff800f39dd220
    
    STACK_TEXT:  
    ffffd000`2714f458 fffff800`f39e7ba9 : 00000000`0000000a fffffa93`f5d26ea0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`2714f460 fffff800`f39e63c8 : ffffc000`cc6deaf0 fffff6fb`400016e8 ffffd000`2714f6f0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    ffffd000`2714f5a0 fffff800`f3aaabf5 : e0000dbc`1b3804c0 80ffffff`ffffffff 7000ffff`01420000 ea200000`001cb56f : nt!KiPageFault+0x248
    ffffd000`2714f730 fffff800`f3aabb53 : fffffa80`05631f30 ffffd000`2714f7e0 00000000`001f36ca 00000000`00000002 : nt!MiInsertNumaStandbyPage+0xc5
    ffffd000`2714f760 fffff800`f39fbbb7 : fffff800`00000000 fffff800`00000000 00000000`00000002 fffff800`f396a06d : nt!MiSwapNumaStandbyPage+0x733
    ffffd000`2714f820 fffff800`f38abdb0 : fffff800`f3bd6a80 fffff800`00000000 00000000`00000001 fffffa80`00000001 : nt! ?? ::FNODOBFM::`string'+0xfdb7
    ffffd000`2714f890 fffff800`f38af328 : 00000000`00000002 00000000`5b9f0000 ffffd000`2714fb00 fffff680`002dcf80 : nt!MiResolveDemandZeroFault+0x300
    ffffd000`2714f9b0 fffff800`f39e62bd : ffffe000`0ee71080 00000000`34a81800 00000000`00000000 ffffe000`0bcd8e70 : nt!MmAccessFault+0x3c8
    ffffd000`2714fb00 00000000`76e11431 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13d
    00000000`4ae3eb60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e11431
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiInsertNumaStandbyPage+c5
    fffff800`f3aaabf5 48330a          xor     rcx,qword ptr [rdx]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiInsertNumaStandbyPage+c5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55b99f32
    
    IMAGE_VERSION:  10.0.10240.16412
    
    IMAGE_NAME:  memory_corruption
    
    BUCKET_ID_FUNC_OFFSET:  c5
    
    FAILURE_BUCKET_ID:  AV_VRF_nt!MiInsertNumaStandbyPage
    
    BUCKET_ID:  AV_VRF_nt!MiInsertNumaStandbyPage
    
    PRIMARY_PROBLEM_CLASS:  AV_VRF_nt!MiInsertNumaStandbyPage
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:av_vrf_nt!miinsertnumastandbypage
    
    FAILURE_ID_HASH:  {6345d564-a9c1-a7dc-ef13-d0efd70b8a88}
    
    Followup:     MachineOwner
    ---------
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 133, {1, 1e00, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b008 )
    
    Followup:     MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  SKU
    
    SYSTEM_VERSION:  System Version
    
    BIOS_DATE:  04/28/2015
    
    BASEBOARD_PRODUCT:  A88X-PLUS
    
    BASEBOARD_VERSION:  Rev X.0x
    
    BUGCHECK_P1: 1
    
    BUGCHECK_P2: 1e00
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 0
    
    DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
    
    CPU_COUNT: 4
    
    CPU_MHZ: c78
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 15
    
    CPU_MODEL: 10
    
    CPU_STEPPING: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0x133
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  d
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff803b3179e08 to fffff803b3160220
    
    STACK_TEXT:  
    ffffd000`8bda2c78 fffff803`b3179e08 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`8bda2c80 fffff803`b301dd4f : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00003309 : nt! ?? ::FNODOBFM::`string'+0xb008
    ffffd000`8bda2d10 fffff803`b3867d15 : 00000000`00000001 ffffe000`63ec22a0 ffffe000`60446b00 00000000`00000000 : nt!KeClockInterruptNotify+0x9f
    ffffd000`8bda2f40 fffff803`b30e22e7 : ffffd000`00000002 00000000`00000000 80000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
    ffffd000`8bda2f70 fffff803`b31615ea : ffffe000`60446b00 ffffe000`63ec22a0 00000000`00000001 80000000`00000000 : nt!KiCallInterruptServiceRoutine+0x87
    ffffd000`8bda2fb0 fffff803`b3161a17 : fffff803`b336dd00 fffffa80`017b0650 ffffe000`63ec22a0 00000000`00000200 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`20aa5fe0 fffff803`b3036580 : 00000000`00000100 ffffe000`63ec38c0 ffffc000`c4796760 ffffd000`20aa6270 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    ffffd000`20aa6170 fffff803`b3419167 : ffffd000`20aa6270 ffffe000`63ec22a0 ffffd000`20aa6b80 ffffe000`63ec2000 : nt!MiIdentifyPfnWrapper+0x90
    ffffd000`20aa61a0 fffff803`b3497b6a : ffffc000`c3a6d060 00000000`00000001 ffffd000`20aa6384 ffffe000`63ec2000 : nt!PfpPfnPrioRequest+0xc7
    ffffd000`20aa6220 fffff803`b3495f6d : 00000000`0000004f ffffe000`63f861a0 000000e7`c1edac90 00000000`00000000 : nt!PfQuerySuperfetchInformation+0x2ea
    ffffd000`20aa6350 fffff803`b3495c6b : fffff803`b38b12e0 fffff803`b3164ccf 00000000`00000000 000000e7`c2329110 : nt!ExpQuerySystemInformation+0x20d
    ffffd000`20aa6ac0 fffff803`b316a863 : ffffe000`63046080 00000000`00000000 ffffe000`63046080 ffffd000`20aa6b80 : nt!NtQuerySystemInformation+0x2b
    ffffd000`20aa6b00 00007ff9`de25385a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000e7`c1edab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`de25385a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+b008
    fffff803`b3179e08 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+b008
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55b99f32
    
    IMAGE_VERSION:  10.0.10240.16412
    
    BUCKET_ID_FUNC_OFFSET:  b008
    
    FAILURE_BUCKET_ID:  0x133_VRF_ISR_nt!_??_::FNODOBFM::_string_
    
    BUCKET_ID:  0x133_VRF_ISR_nt!_??_::FNODOBFM::_string_
    
    PRIMARY_PROBLEM_CLASS:  0x133_VRF_ISR_nt!_??_::FNODOBFM::_string_
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x133_vrf_isr_nt!_??_::fnodobfm::_string_
    
    FAILURE_ID_HASH:  {95177cbe-89c6-8a7f-85c1-3e7734c38bc1}
    
    Followup:     MachineOwner
    ---------
      My ComputerSystem Spec
  7.    15 Aug 2015 #17
    Join Date : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM

    Do you have DV enabled? I need you to let me know what you're doing otherwise I'm guessing. I need the dumps as well, I can't pull anything from text.
      My ComputerSystem Spec
  8.    15 Aug 2015 #18
    Join Date : Aug 2015
    Posts : 26
    Windows 10 Pro x64
    Thread Starter

    Yes, I do have DV enabled since yesterday.
    Here are the dumps you requested
      My ComputerSystem Spec
  9.    15 Aug 2015 #19
    Join Date : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM

    Still no drivers showing. Can you disable DV and run the system as normal.
      My ComputerSystem Spec
  10.    15 Aug 2015 #20
    Join Date : Aug 2015
    Posts : 26
    Windows 10 Pro x64
    Thread Starter

    hm okay
      My ComputerSystem Spec

 
Page 2 of 4 FirstFirst 1234 LastLast


Similar Threads
Thread Forum
BSOD during Windows 10 installation
So I can't upgrade to windows 10. I keep getting a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (wdf01000.sys) error. Then I am stuck until my PC restarts a few times and rolls back to Windows 7 Pro. I am attaching the debug to see if anyone can help me...
BSOD Crashes and Debugging
Windows 10 reset BSOD?
So I'm on the latest Windows 10 build (RTM) 10240 and today I wanted to reset my PC since I was getting some pretty poor gaming performance. Anyway I ran the reset and after it finished resetting, it got constant BSODs of inaccessible_boot_device....
BSOD Crashes and Debugging
BSOD during update from Windows 10 TP
In first, sorry for any English mistakes, I'm Dutch. I'm experiencing a BSOD during the update from Windows 10 TP build 10074 to 10122 or the newer 100130. When the install is at 32% it crashes with the error CRITICAL_PROCESS_DIED or...
BSOD Crashes and Debugging
Windows 10 BSOD Analysis
Hello all, Just wondering if there is any fundamental differences between analyzing Windows 10 dumps in comparison to Windows 7/Windows 8 dumps? If there is, is there are link with more information on it or are we kind of at the forefront of...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:00.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums