Windows 10: BSOD - PC Hanging intermittent - Two Independent Errors Happening

Please find the DUMP file attached

BIOS_VERSION updated to : F9d

Mother Board Model - Z270-HD3P


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



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


Loading Dump File [C:\Windows\Minidump\121118-11093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`23a03000 PsLoadedModuleList = 0xfffff800`23db1170
Debug session time: Tue Dec 11 14:23:58.272 2018 (UTC + 5:30)
System Uptime: 1 days 23:54:16.078
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
........................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`23bac680 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd481`7e7ffbd0=0000000000000133
1: 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: fffff80023e50378, 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 ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z270-HD3P

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F9d

BIOS_DATE: 03/09/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z270-HD3P-CF

BASEBOARD_VERSION: x.x

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80023e50378

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 4

CPU_MHZ: d50

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: DESKTOP-JKNNDPV

ANALYSIS_SESSION_TIME: 12-11-2018 16:13:23.0932

ANALYSIS_VERSION: 10.0.18272.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff80023bfe605 to fffff80023bac680

STACK_TEXT:
ffffd481`7e7ffbc8 fffff800`23bfe605 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd481`7e7ffbd0 fffff800`23ae337a : 00003dd0`d2681666 ffffd481`7e800180 00000000`00000282 00000000`00000000 : nt!KeAccumulateTicks+0x118945
ffffd481`7e7ffc30 fffff800`2435951b : 00003dd0`d267a23c fffff800`23b2fd75 00000000`00000000 ffff9081`adafe000 : nt!KeClockInterruptNotify+0x9da
ffffd481`7e7fff40 fffff800`23b2fd75 : ffff9081`adafe000 00000000`00000068 ffff9081`b299d750 fffff800`23badcdf : hal!HalpTimerClockIpiRoutine+0x1b
ffffd481`7e7fff70 fffff800`23badf3a : ffffab8f`0a436fb0 ffff9081`adafe000 fffff800`23a03000 ffffd481`7e800180 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd481`7e7fffb0 fffff800`23bae427 : ffff9081`b2b95940 00000000`00000000 ffff9081`b2b95b40 fffff800`23dd0620 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffab8f`0a436f30 fffff800`23a42960 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000001 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffab8f`0a4370c0 fffff800`23a41670 : ffffceea`40c03cf8 ffffcee7`75206018 ffff6dc6`f02cf2be ffffcee7`73b9dd48 : nt!KiChooseTargetProcessor+0x6b0
ffffab8f`0a4371f0 fffff800`23a41313 : ffffd481`7e800180 00000000`0009ca88 ffff9081`b72ddbd8 00000000`00000000 : nt!KiDeferredReadyThread+0x240
ffffab8f`0a4372b0 fffff800`23a4111f : ffff9081`b80c01f0 00000000`00000000 00000000`00000001 fffff800`00000001 : nt!KiReadyThread+0x33
ffffab8f`0a4372e0 fffff800`23a40111 : ffff9081`b72ddba0 ffff9081`0000018b ffffd481`7e85d180 00000000`00000000 : nt!KiExitDispatcher+0xff
ffffab8f`0a437350 fffff800`23a3fa97 : 00000000`00000001 ffff9081`b2b9f106 ffff9081`b22bbec0 00000000`00000001 : nt!IopfCompleteRequest+0x661
ffffab8f`0a437470 fffff809`f6eb96d0 : ffff9081`b22bbeb0 00000000`00000002 ffffab8f`0a437511 00000000`00000040 : nt!IofCompleteRequest+0x17
ffffab8f`0a4374a0 fffff809`f6eb9a04 : ffff9081`b2b9f1d0 ffff9081`b2b9f102 ffff9081`b224b3e0 ffff9081`00000040 : HIDCLASS!HidpDistributeInterruptReport+0x1f4
ffffab8f`0a437570 fffff800`23a3fbcf : ffff9081`b22b5b40 ffff9081`b22b5b40 ffffab8f`0a437601 ffff9081`b22b5f2b : HIDCLASS!HidpInterruptReadComplete+0x304
ffffab8f`0a437610 fffff800`23a3fa97 : ffff9081`b1e7a980 00000000`00000200 fffff809`f30ade40 00000000`0000000a : nt!IopfCompleteRequest+0x11f
ffffab8f`0a437730 fffff809`f3009627 : ffff9081`b8307890 ffff9081`b22b5b40 00000000`00000002 ffff9081`b2b9a020 : nt!IofCompleteRequest+0x17
ffffab8f`0a437760 fffff809`f30072fb : ffffab8f`00000001 fffff809`00000000 00000000`ffffff02 ffff9081`00000002 : Wdf01000!FxRequest::CompleteInternal+0x247 [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
ffffab8f`0a437820 fffff809`f833f336 : 00000000`ffffff02 ffff9081`b8307890 ffff9081`b2b9a400 ffff9081`b2b9a400 : Wdf01000!imp_WdfRequestComplete+0x8b [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
ffffab8f`0a437880 fffff809`f833d469 : ffff9081`b8307a30 00000000`00000001 ffff9081`b8307ac0 ffffab8f`0a437b68 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x182
ffffab8f`0a4378e0 fffff809`f833bde0 : 00000000`00000000 00000000`00000000 ffff9081`b1920c00 00000000`00000000 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x40d
ffffab8f`0a4379a0 fffff809`f83312c3 : 00000000`00000001 00000000`00000017 00000000`00000017 00000003`00000001 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
ffffab8f`0a4379d0 fffff809`f8324608 : 00000000`00000001 00000000`00000004 ffff9081`b1efeab0 ffffab8f`0a437ad1 : USBXHCI!TR_TransferEventHandler+0x17
ffffab8f`0a437a00 fffff809`f83437ae : ffffab8f`0a437b68 ffffab8f`0a437b38 00000000`00000000 ffffab8f`0a437b40 : USBXHCI!Endpoint_TransferEventHandler+0x148
ffffab8f`0a437a90 fffff809`f832744d : ffff9081`b1efe9e0 ffffab8f`0a437b89 ffff9081`b1efeab0 ffffab8f`0a437bf4 : USBXHCI!UsbDevice_TransferEventHandler+0x92
ffffab8f`0a437af0 fffff809`f8327e6c : 00000001`00000003 00000000`00000000 00000000`0000000f ffff9081`b1efe7e0 : USBXHCI!Interrupter_DeferredWorkProcessor+0x4c5
ffffab8f`0a437bf0 fffff809`f3001fad : ffffab8f`0a437d60 ffffd481`7e800100 00000000`00000001 ffffab8f`0a437e60 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
ffffab8f`0a437c20 fffff800`23ae0327 : 00000000`00000000 ffff9081`b69f4080 ffff9081`b69f4080 fffff800`23a41313 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]
ffffab8f`0a437c60 fffff800`23adf97b : 00000000`00000012 3365734c`00000000 00000000`00989680 00000000`00000019 : nt!KiExecuteAllDpcs+0x2e7
ffffab8f`0a437da0 fffff800`23bb35d5 : 00000000`00000000 ffffd481`7e800180 ffffab8f`0aa6e400 ffffd481`7f080500 : nt!KiRetireDpcList+0x1db
ffffab8f`0a437fb0 fffff800`23bb33d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffab8f`0aa6e340 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


THREAD_SHA1_HASH_MOD_FUNC: 9ad8c81b75664e6da113cfe35efe8aacb0bf445f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 10bc3e893523aa05184cb469d9e48e0caf749393

THREAD_SHA1_HASH_MOD: cfffd123260f0c98e7869fd8026017023f954c67

FOLLOWUP_IP:
HIDCLASS!HidpDistributeInterruptReport+1f4
fffff809`f6eb96d0 ebc3 jmp HIDCLASS!HidpDistributeInterruptReport+0x1b9 (fffff809`f6eb9695)

FAULT_INSTR_CODE: 3b9c3eb

SYMBOL_STACK_INDEX: d

SYMBOL_NAME: HIDCLASS!HidpDistributeInterruptReport+1f4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME: HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17134.1

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1f4

FAILURE_BUCKET_ID: 0x133_DPC_HIDCLASS!HidpDistributeInterruptReport

BUCKET_ID: 0x133_DPC_HIDCLASS!HidpDistributeInterruptReport

PRIMARY_PROBLEM_CLASS: 0x133_DPC_HIDCLASS!HidpDistributeInterruptReport

TARGET_TIME: 2018-12-11T08:53:58.000Z

OSBUILD: 17134

OSSERVICEPACK: 441

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: 2018-11-09 07:49:47

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 62c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_hidclass!hidpdistributeinterruptreport

FAILURE_ID_HASH: {d959ecac-3642-962b-0e8f-70c518b48d15}

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

1: kd> lmvm HIDCLASS
Browse full module list
start end module name
fffff809`f6eb0000 fffff809`f6ee3000 HIDCLASS (pdb symbols) C:\ProgramData\Dbg\sym\hidclass.pdb\B8B9E5343438CAEEB31BF4E5C9BB91801\hidclass.pdb
Loaded symbol image file: HIDCLASS.SYS
Mapped memory image file: C:\ProgramData\Dbg\sym\HIDCLASS.SYS\CAEE994233000\HIDCLASS.SYS
Image path: \SystemRoot\System32\drivers\HIDCLASS.SYS
Image name: HIDCLASS.SYS
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: CAEE9942 (This is a reproducible build file hash, not a timestamp)
CheckSum: 0002DC27
ImageSize: 00033000
File version: 10.0.17134.1
Product version: 10.0.17134.1
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: hidclass.sys
OriginalFilename: hidclass.sys
ProductVersion: 10.0.17134.1
FileVersion: 10.0.17134.1 (WinBuild.160101.0800)
FileDescription: Hid Class Library
LegalCopyright: © Microsoft Corporation. All rights reserved.


@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

:)

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?

 

BSOD - Registry Error

Your BSOD code is 0X000000051

Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

+1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

Run a Diskchk /R (I know you already ran one, so you can skip this)

Run SFC /SCANNOW

Report back.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.