Question LiveKernal 141 error

[CopyWasTaken]

Ive been having these pc crashes for a while now, and i cant fix for the life of me. Ive searched high and low for a fix and nothing. Everything leads to a driver issue but i've tried several Nvidia drivers and no luck. The main issue i get is LiveKernal 141, sometimes ill get livekernal 117 also. Most of the time a game im playing will close, other times the pc will completely freeze needing a force restart.



Things ive tried to do as a fix:
-reinstall gpu drivers using DDU
-update bios
-restore bios to default
-disable xmp
-older nvidia drivers
-CHKDSK, SFCSCANNOW, DISM
-tried windows 10 and 11 (currently on 11)
-maybe some other stuff i cant remember

my specs are:
-Palit RTX 2070
-Ryzen 7 3800XT
-gigabyte b450 auros pro rev 1.0
-32GB 4x8 dimms 3000mhz corsair vengeance

https://imgur.com/a/MqgqyO3

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffe68cbdc0b010
Parameter 2: fffff80436053ee8
Parameter 3: 0
Parameter 4: 2f84
OS version: 10_0_22000
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.22000.2.0.0.768.101
Locale ID: 2057





also here is a dump file i found which may offer some help with troubleshooting. not too sure if its from the same issue but i would assume so

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

Loading Dump File [C:\Users\Jordan\Desktop\WATCHDOG-20220905-1836.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 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff80420a00000 PsLoadedModuleList = 0xfffff804216296b0
Debug session time: Mon Sep 5 18:36:07.474 2022 (UTC + 1:00)
System Uptime: 0 days 0:14:48.093
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
watchdog!WdpDbgCaptureTriageDump+0xb7:
fffff80431b8948f 488b4628 mov rax,qword ptr [rsi+28h] ds:002b:ffffe68cbf2d8588=????????????????
6: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real BugCheck.)
Arguments:
Arg1: ffffe68cb93da010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80436053ee8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2030

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 14027

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x117

Key : Bugcheck.Code.Register
Value: 0x144f3a20

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: WATCHDOG-20220905-1836.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 117

BUGCHECK_P1: ffffe68cb93da010

BUGCHECK_P2: fffff80436053ee8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe68cb93da010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_NAME: System

STACK_TEXT:
ffffd0884c156660 fffff80431b95040 : ffffe68cb71ce030 ffffe68cb71ce030 ffffe68cbf2d8560 ffffe68cb93da010 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffffd0884c1566d0 fffff80431a16c1d : ffffe68cb93da010 ffffd0884c156890 0000000000000000 0000000000000002 : watchdog!WdDbgReportRecreate+0xf0
ffffd0884c156730 fffff80431a15e02 : ffffad8500000000 ffffad851485cd60 0000000000000002 0000000040000000 : dxgkrnl!TdrUpdateDbgReport+0x11d
ffffd0884c156790 fffff80431a16720 : ffffe68c00000000 ffffe68cb93da010 0000000000000000 0000000000000000 : dxgkrnl!TdrCollectDbgInfoStage1+0xa72
ffffd0884c1568d0 fffff80433945189 : 0000000000000000 ffffe68cb87ac000 01d8c14dfacdfca4 0000000000000000 : dxgkrnl!TdrIsRecoveryRequired+0x140
ffffd0884c156900 fffff804339c826c : 0000000000000000 0000000000000000 ffffe68cb87ac000 ffffe68cb87ac4a8 : dxgmms2!VidSchiReportHwHang+0x5e9
ffffd0884c156a10 fffff8043390b6ac : 0000000000000000 0000000000000000 000000000000dded 0000000000989680 : dxgmms2!VidSchiCheckHwProgress+0x3165c
ffffd0884c156a90 fffff804339ae335 : ffffe68cbeb06000 ffffe68cb87ac000 ffffe68cbeb06010 ffffe68cb884e820 : dxgmms2!VidSchiScheduleCommandToRun+0x5c
ffffd0884c156b60 fffff804339ae2ea : ffffe68cb87ac400 fffff804339ae220 ffffe68cb87ac000 ffffe68cb881d400 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffd0884c156bb0 fffff80420c478f5 : ffffe68cb881d480 fffff80400000001 ffffe68cb87ac000 000f8067b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffd0884c156bf0 fffff80420e19644 : ffff96014136f180 ffffe68cb881d480 fffff80420c478a0 c18148382444110f : nt!PspSystemThreadStartup+0x55
ffffd0884c156c40 0000000000000000 : ffffd0884c157000 ffffd0884c151000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nvlddmkm+d83ee8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x117_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b6b0a2d8-ce7c-30b0-9856-626823269238}

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

6: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real BugCheck.)
Arguments:
Arg1: ffffe68cb93da010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80436053ee8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1952

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1955

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x117

Key : Bugcheck.Code.Register
Value: 0x144f3a20

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: WATCHDOG-20220905-1836.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 117

BUGCHECK_P1: ffffe68cb93da010

BUGCHECK_P2: fffff80436053ee8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe68cb93da010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_NAME: System

STACK_TEXT:
ffffd0884c156660 fffff80431b95040 : ffffe68cb71ce030 ffffe68cb71ce030 ffffe68cbf2d8560 ffffe68cb93da010 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffffd0884c1566d0 fffff80431a16c1d : ffffe68cb93da010 ffffd0884c156890 0000000000000000 0000000000000002 : watchdog!WdDbgReportRecreate+0xf0
ffffd0884c156730 fffff80431a15e02 : ffffad8500000000 ffffad851485cd60 0000000000000002 0000000040000000 : dxgkrnl!TdrUpdateDbgReport+0x11d
ffffd0884c156790 fffff80431a16720 : ffffe68c00000000 ffffe68cb93da010 0000000000000000 0000000000000000 : dxgkrnl!TdrCollectDbgInfoStage1+0xa72
ffffd0884c1568d0 fffff80433945189 : 0000000000000000 ffffe68cb87ac000 01d8c14dfacdfca4 0000000000000000 : dxgkrnl!TdrIsRecoveryRequired+0x140
ffffd0884c156900 fffff804339c826c : 0000000000000000 0000000000000000 ffffe68cb87ac000 ffffe68cb87ac4a8 : dxgmms2!VidSchiReportHwHang+0x5e9
ffffd0884c156a10 fffff8043390b6ac : 0000000000000000 0000000000000000 000000000000dded 0000000000989680 : dxgmms2!VidSchiCheckHwProgress+0x3165c
ffffd0884c156a90 fffff804339ae335 : ffffe68cbeb06000 ffffe68cb87ac000 ffffe68cbeb06010 ffffe68cb884e820 : dxgmms2!VidSchiScheduleCommandToRun+0x5c
ffffd0884c156b60 fffff804339ae2ea : ffffe68cb87ac400 fffff804339ae220 ffffe68cb87ac000 ffffe68cb881d400 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffd0884c156bb0 fffff80420c478f5 : ffffe68cb881d480 fffff80400000001 ffffe68cb87ac000 000f8067b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffd0884c156bf0 fffff80420e19644 : ffff96014136f180 ffffe68cb881d480 fffff80420c478a0 c18148382444110f : nt!PspSystemThreadStartup+0x55
ffffd0884c156c40 0000000000000000 : ffffd0884c157000 ffffd0884c151000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nvlddmkm+d83ee8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x117_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b6b0a2d8-ce7c-30b0-9856-626823269238}

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

6: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real BugCheck.)
Arguments:
Arg1: ffffe68cb93da010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80436053ee8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1952

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1948

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x117

Key : Bugcheck.Code.Register
Value: 0x144f3a20

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: WATCHDOG-20220905-1836.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 117

BUGCHECK_P1: ffffe68cb93da010

BUGCHECK_P2: fffff80436053ee8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe68cb93da010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_NAME: System

