Question Frequent crashing

Jul 5, 2021
5
0
10
0
I built my PC about 2 years ago and didn't really have any issues, but around ~6 months ago I would start getting some crashes here and there, usually while my PC was idle in sleep.

I installed a fresh copy of Windows 10 about 3 months ago to hopefully fix any issues as my crashes would be every few days or within the same day.

When the more frequent crashes started occurring I would either be using Edge/Chrome, playing a game or again idle without any programs running.

So part of my trouble shooting was swapping the same kit of RAM into another Ryzen setup. The other Ryzen setup crashed in the same day, but at the time mine was fine, so I just assumed it was bad RAM and started an RMA for the RAM.

Having just got the replacement RAM I almost immediately crashed, I had reset CMOS incase I had some bad settings, this didn't help resolve my crashes.

Crashes happened in both XMP disabled and enabled. There are no other hardware setting tweaks.

Crashes aren't easy to replicate they would just happen within the day or two.

Ryzen 5 3600
Asrock Fatal1ty B450 Gaming K4
G.Skill Aegis F4-3000C16D-16GISB (8GBx2 kit)
AMD RX 580
Thermaltake TR2 TR-700
 
Jul 5, 2021
5
0
10
0
Some of the minidumps I had after replacing my RAM if that can help resolve any of my issues.

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\avery\Desktop\070521-7296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80011200000 PsLoadedModuleList = 0xfffff80011e2a230
Debug session time: Mon Jul 5 17:05:01.175 2021 (UTC - 7:00)
System Uptime: 0 days 0:03:06.784
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
2: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800115fdff2, The address that the exception occurred at
Arg3: fffffc0f1e959578, Exception Record Address
Arg4: ffffa2800f399920, Context Record Address

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

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

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G64RNUH

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 4

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff800115fdff2

BUGCHECK_P3: fffffc0f1e959578

BUGCHECK_P4: ffffa2800f399920

EXCEPTION_RECORD: fffffc0f1e959578 -- (.exr 0xfffffc0f1e959578)
ExceptionAddress: fffff800115fdff2 (nt!SwapContext+0x0000000000000372)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffffa2800f399920 -- (.cxr 0xffffa2800f399920)
rax=0000000000000004 rbx=ffffa2800f340180 rcx=fffffc0f1e959cc0
rdx=0000000000000000 rsi=ffffb28e34ec9040 rdi=ffffa2800f34b340
rip=fffff800115fdff2 rsp=fffffc0f1e9597b0 rbp=000f8067bcbbbdff
r8=ffffa2800f340180 r9=0000000000000000 r10=000000000000000e
r11=0000000000000000 r12=0000000000000090 r13=0000000000000000
r14=ffffb28e32474080 r15=ffffa2800f34e000
iopl=0 nv up ei pl zr ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050257
nt!SwapContext+0x372:
fffff800115fdff2 0fc719 xrstors [rcx]
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff80011efb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80011e0f388: Unable to get Flags value from nt!KdVersionBlock
fffff80011e0f388: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

EXCEPTION_STR: 0xc0000005

BAD_STACK_POINTER: ffffa2800f3990e8

STACK_TEXT:
fffffc0f
1e9597b0 fffff800115fd9a6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!SwapContext+0x372
fffffc0f
1e9597f0 fffff8001140c970 : ffffa2800f9c0180 fffff800ffffffff ffffb28e34ec9040 0000000000000000 : nt!KiSwapContext+0x76
fffffc0f
1e959930 fffff8001140be9f : 000000000000000b 01d0006000000004 fffffc0f1e959b20 fffff80000000000 : nt!KiSwapThread+0x500
fffffc0f
1e9599e0 fffff8001150941e : 0000000000000000 ffffa28000000000 0000000000000100 0000000000000000 : nt!KiCommitThreadWait+0x14f
fffffc0f
1e959a80 fffff8001634b629 : ffffb28e34ecaa20 0000000000000001 ffffb28e34ec7950 ffffb28e00000050 : nt!KeWaitForMultipleObjects+0x2be
fffffc0f
1e959b90 ffffb28e34ecaa20 : 0000000000000001 ffffb28e34ec7950 ffffb28e00000050 0000000000000000 : WdFilter+0x1b629
fffffc0f
1e959b98 0000000000000001 : ffffb28e34ec7950 ffffb28e00000050 0000000000000000 0000000000000000 : 0xffffb28e34ecaa20
fffffc0f1e959ba0 ffffb28e34ec7950 : ffffb28e00000050 0000000000000000 0000000000000000 0000000000000000 : 0x1
fffffc0f1e959ba8 ffffb28e00000050 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0xffffb28e34ec7950
fffffc0f
1e959bb0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 ffffb28e34ec78c0 : 0xffffb28e00000050


