Frequent crashes(No clue what it is)


  1. TimmyTop
    Posts : 3
    Windows 11
       New #1

    Frequent crashes(No clue what it is)


    I've ran driver verifier, memtest, sfc scannow, disk check. All my drivers are updated, as far as I know, but this is a newly refurbished PC build with some parts remaining from the old build. One note, the bsods happen more frequently as I oc my RAM to higher rates.
    Edit: have reformatted drives and reinstalled windows many times.
    DESKTOP-8GPQVQA-(2022-01-26_12-30-57).zip
    Last edited by TimmyTop; 26 Jan 2022 at 15:46. Reason: Added logs, more detail
      My Computer
    Quote Quote

  3. tomdsr
    Posts : 890
    10 Pro/11 Pro Dual Boot
       New #2

    TimmyTop said:
    I've ran driver verifier, memtest, sfc scannow, disk check. All my drivers are updated, as far as I know, but this is a newly refurbished PC build with some parts remaining from the old build. One note, the bsods happen more frequently as I oc my RAM to higher rates.
    Edit: have reformatted drives and reinstalled windows many times.
    DESKTOP-8GPQVQA-(2022-01-26_12-30-57).zip

    Please remove overclocks and put memory back to stock.

    4 of your 5 dump files consist of flavors of this (wont spam all 5)
    7: 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: 00000000000088b8, memory referenced
    Arg2: 00000000000000ff, 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: fffff802710dbd5f, address which referenced memory

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

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

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2780

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 9363

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

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

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

    Key : WER.OS.Branch
    Value: co_release

    Key : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key : WER.OS.Version
    Value: 10.0.22000.1


    BUGCHECK_CODE: a

    BUGCHECK_P1: 88b8

    BUGCHECK_P2: ff

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff802710dbd5f

    READ_ADDRESS: fffff80271b05450: 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
    00000000000088b8

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    TRAP_FRAME: fffff30e94e7d390 -- (.trap 0xfffff30e94e7d390)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802710dbd5f rsp=fffff30e94e7d520 rbp=fffff30e94e7d569
    r8=0000000000000000 r9=fffff80271b08780 r10=000000000000000f
    r11=fffff30e94e7d5c8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di pl zr na po nc
    nt!KeResumeClockTimerFromIdle+0xbf:
    fffff802`710dbd5f 4c8b80b8880000 mov r8,qword ptr [rax+88B8h] ds:00000000`000088b8=????????????????
    Resetting default scope

    STACK_TEXT:
    fffff30e`94e7d248 fffff802`712285a9 : 00000000`0000000a 00000000`000088b8 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
    fffff30e`94e7d250 fffff802`71224700 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff30e`94e7d390 fffff802`710dbd5f : 00000123`36ac90b1 ffff9a80`dae5d510 00000106`94576934 fffff802`856038d7 : nt!KiPageFault+0x440
    fffff30e`94e7d520 fffff802`710da37f : 00000000`00000052 00000000`00000003 ffff9a80`dae55180 00000000`00000001 : nt!KeResumeClockTimerFromIdle+0xbf
    fffff30e`94e7d5d0 fffff802`710d99e6 : fffff802`71211980 fffff802`7101356a 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0x80f
    fffff30e`94e7da70 fffff802`712198c4 : 00000000`00000000 ffff9a80`dae61340 ffffd00d`7c5db080 00000000`000012fc : nt!PoIdle+0x3a6
    fffff30e`94e7dc40 00000000`00000000 : fffff30e`94e7e000 fffff30e`94e78000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


    SYMBOL_NAME: nt!KeResumeClockTimerFromIdle+bf

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    IMAGE_VERSION: 10.0.22000.376

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: bf

    FAILURE_BUCKET_ID: AV_nt!KeResumeClockTimerFromIdle

    OS_VERSION: 10.0.22000.1

    BUILDLAB_STR: co_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {1bbba434-0e97-4e3e-a4c6-3ba138262364}

    Followup: MachineOwner
    Once back to stock, please test the memory.

    Legacy bios - MemTest86+ - Test RAM
    UEFI bios - Run Windows Memory Diagnostics Tool in Windows 10
    Is the memory new or part of the old build? When you ran memtest was it at stock speeds or overclocked?

    If you have reformatted and reinstalled windows many times, it is either a really odd driver issue or hardware.

    What parts are new and what ones were re-used? Were the new parts to upgrade or for other issues? What power supply specificaly?

    You are one driver behind on the video card. Yours is 497.29 from Dec 14 2021 and the current is 511.23 from Jan 14 2022. Link is Download NVIDIA, GeForce, Quadro, and Tesla Drivers

    Please let me know the answers to my questions and try the newer video driver also :)
      My Computers
    Quote Quote

  4. TimmyTop
    Posts : 3
    Windows 11
    Thread Starter
       New #3

    tomdsr said:
    Please remove overclocks and put memory back to stock.

    4 of your 5 dump files consist of flavors of this (wont spam all 5)


    Once back to stock, please test the memory.

    Legacy bios - MemTest86+ - Test RAM
    UEFI bios - Run Windows Memory Diagnostics Tool in Windows 10
    Is the memory new or part of the old build? When you ran memtest was it at stock speeds or overclocked?

    If you have reformatted and reinstalled windows many times, it is either a really odd driver issue or hardware.

    What parts are new and what ones were re-used? Were the new parts to upgrade or for other issues? What power supply specificaly?

    You are one driver behind on the video card. Yours is 497.29 from Dec 14 2021 and the current is 511.23 from Jan 14 2022. Link is Download NVIDIA, GeForce, Quadro, and Tesla Drivers

    Please let me know the answers to my questions and try the newer video driver also :)
    I updated the GPU drivers then set memory and cpu back to stock by setting BIOS to back to preferred defaults; the clock timings on the memory become different than advertised when I do this(not sure if this has anything to do with BSOD). Then I ran memory diagnostics, which showed "the Windows Memory Diagnostic tested the computer's memory and detected no errors".
    The memory is new, along with the motherboard, gpu, cpu, and power supply(which is a Corsair rm750x gold). The only piece of re-used hardware is the HDD, which is ~7 years old. The new parts were for a performance upgrade.

    Edit: Just in case it comes up, I have opened up my PC and triple-checked each connection, so all connections and cables are firmly fit. Also, something I noticed, the particular dump file you posted says "OSNAME: Windows 10" and I've been running on Windows 11 for a while now.
    Last edited by TimmyTop; 26 Jan 2022 at 22:41.
      My Computer
    Quote Quote

  6. RJARRRPCGP
    Posts : 624
    Windows 10 Pro 21H2 x64
       New #4

    "BUGCHECK_CODE: a" -> That usually means you need to back off on your CPU core overclocking. It can be caused by not enough Vcore.

    On my T-bird, (early AMD socket 462) 1050 Mhz was unstable no matter what I did and caused Windows XP to crash with this stop code. So, I needed to lower the CPU core multiplier.

    I also gotten this one, when Linpack failed on my Pentium E2180, (65nm Core 2 dual core) because a Vcore raise was required.
      My Computers
    Quote Quote

  7. zbook
    Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       New #5

    Were you able to check if the RAM was on the ASUS Qualified Vendor List (QVL)?


    AMD Ryzen 5 3600 6-Core Processor
    ROG STRIX B450-F GAMING
    F4-3600C16-8GVKC



    If yes, please post the images or share links into this thread using one drive, drop box, or google drive.

    And test the RAM with Memtest86 for two tests of four passes each.

    MemTest86 - Official Site of the x86 and ARM Memory Testing Tool

    Memtest86 has a feature to create test reports.

    Please post images or share links including the text reports into this thread.




    If the RAM was not on the QVL please find RAM on the QVL for testing purposes.


    Crucial System Scanner | Memory Upgrade Scanner | Crucial
      My Computer
    Quote Quote

  8. TimmyTop
    Posts : 3
    Windows 11
    Thread Starter
       New #6

    zbook said:
    Were you able to check if the RAM was on the ASUS Qualified Vendor List (QVL)?


    AMD Ryzen 5 3600 6-Core Processor
    ROG STRIX B450-F GAMING
    F4-3600C16-8GVKC



    If yes, please post the images or share links into this thread using one drive, drop box, or google drive.

    And test the RAM with Memtest86 for two tests of four passes each.

    MemTest86 - Official Site of the x86 and ARM Memory Testing Tool

    Memtest86 has a feature to create test reports.

    Please post images or share links including the text reports into this thread.




    If the RAM was not on the QVL please find RAM on the QVL for testing purposes.


    Crucial System Scanner | Memory Upgrade Scanner | Crucial
    I couldn't find my RAM on the QVL. Once I can afford new RAM, I will try memtest.
      My Computer
    Quote Quote

  9. zbook
    Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       New #7

    Memtest86 can test for functioning or malfunctioning RAM.
    It does not test for incompatible RAM.

    The logs were consistent with RAM / motherboard problems.

    When possible please evaluate the computer for stability / instability with RAM on the QVL.

    Crucial has a guarantee for compatible RAM.
    A guarantee of compatibility is the next best testing option.
      My Computer
    Quote Quote

 

  Related Discussions
Frequent Various BSOD crashes
in BSOD Crashes and Debugging

Hello, for the last 2-3 days out of nowhere the last 2-3 days my computer has been getting a variety of different BSODs. Many of which point to faulty hardware, drivers, or memory problems. I've tried a few things including updating any outdated...
Frequent crashes and restarts
in BSOD Crashes and Debugging

Hello, I just built a new system (or really moved an old system to a new motherboard) involving a Foxconn Quantumian1 x79 motherboard and a 3930k processor. On the old system (HP motherboard), I was not having any problems. With the Foxconn, I am...
Frequent Crashes
in BSOD Crashes and Debugging

Right now I have 3 large monitors. When the crash happens my display freezes on my primary monitor and the other monitors go black. On windows 8 it would go straight to BSOD and on 10 it shows the last thing i was looking at.\ The crash typically...
Frequent crashes
in BSOD Crashes and Debugging

My T420s crashes at least once a week. Has been doing so for a long time. I'm sending the analysis files along with this post. Thanks in advance.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 18:50.
Find Us




Windows 10 Forums