Tamam öyle göndereyim bekle.
*******************************************************************************
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints.
The driver/function that caused the problem. Always Note this address.
As well as the link date of the driver/image that contains this address.
Arguments:
Arg1: FffffffFC0000005, the exception code that was not handled.
Arg2: 0000000000000000, the address that the exception occurred at.
Arg3: 0000000000000008, parameter 0 of the exception.
Arg4: 0000000000000000, parameter 1 of the exception.
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: Exceptionrecord *
- *
*************************************************************************
*************************************************************************
* *
- *
- 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: Contextrecord *
- *
*************************************************************************
Key_values_strıng: 1
Key: Analysis. CPU. Msec.
Value: 1312.
Key: Analysis. Elapsed. Msec.
Value: 1312.
Key: Analysis. IO. Other. MB.
Value: 0
Key: Analysis. IO. Read. MB.
Value: 1
Key: Analysis. IO. Write. MB.
Value: 0
Key: Analysis. Init. CPU. Msec.
Value: 406.
Key: Analysis. Init. Elapsed. Msec.
Value: 100492.
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. Legacyapı.
Value: 0x1e.
Key: Bugcheck. Code. Targetmodel.
Value: 0x1e.
Key: Dump. Attributes. Asulong.
Value: 21008.
Key: Dump. Attributes. Diagdatawrittentoheader
Value: 1
Key: Dump. Attributes. Errorcode.
Value: 0
Key: Dump. Attributes. Kernelgeneratedtriagedump
Value: 1
Key: Dump. Attributes. Lastline.
Value: Dump completed successfully.
Key: Dump. Attributes. Progresspercentage.
Value: 0
*******************************************************************************
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints.
The driver/function that caused the problem. Always Note this address.
As well as the link date of the driver/image that contains this address.
Arguments:
Arg1: FffffffFC0000005, the exception code that was not handled.
Arg2: 0000000000000000, the address that the exception occurred at.
Arg3: 0000000000000008, parameter 0 of the exception.
Arg4: 0000000000000000, parameter 1 of the exception.
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: Exceptionrecord *
- *
*************************************************************************
*************************************************************************
* *
- *
- 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: Contextrecord *
- *
*************************************************************************
Key_values_strıng: 1
Key: Analysis. CPU. Msec.
Value: 1312.
Key: Analysis. Elapsed. Msec.
Value: 1312.
Key: Analysis. IO. Other. MB.
Value: 0
Key: Analysis. IO. Read. MB.
Value: 1
Key: Analysis. IO. Write. MB.
Value: 0
Key: Analysis. Init. CPU. Msec.
Value: 406.
Key: Analysis. Init. Elapsed. Msec.
Value: 100492.
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. Legacyapı.
Value: 0x1e.
Key: Bugcheck. Code. Targetmodel.
Value: 0x1e.
Key: Dump. Attributes. Asulong.
Value: 21008.
Key: Dump. Attributes. Diagdatawrittentoheader
Value: 1
Key: Dump. Attributes. Errorcode.
Value: 0
Key: Dump. Attributes. Kernelgeneratedtriagedump
Value: 1
Key: Dump. Attributes. Lastline.
Value: Dump completed successfully.
Key: Dump. Attributes. Progresspercentage.
Value: 0
Key: Failure. Bucket.
Value: Av_nt! Kidispatchexception.
Key: Failure. Hash.
Value: {00781D15-B897-AFAB-75CD-F83221CBf387}
Bugcheck_code: 1E.
Bugcheck_p1: FffffffFC0000005.
Bugcheck_p2: 0
Bugcheck_p3: 8
Bugcheck_p4: 0
Fıle_ın_cab: 022225-13671-01.dmp
Dump_fıle_attrıbutes: 0x21008.
Kernel generated triage dump.
Faultıng_thread: FFFF830D91702080.
Blackboxbsd: 1 (!blackboxbsd)
Blackboxntfs: 1 (!blackboxntfs)
Blackboxpnp: 1 (!blackboxpnp)
Blackboxwınlogon: 1
Customer_crash_count: 1
Process_name: System.
Stack_text:
Ffff9804'1D7de428 fffff807'84591086: 00000000'0000001E ffffffff'C0000005 00000000'00000000 00000000'00000008: NT! Kebugcheckex.
Ffff9804'1D7de430 fffff807'8488D045: 00000000'C0000005 00000000'00000000 07e1FE0D'57D7C4F8 ffff9804'1D7deff0: NT! Kidispatchexception+0xb16
Ffff9804'1D7deb40 fffff807'84888182: 84e6da97'e4C248ab ffff9804'1D7def80 ffffffff'ffffffff 442fbc68'6B11B0FF: NT! Kiexceptiondispatch+0x145
Ffff9804'1D7ded20 00000000'00000000: Fffff807'55e80998 00000000'00040286 fbffecb5'D156EAED bfe2F857'1553E54F: NT! Kipagefault+0x442
Symbol_name: NT! Kidispatchexception+B16
Module_name: NT.
Image_name: ntkrnlmp.exe
Image_versıon: 10.0.26100.3194
Stack_command: Process /r /p 0xffff830d8d743040;.thread 0xffff830d91702080; KB.
Bucket_ıd_func_offset: B16.
Faılure_bucket_ıd: Av_nt! Kidispatchexception.
Osplatform_type: X64.
Osname: Windows 10.
Faılure_ıd_hash: {00781D15-B897-AFAB-75CD-F83221CBf387}
Followup: Machineowner.
---------
Bu doğrusu sanırım.
@Ekrem Solak
