1 Reply Latest reply on Nov 11, 2015 1:01 PM by Amy_Intel

    Windows 10 on C602 causes DPC_WATCHDOG_VIOLATION BSOD with latest driver version (4.3.0.1198)

    matze2ooo

      I am currently running Windows 10 Pro on a Fujitsu Siemens M730 workstation which is using the Intel Patsburg A C602 chipset. I did a fresh installation of Windows 10 Pro and my BIOS is on the latest version available. This is what my hardware configuration looks like:

       

      Intel C600 series chipset SATA AHCI controller

      Port0: Samsung SSD 830 (latest firmware)

      Port1: DVD

      Intel C600 series chipset SAS RAID (SATA mode) controller

      Port2: SATA HD 1TB (part of raid0 array0)

      Port3: SATA HD 1TB (part of raid0 array0)

      Port4: SATA HD 1TB (part of raid0 array0)

      Port5: SATA HD 4TB (backup disk)

       

      I am running and have installed driver version 4.3.0.1198 by using the Fujitsu DesktUpdate utility. Now I am suffering from random kernel crashes (was running just rock solid on Windows 8.1 Pro before). This driver seems to be approved by Fujitsu for Windows 10 Pro x64. However there are several forum posts out there saying the latest intel driver is not compatible with Windows 10.

       

      Are Intel developers already working on this issue? Please let me know if you need some kernel crash dumps!! Thanks in advance!

       

      This is what WinDbg says (further down anothe one).

      ====================================================================================

      3: 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:  S26361-Kxxx-Vyyy

      SYSTEM_VERSION:                       

      BIOS_DATE:  02/17/2015

      BASEBOARD_PRODUCT:  D3128-A2

      BASEBOARD_VERSION:  S26361-D3128-A2           

      BUGCHECK_P1: 1

      BUGCHECK_P2: 1e00

      BUGCHECK_P3: 0

      BUGCHECK_P4: 0

      DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

      CPU_COUNT: 8

      CPU_MHZ: e74

      CPU_VENDOR:  GenuineIntel

      CPU_FAMILY: 6

      CPU_MODEL: 3e

      CPU_STEPPING: 4

      CUSTOMER_CRASH_COUNT:  1

      DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

      BUGCHECK_STR:  0x133

      PROCESS_NAME:  System

      CURRENT_IRQL:  d

      ANALYSIS_VERSION: 10.0.10240.9 x86fre

      LAST_CONTROL_TRANSFER:  from fffff80122980380 to fffff801229672e0

       

       

      STACK_TEXT: 

      ffffd001`d5c86a28 fffff801`22980380 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx

      ffffd001`d5c86a30 fffff801`228248cf : fffff780`00000320 2edf8262`71db2a3f 00000000`0000000b 00000000`000a9c4d : nt! ?? ::FNODOBFM::`string'+0xa480

      ffffd001`d5c86ac0 fffff801`2306dd15 : ffffe001`eb5005b0 ffffd001`d6717bf0 ffffe001`eb500500 00000000`00000000 : nt!KeClockInterruptNotify+0x9f

      ffffd001`d5c86cf0 fffff801`228ed5d7 : 00000000`00000002 00000000`000a9c49 ffffe001`eb500500 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15

      ffffd001`d5c86d20 fffff801`229686aa : ffffe001`eb500500 ffffe001`eddfc2e8 000024a8`1bea9261 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0x87

      ffffd001`d5c86d60 fffff801`22968ad7 : ffffe001`fe330000 fffff801`229a522b ffffe001`fdf6b940 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

      ffffd001`d5c86db0 fffff801`22824453 : ffffffff`00400a02 fffff801`228f4945 fffff801`a39051c0 00000000`00005000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

      ffffd001`d5c86f40 fffff801`228ed66e : ffffd001`d6717b40 00000000`00000000 ffff4efb`ebb53a6e 00000000`00000010 : nt!KxWaitForSpinLockAndAcquire+0x23

      ffffd001`d5c86f70 fffff801`22968468 : ffffd001`d6717b40 5fb83e1c`d196b7e5 bab9f677`f9a204f8 d1200139`b56063c4 : nt!KiCallInterruptServiceRoutine+0x11e

      ffffd001`d5c86fb0 fffff801`229686f7 : ffffd001`00000012 ffffe001`f1fc81b0 ffffd001`d5bf0030 ffffe001`ff385860 : nt!KiInterruptSubDispatch+0x108

      ffffd001`d5bf8310 fffff801`a3143487 : ffffd001`d5bf84d0 00000000`00000000 00000000`00000000 00000064`00000064 : nt!KiInterruptDispatch+0x37

      ffffd001`d5bf84a0 fffff801`a314d75d : ffffd001`d5bf86d0 ffffd001`d5bd4444 00000000`00000000 00000000`00000000 : cng!SymCryptSha512AppendBlocks_ull+0x907

      ffffd001`d5bf86c0 fffff801`a314cd8b : 00000000`00000000 00000000`000000f0 00000000`0001f400 00001f80`00000200 : cng!SymCryptSha512Append+0xcd

      ffffd001`d5bf8700 fffff801`a314cf28 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cng!EntropyPoolAdd+0x6f

      ffffd001`d5bf87a0 fffff801`2291445f : 00000000`0000002f 00000000`00000000 00000000`00000000 ffffe001`faf5cb10 : cng!EntropyProvideData+0x128

      ffffd001`d5bf8890 fffff801`22869e65 : ffffd001`d5bd0f00 00000001`ffffffff ff000100`00010000 00000001`ffffffff : nt!KiEntropyDpcRoutine+0x37

      ffffd001`d5bf88c0 fffff801`22869540 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x275

      ffffd001`d5bf8a10 fffff801`2296a03a : ffffd001`d5bce180 ffffd001`d5bce180 ffffd001`d5bdacc0 ffffe001`ee5fb040 : nt!KiRetireDpcList+0xe0

      ffffd001`d5bf8c60 00000000`00000000 : ffffd001`d5bf9000 ffffd001`d5bf3000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

       

       

      STACK_COMMAND:  kb

      FOLLOWUP_IP:

      nt! ?? ::FNODOBFM::`string'+a480

      fffff801`22980380 cc              int     3

       

       

      SYMBOL_STACK_INDEX:  1

      SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+a480

      FOLLOWUP_NAME:  MachineOwner

      MODULE_NAME: nt

      IMAGE_NAME:  ntkrnlmp.exe

      DEBUG_FLR_IMAGE_TIMESTAMP:  560ca418

      IMAGE_VERSION:  10.0.10240.16545

      BUCKET_ID_FUNC_OFFSET:  a480

      FAILURE_BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_

      BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_

      PRIMARY_PROBLEM_CLASS:  0x133_ISR_nt!_??_::FNODOBFM::_string_

      ANALYSIS_SOURCE:  KM

      FAILURE_ID_HASH_STRING:  km:0x133_isr_nt!_??_::fnodobfm::_string_

      FAILURE_ID_HASH:  {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}

      ====================================================================================

       

       

       

       

      5: 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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

        component can usually be identified with a stack trace.

      Arg2: 0000000000000501, The DPC time count (in ticks).

      Arg3: 0000000000000500, The DPC time allotment (in ticks).

      Arg4: 0000000000000000

       

       

      Debugging Details:

      ------------------

       

       

      *** WARNING: Unable to verify timestamp for iaStorS.sys

      *** ERROR: Module load completed but symbols could not be loaded for iaStorS.sys

       

       

      SYSTEM_SKU:  S26361-Kxxx-Vyyy

      SYSTEM_VERSION:                       

      BIOS_DATE:  10/14/2013

      BASEBOARD_PRODUCT:  D3128-A2

      BASEBOARD_VERSION:  S26361-D3128-A2           

      BUGCHECK_P1: 0

      BUGCHECK_P2: 501

      BUGCHECK_P3: 500

      BUGCHECK_P4: 0

      DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

      CPU_COUNT: 8

      CPU_MHZ: e74

      CPU_VENDOR:  GenuineIntel

      CPU_FAMILY: 6

      CPU_MODEL: 3e

      CPU_STEPPING: 4

      CUSTOMER_CRASH_COUNT:  1

      DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

      BUGCHECK_STR:  0x133

      PROCESS_NAME:  System

      CURRENT_IRQL:  d

      ANALYSIS_VERSION: 10.0.10240.9 amd64fre

      LAST_CONTROL_TRANSFER:  from fffff8007e381326 to fffff8007e3682e0

      STACK_TEXT: 

      ffffd001`430a9c78 fffff800`7e381326 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

      ffffd001`430a9c80 fffff800`7e2258cf : 00000000`00000282 fffff800`7ea6ed15 00000000`00000002 00000000`00002f6c : nt! ?? ::FNODOBFM::`string'+0xa426

      ffffd001`430a9d10 fffff800`7ea6ed15 : ffffffff`00400a02 fffff800`7e2f5945 ffffe001`5a500900 00000000`00000000 : nt!KeClockInterruptNotify+0x9f

      ffffd001`430a9f40 fffff800`7e2ee5d7 : ffffd001`430a9f60 00000000`00000008 ffffd001`430a9f50 00000000`00000010 : hal!HalpTimerClockIpiRoutine+0x15

      ffffd001`430a9f70 fffff800`7e3696aa : ffffe001`5a500900 ffffe001`5d69b858 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x87

      ffffd001`430a9fb0 fffff800`7e369ad7 : fffff801`654c8bf0 ffffe001`649f9e70 ffffe001`649f9e88 fffff801`6552d1a5 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

      ffffd001`4309b660 fffff801`65515513 : fffff801`65524a24 00000000`00000000 ffffe001`5d5fa010 00000000`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x37

      ffffd001`4309b7f8 fffff801`65524a24 : 00000000`00000000 ffffe001`5d5fa010 00000000`00000002 00000000`00000000 : iaStorS+0x65513

      ffffd001`4309b800 00000000`00000000 : ffffe001`5d5fa010 00000000`00000002 00000000`00000000 ffffd001`4342dbf0 : iaStorS+0x74a24

       

       

      STACK_COMMAND:  kb

      FOLLOWUP_IP:

      iaStorS+65513

      fffff801`65515513 ??              ???

      SYMBOL_STACK_INDEX:  7

      SYMBOL_NAME:  iaStorS+65513

      FOLLOWUP_NAME:  MachineOwner

      MODULE_NAME: iaStorS

      IMAGE_NAME:  iaStorS.sys

      DEBUG_FLR_IMAGE_TIMESTAMP:  556d909b

      BUCKET_ID_FUNC_OFFSET:  65513

      FAILURE_BUCKET_ID:  0x133_DPC_iaStorS!Unknown_Function

      BUCKET_ID:  0x133_DPC_iaStorS!Unknown_Function

      PRIMARY_PROBLEM_CLASS:  0x133_DPC_iaStorS!Unknown_Function

      ANALYSIS_SOURCE:  KM

      FAILURE_ID_HASH_STRING:  km:0x133_dpc_iastors!unknown_function

      FAILURE_ID_HASH:  {273366a2-964c-976d-d232-63c3ba9affee}

      Followup:     MachineOwner

      ---------