STACK_TEXT:
ffffd0884c156660 fffff80431b95040 : ffffe68cb71ce030 ffffe68cb71ce030 ffffe68cbf2d8560 ffffe68cb93da010 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffffd0884c1566d0 fffff80431a16c1d : ffffe68cb93da010 ffffd0884c156890 0000000000000000 0000000000000002 : watchdog!WdDbgReportRecreate+0xf0
ffffd0884c156730 fffff80431a15e02 : ffffad8500000000 ffffad851485cd60 0000000000000002 0000000040000000 : dxgkrnl!TdrUpdateDbgReport+0x11d
ffffd0884c156790 fffff80431a16720 : ffffe68c00000000 ffffe68cb93da010 0000000000000000 0000000000000000 : dxgkrnl!TdrCollectDbgInfoStage1+0xa72
ffffd0884c1568d0 fffff80433945189 : 0000000000000000 ffffe68cb87ac000 01d8c14dfacdfca4 0000000000000000 : dxgkrnl!TdrIsRecoveryRequired+0x140
ffffd0884c156900 fffff804339c826c : 0000000000000000 0000000000000000 ffffe68cb87ac000 ffffe68cb87ac4a8 : dxgmms2!VidSchiReportHwHang+0x5e9
ffffd0884c156a10 fffff8043390b6ac : 0000000000000000 0000000000000000 000000000000dded 0000000000989680 : dxgmms2!VidSchiCheckHwProgress+0x3165c
ffffd0884c156a90 fffff804339ae335 : ffffe68cbeb06000 ffffe68cb87ac000 ffffe68cbeb06010 ffffe68cb884e820 : dxgmms2!VidSchiScheduleCommandToRun+0x5c
ffffd0884c156b60 fffff804339ae2ea : ffffe68cb87ac400 fffff804339ae220 ffffe68cb87ac000 ffffe68cb881d400 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffd0884c156bb0 fffff80420c478f5 : ffffe68cb881d480 fffff80400000001 ffffe68cb87ac000 000f8067b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffd0884c156bf0 fffff80420e19644 : ffff96014136f180 ffffe68cb881d480 fffff80420c478a0 c18148382444110f : nt!PspSystemThreadStartup+0x55
ffffd0884c156c40 0000000000000000 : ffffd0884c157000 ffffd0884c151000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nvlddmkm+d83ee8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x117_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b6b0a2d8-ce7c-30b0-9856-626823269238}

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

NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'

please can someone help, i've tried everything :/

 

[Vic 40]

Ooooh wall of text,would use spoiler to al least hide the whole dump file part of the post. Just saying. 😉

What psu do you use? =maker+model+wattage.

Did the ram come in as one set (4x8gb kit) or did you combine 2 sets (2x(2x8gb kit))?

 

[CopyWasTaken]

Ooooh wall of text,would use spoiler to al least hide the whole dump file part of the post. Just saying. 😉

What psu do you use? =maker+model+wattage.

Did the ram come in as one set (4x8gb kit) or did you combine 2 sets (2x(2x8gb kit))?

Yeah sorry about the wall of text lol, i tried using a spoiler and it removed all the spacing etc so decided to leave it like that.

The psu im using rn is a corsair TX550m
and i currently have 2 different kits of 16gbs, both same speeds, timings and model number etc. just one is a older generation set. Ive tried using the sets individually to see if that made a difference but the error still happened. Ive tried with and without XMP also. I assume the 550W PSU is enough though because the GPU is rated for that and the PSU is reliable enough to give it sufficient power under load

 

[Vic 40]

Tested with the latest "Studio Driver " from Nvidia? Is a little more stable version and has little to no impact on gaming performance. Best would be to use DDU again to get rid of current driverset and after that install the latest Studio driver.

Other thing i'm looking at after some googling is maybe somewhat ill advised,

https://substance3d.adobe.com/docum...th-long-computations-tdr-crash-128745489.html

if wanting to try this out make sure you have a back up of the registry and for sure make sure you have a back up of data might it bite you in the behind. Wouldn't set it to 60, but saw in some other older threads about it to set it to 10 which was in those threads the value that Nvidia themselves adviced where the standard is 2 seconds.

https://www.google.com/url?sa=t&rct...recovery.htm&usg=AOvVaw0fT2CunrV6ZehY5nlOdWwk

 

[CopyWasTaken]

Tested with the latest "Studio Driver " from Nvidia? Is a little more stable version and has little to no impact on gaming performance. Best would be to use DDU again to get rid of current driverset and after that install the latest Studio driver.

Other thing i'm looking at after some googling is maybe somewhat ill advised,

https://substance3d.adobe.com/docum...th-long-computations-tdr-crash-128745489.html

if wanting to try this out make sure you have a back up of the registry and for sure make sure you have a back up of data might it bite you in the behind. Wouldn't set it to 60, but saw in some other older threads about it to set it to 10 which was in those threads the value that Nvidia themselves adviced where the standard is 2 seconds.

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjSrJXUqoD6AhUzgf0HHSUQCLwQFnoECAgQAw&url=https://docs.nvidia.com/gameworks/content/developertools/desktop/timeout_detection_recovery.htm&usg=AOvVaw0fT2CunrV6ZehY5nlOdWwk

