i5 480M mavi ekran hatası

İşletim sistemi
Windows 10

doublexir

Hectopat
Katılım
6 Ekim 2020
Mesajlar
37
Çözümler
2
Daha fazla  
Cinsiyet
Erkek
Bilgisayarım olur olmadık yerlerde mavi ekran veriyor. Mavi ekranların sebeplerini çok fazla araştırdım, internetin altını üstüne getirdim. RAM'lerimi tek tek kontrol ettim, chkdsk yaptım. Bütün yolları ve kontrolleri sağladım fakat donanımda herhangi bir soruna rastlamadım. Ben öyle çok çok fazla anlamam ancak şahsi düşüncem C: Diskinde sorun olmasıdır. Veya işlemcim ve anakartımda bir sorun var. Sistem özelliklerini aşağıda belirtip, minidump klasörünü paylaşacağım.

Sistem özellikleri:
  • Windows 10/64Bit
  • Intel Core i5 480M.
  • AMD Radeon R7 200 series (R7 240)
  • Anakart o. E. M
  • RAM 2X 4 GB DDR3.
  • Toshiba HDD 1TB (harici) D:

Minidump.rar dosyasını indir - download minidump dosyası ++

VirusTotal VirusTotal sonuçları ++
 
Son düzenleyen: Moderatör:
1. hata: AMDRSSrcExt.exe
Rehberi uyguladıktan sonra AMD'nin sitesinden en güncel ekran kartı driver'ının kurulumunu yap.

2. hata: dxgmms2.sys
Bu hata da ekran kartına bağlı olarak çıkıyor.

3. hata: LeagueOfLegends.exe
Tahminimce yine ekran kartından ötürü. Değilse, güncellemesi varsa yapmanı, düzelmezse silip yeniden temiz kurulum yapmanı tavsiye ederim.

4. hata: Discord.exe
Discord'un güncellemesi varsa yapmanı, düzelmezse silip yeniden temiz kurulum yapmanı tavsiye ederim.

Ek olarak:
Sonuçları paylaşır mısın?
 
Son düzenleyen: Moderatör:
1. hata: AMDRSSrcExt.exe
Rehberi uyguladıktan sonra AMD'nin sitesinden en güncel ekran kartı driver'ının kurulumunu yap.

2. hata: dxgmms2.sys
Bu hata da ekran kartına bağlı olarak çıkıyor.

3. hata: LeagueOfLegends.exe
Tahminimce yine ekran kartından ötürü. Değilse, güncellemesi varsa yapmanı, düzelmezse silip yeniden temiz kurulum yapmanı tavsiye ederim.

4. hata: Discord.exe
Discord'un güncellemesi varsa yapmanı, düzelmezse silip yeniden temiz kurulum yapmanı tavsiye ederim.

Ek olarak:
Sonuçları paylaşır mısın?

Bütün RAM testlerini yaptım sfc/scannow ve Memtest86 olarak. Muhtemelen bahsettiğiniz gibi ekran kartım bozuk ve bundan dolayı hata alıyorum. Benim için üzücü bir durum oldu bu. Çok sağ olun, bir gelişme olursa haberdar edeceğim.
 
Son düzenleyen: Moderatör:
AMD driver konusunda ezelden beri problemli zaten. O yüzden driver hatası olma ihtimali çok yüksek. Güncel driver yüklediğin halde sorun çözülmediyse eğer, driver versiyonlarını bi tık düşürerek dene.
 
Son düzenleme:
AMD driver konusunda ezelden beri problemli zaten. O yüzden driver hatası olma ihtimali çok yüksek. Güncel driver yüklediğin halde sorun çözülmediyse eğer, driver versiyonlarını bi tık düşürerek dene.
Dediklerini yapmama rağmen sorunum çözülmedi. Tekrar mavi ekran hatası ile karşılaştım, dediğiniz gibi driver sürümünü düşürmeyi deneyeceğim son kez. Aşağıda aldığım mavi ekran hatasına dair yeni Minidump dosyamı paylaştım.

 
Dostum yemin ederim, ben hayatımda görmediğim hataları sayende an itibariyle görmüş oldum. Teşekkür ederim ilkim sensin :D
Yine AMD kaynaklı sorun var, onun dışında Intel sürücüsünden sorun olmuş, sistem uygulaması çökmüş. Benim görebildiğim bunlar, ekstra bişey varsa veya beni aşan kısım varsa bilemeyeceğim. Sana önerebileceğim tek şey tertemiz bir format atman olur.
 
