Windows 10: Windows 10 Home 2004 BSOD Error

Received the following:


Microsoft R Windows Debugger Version 10.0.19041.1 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\031221-16906-01.dmp]

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





************* 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 19041 MP 12 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff800`40000000 PsLoadedModuleList = 0xfffff800`40c2a390

Debug session time: Fri Mar 12 13:49:38.212 2021 UTC - 5:00

System Uptime: 0 days 23:25:50.844

Loading Kernel Symbols

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

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

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

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

Loading User Symbols

Loading unloaded module list

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

For analysis of this file, run !analyze -v

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

additional information regarding the cumulative timeout

Arg4: 0000000000000000



Debugging Details:

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



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

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

*** ***

*** ***

*** 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



Key : Analysis.CPU.Sec

Value: 3



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on ANONYMOUS-PC



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 9



Key : Analysis.Memory.CommitPeak.Mb

Value: 92



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 133



BUGCHECK_P1: 1



BUGCHECK_P2: 1e00



BUGCHECK_P3: fffff80040cfb320



BUGCHECK_P4: 0



DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: Teams.exe



STACK_TEXT:

fffff800`3c99ae18 fffff800`4043ad0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`40cfb320 : nt!KeBugCheckEx

fffff800`3c99ae20 fffff800`4026f9a3 : 0000fb1b`91b99a2a fffff800`3aa59180 00000000`00000000 fffff800`3aa59180 : nt!KeAccumulateTicks+0x1c8b0c

fffff800`3c99ae80 fffff800`4026f48a : fffff800`40cf38c0 fffff800`3c9934d0 00000000`00000000 fffff800`3c99af20 : nt!KeClockInterruptNotify+0x453

fffff800`3c99af30 fffff800`40327ef5 : fffff800`40cf38c0 fffff800`403f7140 ffff9b01`1d9ee648 ffff9b01`1d9ee640 : nt!HalpTimerClockIpiRoutine+0x1a

fffff800`3c99af60 fffff800`403f752a : fffff800`3c9934d0 fffff800`40cf38c0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

fffff800`3c99afb0 fffff800`403f7a97 : ffff9b01`1d9ee640 fffff800`402ec5ca ffff9b01`1d9ee640 fffff800`402ec5ca : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

fffff800`3c993450 fffff800`402fd13d : ffff8881`0fae8750 ffff8881`0d3d1010 ffffffff`ffffff91 fffff800`4025a2fa : nt!KiInterruptDispatchNoLockNoEtw+0x37

fffff800`3c9935e0 fffff800`423d2fa7 : ffff8881`0fae8750 ffff8881`0d3d1010 fffff800`3c993658 ffff888f`fbdea1c0 : nt!IoReleaseRemoveLockEx+0x3d

fffff800`3c993630 fffff800`40316f56 : ffff8881`0fae8750 ffff888f`fbdea1c0 fffff800`3c993688 00000000`00000018 : Wdf01000!FxDevice::_CompletionRoutineForRemlockMaintenance+0x37 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 139]

fffff800`3c993660 fffff800`4024885e : ffff8881`0d3d1010 fffff800`3c993719 ffff8881`0fae8750 ffff8881`0d3d175b : nt!IopUnloadSafeCompletion+0x56

fffff800`3c993690 fffff800`40248727 : ffffffff`ffffff91 fffff800`423d8000 00000000`01000010 00000000`00000282 : nt!IopfCompleteRequest+0x11e

fffff800`3c993780 fffff800`423d811a : 00000000`00000000 ffff888f`ed793d30 ffff8881`0d3d1010 00000000`00000000 : nt!IofCompleteRequest+0x17

fffff800`3c9937b0 fffff800`423d5bbf : ffff8881`0ab4cb02 00000000`00000286 ffff8881`0d3d1010 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]

fffff800`3c993840 fffff800`52ebb91d : 00000000`ffffff02 ffff8881`0ab4ca30 ffff8881`114cde10 ffff8881`114cde10 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]

fffff800`3c9938a0 fffff800`52ebb7e1 : ffff8881`0ab4cbd0 00000000`00000008 ffff8881`0ab4cc60 fffff800`3c993ab8 : USBXHCI!Bulk_Transfer_CompleteCancelable+0xc9

fffff800`3c993900 fffff800`52ebb5d0 : ffffffff`ffffff91 fffff800`52eb6564 00000000`00000000 ffff8881`17bf2a60 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd

