Share via

New GPU, mostly the same crashing

Anonymous
2021-11-29T10:45:38+00:00

I replaced a GPU that finally died (visual artifacts), but I was also getting crashing tabs on Chrome and random blue screens, the latter especially while gaming, usually with buzzing sounds, but it wasn't the only issue? I still get those latter two issues. What's going on? It's always something different on the memory dump.

************* Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. ************* Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff80465e00000 PsLoadedModuleList = 0xfffff80466a2a2d0 Debug session time: Thu Nov 18 22:53:13.578 2021 (UTC - 4:00) System Uptime: 0 days 1:08:33.232 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ......... Loading User Symbols PEB is paged out (Peb.Ldr = 00000081bed19018). Type ".hh dbgerr001" for details Loading unloaded module list ......... For analysis of this file, run !analyze -v 5: 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: 0000000000000038, 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: fffff80466354c3e, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 3 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-5757KSB Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 83 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: a BUGCHECK_P1: 38 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff80466354c3e READ_ADDRESS: 0000000000000038 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: chrome.exe TRAP_FRAME: fffffc880e901a40 -- (.trap 0xfffffc880e901a40) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=ffff93b0ec01b370 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80466354c3e rsp=fffffc880e901bd0 rbp=fffffc880e901ca1 r8=ffffe784616400c0 r9=80040000001b287f r10=0000000fffffffff r11=fffffc880e901c18 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!MiDecrementCloneBlockReference+0x56: fffff80466354c3e 488b4638 mov rax,qword ptr [rsi+38h] ds:0000000000000038=???????????????? Resetting default scope STACK_TEXT: fffffc880e9018f8 fffff80466209269 : 000000000000000a 0000000000000038 0000000000000002 0000000000000000 : nt!KeBugCheckEx fffffc880e901900 fffff80466205569 : ffffd3ddf1c5be54 0000000000000001 000000010e901bf8 0000000000000000 : nt!KiBugCheckDispatch+0x69 fffffc880e901a40 fffff80466354c3e : 0000000000000000 fffff804660f6fd2 000000039531a880 0000000000000000 : nt!KiPageFault+0x469 fffffc880e901bd0 fffff8046603acbb : 0000000000000000 fffffc880e901ca1 0000000000000001 0000000000000000 : nt!MiDecrementCloneBlockReference+0x56 fffffc880e901c20 fffff804660b0b0e : fffffc880e902050 ffffe784616400c0 0000000000000001 fffffc880e902910 : nt!MiDeletePteList+0x32b fffffc880e901d00 fffff804663fa1ed : ffffe7845a32a080 ffffe7845d494268 0000000000000000 0000000000000000 : nt!MiDecommitPages+0x124e fffffc880e9028d0 fffff804663f9853 : fffffc880e902a50 0000000000000000 fffffc880e902a50 ffffe7845d494240 : nt!MiDecommitRegion+0x7d fffffc880e902950 fffff804663f9145 : 0000000000000000 ffffe7845b786780 fffffc880e902b18 0000000000000000 : nt!MmFreeVirtualMemory+0x6d3 fffffc880e902aa0 fffff80466208cb8 : ffffe7845a32a080 ffffe7845b786640 0000000000000000 ffffe78400000000 : nt!NtFreeVirtualMemory+0x95 fffffc880e902b00 00007ffe0530d134 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 00000081c1dfe828 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe0530d134 SYMBOL_NAME: nt!MiDecrementCloneBlockReference+56 MODULE_NAME: nt STACK_COMMAND: .thread ; .cxr ; kb IMAGE_NAME: memory_corruption BUCKET_ID_FUNC_OFFSET: 56 FAILURE_BUCKET_ID: AV_nt!MiDecrementCloneBlockReference OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {48596048-f15a-be0e-9bf6-7fe6d1c9728d} Followup: MachineOwner ---------

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

8 answers

Sort by: Most helpful
  1. DaveM121 891.1K Reputation points Independent Advisor
    2021-11-30T10:22:22+00:00

    Hi Smith

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    1

    Go to the support page for your B450M DS3H-CF Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, check for any BIOS update that may need to be installed

    2

    Wait to see if your system stabilizes, if not, the best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-11-30T10:15:17+00:00

    Only the paid version of that app allows 8-passes. Memtest86+ doesn't boot on my pc. It claims there is no OS on the drive with it.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-11-30T10:13:52+00:00

    Was this answer helpful?

    0 comments No comments
  4. JX313 7,045 Reputation points
    2021-11-29T11:26:53+00:00

    The printout shows that the cause is memory corruption.

    Run a full 8-pass test using Memtest86: https://memtest86.com

    Was this answer helpful?

    0 comments No comments
  5. DaveM121 891.1K Reputation points Independent Advisor
    2021-11-29T11:18:17+00:00

    Hi Smith_5

    I am Dave, I will help you with this.

    Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    Was this answer helpful?

    0 comments No comments