Dostum yemin ederim, ben hayatımda görmediğim hataları sayende an itibariyle görmüş oldum. Teşekkür ederim ilkim sensin :D
Yine AMD kaynaklı sorun var, onun dışında Intel sürücüsünden sorun olmuş, sistem uygulaması çökmüş. Benim görebildiğim bunlar, ekstra bişey varsa veya beni aşan kısım varsa bilemeyeceğim. Sana önerebileceğim tek şey tertemiz bir format atman olur.
İnanır mısın, 2 gün önce bilgisayarı tamirciye götürdüm. Tanıdığım güvendiğim birisi ve bilgisayar tamircide 2 gün boyunca açık kaldı. Oyunlar oynamasını söyledim, discord açıkken oyuna girmesini söyledim. Bugün bilgisayarı almaya gittiğimde sadece ethernet girişinde sorun olduğu söylendi. Ve tamircide bilgisayarımı kontrol ederken oradaki abi google chromedan 5-6 sekme, opera GX den 5-6 sekme yine ve discord açık ve lol oyunu da açık bir şekilde bilgisayar 2 gün boyunca bilgisayar açık kalmış bir kere mavi ekran verdiğini görmedim dedi. Şuan bilgisayar elimde, daha oyuna girmedim ama mavi ekran hatası da almadım. Düşünüyorum ki bu bilgisayarın bi dışarı çıkası mı varmış ki anlamadım yani :D
 
İnanır mısın, 2 gün önce bilgisayarı tamirciye götürdüm. Tanıdığım güvendiğim birisi ve bilgisayar tamircide 2 gün boyunca açık kaldı. Oyunlar oynamasını söyledim, discord açıkken oyuna girmesini söyledim. Bugün bilgisayarı almaya gittiğimde sadece ethernet girişinde sorun olduğu söylendi. Ve tamircide bilgisayarımı kontrol ederken oradaki abi google chromedan 5-6 sekme, opera GX den 5-6 sekme yine ve discord açık ve lol oyunu da açık bir şekilde bilgisayar 2 gün boyunca bilgisayar açık kalmış bir kere mavi ekran verdiğini görmedim dedi. Şuan bilgisayar elimde, daha oyuna girmedim ama mavi ekran hatası da almadım. Düşünüyorum ki bu bilgisayarın bi dışarı çıkası mı varmış ki anlamadım yani :D
Teknoloji işi şans işi... Diyebileceğim bu.
 
Daha önce de konu açmıştım, fakat herhangi bir çözüme ulaşamadım. Yalvarırım anlayan bilen yardım edebilecek birisi bana bu konuda yardım etsin. Bilgisayarı tanıdığım bir tamirciye götürdüm, fakat bu bilgisayar mavi ekran falan vermiyor kardeşim diyerek elime tutuşturdu tekrar kasayı.

Daha öncesinde bilgisayarımda RAM testi yaptım sorun çıkmadı. HDD testi yaptım bad sector veya herhangi bir sorun göremedim. Ekran kartını yük altına soktum yine mavi ekran vermedi. İşlemcimin macununu güzelce temizleyip yeni bir macun sürdüm. Bilgisayar normal halde çalışırken asla mavi ekran vermiyor, veriyorsa bile çok çok nadir. Ancak yaklaşık 3-4 ay öncesine kadar böyle bir sorunum asla olmamıştı. Sadece oyun oynadığımda deli gibi mavi ekran veriyor artık. Oynadığım oyun da LoL sadece, 3-4 ay öncesinde CS:GO oynuyordum. CS oynarken mavi ekran hataları almaya başladım ve ardı arkası kesilmedi o günden sonra. Ne yaptıysam düzeltemedim. Belki donanımsal bir sorun var tamam ama o sorunu bile gözle göremiyorum. Windows'u olduğu gibi hard Disk'e taşımak istedim, fakat nasıl yapacağımı bilmediğimden o işe bulaşmadım. Belki Windows'un dahili diskinde sorun vardır diye düşündüm.

Yeni minidump dosyası indirme linki;


Rica ediyorum yardımcı olun bana.
 
Son düzenleyen: Moderatör:
Dökümlere baktım. Sorunlar çoğunlukla anakart kaynaklı gibi. Hatalardan biri özellikle işlemciyi besleme konusuyla ilgili, WHEA hatası.

Yine de kasayı açıp anakart modelini öğrenirseniz BIOS güncellemesi yapmayı deneyebiliriz. CPU-Z gibi programlarla bakıp bana Intel H55 demeyin...


Kod:
Machine ID Information [From Smbios 2.6, DMIVersion 0, Size=2609]
BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 080015
BiosReleaseDate = 12/05/2014
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
SystemFamily = To Be Filled By O.E.M.
SystemVersion = To Be Filled By O.E.M.
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = INTEL
BaseBoardProduct = INTEL H55
BaseBoardVersion = INTEL

Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80773c0e3ea, Address of the instruction which caused the BugCheck
Arg3: fffffa8101bf0190, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4468

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5078

    Key  : Analysis.Init.CPU.mSec
    Value: 734

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2286

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 71

    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:  111521-25078-01.dmp

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80773c0e3ea

BUGCHECK_P3: fffffa8101bf0190

BUGCHECK_P4: 0

CONTEXT:  fffffa8101bf0190 -- (.cxr 0xfffffa8101bf0190)
rax=00000000000000ad rbx=0000000000000000 rcx=ffffa88d60be1430
rdx=0000000000000013 rsi=0000000000000000 rdi=ffffa88d60be1460
rip=fffff80773c0e3ea rsp=fffffa8101bf0b98 rbp=fffffa8101bf0cc0
 r8=ffffa88d4fc9f640  r9=0000000000000000 r10=ffffa88d60be1460
r11=ffffb888e6aed500 r12=0000000003f32000 r13=000000000f46fda0
r14=0000000000000001 r15=0000000077814660
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ObpGetWaitObject+0x2a:
fffff807`73c0e3ea 498b4120        mov     rax,qword ptr [r9+20h] ds:002b:00000000`00000020=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  League of Legends.exe

