Critical process died

Critical process died

Critical process died
Critical process died
2 weeks ago
Tags: #Windows 10
Model: TL-WN823N  
Hardware Version: V3
Firmware Version:

So i have a problem that after installing drivers, my pc works like max a few minutes then shutdowns to blue screen and displays critical process died. I uninstalled rtwlanu.sys but this didnt work. There is my Kernel crash dump and mother board.


And there is 

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

 

CRITICAL_PROCESS_DIED (ef)

        A critical system process died

Arguments:

Arg1: ffff8e08a7677140, Process object or thread object

Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.

Arg3: 0000000000000000, The process object that initiated the termination.

Arg4: 0000000000000000

 

Debugging Details:

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

 

 

KEY_VALUES_STRING: 1

 

    Key  : Analysis.CPU.mSec

    Value: 2734

 

    Key  : Analysis.Elapsed.mSec

    Value: 7625

 

    Key  : Analysis.IO.Other.Mb

    Value: 14

 

    Key  : Analysis.IO.Read.Mb

    Value: 1

 

    Key  : Analysis.IO.Write.Mb

    Value: 20

 

    Key  : Analysis.Init.CPU.mSec

    Value: 1062

 

    Key  : Analysis.Init.Elapsed.mSec

    Value: 46835

 

    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 87

 

    Key  : Analysis.Version.DbgEng

    Value: 10.0.27725.1000

 

    Key  : Analysis.Version.Description

    Value: 10.2408.27.01 amd64fre

 

    Key  : Analysis.Version.Ext

    Value: 1.2408.27.1

 

    Key  : Bugcheck.Code.LegacyAPI

    Value: 0xef

 

    Key  : Bugcheck.Code.TargetModel

    Value: 0xef

 

    Key  : CriticalProcessDied.ExceptionCode

    Value: aae68080

 

    Key  : CriticalProcessDied.Process

    Value: csrss.exe

 

    Key  : Failure.Bucket

    Value: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_aae68080_nt!PspCatchCriticalBreak

 

    Key  : Failure.Hash

    Value: {9066fb1a-0aa6-558c-9d37-2904aa2537e5}

 

    Key  : WER.OS.Branch

    Value: vb_release

 

    Key  : WER.OS.Version

    Value: 10.0.19041.1

 

 

BUGCHECK_CODE:  ef

 

BUGCHECK_P1: ffff8e08a7677140

 

BUGCHECK_P2: 0

 

BUGCHECK_P3: 0

 

BUGCHECK_P4: 0

 

FILE_IN_CAB:  110824-66750-01.dmp

 

FAULTING_THREAD:  ffff8e08aae68080

 

PROCESS_NAME:  csrss.exe

 

CRITICAL_PROCESS:  csrss.exe

 

EXCEPTION_RECORD:  ffff8e08a7677880 -- (.exr 0xffff8e08a7677880)

ExceptionAddress: 0000000000000000

   ExceptionCode: 00000000

  ExceptionFlags: 00000000

NumberParameters: 0

 

ERROR_CODE: (NTSTATUS) 0xaae68080 - <Unable to get error code text>

 

BLACKBOXBSD: 1 (!blackboxbsd)

 

 

BLACKBOXNTFS: 1 (!blackboxntfs)

 

 

BLACKBOXPNP: 1 (!blackboxpnp)

 

 

BLACKBOXWINLOGON: 1

 

CUSTOMER_CRASH_COUNT:  1

 

EXCEPTION_STR:  0x0

 

STACK_TEXT: 

fffff401`2d581d88 fffff804`4330d762     : 00000000`000000ef ffff8e08`a7677140 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

fffff401`2d581d90 fffff804`4323b4d9     : 00000000`00000001 fffff804`42d3a721 00000000`00000002 fffff804`42d3a64b : nt!PspCatchCriticalBreak+0x10e

fffff401`2d581e30 fffff804`430eb4d0     : ffff8e08`00000000 00000000`00000000 ffff8e08`a7677140 ffff8e08`a7677578 : nt!PspTerminateAllThreads+0x141c39

fffff401`2d581ea0 fffff804`430eb2cc     : ffff8e08`a7677140 00000000`00000001 ffffffff`ffffffff fffff804`42e12ae6 : nt!PspTerminateProcess+0xe0

fffff401`2d581ee0 fffff804`42e12b0b     : ffff8e08`a7677140 ffff8e08`aae68080 fffff401`2d581fd0 fffff804`43134502 : nt!NtTerminateProcess+0x9c

fffff401`2d581f50 fffff804`42e03100     : fffff804`42e6e94f fffff401`2d582a58 fffff401`2d582a58 ffffffff`ffffffff : nt!KiSystemServiceExitPico+0x41f

fffff401`2d5820e8 fffff804`42e6e94f     : fffff401`2d582a58 fffff401`2d582a58 ffffffff`ffffffff 00007ffb`928ff000 : nt!KiServiceLinkage

fffff401`2d5820f0 fffff804`42e12cec     : ffff8e08`a7677880 fffff804`42c3baf6 00000000`00000800 fffff401`2d582b00 : nt!KiDispatchException+0x164f1f

fffff401`2d582920 fffff804`42e0e552     : ffff8e08`aae68000 000002e9`fb02f7b0 fffff401`2d582b80 000000ea`5e7be901 : nt!KiExceptionDispatch+0x12c

fffff401`2d582b00 00007ffb`952a2c62     : 00000000`00000000 000000ea`00000000 000000ea`5e781480 00007ffb`953128bf : nt!KiPageFault+0x452

000000ea`5e781460 00000000`00000000     : 000000ea`00000000 000000ea`5e781480 00007ffb`953128bf 00007ffb`928ff000 : 0x00007ffb`952a2c62

 

 

SYMBOL_NAME:  nt!PspCatchCriticalBreak+10e

 

MODULE_NAME: nt

 

IMAGE_NAME:  ntkrnlmp.exe

 

IMAGE_VERSION:  10.0.19041.5007

 

STACK_COMMAND:  .process /r /p 0xffff8e08a7677140; .thread 0xffff8e08aae68080 ; kb

 

BUCKET_ID_FUNC_OFFSET:  10e

 

FAILURE_BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_aae68080_nt!PspCatchCriticalBreak

 

OS_VERSION:  10.0.19041.1

 

BUILDLAB_STR:  vb_release

 

OSPLATFORM_TYPE:  x64

 

OSNAME:  Windows 10

 

FAILURE_ID_HASH:  {9066fb1a-0aa6-558c-9d37-2904aa2537e5}

 

Followup:     MachineOwner

---------

 

  0      
  0      
#1
Options
2 Reply
Re:Critical process died
2 weeks ago

  @dd311658 

Hi, Thank you very much for your feedback.

May I know how long you have had the TL-WN823N?

 

 

It is suggested to refer to this link to delete the incompatible driver file first:

How to troubleshoot if your computer goes to a blue screen when installing TP-Link wireless adapter

Then install the following driver here:

https://static.tp-link.com/upload/beta/2024/202405/20240527/RTWlanUSB_WindowsDriver_1030.44.0408.2024_Drv_3.00.0043_TS.L(153650).zip

Thanks a lot and best regards.

  0  
  0  
#2
Options
Re:Critical process died
2 weeks ago

  @David-TP 
I did as u said, and problem still occurs. I get connected to wifi and it works fine for like a minute or two then computers shutdown with bsod saying critical process died. This tp link 823n is brand new, i have never used it before. Whats funny i got tp link wn 727n and it works fine even though it is supposed to be working only to windows 8.

 

  0  
  0  
#3
Options