Andersoon
Kilopat
- Katılım
- 6 Ekim 2016
- Mesajlar
- 8
Daha fazla
- Cinsiyet
- Erkek
Sanırım kayıt defteriyle bunu ortaya çıkardım daha önce CS2 FPS için birkaç ayar değiştirimiştim başka bir sorun ile karşılaştım bu sefer sorunu gidermek için uğraştığımda ki başardım ama FIFA24 girerken ya da Battlefield bu hatayı alıyorum biraz araştırdım sanırım dump dosyası vs istiyorsunuz onu da yaptım ve analiz sonuçları bunlar. Bilgisayarı yeni açıyorum hiçbir uygulama açmadan oyuna giriyorum ve reset atıyor PC şimdiden teşekkür ederim.
KERNEL_APC_PENDING_DURING_EXIT (20)
The key data item is the thread's APC disable count.
If this is non-Zero, then this is the Source of the problem.
The APC disable count is decremented each time a driver calls.
Keentercriticalregion, fsrtlenterfilesystem, or acquires a mutex. The APC.
Disable count is incremented each time a driver calls keleavecriticalregion,
Fsrtlexitfilesystem, or kereleasemutex. Since these calls should always be in.
Pairs, this Value should be Zero when a thread exits. A negative Value.
İndicates that a driver has disabled APC calls without re-enabling them. A
Positive Value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the.
Machine -- especially unusual or non-standard drivers. Third party file.
System redirectors are especially suspicious since they do not generally.
Receive the heavy duty testing that NTFS, fat, RDR, ETC receive.
This current IRQL should also be 0. ıf it is not, that a driver's.
Cancellation routine can cause this bugcheck by returning at an elevated.
IRQL. Always attempt to Note what you were doing/closing at the.
Time of the crash, and Note all of the installed drivers at the time of.
The crash. This symptom is usually a severe bug in a Third party.
Driver.
Arguments:
Arg1: 0000000000000000, the address of the APC found pending during exit.
Arg2: 000000000000FFFF, the thread's APC disable count.
Arg3: 0000000000000000, the current IRQL.
Arg4: 0000000000000001.
Debugging details:
------------------
Key_values_strıng: 1
Key: Analysis. CPU. Msec.
Value: 1921.
Key: Analysis. Elapsed. Msec.
Value: 1910.
Key: Analysis. IO. Other. MB.
Value: 22.
Key: Analysis. IO. Read. MB.
Value: 12.
Key: Analysis. IO. Write. MB.
Value: 36.
Key: Analysis. Init. CPU. Msec.
Value: 4468.
Key: Analysis. Init. Elapsed. Msec.
Value: 48966.
Key: Analysis. Memory.commitpeak. MB.
Value: 91.
Key: Bugcheck. Code. Legacyapı.
Value: 0x20.
Key: Dump. Attributes. Asulong.
Value: 8
Key: Dump. Attributes. Kernelgeneratedtriagedump
Value: 1
Key: Failure. Bucket.
Value: 0x20_nullapc_kapc_negatıve_nt! Pspexitthread.
Key: Failure. Hash.
Value: {fcbbc787-B7CC-0CA4-C274-C788B86A9951}
Bugcheck_code: 20.
Bugcheck_p1: 0
Bugcheck_p2: Ffff.
Bugcheck_p3: 0
Bugcheck_p4: 1
Fıle_ın_cab: 022624-10859-01.dmp
Dump_fıle_attrıbutes: 0x8.
Kernel generated triage dump.
Blackboxbsd: 1 (!blackboxbsd)
Blackboxntfs: 1 (!blackboxntfs)
Blackboxwınlogon: 1
Customer_crash_count: 1
Process_name: System.
Stack_text:
Fffffd03'7ddaf9F8 fffff802'688146F0: 00000000'00000020 00000000'00000000 00000000'0000FFFF 00000000'00000000: NT! Kebugcheckex.
Fffffd03'7ddafa00 fffff802'686AC193: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! Pspexitthread+0x187888
Fffffd03'7ddafb00 fffff802'686AA5e4: Ffffae0b'8C66D080 00000000'00000080 fffff802'68770C40 ffffae0b'73CC7080: NT! Pspterminatethreadbypointer+0x53
Fffffd03'7ddafb40 fffff802'68770C88: 00000000'00000000 00000000'00000000 00000000'00002000 00008E10'006070F6: NT! Psterminatesystemthread+0x24
Fffffd03'7ddafb70 fffff802'683078E5: Ffffae0b'8C66D080 fffff802'68770C40 ffff860D'887bc7F0 00000000'00000000: NT! Iopthreadstart+0x48
Fffffd03'7ddafbd0 fffff802'68406378: Ffffc200'63F40180 ffffae0b'8C66D080 fffff802'68307890 fffff737'46892840: NT! Pspsystemthreadstartup+0x55
Fffffd03'7ddafc20 00000000'00000000: Fffffd03'7ddb0000 fffffd03'7dda9000 00000000'00000000 00000000'00000000: NT! Kistartsystemthread+0x28
Symbol_name: NT! Pspexitthread+187888
Module_name: NT.
Image_name: ntkrnlmp.exe
Image_versıon: 10.0.19041. 4046.
Stack_command: Cxr. Ecxr; KB.
Bucket_ıd_func_offset: 187888.
Faılure_bucket_ıd: 0x20_nullapc_kapc_negatıve_nt! Pspexitthread.
Osplatform_type: X64.
Osname: Windows 10.
Faılure_ıd_hash: {fcbbc787-B7CC-0CA4-C274-C788B86A9951}
Followup: Machineowner.
KERNEL_APC_PENDING_DURING_EXIT (20)
The key data item is the thread's APC disable count.
If this is non-Zero, then this is the Source of the problem.
The APC disable count is decremented each time a driver calls.
Keentercriticalregion, fsrtlenterfilesystem, or acquires a mutex. The APC.
Disable count is incremented each time a driver calls keleavecriticalregion,
Fsrtlexitfilesystem, or kereleasemutex. Since these calls should always be in.
Pairs, this Value should be Zero when a thread exits. A negative Value.
İndicates that a driver has disabled APC calls without re-enabling them. A
Positive Value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the.
Machine -- especially unusual or non-standard drivers. Third party file.
System redirectors are especially suspicious since they do not generally.
Receive the heavy duty testing that NTFS, fat, RDR, ETC receive.
This current IRQL should also be 0. ıf it is not, that a driver's.
Cancellation routine can cause this bugcheck by returning at an elevated.
IRQL. Always attempt to Note what you were doing/closing at the.
Time of the crash, and Note all of the installed drivers at the time of.
The crash. This symptom is usually a severe bug in a Third party.
Driver.
Arguments:
Arg1: 0000000000000000, the address of the APC found pending during exit.
Arg2: 000000000000FFFF, the thread's APC disable count.
Arg3: 0000000000000000, the current IRQL.
Arg4: 0000000000000001.
Debugging details:
------------------
Key_values_strıng: 1
Key: Analysis. CPU. Msec.
Value: 1921.
Key: Analysis. Elapsed. Msec.
Value: 1910.
Key: Analysis. IO. Other. MB.
Value: 22.
Key: Analysis. IO. Read. MB.
Value: 12.
Key: Analysis. IO. Write. MB.
Value: 36.
Key: Analysis. Init. CPU. Msec.
Value: 4468.
Key: Analysis. Init. Elapsed. Msec.
Value: 48966.
Key: Analysis. Memory.commitpeak. MB.
Value: 91.
Key: Bugcheck. Code. Legacyapı.
Value: 0x20.
Key: Dump. Attributes. Asulong.
Value: 8
Key: Dump. Attributes. Kernelgeneratedtriagedump
Value: 1
Key: Failure. Bucket.
Value: 0x20_nullapc_kapc_negatıve_nt! Pspexitthread.
Key: Failure. Hash.
Value: {fcbbc787-B7CC-0CA4-C274-C788B86A9951}
Bugcheck_code: 20.
Bugcheck_p1: 0
Bugcheck_p2: Ffff.
Bugcheck_p3: 0
Bugcheck_p4: 1
Fıle_ın_cab: 022624-10859-01.dmp
Dump_fıle_attrıbutes: 0x8.
Kernel generated triage dump.
Blackboxbsd: 1 (!blackboxbsd)
Blackboxntfs: 1 (!blackboxntfs)
Blackboxwınlogon: 1
Customer_crash_count: 1
Process_name: System.
Stack_text:
Fffffd03'7ddaf9F8 fffff802'688146F0: 00000000'00000020 00000000'00000000 00000000'0000FFFF 00000000'00000000: NT! Kebugcheckex.
Fffffd03'7ddafa00 fffff802'686AC193: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! Pspexitthread+0x187888
Fffffd03'7ddafb00 fffff802'686AA5e4: Ffffae0b'8C66D080 00000000'00000080 fffff802'68770C40 ffffae0b'73CC7080: NT! Pspterminatethreadbypointer+0x53
Fffffd03'7ddafb40 fffff802'68770C88: 00000000'00000000 00000000'00000000 00000000'00002000 00008E10'006070F6: NT! Psterminatesystemthread+0x24
Fffffd03'7ddafb70 fffff802'683078E5: Ffffae0b'8C66D080 fffff802'68770C40 ffff860D'887bc7F0 00000000'00000000: NT! Iopthreadstart+0x48
Fffffd03'7ddafbd0 fffff802'68406378: Ffffc200'63F40180 ffffae0b'8C66D080 fffff802'68307890 fffff737'46892840: NT! Pspsystemthreadstartup+0x55
Fffffd03'7ddafc20 00000000'00000000: Fffffd03'7ddb0000 fffffd03'7dda9000 00000000'00000000 00000000'00000000: NT! Kistartsystemthread+0x28
Symbol_name: NT! Pspexitthread+187888
Module_name: NT.
Image_name: ntkrnlmp.exe
Image_versıon: 10.0.19041. 4046.
Stack_command: Cxr. Ecxr; KB.
Bucket_ıd_func_offset: 187888.
Faılure_bucket_ıd: 0x20_nullapc_kapc_negatıve_nt! Pspexitthread.
Osplatform_type: X64.
Osname: Windows 10.
Faılure_ıd_hash: {fcbbc787-B7CC-0CA4-C274-C788B86A9951}
Followup: Machineowner.
Yanlış anlattım kusura bakma. Ama aynen Battlefield çözüldü, sadece FIFA24 sorun yaratıyor.
