Jump to content

BlueScreen on ntoskrnl.exe+3f5e40

Pashlyander

Hello, My Pc is going through a tough times.

Almost once per 24 hours its crushing on Bluescreen, by checking with BlueScreenView app 

I see its crushing on : ntoskrnl.exe+3f5e40

Attaching the Dump file as well. Please need help, have no clue where its coming from 

041821-23812-01.dmp

Link to comment
Share on other sites

Link to post
Share on other sites

Give me a minute, I'll dig into this and tell you whats going on.

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to comment
Share on other sites

Link to post
Share on other sites

Ok, I'm going to post some relevant details from the crash dump, and then my thoughts on how to fix after

____

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: fffff80615efb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000
 

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80615efb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

 

PROCESS_NAME:  OUTLOOK.EXE

SYMBOL_NAME:  nt!KeAccumulateTicks+1c8c42

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.928

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c8c42

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
_____

 

So Outlook crashed, because of DPC_WATCHDOG_VIOLATION (133) with a specific cause of DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

 

Those are the things you need to look into to fix.

 

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation

I'd start by testing your RAM with MemTest86, and update all drivers.

 

 

NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. 

Link to comment
Share on other sites

Link to post
Share on other sites

Maybe Simple uninstall to outlook can help me with that as well ? 

Link to comment
Share on other sites

Link to post
Share on other sites

11 minutes ago, Pashlyander said:

Maybe Simple uninstall to outlook can help me with that as well ? 

Hi, 

 

What machine has this issue, is it a Lenovo?

 

one of my clients is having the very same issue, BSOD ntoskrnl.exe+3f5e40 as of Saturday.. 

 

we can only get in via Safe Mode.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×