AteşliKazanova99
Hectopat
- Katılım
- 26 Ağustos 2021
- Mesajlar
- 497
- Çözümler
- 2
Daha fazla  
				
					
						
						
							
	
		
	
		
			
			
				
			
			
		
		
	- Cinsiyet
- Erkek
- RAM
- 8 GB 4x2
- SSD veya HDD modeli
- 480 GB SSD
- Ekran kartı
- 3050 Ti
- İşlemci
- Ryzen 5 5600H
Arkadaşlar Rainbow Six indirmiştim açarken evet hayır seçeneği geldi sonra mavi ekran verdi, önceden de vermişti.
3 tane minidump dosyası gördüm linki burada.
GoogleDriveLink
	
	
	
	
	
		
Yukarıda Valorant ile ilgili bir sıkıntı mı çıktığını söylüyor ?
2.Minidump
	
	
	
	
	
		
Burdada yukarıdaki söylenen şeyle aynısı fakat 2 tane farklı dosyadan çıktı.
	
	
	
	
	
		
	
		
			
		
		
	
				
			3 tane minidump dosyası gördüm linki burada.
GoogleDriveLink
		Kod:
	
	0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffff9684709457e3, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8034668ee34, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 3405
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 18625
    Key  : Analysis.IO.Other.Mb
    Value: 0
    Key  : Analysis.IO.Read.Mb
    Value: 0
    Key  : Analysis.IO.Write.Mb
    Value: 1
    Key  : Analysis.Init.CPU.mSec
    Value: 437
    Key  : Analysis.Init.Elapsed.mSec
    Value: 14495
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 97
    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa
    Key  : Bugcheck.Code.Register
    Value: 0xa
    Key  : WER.OS.Branch
    Value: vb_release
    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z
    Key  : WER.OS.Version
    Value: 10.0.19041.1
