Results 1 to 1 of 1
  1. #1
    New ROGer Array
    Join Date
    Dec 2021
    Reputation
    10
    Posts
    3

    ASUS ROG STRIX Z690-G Gaming wifi and many, many BSOD

    Hi all,
    I need help to figure out what's happening with my new build.
    I recently bought a custom PC with this configuration:

    ASUS ROG STRIX Z690-G Gaming wifi
    INTEL Core i5-12600K
    ADATA DDR5 5200 (2 x16GB)
    NVIDIA Geforce GTX 1660
    ENERMAX AQUAFUSION 240MM RGB
    Coolermaster MWE Gold V2 FM 650W
    Windows 11

    The PC boots with no problem , with XMP profile set to XMP 1; it may run with no issues for a couple of hourse and then, suddenly, start to crash even 3 times in a row in a 10 min. range. Yesterday it crashed immediately after it restarted from a previous crash, even if I was just staring at the screen...
    Here are the list of the last BSOD:

    On Sun 23/01/2022 18:49:23 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\012322-18593-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x415B00)
    Bugcheck code: 0x1A (0x61941, 0x7FF872A20000, 0x1D, 0xFFFFF88A64D20A20)
    Error: MEMORY_MANAGEMENT
    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 severe memory management error occurred.
    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. This problem might also be caused because of overheating (thermal issue).
    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 23/01/2022 18:44:02 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP

    This was probably caused by the following module: ntkrnlmp.exe (nt!ExTryAcquireSpinLockSharedAtDpcLevel+0x783AB)
    Bugcheck code: 0x1A (0x403, 0xFFFFC40000390CF8, 0x1000001D7AF0025, 0xFFFFC400D4581798)
    Error: MEMORY_MANAGEMENT
    Bug check description: This indicates that a severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
    This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
    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 23/01/2022 18:42:44 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\012322-19140-01.dmp
    This was probably caused by the following module: win32kbase.sys (0xFFFFDBBE810188C0)
    Bugcheck code: 0x50 (0xFFFFDBD444133000, 0x0, 0xFFFFDBBE810188C0, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\win32kbase.sys
    product: Sistema operativo Microsoft® Windows®
    company: Microsoft Corporation
    description: Driver kernel Win32k di base
    Bug check description: This indicates that invalid system memory has been referenced.
    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 23/01/2022 18:38:50 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8569)
    Bugcheck code: 0xA (0xFFFFB58018A71E88, 0x2, 0x0, 0xFFFFF8077F725B72)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    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 23/01/2022 18:10:19 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe (nt!ExTryAcquireSpinLockSharedAtDpcLevel+0x783AB)
    Bugcheck code: 0x1A (0x403, 0xFFFF953FFF2BFBF8, 0x6000007AF262005, 0xFFFF9503FE000760)
    Error: MEMORY_MANAGEMENT
    Bug check description: This indicates that a severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
    This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
    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 23/01/2022 16:23:55 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\012322-19265-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x415B00)
    Bugcheck code: 0x139 (0x3, 0xFFFFC2051264F500, 0xFFFFC2051264F458, 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.

    I've already tested the memory with memtest86x, 4 passes, four times: no errors.
    I've just chatted with MS support and they suggest an overheating issue: as far as I can tell the CPU temperature never exceeded 40 degrees, (I was just surfing the internet or installing new software, nothing CPU bound).
    So, what overheating issues there may be ?
    I'll of course return the PC to the shop where it was built, but they don't seem to have many ideas on where to look...
    Any help will be appreciated!
    Last edited by drosso; 01-24-2022 at 02:16 PM.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •