The BSOD are back with a vengeance and some extra too. Suddenly my on board audio is completely dead. Does not show up anymore in Device Manager. No matter what I do the on board audio is dead. Even the SPDIF output does not have the red light anymore, completely dead. I think the audio chip and/or the power to this chip is broken for some reason. Clean install of Windows 10, chip set drivers and all the drivers from the gigabyte website for this motherboard, still the on board audio does not show up anymore in Device Manager. And no, on board audio is NOT disabled in the BIOS. I don’t use the on board audio because I use the HD audio of my video card. But if the on board audio suddenly died maybe there is something wrong with this motherboard in general. Besides the BSOD that are back again with a vengeance and now this. I think I reached my limit with this motherboard. I’m going to ask to replace the motherboard because this becomes ridiculous. The issues with this motherboard are getting even worse. I re-installed Windows 10 so many times now that my productivity is almost reduced to 0. Other then working on my projects the only thing I do is troubleshooting issues I have with this motherboard.
Just a small overview of the BSOD I had since yesterday …
And strangly, most of the BSOD occur when watching Youtube videos on Autoplay. Mostly never with something else. Maybe you can tell what is wrong…!
On Sun 8-9-2019 01:08:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090819-10625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x139 (0x1D, 0xFFFFAF0B964E6220, 0xFFFFAF0B964E6178, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 8-9-2019 09:35:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090819-10796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x13A (0x12, 0xFFFFDF0D9A010100, 0xFFFFDF0DBB4B3000, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 8-9-2019 09:35:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidMmInterface+0x2D72B)
Bugcheck code: 0x13A (0x12, 0xFFFFDF0D9A010100, 0xFFFFDF0DBB4B3000, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 8-9-2019 07:32:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090819-10203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x139 (0x1D, 0xFFFFEA05D69A95D0, 0xFFFFEA05D69A9528, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 7-9-2019 23:46:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090719-10578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x13A (0x12, 0xFFFF928F6D010100, 0xFFFF928F8DFDC000, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 7-9-2019 21:59:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090719-10187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80475C449A9, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Hmm that is kinda weird.
Are you sure that your motherboard doesn’t make any unwanted contact with the case?
I would definitelly contact Gigabyte or Megekko about this.
Maybe they take it in for an RMA or send you a new board or refund.
I didn’t expect this much headaches with on paper a very decent highend board.
This kinda sucks…
Its gets even more strange, when I watch YouTube on Autoplay via Edge the system does not crash.
I installed Windows debug tools and what I found in analyzing these crash dumps was this in Windebugger using the !analyze -v command.
It looks like Chrome is the colperate and dxgmms2.
@MysteryAngel Even zonder gekheid, dit begint echt de spuigaten uit te lopen. Nooit eerder heb ik zoveel problemen gehad met een moederbord als met dit AMD bord. Deze problemen overstijgen werkelijk alles. Tijdens het werken zet ik altijd YouTube aan met muziek op de achtergrond. En als je dan steeds maar weer een BSOD krijgt dan wordt je daar horendol van. Het probleem oplossingsvermogen van mij begint aardig zijn grens te bereiken.
-
* -
Bugcheck Analysis * -
*
KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000012, Type of corruption detected
Arg2: ffffdf0d9a010100, Address of the heap that reported the corruption
Arg3: ffffdf0dbb4b3000, Address at which the corruption was detected
Arg4: 0000000000000000
Debugging Details:
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: X570 AORUS MASTER
SYSTEM_SKU: Default string
SYSTEM_VERSION: -CF
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F5
BIOS_DATE: 08/29/2019
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: X570 AORUS MASTER
BASEBOARD_VERSION: x.x
DUMP_TYPE: 2
BUGCHECK_P1: 12
BUGCHECK_P2: ffffdf0d9a010100
BUGCHECK_P3: ffffdf0dbb4b3000
BUGCHECK_P4: 0
CORRUPTING_POOL_ADDRESS: Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffdf0dbb4b3000
FAULTING_IP:
nt!ExAllocatePoolWithTag+5d
fffff800`7a16e06d 4885c0 test rax,rax
BUGCHECK_STR: 0x13a_12
CPU_COUNT: 10
CPU_MHZ: e10
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 71
CPU_STEPPING: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-NKLFOF2
ANALYSIS_SESSION_TIME: 09-08-2019 12:32:05.0809
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
LAST_CONTROL_TRANSFER: from fffff8007a11a9f8 to fffff80079fc10a0
STACK_TEXT:
ffffc40923971d48 fffff8007a11a9f8 : 000000000000013a 0000000000000012 ffffdf0d9a010100 ffffdf0dbb4b3000 : nt!KeBugCheckEx
ffffc40923971d50 fffff8007a11aa58 : 0000000000000012 0000000005330000 ffffdf0d9a010100 0000000100042003 : nt!RtlpHeapHandleError+0x40
ffffc40923971d90 fffff8007a11a681 : ffffdf0d9a010280 0000000000000000 00000000000000ff 0000000000000018 : nt!RtlpHpHeapHandleError+0x58
ffffc40923971dc0 fffff80079e42cfd : 0000000000000000 0000000000000000 0000000000000000 fffff8008f13587f : nt!RtlpLogHeapFailure+0x45
ffffc40923971df0 fffff80079e32ad8 : 0000000000000533 ffffb20c00005310 0000000000005310 ffffdf0d9a010000 : nt!RtlpHpVsContextAllocateInternal+0x38d
ffffc40923971e60 fffff8007a16e06d : ffffdf0d00000200 0000000000000000 0000000000000000 0000000000005308 : nt!ExAllocateHeapPool+0x418
ffffc40923971fa0 fffff80079e31501 : 0000000000000a5b 0000000000000000 000000009844b000 0000000000000000 : nt!ExAllocatePoolWithTag+0x5d
ffffc40923971ff0 fffff8008ba79f0b : 0000000000000000 ffffc40900000000 0000000000a5b000 ffffb20c2ca64d50 : nt!IoAllocateMdl+0x161
ffffc40923972040 fffff8008ba79e09 : ffffb20c2ca64d50 ffffb20c2ca64d50 ffffdf0d00000000 000002499844b000 : dxgmms2!VIDMM_MDL_RANGE::Lock+0x4b
ffffc409239720a0 fffff8008ba76b17 : ffffb20c2cb31da0 ffffb20c2ca26960 ffffdf0d00000000 ffffdf0daa370df0 : dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::LockRange+0x109
ffffc40923972120 fffff8008ba769ff : ffffb20c2bc06c10 0000000000a5b000 0000000000000000 0000000000000001 : dxgmms2!VIDMM_RECYCLE_RANGE::Lock+0x7b
ffffc40923972180 fffff8008ba7693b : ffffb20c2b6bc390 0000000000000000 0000000000000000 0000000000a5b000 : dxgmms2!VIDMM_RECYCLE_MULTIRANGE::Lock+0x83
ffffc409239721e0 fffff8008ba7acd9 : ffffb20c2b6bc390 0000000000000001 0000000000a5b000 ffffdf0dacd7c670 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::ProbeAndLockAllocation+0x7b
ffffc40923972260 fffff8008ba9257d : 0000000000000001 ffffdf0daa370df0 ffffc40900000000 0000000000000000 : dxgmms2!VIDMM_GLOBAL::ProbeAndLockAllocation+0x55
ffffc409239722b0 fffff8008ba91523 : ffffb20c2883ae08 0000000000000000 ffffb20c2898cb01 fffff8008ba8d1a4 : dxgmms2!VIDMM_SYSMEM_SEGMENT::LockAllocationRange+0x12d
ffffc409239723b0 fffff8008ba91461 : 0000000000000000 0000000001580000 ffffdf0da880a890 0000000000000000 : dxgmms2!VIDMM_MEMORY_SEGMENT::TransferMemoryFast+0x8f
ffffc40923972450 fffff8008ba6b7cd : 0000000000000000 ffffdf0db126b000 0000000000000000 ffffb20c2ca26960 : dxgmms2!VIDMM_MEMORY_SEGMENT::TransferMemory+0x6d
ffffc409239724a0 fffff8008ba6b3c2 : ffffb20c2ca26960 fffff80079e39bdd ffffdf0d00000000 ffffb20c00000001 : dxgmms2!VIDMM_MEMORY_SEGMENT::TransferToSegment+0x22d
ffffc40923972610 fffff8008ba7c99f : ffffdf0db5573710 ffffdf0db126b000 0000000000000000 ffffb20c2ca26960 : dxgmms2!VIDMM_MEMORY_SEGMENT::CommitResource+0x62
ffffc40923972660 fffff8008ba87eb2 : ffffdf0d00000000 0000000000000000 0000000000000000 0000000000000000 : dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x1ef
ffffc40923972770 fffff8008ba97da4 : 0000000000000001 0000000000989680 ffffb20c27864e70 0000000000000001 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x862
ffffc409239729e0 fffff8008ba96ee9 : ffffb20c1ba0f810 ffffcc01271d1401 ffffdf0daa2a5400 0000000000000100 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xea4
ffffc40923972be0 fffff80079f2a715 : ffffdf0daa2a54c0 fffff8008ba96ee0 ffffb20c1ba0f810 00000067b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffc40923972c10 fffff80079fc86ea : ffffcc01271c0180 ffffdf0daa2a54c0 fffff80079f2a6c0 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffffc40923972c60 0000000000000000 : ffffc40923973000 ffffc4092396d000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x2a
THREAD_SHA1_HASH_MOD_FUNC: 537cf56b2d22ec0abeeaaba6b16bc2b458bc66a6
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ee7c1c3b0c9eb9ba85b34fe4a605302947b5a2ba
THREAD_SHA1_HASH_MOD: 230cb4f81182f68431ed2137b9a6a22367b71d12
FOLLOWUP_IP:
dxgmms2!VIDMM_MDL_RANGE::Lock+4b
fffff800`8ba79f0b 488903 mov qword ptr [rbx],rax
FAULT_INSTR_CODE: 48038948
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: dxgmms2!VIDMM_MDL_RANGE::Lock+4b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 79e12d93
IMAGE_VERSION: 10.0.18362.329
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 4b
FAILURE_BUCKET_ID: 0x13a_12_dxgmms2!VIDMM_MDL_RANGE::Lock
BUCKET_ID: 0x13a_12_dxgmms2!VIDMM_MDL_RANGE::Lock
PRIMARY_PROBLEM_CLASS: 0x13a_12_dxgmms2!VIDMM_MDL_RANGE::Lock
TARGET_TIME: 2019-09-08T07:35:46.000Z
OSBUILD: 18362
OSSERVICEPACK: 329
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-04-22 17:00:30
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 52c1
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x13a_12_dxgmms2!vidmm_mdl_range::lock
FAILURE_ID_HASH: {ee5c125d-5ddd-a97b-6710-0085e47d5c6d}
Followup: MachineOwner
Well if you boot lets say a live image from Linux like Manjaro.
Might be worth trying that, to see if your audio drop out is hardware or software related.
You can boot manjaro live session from a usb stick without having to install the OS.
If you do get audio from your onboard audio solution, then it’s likely windows / driver related.
If not, then it’s likely hardware related.
Also double check for uefi updates, but i assume since you follow up on @wendell 's,
topic on the Aorus Master settings.
In terms of the bsod’s does this also happens when your ram runs at jedec 2133mhz?
I already tried this, I booted a Live Image from Linux mint via USB and the onboard audio was not present. I think the on board audio just died on me. And no, I checked if there is a false connection from the motherboard to my case. I took the motherboard out and used it as an open case to make troubleshooting more easy and still the same issues and BSOD.
Well maybe you could try Manjaro instead, because RYzen X570 newer platform,
likely needing kernel 5.x
I’m downloading Manjaro as we speak, update as soon as I booted the OS.
Yup eventuelly try to fireup the driver manager, and let it search for drivers.
Like Mint, Manjaro has a similar driver tool.
I can’t get Manjaro to boot, not with free drivers or non-free, it hangs on “Started TLP System Startup/Shutdown”, I think I need to change something in to the grub I believe. Linux Mint booted fine but Manjaro did not I’m afraid. I will check this further this evening. I have to walk my 2 German Shepherds, they don’t care if there master has issues with his PC they are in need of a long walk and me too… Update will follow this evening.
Hi,
I booted Manjaro ( I had to enable CSM in the BIOS to get it to boot???) and again the on board audio is not present. The on board audio is dead. I contacted Gigabyte and awaiting there response. I think the motherboard will be an RMA and/or will be replaced. Further, as long as I use Edge instead of Chrome to watch/listen to YouTube videos on Autoplay my system does not crash. As soon as I use Chrome I get several BSOD. Investigation using Windows debug tools came up with 3 different BSOD errors. “Pool Corruption” with no specific driver and/or program as root cause. “Chrome and dxgmms2” and a “atikmdag.sys” BSOD error. The last one is AMD Adrenaline driver related. The Pool corruption needs further investigation because this could be anything. Extensive RAM tests did not produce a RAM issue. The Chrome and dxgmm3.sys BSOD error is Windows 10 related I think. But first things first, it seems that my motherboard is not okay. The on board audio is dead and that is not good. The motherboard needs to be replaced. Update soon.
Yeah likely indeed, this kinda sucks.
I suppose they will likely replace it, or refund it.
I personally never really had the greatest luck with Abit / Gigabyte boards either.
But based on users reviews and spec’s, this board should be really decent.
But of course a bad example can always fall off the production line.
Kinda bad luck i guess…
Update.
Gigabyte advised replacing the motherboard because of the dead on board audio. I need to contact Megekko and they will handle the RMA. And another thing, they analyzed all the dump files again and they found out that the root cause of all the BSOD etc is the RAM apparently. The advised to replace the RAM as well. They even said not to use this type of RAM and ask for another version. Even the RAM I bought was on the QVL list but they tested this RAM and found out that it is not a perfect match with this motherboard. So in a nutshell, my motherboard and RAM will be replaced. For the motherboard Megekko needs to handle this and for the RAM my local computer shop.
@MisteryAngel Maybe a good idea to check what RAM is the best for this board. Choosing RAM from the QVL list seems to be no guarantee that it works. Proof is me buying RAM that is on the QVL list and Gigabyte telling me that the RAM I bought is not a good match after all. Maybe you or somebody else knows RAM that absolutely works with this Motherboard.
I asked Gigabyte and they send me the QVL list??? After they tell me that the RAM I bought via the QVL list is not a good match… I need minimum 32GB of RAM ( for my Autocad etc), preferably 2 sticks. I hope you guys can help me choose the right RAM for this board.
Many thanks in advance.
I may be able to reply before mistery angel in this case… For the X570 well much like the rest of the platform you would want Samsung B-Die memory… less so with this release but its always less problematic
Here is the QVL
http://download.gigabyte.us/FileList/Memory/mb_memory_x570-aorus-master_matisse_190812.pdf
but if I may suggest look for 3200 MHz or higher. Gskill trident Z and flare x have been the most consistent kits This will help you find it : https://benzhaomin.github.io/bdiefinder/
MisteryAngel and I have both done the research to find that 2 sticks is going to be better than 4 at least on this platform. We both have seen 3600 MHz kits work but this is when the memory controller is no longer 1:1 but it usually works better with an OC.
You should know you might wanna grab it quick. Samsung has officially ceased production on B die memory and replaced it with A die. If you cant find B die I would grab A die before M or E die memory…
Yeah or Micron E-die also seems to work okay with Ryzen.
But again it all depends on the modules again.
It’s true that Ryzen is really picky on memory module type.
It’s kinda weird that the memory on the QVL not really seem to work well.
I generally tempt to use G.Skill Trident Z modules.
But not all of those are B-die either.
inb4 major cringe from you but there RGB ones are haha…
Worst case he can just use flare x?
These are fine for people that arent like me and dont despise the company behind the memory. They are good memory makers though… They dont overclock well… but they are great OOB
Are those B-die?
Because those are a bit cheaper then Trident Z´s,
and i see them getting selected for a Ryzen setup more often.
G.skill also has those Sniper kits as well,
but not sure what those are, but likely not Samsung B-die.
There has been a list somewhere about memory kits.
yeah the flare x are B die… yeah reddit had a list. I posted a list above to find B die
Megekko accepted the RMA request and I can send in the motherboard. I don;t know yet what they are going to do, repair it or replace it. Gigabyte said the motherboard needs replacement. For the RAM I run into another issue. The local computer shop will not replace the RAM for other RAM. By law they only have to replace the RAM when it is returned within 30 days of buying, I’m a little over 30 days so they say they can’t do anything for me. Bad service and it will be the last time I buy something from this shop. I going to sell the RAM I have and buy new RAM as you mentioned from the B-Die selector list. Hoping that this RAM will work better. My motherboard will be send to Megekko tomorrow morning, I hope that I have it back very soon.