STACK_TEXT:
fffffa81`01bf0b98 fffff807`73ff7b1c     : ffffa88d`5d8b3080 fffff807`73d3973c ffffa88d`00000000 ffffa88d`00000000 : nt!ObpGetWaitObject+0x2a
fffffa81`01bf0ba0 fffff807`73ff7bfa     : ffffa88d`5d8b3080 00000000`00000000 00000000`00000000 fffffa81`01bf0cc0 : nt!ObWaitForSingleObject+0x5c
fffffa81`01bf0c00 fffff807`73e08cb8     : 00000000`0f24e100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x6a
fffffa81`01bf0c40 00000000`77811cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0f46f028 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77811cfc


SYMBOL_NAME:  nt!ObpGetWaitObject+2a

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr 0xfffffa8101bf0190 ; kb

BUCKET_ID_FUNC_OFFSET:  2a

FAILURE_BUCKET_ID:  0x3B_c0000005_nt!ObpGetWaitObject

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4d90da16-f984-61bc-2086-6116b4680deb}

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8000ca4ff3e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8000ca4ff3e, address which referenced memory

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nwifi.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8937

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 15901

    Key  : Analysis.Init.CPU.mSec
    Value: 687

    Key  : Analysis.Init.Elapsed.mSec
    Value: 4009

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 92

    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:  111921-27734-01.dmp

BUGCHECK_CODE:  d1

BUGCHECK_P1: fffff8000ca4ff3e

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: fffff8000ca4ff3e

READ_ADDRESS: fffff800076fb390: 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
 fffff8000ca4ff3e

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffee0ca74c9bd0 -- (.trap 0xffffee0ca74c9bd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=fffff8000ca4ff3e
rdx=fffff8000c84ff00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000ca4ff3e rsp=ffffee0ca74c9d60 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000050 r10=0000fffff8000c85
r11=ffffc27f95200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`0ca4ff3e ??              ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
fffff800`0ca4ff3e ??              ???

STACK_TEXT:
ffffee0c`a74c9a88 fffff800`06e09269     : 00000000`0000000a fffff800`0ca4ff3e 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffee0c`a74c9a90 fffff800`06e05569     : ffffa88d`91761200 00000000`00000000 ffffa88d`917427c0 0000054e`00000000 : nt!KiBugCheckDispatch+0x69
ffffee0c`a74c9bd0 fffff800`0ca4ff3e     : ffffa88d`a07ca502 ffffee0c`10000001 ffffa88d`99add460 fffff800`099a9147 : nt!KiPageFault+0x469
ffffee0c`a74c9d60 ffffa88d`a07ca502     : ffffee0c`10000001 ffffa88d`99add460 fffff800`099a9147 ffffa88d`99add460 : 0xfffff800`0ca4ff3e
ffffee0c`a74c9d68 ffffee0c`10000001     : ffffa88d`99add460 fffff800`099a9147 ffffa88d`99add460 fffff800`06c0827e : 0xffffa88d`a07ca502
ffffee0c`a74c9d70 ffffa88d`99add460     : fffff800`099a9147 ffffa88d`99add460 fffff800`06c0827e 00000000`00000000 : 0xffffee0c`10000001
ffffee0c`a74c9d78 fffff800`099a9147     : ffffa88d`99add460 fffff800`06c0827e 00000000`00000000 ffffa88d`99add460 : 0xffffa88d`99add460
ffffee0c`a74c9d80 fffff800`09d61116     : ffffee0c`a74c9e39 ffffa88d`9a187d30 00000000`00000000 ffffee0c`a74ca100 : NETIO!WfpNblInfoDestroyIfUnused+0x117
ffffee0c`a74c9dc0 fffff800`09ae99ee     : ffffa88d`a1d1e5f0 00000000`00000000 00000000`00000000 d9e651af`00000000 : fwpkclnt!FwppNetBufferListEventNotify+0xd6
ffffee0c`a74c9ea0 fffff800`099946be     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfppTaggedContextFree+0x1e
ffffee0c`a74c9ed0 fffff800`09815440     : ffffa88d`a1d1e5f0 ffffa88d`a1d1e5f0 ffffee0c`a74c9fd0 ffffa88d`961ea771 : NETIO!WfpNblInfoCleanup+0x4e
ffffee0c`a74c9f10 fffff800`0c3aa70b     : 00000000`00000000 ffffa88d`a1d1e5f0 fffff800`0c43fa00 ffffa88d`8fce2020 : ndis!NdisFreeNetBufferList+0x130
ffffee0c`a74c9f50 00000000`00000000     : ffffa88d`a1d1e5f0 fffff800`0c43fa00 ffffa88d`8fce2020 ffffa88d`9ac462f0 : nwifi+0xa70b


SYMBOL_NAME:  NETIO!WfpNblInfoDestroyIfUnused+117

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

IMAGE_VERSION:  10.0.19041.1165

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  117

FAILURE_BUCKET_ID:  AV_CODE_AV_BAD_IP_NETIO!WfpNblInfoDestroyIfUnused

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {55597693-f362-cb38-59c5-33ae2f852c97}

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb30669b8f028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6484

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 13857

    Key  : Analysis.Init.CPU.mSec
    Value: 827

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3237

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 85

    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:  111921-26546-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb30669b8f028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff800`78a988e8 fffff800`760b453a     : 00000000`00000124 00000000`00000000 ffffb306`69b8f028 00000000`be000000 : nt!KeBugCheckEx
fffff800`78a988f0 fffff800`71cf15b0     : 00000000`00000000 ffffb306`69b8f028 ffffb306`695482b0 ffffb306`69b8f028 : nt!HalBugCheckSystem+0xca
fffff800`78a98930 fffff800`761b61de     : 00000000`00000000 fffff800`78a989d9 ffffb306`69b8f028 ffffb306`695482b0 : PSHED!PshedBugCheckSystem+0x10
fffff800`78a98960 fffff800`760b5e61     : ffffb306`698580b0 ffffb306`698580b0 ffffb306`69548300 ffffb306`695482b0 : nt!WheaReportHwError+0x46e
fffff800`78a98a40 fffff800`760b61d3     : 00000000`00000000 ffffb306`69548300 ffffb306`695482b0 00000000`00000000 : nt!HalpMcaReportError+0xb1
fffff800`78a98bb0 fffff800`760b60b0     : ffffb306`67caeb40 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
fffff800`78a98c00 fffff800`760b6301     : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
fffff800`78a98c40 fffff800`760b556b     : 00000000`00000000 00000000`00000000 fffff800`78a98ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
fffff800`78a98c70 fffff800`760b7db5     : ffffb306`67caeb40 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
fffff800`78a98ca0 fffff800`7610d4c9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
fffff800`78a98cd0 fffff800`760063fa     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
fffff800`78a98d00 fffff800`760060b7     : ffffb306`00000000 fffff800`76005fec 00000000`0014079c 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff800`78a98e40 fffff800`78014a77     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffff800`78a74b30 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0xe7


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3fcb9ba4-4151-054d-a420-874ecf0a1f94}

Followup:     MachineOwner
---------
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: 0000000000000014, 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: fffff8047f21521f, address which referenced memory

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6734

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 13737

    Key  : Analysis.Init.CPU.mSec
    Value: 765

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3187

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 82

    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:  111521-25015-02.dmp

BUGCHECK_CODE:  a

BUGCHECK_P1: 14

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8047f21521f

READ_ADDRESS: fffff8047fafb390: 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
 0000000000000014

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  System