FILE_IN_CAB:  021823-11312-01.dmp
BUGCHECK_CODE:  a
BUGCHECK_P1: ffff9684709457e3
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff8034668ee34
READ_ADDRESS: fffff803470fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffff9684709457e3
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  VALORANT-Win64-Shipping.exe
TRAP_FRAME:  ffffd68e0a9274e0 -- (.trap 0xffffd68e0a9274e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80346400000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8034668ee34 rsp=ffffd68e0a927670 rbp=ffffd68e0a9277a0
 r8=0000000000000001  r9=0000000000000001 r10=ffffe78f00d1e628
r11=0000000000000076 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExFreeHeapPool+0x124:
fffff803`4668ee34 f646f304        test    byte ptr [rsi-0Dh],4 ds:ffffffff`fffffff3=??
Resetting default scope
STACK_TEXT:
ffffd68e`0a927398 fffff803`4680e129     : 00000000`0000000a ffff9684`709457e3 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd68e`0a9273a0 fffff803`46809ce3     : 00000000`000000e8 00000000`00000000 00000000`00000000 fffff803`61f70000 : nt!KiBugCheckDispatch+0x69
ffffd68e`0a9274e0 fffff803`4668ee34     : ffffe78f`08b0ecb0 ba404154`31f87c88 fffff803`61f70000 fffff803`61febc40 : nt!KiPageFault+0x463
ffffd68e`0a927670 fffff803`46db4019     : fffff803`61febc40 00000000`00000000 00000000`00000008 01000000`00100000 : nt!ExFreeHeapPool+0x124
ffffd68e`0a927750 fffff803`620e7785     : 00000000`00000000 ffffe78f`00d1e080 00000000`00000001 00000000`0000046c : nt!ExFreePool+0x9
ffffd68e`0a927780 00000000`00000000     : ffffe78f`00d1e080 00000000`00000001 00000000`0000046c 00000000`00000001 : vgk+0x177785
SYMBOL_NAME:  vgk+177785
MODULE_NAME: vgk
IMAGE_NAME:  vgk.sys
STACK_COMMAND:  .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET:  177785
FAILURE_BUCKET_ID:  AV_vgk!unknown_function
OS_VERSION:  10.0.19041.1
BUILDLAB_STR:  vb_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {56c5cf79-d160-8711-720f-03c630d4c72b}
Followup:     MachineOwner
---------Yukarıda Valorant ile ilgili bir sıkıntı mı çıktığını söylüyor ?
2.Minidump
		Kod:
	
	4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffff9d8ba21f12c3, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8023268ee34, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 4421
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 14058
    Key  : Analysis.IO.Other.Mb
    Value: 0
    Key  : Analysis.IO.Read.Mb
    Value: 0
    Key  : Analysis.IO.Write.Mb
    Value: 0
    Key  : Analysis.Init.CPU.mSec
    Value: 468
    Key  : Analysis.Init.Elapsed.mSec
    Value: 4081
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 98
    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa
    Key  : Bugcheck.Code.Register
    Value: 0xa
    Key  : WER.OS.Branch
    Value: vb_release
    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z
    Key  : WER.OS.Version
    Value: 10.0.19041.1
FILE_IN_CAB:  021723-13296-01.dmp
BUGCHECK_CODE:  a
BUGCHECK_P1: ffff9d8ba21f12c3
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff8023268ee34
READ_ADDRESS: fffff802330fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffff9d8ba21f12c3
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  VALORANT-Win64-Shipping.exe
TRAP_FRAME:  fffff9823ccd74e0 -- (.trap 0xfffff9823ccd74e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80232400000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023268ee34 rsp=fffff9823ccd7670 rbp=fffff9823ccd77a0
 r8=0000000000000001  r9=0000000000000001 r10=ffffb68ac80cf628
r11=0000000000000076 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ExFreeHeapPool+0x124:
fffff802`3268ee34 f646f304        test    byte ptr [rsi-0Dh],4 ds:ffffffff`fffffff3=??
Resetting default scope
STACK_TEXT:
fffff982`3ccd7398 fffff802`3280e129     : 00000000`0000000a ffff9d8b`a21f12c3 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff982`3ccd73a0 fffff802`32809ce3     : 00000000`000000e8 00000000`00000000 00000000`00000000 fffff802`4afa0000 : nt!KiBugCheckDispatch+0x69
fffff982`3ccd74e0 fffff802`3268ee34     : ffffb68a`bfd666b0 ba404154`31f87c88 fffff802`4afa0000 fffff802`4b01bc40 : nt!KiPageFault+0x463
fffff982`3ccd7670 fffff802`32db4019     : fffff802`4b01bc40 00000000`00000000 00000000`00000008 01000000`00100000 : nt!ExFreeHeapPool+0x124
fffff982`3ccd7750 fffff802`4b117785     : 00000000`00000000 ffffb68a`c80cf080 00000000`00000001 00000000`00001bdc : nt!ExFreePool+0x9
fffff982`3ccd7780 00000000`00000000     : ffffb68a`c80cf080 00000000`00000001 00000000`00001bdc 00000000`00000001 : vgk+0x177785
SYMBOL_NAME:  vgk+177785
MODULE_NAME: vgk
IMAGE_NAME:  vgk.sys
STACK_COMMAND:  .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET:  177785
FAILURE_BUCKET_ID:  AV_vgk!unknown_function
OS_VERSION:  10.0.19041.1
BUILDLAB_STR:  vb_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {56c5cf79-d160-8711-720f-03c630d4c72b}
Followup:     MachineOwner
---------Burdada yukarıdaki söylenen şeyle aynısı fakat 2 tane farklı dosyadan çıktı.
		Kod:
	
	0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80467995f7b, The address that the exception occurred at
Arg3: ffff9b0bbd8c7348, Exception Record Address
Arg4: ffff9b0bbd8c6b80, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
    Key  : AV.Dereference
    Value: NullClassPtr
    Key  : AV.Fault
    Value: Read
    Key  : Analysis.CPU.mSec
    Value: 3983
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 49431
    Key  : Analysis.IO.Other.Mb
    Value: 4
    Key  : Analysis.IO.Read.Mb
    Value: 0
    Key  : Analysis.IO.Write.Mb
    Value: 8
    Key  : Analysis.Init.CPU.mSec
    Value: 374
    Key  : Analysis.Init.Elapsed.mSec
    Value: 4775
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 97
    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1000007e
    Key  : Bugcheck.Code.Register
    Value: 0x7e
    Key  : WER.OS.Branch
    Value: vb_release
    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z
    Key  : WER.OS.Version
    Value: 10.0.19041.1
FILE_IN_CAB:  101122-11453-01.dmp
BUGCHECK_CODE:  7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80467995f7b
BUGCHECK_P3: ffff9b0bbd8c7348
BUGCHECK_P4: ffff9b0bbd8c6b80
EXCEPTION_RECORD:  ffff9b0bbd8c7348 -- (.exr 0xffff9b0bbd8c7348)
ExceptionAddress: fffff80467995f7b (dxgmms2!VIDMM_PAGE_TABLE_BASE::GetSegmentOffsetInPages+0x000000000000000b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000050
Attempt to read from address 0000000000000050
CONTEXT:  ffff9b0bbd8c6b80 -- (.cxr 0xffff9b0bbd8c6b80)
rax=0000000000000000 rbx=0000000000000002 rcx=ffffb9874efcb880
rdx=ffffb987520ee2b0 rsi=ffffb9874efcb880 rdi=ffffb9874d5023b8
rip=fffff80467995f7b rsp=ffff9b0bbd8c7588 rbp=0000000000000200
 r8=ffff9b0bbd8c74a0  r9=0000000000000000 r10=0000000000000000
r11=ffff9b0bbd8c7400 r12=00000000000000f3 r13=ffffb98747a068b0
r14=ffffb9874765b2d0 r15=0000000000000798
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
dxgmms2!VIDMM_PAGE_TABLE_BASE::GetSegmentOffsetInPages+0xb:
fffff804`67995f7b f7405000100000  test    dword ptr [rax+50h],1000h ds:002b:00000000`00000050=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
READ_ADDRESS: fffff8046c4fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000050
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.
EXCEPTION_CODE_STR:  c0000005
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000050
EXCEPTION_STR:  0xc0000005
STACK_TEXT:
ffff9b0b`bd8c7588 fffff804`67a2e8d0     : ffff9b0b`bd8c7401 ffffb987`4efcb880 00000000`00000000 00000000`00000005 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetSegmentOffsetInPages+0xb
ffff9b0b`bd8c7590 fffff804`67a2e948     : 00000000`00000000 00000000`00000000 00000000`00000800 ffffb987`4765b2d0 : dxgmms2!VIDMM_PAGE_DIRECTORY::MapPageTablesToVaSpace+0x130
ffff9b0b`bd8c7630 fffff804`67a1df67     : 00000000`00000000 00000000`00000000 ffff9b0b`bd8c77d0 ffff800c`e428b000 : dxgmms2!VIDMM_PAGE_DIRECTORY::MapPageTablesToVaSpace+0x1a8
ffff9b0b`bd8c76d0 fffff804`67a0efec     : 00000000`00000000 00000000`00000000 00000000`00000076 ffffb987`a94a7e20 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x18807
ffff9b0b`bd8c7840 fffff804`679fc8f2     : ffffb987`47a07250 ffff9b0b`00000001 00000000`00000001 ffffb987`4632bbc0 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x2ab20
ffff9b0b`bd8c79c0 fffff804`67a06499     : ffffb987`4632bb50 ffff800c`dec59301 00000000`00000000 00000000`0641f900 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462
ffff9b0b`bd8c7ba0 fffff804`6ba71d25     : ffff800c`dec59380 fffff804`67a06490 ffffb987`4632bb50 000fe067`bcbbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff9b0b`bd8c7bd0 fffff804`6bc00628     : ffffcd00`2c980180 ffff800c`dec59380 fffff804`6ba71cd0 dc02e36d`3bae8907 : nt!PspSystemThreadStartup+0x55
ffff9b0b`bd8c7c20 00000000`00000000     : ffff9b0b`bd8c8000 ffff9b0b`bd8c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME:  dxgmms2!VIDMM_PAGE_TABLE_BASE::GetSegmentOffsetInPages+b
MODULE_NAME: dxgmms2
IMAGE_NAME:  dxgmms2.sys
IMAGE_VERSION:  10.0.19041.1202
STACK_COMMAND:  .cxr 0xffff9b0bbd8c6b80 ; kb
BUCKET_ID_FUNC_OFFSET:  b
FAILURE_BUCKET_ID:  AV_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetSegmentOffsetInPages
OS_VERSION:  10.0.19041.1
BUILDLAB_STR:  vb_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {d4538a3c-36c4-b05e-0370-e84dc529541d}
Followup:     MachineOwner
---------
			
				Son düzenleyen: Moderatör: 
			
		
	
								
								
									
	
		
			
		
		
	
	
	
	
		
			
		
		
	
								
							
							 
 
		 
 
		 
					
				 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		