SYMBOL_NAME: WdFilter+1b629

MODULE_NAME: WdFilter

IMAGE_NAME: WdFilter.sys

STACK_COMMAND: .cxr 0xffffa2800f399920 ; kb

BUCKET_ID_FUNC_OFFSET: 1b629

FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_WdFilter!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e782c876-454e-c4d3-2d58-4bc5ab2856ef}

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

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\avery\Desktop\070521-7312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80665200000 PsLoadedModuleList = 0xfffff80665e2a230
Debug session time: Mon Jul 5 17:17:35.516 2021 (UTC - 7:00)
System Uptime: 0 days 0:12:00.126
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
2: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fdf59777a353c, Reserved
Arg2: b3b6ebdfc9f87df4, Reserved
Arg3: fffff80665483730, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
2a : Type 4 pool corruption
2b : Modification of a function or .pdata
2c : Image integrity corruption
2d : Processor misconfiguration
2e : Type 5 process list corruption
2f : Process shadow corruption
30 : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G64RNUH

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 5

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 109

BUGCHECK_P1: a39fdf59777a353c

BUGCHECK_P2: b3b6ebdfc9f87df4

BUGCHECK_P3: fffff80665483730

BUGCHECK_P4: 1

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffc871f2dee28 0000000000000000 : 0000000000000109 a39fdf59777a353c b3b6ebdfc9f87df4 fffff80665483730 : nt!KeBugCheckEx


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80665483af8 - nt!KiInitializeUserApc+3c8
[ e8:e9 ]
1 error : !nt (fffff80665483af8)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption
---------

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\avery\Desktop\070521-7171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8023a000000 PsLoadedModuleList = 0xfffff8023ac2a230
Debug session time: Mon Jul 5 17:18:54.670 2021 (UTC - 7:00)
System Uptime: 0 days 0:00:44.279
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
6: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8023a378628, The address that the exception occurred at
Arg3: ffff8482b9f362f8, Exception Record Address
Arg4: ffff8482b9f35b30, Context Record Address

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

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

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Write

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G64RNUH

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 4

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8023a378628

BUGCHECK_P3: ffff8482b9f362f8

BUGCHECK_P4: ffff8482b9f35b30

EXCEPTION_RECORD: ffff8482b9f362f8 -- (.exr 0xffff8482b9f362f8)
ExceptionAddress: fffff8023a378628 (nt!KeSetIdealProcessorThreadByNumber+0x0000000000000014)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: ffffd68c206e3919
Attempt to write to address ffffd68c206e3919

CONTEXT: ffff8482b9f35b30 -- (.cxr 0xffff8482b9f35b30)
rax=0000000000000000 rbx=ffffd68c55e2f040 rcx=ffffd68c55e2f040
rdx=ffff8482b9f365b4 rsi=0000000000000004 rdi=ffff8482b9f369c0
rip=fffff8023a378628 rsp=ffff8482b9f36530 rbp=ffff8482b9f36860
r8=ffff8482b9f365b4 r9=fffff8023a000000 r10=ffffffff80004600
r11=ffff9f0e23a7b080 r12=0000000000000000 r13=ffffd68c4bf0e100
r14=0000000000000003 r15=00007fffffff0000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!KeSetIdealProcessorThreadByNumber+0x14:
fffff8023a378628 088bd9488bca or byte ptr [rbx-3574B727h],cl ds:002b:ffffd68c206e3919=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