TRAP_FRAME:  fffff680836d8a90 -- (.trap 0xfffff680836d8a90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffff0001 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffffffffffffe rsi=0000000000000000 rdi=0000000000000000
rip=fffff8047f21521f rsp=fffff680836d8c20 rbp=0000000000000010
 r8=0000000000000010  r9=0000000000000000 r10=ffff8100a6080180
r11=fffff680836d8b50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KeReleaseInStackQueuedSpinLock+0x155aff:
fffff804`7f21521f 458b4114        mov     r8d,dword ptr [r9+14h] ds:00000000`00000014=????????
Resetting default scope

STACK_TEXT: 
fffff680`836d8948 fffff804`7f209269     : 00000000`0000000a 00000000`00000014 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff680`836d8950 fffff804`7f205569     : fffff680`00000003 00000000`00000008 00000000`83018b00 ffffdd8f`bded0760 : nt!KiBugCheckDispatch+0x69
fffff680`836d8a90 fffff804`7f21521f     : 00000000`00000000 ffffdd8f`cda8b4e0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469
fffff680`836d8c20 fffff804`8cab2903     : ffffdd8f`c6ea8000 00000000`00000000 ffffdd8f`c6ea86d0 fffff804`8caaff00 : nt!KeReleaseInStackQueuedSpinLock+0x155aff
fffff680`836d8c50 fffff804`8cb2d443     : ffffdd8f`c6ea8000 ffffdd8f`bded0760 ffffdd8f`c6ea8000 00000000`00000000 : dxgmms2+0x12903
fffff680`836d8cc0 fffff804`8cb2d38a     : ffffdd8f`c6ea8400 fffff804`8cb2d2c0 ffffdd8f`c6ea8000 ffff8100`a6129100 : dxgmms2!VidMmInterface+0x4db63
fffff680`836d8d10 fffff804`7f155855     : ffffdd8f`c6673400 fffff804`00000001 ffffdd8f`c6ea8000 00038404`ad1b3ffe : dxgmms2!VidMmInterface+0x4daaa
fffff680`836d8d50 fffff804`7f1fe8f8     : ffff8100`a6129180 ffffdd8f`c6673400 fffff804`7f155800 00206b6e`ffffff88 : nt!PspSystemThreadStartup+0x55
fffff680`836d8da0 00000000`00000000     : fffff680`836d9000 fffff680`836d3000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2+12903

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1387

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  12903

FAILURE_BUCKET_ID:  AV_dxgmms2!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ef88c03d-a690-ebe1-e688-902a4fce2373}

Followup:     MachineOwner
---------
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8023a8ed0cc, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8023a8ed0cc, address which referenced memory

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for amdkmdag.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5952

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 77517

    Key  : Analysis.Init.CPU.mSec
    Value: 733

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3326

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 80

    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:  111921-25671-01.dmp

BUGCHECK_CODE:  d1

BUGCHECK_P1: fffff8023a8ed0cc

BUGCHECK_P2: 9

BUGCHECK_P3: 8

BUGCHECK_P4: fffff8023a8ed0cc

