Gå til innhold
Trenger du hjelp med PCen? Still spørsmål her! ×

Feil på Asus X99-Deluxe II


Anbefalte innlegg

Videoannonse
Annonse

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

 

 

Microsoft ® Windows Debugger Version 10.0.15063.468 AMD64

Copyright © Microsoft Corporation. All rights reserved.
 
 
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:
------------------
 
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                   ***
***                                                                   ***
*************************************************************************
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 400
 
BUILD_VERSION_STRING:  10.0.15063.608 (WinBuild.160101.0800)
 
DUMP_TYPE:  2
 
DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump
 
BUGCHECK_P1: 0
 
BUGCHECK_P2: 501
 
BUGCHECK_P3: 500
 
BUGCHECK_P4: fffff80128c5e348
 
DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
 
CPU_COUNT: c
 
CPU_MHZ: e16
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 4f
 
CPU_STEPPING: 1
 
CPU_MICROCODE: 6,4f,1,0 (F,M,S,R)  SIG: B00001C'00000000 (cache) B00001C'00000000 (init)
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x133
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  d
 
ANALYSIS_SESSION_HOST:  GAMER-PC
 
ANALYSIS_SESSION_TIME:  10-09-2017 17:37:06.0431
 
ANALYSIS_VERSION: 10.0.15063.468 amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff80128a19568 to fffff801289e9580
 
STACK_TEXT:  
ffffc601`9d64dbc8 fffff801`28a19568 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffc601`9d64dbd0 fffff801`288f2d49 : 000011dd`e16e70fc ffffc601`9d5cf180 00000000`000113ff 00000000`00000006 : nt!KeAccumulateTicks+0x124b88
ffffc601`9d64dc30 fffff801`28804676 : 000011dd`e16dd728 00000000`00100000 ffffc601`9d6469d0 ffffb28e`c26c81b0 : nt!KeClockInterruptNotify+0x599
ffffc601`9d64df40 fffff801`2888c675 : ffffb28e`c26c8100 ffffc601`9d646a50 00000000`00000000 ffffa8d4`4c8702fd : hal!HalpTimerClockInterrupt+0x56
ffffc601`9d64df70 fffff801`289eac1a : ffffc601`9d646a50 ffffb28e`c26c8100 ffffc601`9d646e60 ffffc601`9d5cf180 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc601`9d64dfb0 fffff801`289eb067 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffc601`9d6469d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
 
 
STACK_COMMAND:  kb
 
THREAD_SHA1_HASH_MOD_FUNC:  5e958d63ed6cce864bfe4c595207e0e484aa7e7c
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b1ab1ad688253afe00c5b61330e101015423f505
 
THREAD_SHA1_HASH_MOD:  e2266a530ca7fbace00cfa9add8dc0ac4504d759
 
FOLLOWUP_IP: 
nt!KeAccumulateTicks+124b88
fffff801`28a19568 cc              int     3
 
FAULT_INSTR_CODE:  f68445cc
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt!KeAccumulateTicks+124b88
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  59ae237e
 
IMAGE_VERSION:  10.0.15063.608
 
BUCKET_ID_FUNC_OFFSET:  124b88
 
FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks
 
BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks
 
PRIMARY_PROBLEM_CLASS:  0x133_DPC_nt!KeAccumulateTicks
 
TARGET_TIME:  2017-10-09T12:34:47.000Z
 
OSBUILD:  15063
 
OSSERVICEPACK:  608
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2017-09-05 06:09:34
 
BUILDDATESTAMP_STR:  160101.0800
 
BUILDLAB_STR:  WinBuild
 
BUILDOSVER_STR:  10.0.15063.608
 
ANALYSIS_SESSION_ELAPSED_TIME:  689
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x133_dpc_nt!keaccumulateticks
 
FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}
 
Followup:     MachineOwner
---------
 

 

 

 

Minidump analysis.txt

Lenke til kommentar

Tja, nei, egentlig ikke. Men jeg har gjort en liten test som fortsetter i natt/morgen. PC'en funket helt normalt i nesten 5 timer etter at jeg tok ut Areca RAID kortet, så da er frågen: Er det Areca 1224-8i kortet, Areca driver (siste versjon) eller PCIe sportet som er den skyldig?

 

Kunne ikke fortsette lenger da det er tid for å spille litt, og alle spill ligger på Areca RAID , så jeg må bruke den bærbare nå.

 

Følg med, følg med, spennende fortsettelse i morgen.  :rofl:

Lenke til kommentar

Javel,  da var PC'en vært på i hele natt uten problemer, så problemet har med Areca kortet eller PCIe sporet å gjøre. Skal se om jeg får trykket Areca kortet inn i et annet PCIe spor da HK har 3 spor ledige, men jeg kan kun bruke 2 av de ledige PCIe sporene pga et PCIe spor er for nær det andre 980 Ti kortet..

Lenke til kommentar

Nei, men jeg lurer på å bytte om kortene da jeg har et Areca kort i serveren også. På en annen side hvis jeg setter Areca kortet i PCIe spor 2 og samme feil skjer, så må jeg nesten anta at det er Areca kortet som tuller. Nekter å tro at PCIe_2 og PCIe_5 sporene har begge samme problem.

Lenke til kommentar

Ja, det kan man si. Men jeg må jo "skryte" litt av Iwill, de var raske å svare, så i morgen blir Areca kortet sent til dem. Areca vil enten prøve å reparere kortet eller så får jeg et nytt et. Vi får se hvordan det går. 

Endret av Chavalito
Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!

Start en konto

Logg inn

Har du allerede en konto? Logg inn her.

Logg inn nå
×
×
  • Opprett ny...