WRITE_ADDRESS: fffff8023acfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8023ac0f388: Unable to get Flags value from nt!KdVersionBlock
fffff8023ac0f388: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffd68c206e3919

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: ffffd68c206e3919

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff8482b9f36530 fffff8023a6e15e6 : ffffd68c55e2f040 0000000000000004 0000000000000000 0000000000000000 : nt!KeSetIdealProcessorThreadByNumber+0x14
ffff8482b9f36560 fffff8023a4085b8 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!NtSetInformationThread+0xd46
ffff8482b9f367e0 fffff8023a3faa80 : fffff8024171a25d 0000000000800000 ffffd68c56b03e40 0000000000000040 : nt!KiSystemServiceCopyEnd+0x28
ffff8482b9f36978 fffff8024171a25d : 0000000000800000 ffffd68c56b03e40 0000000000000040 0000000000000000 : nt!KiServiceLinkage
ffff8482b9f36980 fffff80241719f69 : 0000000000000000 0000000000800000 ffffd68c5586d400 fffff80241719f30 : HTTP!UlpInitializeThreadPoolWorkers+0x2b9
ffff8482b9f36aa0 fffff8023a274843 : ffffd68c52b4d720 ffffd68c52aade30 ffffd68c5586d400 fffff802407d5440 : HTTP!UlpThreadPoolStarter+0x39
ffff8482b9f36b00 fffff8023a341225 : ffffd68c4bf0e100 ffffd68c4bf0e100 fffff8023a2747b0 ffffd68c00000000 : nt!IopProcessWorkItem+0x93
ffff8482b9f36b70 fffff8023a2f53b5 : ffffd68c4bf0e100 0000000000000080 ffffd68c49874080 000f8067bcbbbdff : nt!ExpWorkerThread+0x105
ffff8482b9f36c10 fffff8023a3fe278 : ffffc4002adc0180 ffffd68c4bf0e100 fffff8023a2f5360 ffff9f0e23b90c89 : nt!PspSystemThreadStartup+0x55
ffff8482b9f36c60 0000000000000000 : ffff8482b9f37000 ffff8482b9f31000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
18 errors : !nt (fffff8023a378010-fffff8023a378eb8)
fffff8023a378010 *4a 03 e8 5d 01 00 00 eb 96 cc cc cc cc cc cc cc J..]............
...
fffff8023a378270 48 c1 e0 0c 48 03 c1 4c *7b c0 72 20 48 8b 5b 08 H...H..L{.r H.[.
...
fffff8023a378440 *09 00 00 c0 eb df 48 8b 05 83 57 cb ff eb b2 cc ......H...W.....
fffff8023a378450 *ce cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc ................
...
fffff8023a378470 *08 66 89 44 24 30 8b 44 *2c 78 89 44 24 28 48 8b .f.D$0.D,x.D$(H.
...
fffff8023a378620 83 ec 20 83 64 24 48 00 *08 8b d9 48 8b ca 49 8b .. .d$H....H..I.
fffff8023a378630 *f8 e8 3a 89 fa ff 83 f8 ff 74 30 4c 8d 44 24 48 ..:......t0L.D$H
...
fffff8023a3786e0 8b e0 00 00 00 48 8d 4e *38 44 8b 83 c0 00 00 00 .....H.N8D......
...
fffff8023a378840 *8b 43 e8 48 8b f1 48 0f be 41 42 48 8d 14 c0 48 .C.H..H..ABH...H
...
fffff8023a378860 8a 00 48 8b bb c8 00 00 *08 48 8b 6b 20 4c 8b 73 ..H......H.k L.s
fffff8023a378870 18 e8 1a 10 fd ff 48 8b *1b 48 39 5a 08 0f 85 eb ......H..H9Z....
...
fffff8023a378c20 5f c3 cc cc cc cc cc cc *ce cc cc cc cc cc cc cc _...............
fffff8023a378c30 40 53 48 83 ec 40 0f 10 *0a 48 8b d9 4c 8d 4c 24 @sh..@...H..L.L$
...
fffff8023a378ce0 c0 0f 84 29 70 0f 00 0f *12 06 44 89 78 14 48 8d ...)p.....D.x.H.
...
fffff8023a378e50 48 8d 93 c8 38 00 00 48 *8b 54 24 30 48 8d 05 4d H...8..H.T$0H..M
...
fffff8023a378e70 05 cb e9 ed ff 4c 89 7c *34 28 48 89 45 e0 49 8b .....L.|4(H.E.I.
...
fffff8023a378eb0 8d 4f 68 e8 c8 41 40 00 *4d 33 c0 33 d2 49 8b cc .Oh..A@.M3.3.I..

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .cxr 0xffff8482b9f35b30 ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

Followup: memory_corruption
---------

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\avery\Desktop\070521-4625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8064e41a000 PsLoadedModuleList = 0xfffff8064f044230
Debug session time: Mon Jul 5 17:48:07.371 2021 (UTC - 7:00)
System Uptime: 0 days 0:00:08.033
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
For analysis of this file, run !analyze -v
5: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff80e172524cf, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 0000000065447a52, Pool Tag (if provided).

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G64RNUH

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: c4

BUGCHECK_P1: 2000

BUGCHECK_P2: fffff80e172524cf

BUGCHECK_P3: 0

BUGCHECK_P4: 65447a52

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffda83af3aac88 fffff8064ede9e24 : 00000000000000c4 0000000000002000 fffff80e172524cf 0000000000000000 : nt!KeBugCheckEx
ffffda83af3aac90 fffff8064e9b6c35 : fffff8064f02ccb0 0000000000002000 fffff80e172524cf 0000000000000000 : nt!VerifierBugCheckIfAppropriate+0xe0
ffffda83af3aacd0 fffff8064ede0de4 : 0000000065447a52 fffff8064f02ccb0 fffff80e172524cf 0000000000000000 : nt!VfReportIssueWithOptions+0x101
ffffda83af3aad20 fffff8064e9b5512 : ffffc90fc8e15e00 0000000000000001 000036f037277f28 fffff8064f8768a3 : nt!VfCheckPoolType+0x90
ffffda83af3aad60 fffff8064f8a7069 : 0000000000000000 000036f037277f28 0000000000000000 0000000000000000 : nt!VfCheckNxPoolType+0x12
ffffda83af3aad90 fffff80e172524cf : ffffc90fc8d880d0 0000000000000000 ffffda83af3aaef0 ffffc90fc8d883c0 : Wdf01000!imp_WdfDeviceAllocAndQueryProperty+0x99 [minkernel\wdf\framework\shared\core\fxdeviceapi.cpp @ 1196]
ffffda83af3aadf0 ffffc90fc8d880d0 : 0000000000000000 ffffda83af3aaef0 ffffc90fc8d883c0 0000000000000000 : RzDev_0084+0x24cf
ffffda83af3aadf8 0000000000000000 : ffffda83af3aaef0 ffffc90fc8d883c0 0000000000000000 ffffda83af3aae40 : 0xffffc90fc8d880d0


SYMBOL_NAME: RzDev_0084+24cf

MODULE_NAME: RzDev_0084

IMAGE_NAME: RzDev_0084.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 24cf

FAILURE_BUCKET_ID: 0xc4_2000_VRF_RzDev_0084!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {cff503a9-b104-a561-e94c-70504bd0cf1a}

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

[/SPOILER]
 
Last edited:
Jul 5, 2021
5
0
10
0
Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\avery\Desktop\070521-6937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806[/ICODE]6e600000 PsLoadedModuleList = 0xfffff8066f22a230
Debug session time: Mon Jul 5 17:55:07.468 2021 (UTC - 7:00)
System Uptime: 0 days 0:02:11.080
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffbc8d5f806010, Address of the IRP
Arg2: 0000000000001232
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G64RNUH

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 5

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 44

BUGCHECK_P1: ffffbc8d5f806010

BUGCHECK_P2: 1232

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffffbc8d5f806010

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

DEVICE_OBJECT: ffffbc8d56933030

DRIVER_OBJECT: ffffbc8d551cfe10

IMAGE_NAME: Ntfs.sys

MODULE_NAME: Ntfs

FAULTING_MODULE: fffff80673800000 Ntfs

STACK_TEXT:
ffff8e88
b3030098 fffff8066ea7f85c : 0000000000000044 ffffbc8d5f806010 0000000000001232 0000000000000000 : nt!KeBugCheckEx
ffff8e88
b30300a0 fffff8066e90dda7 : ffffbc8d567b4d30 0000000000000001 ffffbc8d60b73a28 ffffbc8d5f806010 : nt!IopfCompleteRequest+0x171a9c
ffff8e88
b3030190 fffff80673804c18 : 0000000000000000 0000000000000001 ffffbc8d60b73a28 fffff80673804822 : nt!IofCompleteRequest+0x17
ffff8e88
b30301c0 fffff80673934da3 : 0000000000000000 ffffbc8d60b73a28 0000000000000001 0000000000000004 : Ntfs!NtfsExtendedCompleteRequestInternal+0x178
ffff8e88
b3030220 fffff806739329dd : ffffbc8d60b73a28 ffffbc8d5f806010 ffff8e88b3030501 ffffbc8d0000006c : Ntfs!NtfsPrefetchFile+0x653
ffff8e88
b3030360 fffff8067393242d : ffffbc8d60b73a28 0000000000000001 0000000000000000 0000000000000000 : Ntfs!NtfsUserFsRequest+0x28d
ffff8e88
b30303e0 fffff8066e9185b5 : ffffbc8d5f8618b0 fffff8066d604b46 ffffbc8d5f806010 ffff8e88b302b000 : Ntfs!NtfsFsdFileSystemControl+0x17d
ffff8e88
b3030500 fffff8066d606ccf : 0000000000000000 0000000000000000 0000000000000000 fffff8066efb3149 : nt!IofCallDriver+0x55
ffff8e88
b3030540 fffff8066d63caf4 : ffff8e88b30305d0 0000000000000000 00000000000000e0 ffffbc8d53f460c0 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffff8e88
b30305b0 fffff8066e9185b5 : 000000000000000a ffffbc8d5f806010 0000000000000002 0000000000000000 : FLTMGR!FltpFsControl+0x104
ffff8e88
b3030610 fffff8066ece2748 : ffffbc8d5f806010 0000000000000000 0000000000000000 ffffbc8d60a4e080 : nt!IofCallDriver+0x55
ffff8e88
b3030650 fffff8066ece2015 : 0000000000090120 ffff8e88b3030990 0000000000440005 ffff8e88b3030990 : nt!IopSynchronousServiceTail+0x1a8
ffff8e88
b30306f0 fffff8066ec680c0 : 0000000000000000 ffffffff8000323c 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0x5e5
ffff8e88
b3030830 fffff8066ede4a45 : ffffa60c554ec118 ffffffff800047c0 ffff8e88b30309b1 ffffa60c60f791c8 : nt!PfSnPrefetchFileMetadata+0xe8
ffff8e88
b30308d0 fffff8066ec04695 : 000000000000006c ffff8e88b3030b00 ffffa60c60f7f78e ffffa60c00000000 : nt!PfSnGetSectionObject+0x1e012d
ffff8e88
b3030a00 fffff8066e941225 : ffffbc8d53f98080 ffffbc8d53f98080 ffffbc8d53e64810 0000000000000000 : nt!PfSnPopulateReadList+0x2b5
ffff8e88
b3030b70 fffff8066e8f53b5 : ffffbc8d53f98080 0000000000000080 ffffbc8d53e74080 0000000000000000 : nt!ExpWorkerThread+0x105
ffff8e88
b3030c10 fffff8066e9fe278 : ffff9500b6f40180 ffffbc8d53f98080 fffff8066e8f5360 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffff8e88
b3030c60 0000000000000000 : ffff8e88b3031000 ffff8e88b302b000 0000000000000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: Ntfs!NtfsExtendedCompleteRequestInternal+178

IMAGE_VERSION: 10.0.19041.1052

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 178

FAILURE_BUCKET_ID: 0x44_Ntfs!NtfsExtendedCompleteRequestInternal

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {42ccd47d-ee92-af2f-d440-362d08bb3bda}

Followup: MachineOwner
---------
 
Jul 5, 2021
5
0
10
0
I swapped the PSU out, Termaltake for a more recent EVGA BR 600W bought around 1-2 years ago and got the 2 crash dumps below

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\avery\Desktop\070621-7437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8015bc00000 PsLoadedModuleList = 0xfffff8015c82a230
Debug session time: Tue Jul 6 15:10:04.972 2021 (UTC - 7:00)
System Uptime: 0 days 0:00:45.581
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
8: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G64RNUH

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 4

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8015be0a996

BUGCHECK_P3: ffff9689e5ee5d80

BUGCHECK_P4: 0

CONTEXT: ffff9689e5ee5d80 -- (.cxr 0xffff9689e5ee5d80)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000001
rip=fffff8015be0a996 rsp=ffff9689e5ee6780 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffff8015bec81f0
r11=ffffc386c298e8b8 r12=0000000000000000 r13=0000000000000000
r14=ffffffffffffffff r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!PsBoostThreadIoEx+0x56:
fffff8015be0a996 399e50050000 cmp dword ptr [rsi+550h],ebx ds:002b:0000000000000550=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffff9689e5ee6780 fffff8015bec820a : ffffc386c07ce010 ffff9689e5ee6904 0000000000000000 ffffc386c298e8b8 : nt!PsBoostThreadIoEx+0x56
ffff9689e5ee67d0 ffffc3de13a55c1b : 0000000000000001 ffffc3de13a59903 ffffc386c09f48c0 ffff9d8d3a4d0e50 : nt!PsLeavePriorityRegion+0x1a
ffff9689e5ee6800 ffffc3de13acef50 : 0000000000000000 ffff9689e5ee6904 0000000000000000 ffffc386c298e8b8 : win32kbase!GreReleaseHmgrSemaphore+0x3b
ffff9689e5ee6840 ffffc3de13a5771a : 0000000000000000 ffffc386c09f48c0 000000000000003e 0000000000000000 : win32kbase!HmgIncProcessHandleCountEx+0x68
ffff9689e5ee6870 ffffc3de13d5fe99 : ffffc386c09f48c0 0000000000000000 ffff9689e5ee6980 0000000000000000 : win32kbase!HmgInsertObjectInternal+0x12a
ffff9689e5ee68d0 ffffc3de13d5fe51 : ffffc386c074a810 0000000000000000 0000000000000000 ffff9689e5ee68f0 : win32kfull!HmgInsertObjectHelper::Insert+0x2d
ffff9689e5ee6900 ffffc3de13d5fdb1 : 0000000000000000 ffffc386c074a810 ffff9689e5ee6980 0000000000000000 : win32kfull!RGNOBJ::hrgnAssociate+0x1d
ffff9689e5ee6930 ffffc3de13d60e8d : 0000000000000000 ffffc386c074a810 ffff9689e5ee6a70 00000000061206a9 : win32kfull!GrepSfmGetDirtyRgn+0x1d9
ffff9689e5ee69b0 ffffc3de13d5fb12 : 00000000c000000d ffff9689e5ee6b80 0000000000000038 0000000000000000 : win32kfull!GreSfmGetDirtyRgn+0x109
ffff9689e5ee6a10 ffffc3de148ac281 : ffff9d8d3cf570c0 000001e62d89f0a0 0000000000000020 000001e624eb3901 : win32kfull!NtGdiHLSurfGetInformation+0x142
ffff9689e5ee6ac0 fffff8015c0085b8 : ffff9d8d00000000 0000000000000001 0000000000000000 ffff9689e5ee6b80 : win32k!NtGdiHLSurfGetInformation+0x15
ffff9689e5ee6b00 00007ffa99806be4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
00000089cf61f378 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa99806be4


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8015bec81fa - nt!PsLeavePriorityRegion+a
[ 01:03 ]
1 error : !nt (fffff8015bec81fa)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: .cxr 0xffff9689e5ee5d80 ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption
---------[/SPOILER]


[SPOILER="second crash"]
Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\avery\Desktop\070621-7500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803
74000000 PsLoadedModuleList = 0xfffff80374c2a230
Debug session time: Tue Jul 6 15:34:38.182 2021 (UTC - 7:00)
System Uptime: 0 days 0:01:35.791
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
5: kd> !analyze -v
*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff8037433103a, 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-G64RNUH

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: a

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8037433103a

WRITE_ADDRESS: fffff80374cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80374c0f388: Unable to get Flags value from nt!KdVersionBlock
fffff80374c0f388: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RadeonSoftware.exe

TRAP_FRAME: ffff8e049739c590 -- (.trap 0xffff8e049739c590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=fffff180032e3dc3
rdx=ffffa0d2c3d03c70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8037433103a rsp=ffff8e049739c720 rbp=ffff8e049739c920
r8=0004000000101db4 r9=80000000000000f2 r10=ffffa0bfffffff78
r11=fffff180032e3da0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiResolveProtoPteFault+0xa2a:
fffff803
7433103a 49ab stos qword ptr [rdi] ds:0000000000000000=????????????????
Resetting default scope

STACK_TEXT:
ffff8e04
9739c448 fffff80374408b69 : 000000000000000a 0000000000000000 0000000000000002 0000000000000001 : nt!KeBugCheckEx
ffff8e04
9739c450 fffff80374404e69 : 0000000000000000 0000000000000000 0000000000000000 fffff8037432d53f : nt!KiBugCheckDispatch+0x69
ffff8e04
9739c590 fffff8037433103a : 0000000000000001 ffff8e049739c8b8 ffffa080ae53aa10 0000000000000000 : nt!KiPageFault+0x469
ffff8e04
9739c720 fffff8037432a055 : ffff8e049739c880 0000000000000000 ffff8e049739c860 ffffba84bbeb4700 : nt!MiResolveProtoPteFault+0xa2a
ffff8e04
9739c820 fffff80374327f99 : 0000000000000110 0000000000000100 00000000c0000016 ffffa587a078ede0 : nt!MiDispatchFault+0x3d5
ffff8e04
9739c960 fffff80374404d5e : 0000000000000084 0000000000000001 0000000000000001 ffff8e049739cb80 : nt!MmAccessFault+0x189
ffff8e04
9739cb00 00007ffe419d0be0 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e
00000019
ab6ff5d8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe419d0be0


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8037433103b - nt!MiResolveProtoPteFault+a2b
[ 8b:ab ]
1 error : !nt (fffff8037433103b)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption
---------

I did some other parts swap again,

Swapped my Ryzen 5 3600 out for a Ryzen 5 2600
Then I proceeded to run Prime95 with XMP disabled then enabled; disabled ran just fine, but when I enabled XMP my PC would not post, it would not be able to reach the boot menu either (no video out).
The only other option I had on hand was to swap RAM kits out (the RMA'd one was installed and failed to post with XMP enabled)
Once again with the Ryzen 5 2600 I was able to go into the boot menu and run Prime95 while having XMP off and on with no issues.

That leads me to believe my RAM kit is incompatible with Ryzen 5 3600 and Asrock Fatal1ty B450 Gaming K4 motherboard together, I also did not see my specific RAM on either QVL listings.
 
Last edited:
Jul 5, 2021
5
0
10
0
I picked up some Corsair RAM CMK16GX4M2B320016W (I saw this was on the QVL for Corsair's site that was compatible with my motherboard) and tried with my system again, and more or less the same result; but instead of blue screens with a crash code and minidumps, it will freeze for about 5-20 seconds then hard reboot. This again can happen either under some load or having a browser up, or just file explorer.

I again preceded with a fresh install of windows 10, swapping out peripherals to the basic microsoft ones, I also had tried running with only the boot drive, including swapping SATA ports, and also I had swapped the boot drive with the other ryzen 2600 PC, there was no difference using another GPU in place of mine. The crashes persisted through all of the changes I had been doing, no difference in the crashes I was getting today either.

So now the only two parts that I haven't thoroughly been able to trouble shoot if the CPU or the MotherBoard is causing my crashes.
 

ASK THE COMMUNITY