fffff800`3c9939b0 fffff800`52eb6571 : 00000000`00000004 fffff800`3c993a88 ffff888f`f4244730 fffff800`3c993ad9 : USBXHCI!Bulk_EP_TransferEventHandler+0x10

fffff800`3c9939e0 fffff800`52eb60a5 : 00000000`00000780 ffff888f`f4244500 ffff888f`f4244730 ffff888f`fb21b7f0 : USBXHCI!Endpoint_TransferEventHandler+0xb1

fffff800`3c993a40 fffff800`52eb5d7c : 00000000`01000010 00000000`00000202 00007770`121aff98 00000000`00000018 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315

fffff800`3c993b40 fffff800`423d38f6 : ffffffff`ffffff91 fffff800`423d385a 00000000`01000010 00000000`00000246 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc

fffff800`3c993b70 fffff800`4020781e : fffff800`3aa5c240 ffff888f`ebc0f000 fffff800`3c993ea0 fffff800`00000002 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa6 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]

fffff800`3c993bb0 fffff800`40206b04 : fffff800`3aa59180 00000000`00000000 00000000`00000008 00000000`00310773 : nt!KiExecuteAllDpcs+0x30e

fffff800`3c993d20 fffff800`403fcac5 : 00000000`00000000 fffff800`3aa59180 ffff9b01`1d9ee640 ffff888f`f8d40010 : nt!KiRetireDpcList+0x1f4

fffff800`3c993fb0 fffff800`403fc8b0 : ffffffff`ffffff91 fffff800`403fc151 00000000`01000010 00000000`00000286 : nt!KxRetireDpcList+0x5

fffff004`0620d960 fffff800`403fc165 : ffff888f`f8d40010 fffff800`403f6dd1 00000000`00000013 fffff004`0620da40 : nt!KiDispatchInterruptContinue

fffff004`0620d990 fffff800`403f6dd1 : 00000000`00000013 fffff004`0620da40 ffff888f`f85f2b30 00000000`00000000 : nt!KiDpcInterruptBypass+0x25

fffff004`0620d9a0 fffff800`5405aa50 : fffff800`5435c46a 00000000`0010a000 ffff888f`0000000a 00000000`00000040 : nt!KiChainedDispatch+0xb1

fffff004`0620db38 fffff800`5435c46a : 00000000`0010a000 ffff888f`0000000a 00000000`00000040 00000000`00000000 : nvlddmkm+0x43aa50

fffff004`0620db40 00000000`0010a000 : ffff888f`0000000a 00000000`00000040 00000000`00000000 ffff888f`f85f2b30 : nvlddmkm+0x73c46a

fffff004`0620db48 ffff888f`0000000a : 00000000`00000040 00000000`00000000 ffff888f`f85f2b30 fffff800`5435bb97 : 0x10a000

fffff004`0620db50 00000000`00000040 : 00000000`00000000 ffff888f`f85f2b30 fffff800`5435bb97 00000000`00000000 : 0xffff888f`0000000a

fffff004`0620db58 00000000`00000000 : ffff888f`f85f2b30 fffff800`5435bb97 00000000`00000000 ffff888f`f8d40010 : 0x40





SYMBOL_NAME: USBXHCI!Bulk_Transfer_CompleteCancelable+c9



MODULE_NAME: USBXHCI



IMAGE_NAME: USBXHCI.SYS



IMAGE_VERSION: 10.0.19041.508



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: c9



FAILURE_BUCKET_ID: 0x133_ISR_USBXHCI!Bulk_Transfer_CompleteCancelable



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {d260b770-d2fa-e728-70c2-bee182a5e8b3}



Followup: MachineOwner

---------

:)

 

2004 update windows 10 error 0x80070002

Hello everyone,

thanks to some of the suggestions here and to some from other sources I have managed to fix the 0x80070002 error breaking up my feature update to 2004.

For completeness' sake and since it may help others, the following steps worked for me.

1. Download Media Creation Tool from Microsoft's official website
2. Create a bootable USB drive with the MCT
3. Boot up from this USB Drive
4. Choose install settings, click 'Next', but on the next screen select "Repair your computer" instead of "Install"
5. Choose "Troubleshoot" -> "Startup Repair" and let it finish
6. Restart into Windows and attempt the usual Windows update

It looks like the BCD on my computer had been damaged by the boot loader (Windows 10 + Recovery partition) and running the "Startup Repair" from the installation USB Drive corrected the errors.

 

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.

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.