Feil på Asus X99-Deluxe II

Kjetil Lura · 7. oktober 2017

Hehe, planlegger du 3 gpu til folding. :tease: Har du 5960x?

Chavalito · 7. oktober 2017

Neida, har 2 x GTX 980 Ti pluss et Areca 1224i RAID kort og 6850K. Har jo lyst på 2 x GTX 1080 Ti, men det blir ikke enda.

Kjetil Lura · 7. oktober 2017

Har 3 jeg, skulle ikke kjøpe flere gpu enda. Men ti er raske på folding,

Chavalito · 9. oktober 2017

Javel ja, da fikk man svar fra nettbutikken, så det er bare å begynne å demontere hele stasen og sende HK til dem. Har en liten mistanke om at de ikke kommer til å oppleve samme problemet. :hmm:

Chavalito · 9. oktober 2017

Kjørte en liten debug på crashene, samme feil som skjer hver gang.

Microsoft ® Windows Debugger Version 10.0.15063.468 AMD64

Loading Dump File [C:\Windows\Minidump\100917-17390-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 15063 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff801`2887d000 PsLoadedModuleList = 0xfffff801`28bc95c0

Debug session time: Mon Oct 9 14:34:47.284 2017 (UTC + 2:00)

System Uptime: 0 days 0:18:23.984

Loading Kernel Symbols

...............................................................

................................................................

...............

Loading User Symbols

Loading unloaded module list

.............

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {0, 501, 500, fffff80128c5e348}

*************************************************************************

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: TickPeriods ***

*** ***

*************************************************************************

Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+124b88 )

Followup: MachineOwner

---------

4: 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: fffff80128c5e348, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding this single DPC timeout

Debugging Details:

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