BSOD DPC_WATCHDOG_VIOLATION (133)

Hi,

I keep getting this BSOD 133 after installing Windows 10.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+a07a )

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

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


DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff802fd56ee7a to fffff802fd556240

STACK_TEXT:  
ffffd000`26169a28 fffff802`fd56ee7a : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
ffffd000`26169a30 fffff802`fd4121cf : ffffe000`35795100 00000000`00000000 00000000`00000009 00000000`0000298b : nt! ?? ::FNODOBFM::`string'+0xa07a
ffffd000`26169ac0 fffff802`fdc5cd15 : 00000000`00000010 00000000`00000246 ffffe000`35795100 00000000`00000000 : nt!KeClockInterruptNotify+0x9f
ffffd000`26169cf0 fffff802`fd4d9257 : ffffbd3a`a3d8b40e 00000000`00002962 00000000`00000001 fffff800`416b9ee8 : hal!HalpTimerClockIpiRoutine+0x15
ffffd000`26169d20 fffff802`fd55760a : ffffe000`35795100 ffffe000`375dccd0 00000059`58fce48d 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0x87
ffffd000`26169d60 fffff802`fd557a37 : 00000000`00000060 fffff800`41701e0b ffffe000`3ba1e000 00000000`00000f82 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`26169db0 fffff802`fd411d53 : ffffffff`ffffffd2 00000000`00010008 ffffe000`35795100 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd000`26169f40 fffff802`fd4d92ee : ffffd000`24a3fdc0 ffffd000`2615b390 ffffffff`ffffffd2 fffff802`fd557385 : nt!KxWaitForSpinLockAndAcquire+0x23
ffffd000`26169f70 fffff802`fd5573c8 : ffffd000`24a3fdc0 5ce97c12`cd4dbc01 8adec6de`0fa33906 c9bc16f6`1ac5ed3a : nt!KiCallInterruptServiceRoutine+0x11e
ffffd000`26169fb0 fffff802`fd557657 : ffffe000`35772712 ffffe000`375ba1b0 ffffe000`375b00d0 ffffe000`3a104010 : nt!KiInterruptSubDispatch+0x108
ffffd000`2615b310 fffff800`3ad8354a : 00000000`00000000 ffffe000`3a104010 00000000`00000000 fffff802`fd45326d : nt!KiInterruptDispatch+0x37
ffffd000`2615b4a0 fffff800`3ad8d6df : 00000000`1b82b889 ffffd000`26106424 00000000`1b891583 00000000`00000000 : cng!SymCryptSha512AppendBlocks_ull+0x9ca
ffffd000`2615b6c0 fffff800`3ad8cd8b : 00000000`00000000 00000000`00000000 00000000`0001f400 00000000`00000000 : cng!SymCryptSha512Append+0x4f
ffffd000`2615b700 fffff800`3ad8cf28 : ffffd000`2615b940 fffff985`71576436 ffffd000`2615b7d0 ffffd000`2615b934 : cng!EntropyPoolAdd+0x6f
ffffd000`2615b7a0 fffff802`fd50358f : ffffe000`399d84c0 ffffe000`399d84c0 00000000`00000000 ffffe000`399d84c0 : cng!EntropyProvideData+0x128
ffffd000`2615b890 fffff802`fd457735 : ffffd000`26102f00 00000000`00000000 ff000100`00010000 00000001`ffffffff : nt!KiEntropyDpcRoutine+0x37
ffffd000`2615b8c0 fffff802`fd456e10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x275
ffffd000`2615ba10 fffff802`fd558f9a : ffffd000`26100180 ffffd000`26100180 ffffd000`2610cbc0 ffffe000`3a7b6040 : nt!KiRetireDpcList+0xe0
ffffd000`2615bc60 00000000`00000000 : ffffd000`2615c000 ffffd000`26156000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+a07a
fffff802`fd56ee7a cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  55d5626b

IMAGE_VERSION:  10.0.10240.16463

BUCKET_ID_FUNC_OFFSET:  a07a

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

BUCKET_ID:  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}

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


If it is a driver issue, which driver is causing BSOD?
EducadAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ThommyCommented:
Your bug check Analysis states that the "DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above". This seems to be a typical driver fault.

Install the latest hardware drivers.
Especially take care of the chipset and video Drivers...
0
nobusCommented:
try disconnecting all external devices  -do you still have the BSOD?
0
EducadAuthor Commented:
Yes, I still have the issue. It happens when I put my laptop to sleep mode and it does not wake up then show me the BSOD. I think it is graphics driver, but I cannot upgrade graphics driver because when I try to install the latest version of its driver, my computer gets stuck during installation. My computer keeps blinking while the driver was installing and I have to manually restart it.
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

nobusCommented:
try booting into safe mode -  does it happen then?
it could be bad hardware - try running from a live cd, like Knoppix to test
http://www.knopper.net/knoppix-mirrors/index-en.html
0
EducadAuthor Commented:
In the safe mode, it was okay. Does it work with Windows as well?
0
nobusCommented:
>>  Does it work with Windows as well?   <<  what is "it" ? what do you mean with does it work with windows??

a live cd is a bootable cd that lets you run your pc like when booting from disk
knoppix usually has all drivers - so if that runs fine - your hardware should be ok, and you have to look for software solutions - or vice versa
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.