READ_ADDRESS: fffff801640fb390: 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
 fffff8023a8ed0cc

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff9281ea0769e0 -- (.trap 0xffff9281ea0769e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000009 rbx=0000000000000000 rcx=fffff8023a8ed0cc
rdx=ffff9281ea076bc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023a8ed0cc rsp=ffff9281ea076b70 rbp=ffff9281ea076c20
 r8=fffff8016dc20400  r9=0000000000000003 r10=0000000000000013
r11=ffff9281ea076c00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff802`3a8ed0cc ??              ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
fffff802`3a8ed0cc ??              ???

STACK_TEXT: 
ffff9281`ea076898 fffff801`63809269     : 00000000`0000000a fffff802`3a8ed0cc 00000000`00000009 00000000`00000008 : nt!KeBugCheckEx
ffff9281`ea0768a0 fffff801`63805569     : 00000000`00000000 00000000`00000000 00000000`0000000a 00000000`00000100 : nt!KiBugCheckDispatch+0x69
ffff9281`ea0769e0 fffff802`3a8ed0cc     : ffffdd8e`aced3028 fffff801`6ddb6bda ffff9281`ea076c40 00000000`00000000 : nt!KiPageFault+0x469
ffff9281`ea076b70 ffffdd8e`aced3028     : fffff801`6ddb6bda ffff9281`ea076c40 00000000`00000000 ffffdd8e`aced3028 : 0xfffff802`3a8ed0cc
ffff9281`ea076b78 fffff801`6ddb6bda     : ffff9281`ea076c40 00000000`00000000 ffffdd8e`aced3028 fffff801`6ddb6bda : 0xffffdd8e`aced3028
ffff9281`ea076b80 ffff9281`ea076c40     : 00000000`00000000 ffffdd8e`aced3028 fffff801`6ddb6bda ffff9281`ea076c60 : amdkmdag+0x196bda
ffff9281`ea076b88 00000000`00000000     : ffffdd8e`aced3028 fffff801`6ddb6bda ffff9281`ea076c60 00000000`00000008 : 0xffff9281`ea076c40


SYMBOL_NAME:  amdkmdag+196bda

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  196bda

FAILURE_BUCKET_ID:  AV_CODE_AV_BAD_IP_amdkmdag!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f98f2785-f380-48c7-ba03-ac3be250ce83}

Followup:     MachineOwner
---------
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: fffff8007801f1d2, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6281

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 15383

    Key  : Analysis.Init.CPU.mSec
    Value: 686

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2099

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 80

    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:  111621-25765-01.dmp

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8007801f1d2

BUGCHECK_P3: 0

BUGCHECK_P4: 0

READ_ADDRESS: fffff800788fb390: 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
 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT: 
ffffbd82`d50285f8 fffff800`780f5b1e     : 00000000`0000001e ffffffff`c0000005 fffff800`7801f1d2 00000000`00000000 : nt!KeBugCheckEx
ffffbd82`d5028600 fffff800`78000162     : fffff800`780f5afc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffffbd82`d5028640 fffff800`77ee6dd7     : ffffbd82`d5028bb0 00000000`00000000 ffffbd82`d5029da0 fffff800`77ffadc4 : nt!RtlpExecuteHandlerForException+0x12
ffffbd82`d5028670 fffff800`77ee59d6     : ffffbd82`d5029588 ffffbd82`d50292c0 ffffbd82`d5029588 00000000`00000000 : nt!RtlDispatchException+0x297
ffffbd82`d5028d90 fffff800`780093ac     : 00000000`00001000 ffffbd82`d5029630 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
ffffbd82`d5029450 fffff800`78005543     : 00000000`00000000 ffff8888`c90e0d28 ffff8888`c90e0d28 00000000`00000002 : nt!KiExceptionDispatch+0x12c
ffffbd82`d5029630 fffff800`7801f1d2     : ffffbf81`b228b140 fffff800`7eb0dcaa 00000000`00000000 ffff8888`c9505db8 : nt!KiPageFault+0x443
ffffbd82`d50297c0 fffff800`77e18a9c     : ffff8888`c5b57328 00000000`00000000 000000db`a8026303 00000000`00000000 : nt!PpmExitCoordinatedIdle+0x206432
ffffbd82`d5029830 fffff800`77e17104     : 80808080`80808080 80808080`80808080 00000000`80808000 80808080`80808080 : nt!PpmIdleExecuteTransition+0x181c
ffffbd82`d5029c30 fffff800`77ffadc4     : 00000000`00000000 ffffbf81`b228b140 ffff8888`d5bd4080 00000000`000009c0 : nt!PoIdle+0x374
ffffbd82`d5029da0 00000000`00000000     : ffffbd82`d502a000 ffffbd82`d5024000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  nt!PpmExitCoordinatedIdle+206432

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  206432

FAILURE_BUCKET_ID:  0x1E_c0000005_R_nt!PpmExitCoordinatedIdle

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b852c8e8-d5c1-63f7-bd06-1fbc286d09af}

Followup:     MachineOwner
---------
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000e, type of pool violation the caller is guilty of.
Arg2: 0000000000000000
Arg3: 0000000000000200
Arg4: 0000000041777445

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5233

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7581

    Key  : Analysis.Init.CPU.mSec
    Value: 686

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2244

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 73

    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:  111921-27109-01.dmp

BUGCHECK_CODE:  c2

BUGCHECK_P1: e

BUGCHECK_P2: 0

BUGCHECK_P3: 200

BUGCHECK_P4: 41777445

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT: 
ffffa483`a5ee6888 fffff803`7e43dbb9     : 00000000`000000c2 00000000`0000000e 00000000`00000000 00000000`00000200 : nt!KeBugCheckEx
ffffa483`a5ee6890 fffff803`7e9b11c4     : ffff908f`00000002 ffff908f`11ce8118 ffffa483`41777445 fffff803`7e224aae : nt!ExAllocateHeapPool+0x1b14e9
ffffa483`a5ee69d0 fffff803`7e6b3c1f     : 73d50000`001a8000 00000000`73d50000 ffff908f`125e9080 00000001`00000000 : nt!ExAllocatePoolWithTag+0x64
ffffa483`a5ee6a20 fffff803`7e601075     : ffff908f`11ce8118 ffff908f`11ce80c0 ffff908f`125e9080 00000000`73d50000 : nt!PerfLogImageUnload+0xe3
ffffa483`a5ee6ae0 fffff803`7e600d99     : ffff908f`11bd4080 fffff803`7e408cb8 00000000`00000000 00000000`00000000 : nt!MiUnmapViewOfSection+0x2a5
ffffa483`a5ee6bc0 fffff803`7e6fcc3c     : ffff908f`11bd4080 00007ffc`64016e01 00000000`77be5b5c ffff908f`125e9080 : nt!NtUnmapViewOfSectionEx+0x99
ffffa483`a5ee6c10 fffff803`7e408cb8     : ffff908f`11bd4000 00000000`00000000 ffffa483`a5ee6cc0 ffff908f`12f82d50 : nt!NtUnmapViewOfSection+0xc
ffffa483`a5ee6c40 00007ffc`65ced2b4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`11dfe328 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`65ced2b4