Okay, ill try the TDR stuff first as it sounds more promising, if it doesn't help i'll try the studio driver as I've never thought of that. Ill keep you posted. Thanks for the help

 

[Vic 40]

Hope it helps, do let me know.

 

[CopyWasTaken]

Hope it helps, do let me know.

Just had a large crash while playing SOTTR. All audio went fuzzy then both screens go black. and whole pc locks up needing a force restart. That was with the TDR changes so i will revert them not and try the studio drivers.

 

[Vic 40]

try the studio drivers.

Hope that these make difference.

 

[CopyWasTaken]

Just had another crash with the studio drivers installed. Was playing FIFA 22 which isn't really graphically intense tbh. The game instantly crashed with an error, then around 5-10 seconds later all the audio went robotic and the whole system was like stuttering and lagging really bad. then it all locked up but audio continued to play. just checked reliability history after reboot and was livekernal 141 again with locale 2057 etc

 

[Vic 40]

You also updated to the latest chipset drivers and lan drivers?

Looked at your first post and saw you used both W10 and W11 and had issue, starts to sound like maybe some hardware doesn't want to play ball. Am starting to wonder if the psu might be an issue, or the ram.
Ram can be checked with Memtest86, make a bootable usb and let it at least do 4 passes. First check with all sticks in, if there are problems check each stick at a time.

I also use a 2070 in a system where i needed to use two seperate power cables to power it correctly which your psu doesn't have. Anyway to test with another higher power psu? Maybe from a friend or local shop ... one of decent quality and at least two cables (4 connectors /use first one of each cable).
Did you by any chance make sure the pcie power cable is seated correctly at the psu side?

 

[CopyWasTaken]

You also updated to the latest chipset drivers and lan drivers?

Looked at your first post and saw you used both W10 and W11 and had issue, starts to sound like maybe some hardware doesn't want to play ball. Am starting to wonder if the psu might be an issue, or the ram.
Ram can be checked with Memtest86, make a bootable usb and let it at least do 4 passes. First check with all sticks in, if there are problems check each stick at a time.

I also use a 2070 in a system where i needed to use two seperate power cables to power it correctly which your psu doesn't have. Anyway to test with another higher power psu? Maybe from a friend or local shop ... one of decent quality and at least two cables (4 connectors /use first one of each cable).
Did you by any chance make sure the pcie power cable is seated correctly at the psu side?

Ive just updated my chipset and LAN drivers to the latest versions, ill do 4 passes of memtest now and let you know the results. i will check all the PSU cables are seated correctly etc if the memtest returns no issues. Thanks for the help once again

 

[CopyWasTaken]

Okay so i ran memtest with all 4 modules and got errors, so i ran each stick individually and 3 of the sticks were completely fine with the 4th and final stick showing these errors on both runs i did

https://imgur.com/a/mv8U1Ij

View: https://imgur.com/a/mv8U1Ij

https://imgur.com/hUJj2wf

View: https://imgur.com/hUJj2wf


if possible would you be to explain what these errors are because theyre mentioning CPU as far as i can see but it only happened with one of my ram sticks

here are also the reports from the end of the tests that had errors.
https://www.dropbox.com/s/wah6z6x110cc3g6/MemTest86-Report-20220911-125748.html?dl=0

Dropbox

www.dropbox.com

any information on this would be appreciated thanks. but i guess i now know that the issue was within that ram module

 

[Vic 40]

if possible would you be to explain what these errors are because theyre mentioning CPU as far as i can see but it only happened with one of my ram sticks

The cpu mentioned was the core that ran into the error, has nothing to do with that the cpu might be cause. Since you only have faults with one stick rma the complete set it was part of, ram usually has a lifetime warranty. If the store you bought it from doesn't want to acknowledge than contact the Corsair service department and create a ticket there, but first contact the store's support for an rma.

 

[CopyWasTaken]

The cpu mentioned was the core that ran into the error, has nothing to do with that the cpu might be cause. Since you only have faults with one stick rma the complete set it was part of, ram usually has a lifetime warranty. If the store you bought it from doesn't want to acknowledge than contact the Corsair service department and create a ticket there, but first contact the store's support for an rma.

Okay, appreciate the help with the issue. ill try and RMA the faulty kit and hopefully the issue has been fixed.

 

[Vic 40]

Okay, appreciate the help with the issue. ill try and RMA the faulty kit and hopefully the issue has been fixed.

You're welcome. Hope so too.