BSOD on new PC

[tempus319]

Hi,

The computer is a new setup. It keeps crashing and i need some assistance with seeing what may be the issue. I’m using Windbg tool and pasted the results. I made sure all drivers is up to date.

Here is my pc build.

http://speccy.piriform.com/results/DXFUbZUoYo8UcTBui4KGdYB

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

Loading Dump File [C:\Windows\Minidump\030122-5015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred SRVC:\Windows\symbol_cache Symbol information
Symbol search path is: SRVC:\Windows\symbol_cache Symbol information
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806[ICODE]0e200000 PsLoadedModuleList = 0xfffff806[/ICODE]0ee2a270
Debug session time: Tue Mar 1 09:39:00.677 2022 (UTC - 5:00)
System Uptime: 0 days 0:01:36.313
Loading Kernel Symbols
…
…
…
Loading User Symbols
Loading unloaded module list
…
For analysis of this file, run !analyze -v
3: kd> !analyze -v

---

•                                                                         *

•                    Bugcheck Analysis                                    *

•                                                                         *

---

CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffc08ff9ed90c0, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
[HEADING=1]Debugging Details:[/HEADING]
KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 4468

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 12240

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

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

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

Key  : CriticalProcessDied.ExceptionCode
Value: f9f15040

Key  : CriticalProcessDied.ImageName
Value: RPCRT4.dll

Key  : CriticalProcessDied.ImageOffset
Value: 40694

Key  : CriticalProcessDied.ImageSize
Value: 12a000

Key  : CriticalProcessDied.ImageTimestamp
Value: 9f38e81d

Key  : CriticalProcessDied.Process
Value: wininit.exe

Key  : CriticalProcessDied.Symbol
Value: RPCRT4.dll!RpcBindingFromStringBindingW

Key  : CriticalProcessDied.WERReportId
Value: 2a15df43-00d1-4d81-bf45-93c9954d61ef

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: ef

BUGCHECK_P1: ffffc08ff9ed90c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: wininit.exe

CRITICAL_PROCESS: wininit.exe

ERROR_CODE: (NTSTATUS) 0xf9f15040 -

CRITICAL_PROCESS_REPORTGUID: {2a15df43-00d1-4d81-bf45-93c9954d61ef}

IMAGE_NAME: RPCRT4.dll

MODULE_NAME: RPCRT4

FAULTING_MODULE: 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffbc06[ICODE]789b1938 fffff806[/ICODE]0eb07cb2 : 00000000[ICODE]000000ef ffffc08f[/ICODE]f9ed90c0 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nt!KeBugCheckEx
ffffbc06[ICODE]789b1940 fffff806[/ICODE]0ea0eabf : 00000000[ICODE]00000000 fffff806[/ICODE]0e4fd6ed 00000000[ICODE]00000002 fffff806[/ICODE]0e4fcd07 : nt!PspCatchCriticalBreak+0x10e
ffffbc06[ICODE]789b19e0 fffff806[/ICODE]0e8b3cb4 : ffffc08f[ICODE]00000000 00000000[/ICODE]00000000 ffffc08f[ICODE]f9ed90c0 ffffc08f[/ICODE]f9ed94f8 : nt!PspTerminateAllThreads+0x15b543
ffffbc06[ICODE]789b1a50 fffff806[/ICODE]0e8b3fdc : ffffc08f[ICODE]f9ed90c0 00000000[/ICODE]00000000 0000009d[ICODE]be9ff62c fffff806[/ICODE]0e800daa : nt!PspTerminateProcess+0xe0
ffffbc06[ICODE]789b1a90 fffff806[/ICODE]0e608bb8 : ffffc08f[ICODE]f9ed90c0 ffffc08f[/ICODE]f9f15040 ffffbc06[ICODE]789b1b80 ffffc08f[/ICODE]f9ed90c0 : nt!NtTerminateProcess+0x9c
ffffbc06[ICODE]789b1b00 00007ffa[/ICODE]8f96d2f4 : 00007ffa[ICODE]8f9e2b53 00007ffa[/ICODE]8fa16708 0000009d[ICODE]be9ff5f0 00000000[/ICODE]00000000 : nt!KiSystemServiceCopyEnd+0x28
0000009d[ICODE]be9fe228 00007ffa[/ICODE]8f9e2b53 : 00007ffa[ICODE]8fa16708 0000009d[/ICODE]be9ff5f0 00000000[ICODE]00000000 00007ffa[/ICODE]8f8d0000 : 0x00007ffa[ICODE]8f96d2f4 0000009d[/ICODE]be9fe230 00007ffa[ICODE]8fa16708 : 0000009d[/ICODE]be9ff5f0 00000000[ICODE]00000000 00007ffa[/ICODE]8f8d0000 00000000[ICODE]00000006 : 0x00007ffa[/ICODE]8f9e2b53
0000009d[ICODE]be9fe238 0000009d[/ICODE]be9ff5f0 : 00000000[ICODE]00000000 00007ffa[/ICODE]8f8d0000 00000000[ICODE]00000006 00007ffa[/ICODE]8f97530e : 0x00007ffa[ICODE]8fa16708 0000009d[/ICODE]be9fe240 00000000[ICODE]00000000 : 00007ffa[/ICODE]8f8d0000 00000000[ICODE]00000006 00007ffa[/ICODE]8f97530e 00007ffa[ICODE]8fa16708 : 0x0000009d[/ICODE]be9ff5f0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0xEF_wininit.exe_BUGCHECK_CRITICAL_PROCESS_f9f1504 0_RPCRT4.dll!RpcBindingFromStringBindingW_IMAGE_RP CRT4.dll

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {bffc3f6b-df9e-fb5b-113f-d570cb3a4253}
[HEADING=1]Followup: MachineOwner[/HEADING]
Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\030122-4828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred SRVC:\Windows\symbol_cache Symbol information
Symbol search path is: SRVC:\Windows\symbol_cache Symbol information
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804[ICODE]1a200000 PsLoadedModuleList = 0xfffff804[/ICODE]1ae2a270
Debug session time: Tue Mar 1 09:57:19.173 2022 (UTC - 5:00)
System Uptime: 0 days 0:06:27.785
Loading Kernel Symbols
…
…
…
…
Loading User Symbols
Loading unloaded module list
…
For analysis of this file, run !analyze -v
10: 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: ffff968f19e92d90, 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: fffff8041a44a2f0, address which referenced memory
[HEADING=1]Debugging Details:[/HEADING]
KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3359

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 9481

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

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

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

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: a

BUGCHECK_P1: ffff968f19e92d90

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8041a44a2f0

READ_ADDRESS: fffff8041aefb390: 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
ffff968f19e92d90

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

TRAP_FRAME: ffff840d76387550 – (.trap 0xffff840d76387550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8041a44a2f0 rsp=ffff840d763876e0 rbp=0000000000000000
r8=fffff8041ae50b00 r9=ffff9e8f19e43000 r10=ffff9e8f19e43080
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiDecrementSubsections+0x30:
fffff804[ICODE]1a44a2f0 48837b0800 cmp qword ptr [rbx+8],0 ds:00000000[/ICODE]00000008=???
Resetting default scope

STACK_TEXT:
ffff840d[ICODE]76387408 fffff804[/ICODE]1a609169 : 00000000[ICODE]0000000a ffff968f[/ICODE]19e92d90 00000000[ICODE]00000002 00000000[/ICODE]00000000 : nt!KeBugCheckEx
ffff840d[ICODE]76387410 fffff804[/ICODE]1a605469 : 00000000[ICODE]00000000 ffff9e8f[/ICODE]213b32c0 ffff9e8f[ICODE]217fca70 fffff804[/ICODE]1abb1149 : nt!KiBugCheckDispatch+0x69
ffff840d[ICODE]76387550 fffff804[/ICODE]1a44a2f0 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 ffff9e8f[ICODE]220cf080 ffff840d[/ICODE]763877b9 : nt!KiPageFault+0x469
ffff840d[ICODE]763876e0 fffff804[/ICODE]1a413294 : 00000000[ICODE]00000000 ffff840d[/ICODE]763877b9 ffff9e8f[ICODE]19e9b028 ffff9e8f[/ICODE]19e43080 : nt!MiDecrementSubsections+0x30
ffff840d[ICODE]76387710 fffff804[/ICODE]1a801149 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 ffff9e8f[ICODE]00000000 ffff9e8f[/ICODE]00000000 : nt!MiDeleteVad+0xb54
ffff840d[ICODE]76387820 fffff804[/ICODE]1a8007e0 : ffff9e8f[ICODE]22a56150 ffff9e8f[/ICODE]227732f0 ffff9e8f[ICODE]220cf080 00000000[/ICODE]00000000 : nt!MiUnmapVad+0x49
ffff840d[ICODE]76387850 fffff804[/ICODE]1a7feaaf : ffff9e8f[ICODE]22a54350 ffff9e8f[/ICODE]22a54350 ffff9e8f[ICODE]22a56150 ffff9e8f[/ICODE]213b32c0 : nt!MiCleanVad+0x30
ffff840d[ICODE]76387880 fffff804[/ICODE]1a85c5a8 : ffffffff[ICODE]00000000 ffffffff[/ICODE]ffffffff 00000000[ICODE]00000001 ffff9e8f[/ICODE]213b32c0 : nt!MmCleanProcessAddressSpace+0x137
ffff840d[ICODE]76387900 fffff804[/ICODE]1a8b0ab6 : ffff9e8f[ICODE]213b32c0 ffffb005[/ICODE]05abe630 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nt!PspRundownSingleProcess+0x20c
ffff840d[ICODE]76387990 fffff804[/ICODE]1a8b401e : ffff9e8f[ICODE]00000000 00000000[/ICODE]00000001 00000000[ICODE]00000000 000000ab[/ICODE]a6d06000 : nt!PspExitThread+0x5f6
ffff840d[ICODE]76387a90 fffff804[/ICODE]1a608bb5 : ffff9e8f[ICODE]213b32c0 ffff9e8f[/ICODE]220cf080 ffff840d[ICODE]76387b80 ffff9e8f[/ICODE]00000000 : nt!NtTerminateProcess+0xde
ffff840d[ICODE]76387b00 00007ffd[/ICODE]0a22d2f4 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nt!KiSystemServiceCopyEnd+0x25
000000ab[ICODE]a6aafb28 00000000[/ICODE]00000000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : 0x00007ffd`0a22d2f4

SYMBOL_NAME: nt!MiDecrementSubsections+30

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.1288

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 30

FAILURE_BUCKET_ID: AV_nt!MiDecrementSubsections

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c3f8815f-6a52-e018-43b8-0890a171d8f0}
[HEADING=1]Followup: MachineOwner[/HEADING]
Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\030122-5953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred SRVC:\Windows\symbol_cache Symbol information
Symbol search path is: SRVC:\Windows\symbol_cache Symbol information
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802[ICODE]25600000 PsLoadedModuleList = 0xfffff802[/ICODE]2622a2d0
Debug session time: Tue Mar 1 10:37:24.753 2022 (UTC - 5:00)
System Uptime: 0 days 0:01:14.388
Loading Kernel Symbols
…
…
…
Loading User Symbols
Loading unloaded module list
…
For analysis of this file, run !analyze -v
0: 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: 0000000000d800bd, 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: fffff802258a449a, address which referenced memory
[HEADING=1]Debugging Details:[/HEADING]
KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 4062

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 4383

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

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

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

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: a

BUGCHECK_P1: d800bd

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff802258a449a

READ_ADDRESS: fffff802262fa390: 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
0000000000d800bd

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: iCUE.exe

TRAP_FRAME: ffffb80387ce6590 – (.trap 0xffffb80387ce6590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9719f0f443b2 rbx=0000000000000000 rcx=0000000000d80005
rdx=ffffc2398b110000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802258a449a rsp=ffffb80387ce6720 rbp=ffffb80387ce67a9
r8=000000000000f085 r9=0000000000000005 r10=0000000000d80005
r11=ffffb80387ce6b00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiAddWorkingSetEntries+0x2a:
fffff802[ICODE]258a449a 0fb681b8000000 movzx eax,byte ptr [rcx+0B8h] ds:00000000[/ICODE]00d800bd=??
Resetting default scope

STACK_TEXT:
ffffb803[ICODE]87ce6448 fffff802[/ICODE]25a09569 : 00000000[ICODE]0000000a 00000000[/ICODE]00d800bd 00000000[ICODE]00000002 00000000[/ICODE]00000000 : nt!KeBugCheckEx
ffffb803[ICODE]87ce6450 fffff802[/ICODE]25a05869 : ffffb803[ICODE]87ce6b00 ffff9080[/ICODE]034da4b0 ffff9719[ICODE]f0f44022 fffff802[/ICODE]26250b80 : nt!KiBugCheckDispatch+0x69
ffffb803[ICODE]87ce6590 fffff802[/ICODE]258a449a : ffffb803[ICODE]87ce6880 ffffa10e[/ICODE]24049610 ffff9080[ICODE]034da4b0 ffffb803[/ICODE]87ce6860 : nt!KiPageFault+0x469
ffffb803[ICODE]87ce6720 fffff802[/ICODE]2585d2d2 : 00000000[ICODE]00000000 fffff802[/ICODE]258a12e8 ffffb803[ICODE]87ce6880 ffff8006[/ICODE]fac07960 : nt!MiAddWorkingSetEntries+0x2a
ffffb803[ICODE]87ce6810 fffff802[/ICODE]25a4afab : ffff8006[ICODE]fac07960 ffffa10e[/ICODE]24049610 ffff8006[ICODE]f9545910 fffff802[/ICODE]258294f2 : nt!MiEmptyDeferredWorkingSetEntries+0x6e
ffffb803[ICODE]87ce6840 fffff802[/ICODE]2585be65 : 00000000[ICODE]00000001 00000000[/ICODE]00d80005 00000000[ICODE]00008000 00000000[/ICODE]00000000 : nt!MiUnlockFaultPageTable+0x18cd03
ffffb803[ICODE]87ce6870 fffff802[/ICODE]2585b7d5 : 00000000[ICODE]00000000 ffffb803[/ICODE]87ce68e0 ffff8006[ICODE]fac07960 ffff8006[/ICODE]faafe5f0 : nt!MiReleaseFaultState+0x2d
ffffb803[ICODE]87ce68a0 fffff802[/ICODE]2589f5a8 : 00000000[ICODE]c0033333 00000000[/ICODE]00000001 00007ffe[ICODE]7f252650 ffffa10e[/ICODE]24049610 : nt!MiIssueHardFault+0x95
ffffb803[ICODE]87ce6960 fffff802[/ICODE]25a0575e : ffff8006[ICODE]fa8a1000 ffff8006[/ICODE]00000000 ffffb803[ICODE]87ce6b80 ffff8006[/ICODE]f6bd8080 : nt!MmAccessFault+0x468
ffffb803[ICODE]87ce6b00 00007ffe[/ICODE]7f252650 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nt!KiPageFault+0x35e
000000c8[ICODE]b70fb2c8 00000000[/ICODE]00000000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : 0x00007ffe`7f252650

SYMBOL_NAME: nt!MiAddWorkingSetEntries+2a

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.1566

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 2a

FAILURE_BUCKET_ID: AV_nt!MiAddWorkingSetEntries

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f5a11243-4cf5-5895-9c75-d32dc752b601}
[HEADING=1]Followup: MachineOwner[/HEADING]

[phillpower2]

While we look at Speccy;

If the computer is a desktop can you post the brand and model name or number of the power supply (PSU).

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the Attach button, bottom left of the dialogue input box

[tempus319]

Hi,

It’s a custom pc. EVGA 600 GD PSU

Thanks

[phillpower2]

Thanks for the additional info, decent enough PSU (y)

Will take a look at the crash dmps but before I do a couple of pointers from Speccy
RAM
16.0GB Dual-Channel Unknown @ [COLOR=rgb(226, 80, 65)]1798MHz

You have the wrong RAM for your CPU, AMD state here up to 2933MHz and if you have XMP or DOCP enabled the RAM will get auto OCd past what the CPU can handle and the PC fall over.

Go into the BIOS, disable XMP and then manually set the RAM to run at 2933MHz and the voltage to 1.35V.

In addition to the above, Windows updates and drivers are failing to install and the drivers that did install have been done wrong.

Once Windows has been clean installed you must then install first the chipset drivers, then the storage/SATA drivers and third the graphics drivers, the drivers can either come from a disk provided by the motherboard manufacturer or downloaded from the site and saved to a flash drive etc, this is a must and Windows should not be allowed to check for updates before it has been done as more often than not Windows installs the wrong drivers or in the incorrect order and this can cause all sorts of problems.[/COLOR]

[phillpower2]

Address my reply #4 above before doing anything else, the thread will end up all over the place otherwise.

[tempus319]

I check the BIOS, under AI Overclock Tuner - It’s set to DOCP. I don’t have XMP. Do you like me to change it to AUTO? I change the memory frequency 2933 and 1.35V

[phillpower2]

if you have XMP or DOCP enabled

They are one and the same thing and your MB being an older version merely has DOCP instead of XMP.

[tempus319]

Thanks, i change it to Auto since that’s only option i had.

[phillpower2]

No, as in my reply #4 but you disable DOCP instead, if not sure how to do this take a look at your MBs user manual.

Go into the BIOS, disable XMP and then [COLOR=rgb(226, 80, 65)]manually set the RAM to run at 2933MHz and the voltage to 1.35V.
[/COLOR]

[COLOR=rgb(226, 80, 65)][/color]

[tempus319]

No, as in my reply #4 but you disable DOCP instead, if not sure how to do this take a look at your MBs user manual.

Setting it to Auto on my motherboard i think disabled DOCP. I double-check and it shows disabled now once I saved the BIOS. I did change the RAM frequency to 2933 and voltage to 1.35

[phillpower2]

Been a couple of days now, any further issues since you changed the RAM speed and voltage.

[tempus319]

Been a couple of days now, any further issues since you changed the RAM speed and voltage.

Sorry for the delay but it’s been working fine since changing RAM speed on the bios. We can close this out.

[phillpower2]

No worries, glad we were able to help and thanks for letting us know that the issue is now resolved.