SYMBOL_NAME:  nt!PerfLogImageUnload+e3

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  e3

FAILURE_BUCKET_ID:  0xc2_e_nt!PerfLogImageUnload

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {abbd650c-e096-18eb-fbc2-0680e98ea81e}

Followup:     MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: ffff86365de35fa7, Address of the instruction which caused the BugCheck
Arg3: ffffe08b857a3120, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6906

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 12837

    Key  : Analysis.Init.CPU.mSec
    Value: 843

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3561

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 85

    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:  111921-26500-01.dmp

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: ffff86365de35fa7

BUGCHECK_P3: ffffe08b857a3120

BUGCHECK_P4: 0

CONTEXT:  ffffe08b857a3120 -- (.cxr 0xffffe08b857a3120)
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff8016115c710 rsi=0000000000000004 rdi=ffffe08b857a3cd0
rip=ffff86365de35fa7 rsp=ffffe08b857a3b20 rbp=ffffe08b857a3c20
 r8=ffffe08b857a3b30  r9=0000000000000001 r10=fffff8016118c6c0
r11=0000000000000100 r12=ffffe08b857a3ce0 r13=0000000000000000
r14=ffff9f08fc6ed080 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32kbase!SURFMEM::bCreateDIB+0xb97:
ffff8636`5de35fa7 488b00          mov     rax,qword ptr [rax] ds:002b:00000000`00000001=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  explorer.exe

STACK_TEXT: 
ffffe08b`857a3b20 ffff8636`5de4c705     : ffff9f08`fc6ed001 ffffe08b`00000000 00000000`00000000 00000000`00000000 : win32kbase!SURFMEM::bCreateDIB+0xb97
ffffe08b`857a3c70 ffff8636`5f3b065a     : ffffe08b`857a3d90 00000000`00000001 00000000`00000000 00000000`00000000 : win32kbase!GreCreateBitmap+0xf5
ffffe08b`857a3d10 ffff8636`5e3d9c43     : ffff860b`00000010 00000000`00000020 00000000`00000001 00000000`00000001 : win32kfull!NtGdiCreateBitmap+0x6a
ffffe08b`857a3d90 fffff801`5ce08cb8     : ffff9f08`fc6ed080 00000000`0085000f 00000000`0085000f 00000000`00000020 : win32k!NtGdiCreateBitmap+0x1f
ffffe08b`857a3dd0 00007ffb`0d5c1da4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`02a7aee8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`0d5c1da4


SYMBOL_NAME:  win32kbase!SURFMEM::bCreateDIB+b97

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr 0xffffe08b857a3120 ; kb

BUCKET_ID_FUNC_OFFSET:  b97

FAILURE_BUCKET_ID:  0x3B_c0000005_win32kbase!SURFMEM::bCreateDIB

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2702b53f-4970-0c5e-a044-7ade7e22d7b7}

Followup:     MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80310e08b6d, Address of the instruction which caused the BugCheck
Arg3: ffffaa088d6fb240, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4608

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 17796

    Key  : Analysis.Init.CPU.mSec
    Value: 734

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2122

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 73

    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:  111521-25015-01.dmp

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80310e08b6d

BUGCHECK_P3: ffffaa088d6fb240

BUGCHECK_P4: 0

CONTEXT:  ffffaa088d6fb240 -- (.cxr 0xffffaa088d6fb240)
rax=0000000000000034 rbx=ffff800c6fd7b080 rcx=0000000000000000
rdx=000000afc8f0b520 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80310e08b6d rsp=ffffaa088d6fbc40 rbp=ffffaa088d6fbcc0
 r8=000000afc9011000  r9=00007ff942315c90 r10=0000000100000000
r11=fffff803116fc940 r12=000001d4147ff4e0 r13=0000000000000003
r14=0000000000000017 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!KiSystemServiceRepeat+0x39:
fffff803`10e08b6d 4d631c82        movsxd  r11,dword ptr [r10+rax*4] ds:002b:00000001`000000d0=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  AMDRSSrcExt.exe

STACK_TEXT: 
ffffaa08`8d6fbc40 00007ff9`48d8d3f4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceRepeat+0x39
000000af`c8f0b4f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`48d8d3f4


SYMBOL_NAME:  nt!KiSystemServiceRepeat+39

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr 0xffffaa088d6fb240 ; kb

BUCKET_ID_FUNC_OFFSET:  39

FAILURE_BUCKET_ID:  0x3B_c0000005_nt!KiSystemServiceRepeat

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {54ff1359-4199-299c-a403-3f3177961400}

Followup:     MachineOwner
---------
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff891c97ff0068, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: ffffbc16c08d3446, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 7686

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14919

    Key  : Analysis.Init.CPU.mSec
    Value: 827

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3636

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 85

    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:  111721-29390-01.dmp

BUGCHECK_CODE:  50

BUGCHECK_P1: ffff891c97ff0068

BUGCHECK_P2: 0

BUGCHECK_P3: ffffbc16c08d3446

BUGCHECK_P4: 2

READ_ADDRESS: fffff8035fefb390: 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
 ffff891c97ff0068

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

TRAP_FRAME:  fffffd80d37bf990 -- (.trap 0xfffffd80d37bf990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000b0fffff8035f rbx=0000000000000000 rcx=ffffbc8e69786080
rdx=ffff830067617000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffbc16c08d3446 rsp=fffffd80d37bfb20 rbp=fffffd80d37bfbd0
 r8=ffff94843e36a001  r9=0000000000000000 r10=b0fffff8035fefc7
r11=ffff72fc98000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
ffffbc16`c08d3446 490fa303        bt      qword ptr [r11],rax ds:ffff72fc`98000000=????????????????
Resetting default scope

STACK_TEXT: 
fffffd80`d37bf6e8 fffff803`5f64a56f     : 00000000`00000050 ffff891c`97ff0068 00000000`00000000 fffffd80`d37bf990 : nt!KeBugCheckEx
fffffd80`d37bf6f0 fffff803`5f49f390     : 00000000`00000000 00000000`00000000 fffffd80`d37bfa10 00000000`00000000 : nt!MiSystemFault+0x18d1bf
fffffd80`d37bf7f0 fffff803`5f60545e     : 00000000`00000000 ffffbc3b`02eb4330 00000000`0000000a 00000000`00000019 : nt!MmAccessFault+0x400
fffffd80`d37bf990 ffffbc16`c08d3446     : 00000000`01100100 fffffd80`d37bfb60 fffff803`5f542080 ffffbc16`c068956e : nt!KiPageFault+0x35e
fffffd80`d37bfb20 00000000`01100100     : fffffd80`d37bfb60 fffff803`5f542080 ffffbc16`c068956e ffffbc8e`69786080 : 0xffffbc16`c08d3446
fffffd80`d37bfb28 fffffd80`d37bfb60     : fffff803`5f542080 ffffbc16`c068956e ffffbc8e`69786080 00000000`001f0003 : 0x1100100
fffffd80`d37bfb30 fffff803`5f54207f     : ffffbc16`c068956e ffffbc8e`69786080 00000000`001f0003 ffff151d`8c547ef9 : 0xfffffd80`d37bfb60
fffffd80`d37bfb38 ffffbc16`c068956e     : ffffbc8e`69786080 00000000`001f0003 ffff151d`8c547ef9 00000000`00000000 : nt!HalpDmaGetAdapterVersion+0x2f
fffffd80`d37bfb40 ffffbc16`c099e6ac     : ffffbc8e`69786080 ffffbc8e`69786080 00000000`00001dc0 00000000`10a6c1f8 : win32kbase!PtiFromThreadId+0x9e
fffffd80`d37bfb80 ffffbc16`c14a7261     : ffffbc8e`69786080 00000000`00000000 00000000`00000020 00000000`10a6c1f8 : win32kfull!NtUserPostThreadMessage+0x5c
fffffd80`d37bfc00 fffff803`5f608cb8     : ffffbc8e`00000000 ffffbc8e`00000001 00000000`10a6c2a0 fffffd80`d37bfcc0 : win32k!NtUserPostThreadMessage+0x15
fffffd80`d37bfc40 00007ff8`2c1c0b14     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`195fe448 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`2c1c0b14


SYMBOL_NAME:  win32kbase!PtiFromThreadId+9e

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.1348

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  9e

FAILURE_BUCKET_ID:  AV_R_(null)_win32kbase!PtiFromThreadId

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {00bc0bc9-5fe2-66a0-9a60-a892ba61e042}

Followup:     MachineOwner
---------
 

Geri
Yukarı