Question WHEA_Uncorrectable_Error (124) while gaming ?

[scorz18]

Hi!
As of building a new PC recently im getting the error above while gaming. Two times it was a green screen freeze, and the last time it was a green screen freeze with white cubes on the screen. All three times I had to restart the PC with the power button. I'm getting these error with a newly bought RX 6600.

• Before it i've had a GTX 1050 TI in the same system, with that I've encountered no errors.
• I've ran OCCT tests, testmem5 with anta777 absolut cfg, corecycler and Intel Processor Diagnostic Tool...all without any errors.
• I've also updated the BIOS.
• I'd like to also add that before there green screen WHEA error crashes I've got amduw23g stopped responding and has successfully recovered errors with the latest drivers. After this I've rolled back to the 23.11.1 driver only...and now i'm getting the error above.
• All of this is happened only while gaming as I've already mentioned before.
• Now after switching back to the old GTX 1050 Ti from the RX 6600 im getting no errors, crashes, BSODs...nothing.

Here's a link to all the dump files
This is the PC:

• INTEL CORE I3-12100F without any OC
• MSI PRO H610M-E DDR4
• KINGSTON FURY 16GB BEAST DDR4 3200MHZ CL16 KIT KF432C16BBK2/16 (now without XMP)
• XFX Speedster SWFT 210 AMD Radeon RX 6600 Core 8GB
• SILICON POWER 512GB P34A80 M.2 PCIE M.2 2280 SP512GBP34A80M28
• ToshibaP300 3.5 3TB 7200rpm 64MB SATA3 (HDWD130UZSVA)
• SEASONIC B12 BC 650W

And this is the error:
...............................................................
................................................................
................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000005c`ec9d3018). Type ".hh dbgerr001" for details
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
nt!LkmdTelCreateReport+0x1d4:
fffff801`2a874e38 0f1f440000 nop dword ptr [rax+rax]
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000007, BOOT Error
Arg2: ffffa80f52714020, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 453
Key : Analysis.Elapsed.mSec
Value: 1927
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 93
Key : Analysis.Init.Elapsed.mSec
Value: 4439
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
Key : Bugcheck.Code.LegacyAPI
Value: 0x124
Key : Dump.Attributes.AsUlong
Value: 18
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys
Key : Failure.Hash
Value: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}
BUGCHECK_CODE: 124
BUGCHECK_P1: 7
BUGCHECK_P2: ffffa80f52714020
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: WHEA-20240301-2034.dmp
DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump
PROCESS_NAME: smss.exe
STACK_TEXT:
ffffe103`e7e2ee70 fffff801`2a807157 : ffffa80f`52714000 00000000`00000000 ffffa80f`52714020 0000005c`ecc7fa78 : nt!LkmdTelCreateReport+0x1d4
ffffe103`e7e2f3b0 fffff801`2a80704e : ffffa80f`52714000 ffffe103`e7e2faa0 00000000`00000000 00000000`00000000 : nt!WheapReportLiveDump+0x7b
ffffe103`e7e2f3f0 fffff801`2a64eb95 : 00000000`00000001 ffffe103`e7e2faa0 00000000`00000000 00000000`00000000 : nt!WheapReportDeferredLiveDumps+0x7a
ffffe103`e7e2f420 fffff801`2a54fca1 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff801`2f0aa22c : nt!WheaCrashDumpInitializationComplete+0x59
ffffe103`e7e2f450 fffff801`2a22bce5 : ffffa80f`54eb7080 00000000`00000000 00000000`0000022c 00000000`00000001 : nt!NtSetSystemInformation+0x971
ffffe103`e7e2fa20 00007ff8`8b092a84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000005c`ecc7fa18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`8b092a84
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}
Followup: MachineOwner
---------
4: kd> !errrec ffffa80f52714020
===============================================================================
Common Platform Error Record @ ffffa80f52714020
-------------------------------------------------------------------------------
Record Id : 01da6c0f682d1e43
Severity : Fatal (1)
Length : 28896
Creator : Microsoft
Notify Type : BOOT Error Record
Timestamp : 3/1/2024 19:34:01 (UTC)
Flags : 0x00000002 PreviousError
===============================================================================
Section 0 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffa80f527140a0
Section @ ffffa80f527142e0
Offset : 704
Length : 2592
Flags : 0x00000000
Severity : Fatal
===============================================================================
Section 1 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffa80f527140e8
Section @ ffffa80f52714d00
Offset : 3296
Length : 544
Flags : 0x00000000
Severity : Fatal
===============================================================================
Section 2 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffa80f52714130
Section @ ffffa80f52714f20
Offset : 3840
Length : 72
Flags : 0x00000000
Severity : Fatal

And the WATCHDOG error generated at the same time:
...............................................................
................................................................
..............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
watchdog!WdpDbgCaptureTriageDump+0xb7:
fffff806`9c34396d 488b4628 mov rax,qword ptr [rsi+28h] ds:002b:ffff900d`9d4432c8=????????????????
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the display engines failed to respond in timely fashion.
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Arguments:
Arg1: ffff900dafcda050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff806b4a28aa0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000002740, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1280
Key : Analysis.Elapsed.mSec
Value: 2343
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 171
Key : Analysis.Init.Elapsed.mSec
Value: 3549
Key : Analysis.Memory.CommitPeak.Mb
Value: 111
Key : Bugcheck.Code.LegacyAPI
Value: 0x141
Key : Dump.Attributes.AsUlong
Value: 18
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: LKD_0x141_IMAGE_amdkmdag.sys
Key : Failure.Hash
Value: {48b738dd-5a92-7ff8-63d0-f075fc680fe0}
BUGCHECK_CODE: 141
BUGCHECK_P1: ffff900dafcda050
BUGCHECK_P2: fffff806b4a28aa0
BUGCHECK_P3: 0
BUGCHECK_P4: 2740
FILE_IN_CAB: WATCHDOG-20240301-2033.dmp
DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff900dafcda050
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000002740
PROCESS_NAME: System
STACK_TEXT:
ffffef0b`13a07550 fffff806`9c358f24 : ffff900d`94c14030 ffff900d`94c14030 ffff900d`9d4432a0 ffff900d`afcda050 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffffef0b`13a075c0 fffff806`9c1b39dd : ffff900d`afcda050 ffffef0b`13a07780 00000000`00000000 fffff806`a0465419 : watchdog!WdDbgReportRecreate+0xd4
ffffef0b`13a07620 fffff806`a039bf7b : ffff900d`00000000 ffff900d`9c76fbd0 ffff900d`afcda050 ffff900d`9cc56000 : dxgkrnl!TdrUpdateDbgReport+0x11d
ffffef0b`13a07680 fffff806`a0465789 : ffff900d`9cc56000 00000000`00000000 ffff900d`9c76f000 ffff900d`9cc56001 : dxgmms2!VidSchiResetEngine+0x70f
ffffef0b`13a07830 fffff806`a0430feb : ffff900d`9c76f000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xb1
ffffef0b`13a07880 fffff806`a03ff53f : 00000000`00000000 00000000`00000000 00000000`0014dbcf 00000000`00989680 : dxgmms2!VidSchiCheckHwProgress+0x31a6b
ffffef0b`13a07900 fffff806`a0367c29 : 00000000`00000002 ffff900d`9c76f000 ffffef0b`13a07a39 00000000`00000002 : dxgmms2!VidSchiWaitForSchedulerEvents+0x37f
ffffef0b`13a079d0 fffff806`a0418815 : ffff900d`a7627000 ffff900d`9c76f000 ffff900d`a7627010 ffff900d`adc10010 : dxgmms2!VidSchiScheduleCommandToRun+0x309
ffffef0b`13a07aa0 fffff806`a041878a : 00000000`00000000 fffff806`a04186c0 ffff900d`9c76f000 00000000`00050246 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffef0b`13a07af0 fffff806`83507317 : ffff900d`9a3ed3c0 fffff806`00000001 ffff900d`9c76f000 004fe47f`b19bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffffef0b`13a07b30 fffff806`8361bcc4 : ffffa100`f4ca2180 ffff900d`9a3ed3c0 fffff806`835072c0 c08545c8`450fc0b6 : nt!PspSystemThreadStartup+0x57
ffffef0b`13a07b80 00000000`00000000 : ffffef0b`13a08000 ffffef0b`13a01000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: amdkmdag+f8aa0
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: LKD_0x141_IMAGE_amdkmdag.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {48b738dd-5a92-7ff8-63d0-f075fc680fe0}
Followup: MachineOwner
---------
At this point i'm not sure whether its the CPU or GPU or something else thats faulty here. However, as I mentioned it at the beggining, I've had no errors since putting back my old GPU.
Thanks for any help.

 

[Fix_that_Glitch]

What psu are you using?

 

[scorz18]

What psu are you using?

It's a Seasonic B12 BC 650W

 

[Satan-IR]

Anything in the Windows Event Viewer pinting to issue or errors?

Checked some of the dump, all in AMD Report and AMD Watchdog folders point to amdfendr.sys which is an AMD driver that's supposed to prevent crashes or somehing?

The dumps in Watchdog folder point to amdkmdag.sys which is AMD driver.

When you switched from GTX to the AMD and back did you uninstall drivers with something like DDU or just installed AMD alongside nVidida drivers? I would use DDU to uninstall all nvidia and AMD drivers. Reboot install AMD drivers with the new card and see if that helps.

You can also do system files check with "sfc /scannow" from an elevated Command Prompt. Right click CMD and click Run as administrator. Run sfc /scannow without the "s. Type sfc /scannow and hit enter.

How old is the PSU? It's one of the medium to low quality units by SeaSonic. If a PSU can't provide good clean power under load it might cause erratic behavior by some hardware such as graphic cards.

 

[scorz18]

The psu is new. Yes, I uninstalled with ddu in safe mode. And since I switched back from the RX 6600 to the GTX 1050 Ti, i've had no errors. The GTX consumes something like 90 watts and the amd's like 100-110 watts. It should be enough...total system consumption should be around 330-400w under load. Also when I tried testing the RX 6600 witch gpumemtest, it didn't recognized the card, but it did the 1050 ti.

 

[scorz18]

Okay, so I've put the RX 6600 back out of curiosity if I may put it in badly somehow before, ran furmark and when exiting furmark i got another green screen with this card. The card was consumpting around 90 Watts (not to much difference compared to the 1050 Ti's consumption) during the test. I've also ran furmark on the 1050 Ti before for hours in this system and never got any crashes with that. Here's the error, it's the same on as before with the 6600, process name is smss.exe:

Loading Dump File [C:\Windows\LiveKernelReports\WHEA\WHEA-20240308-1020.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22631 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`0da00000 PsLoadedModuleList = 0xfffff806`0e613550
Debug session time: Fri Mar 8 10:20:19.425 2024 (UTC + 1:00)
System Uptime: 0 days 0:00:05.106
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000ed`36e49018). Type ".hh dbgerr001" for details
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
nt!LkmdTelCreateReport+0x1d4:
fffff806`0e474e38 0f1f440000 nop dword ptr [rax+rax]
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000007, BOOT Error
Arg2: ffffce09aa524020, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 765

Key : Analysis.Elapsed.mSec
Value: 1922

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}


BUGCHECK_CODE: 124

BUGCHECK_P1: 7

BUGCHECK_P2: ffffce09aa524020

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: WHEA-20240308-1020.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

PROCESS_NAME: smss.exe

STACK_TEXT:
ffffde0e`80666e70 fffff806`0e407157 : ffffce09`aa524000 00000000`00000000 ffffce09`aa524020 000000ed`371ff568 : nt!LkmdTelCreateReport+0x1d4
ffffde0e`806673b0 fffff806`0e40704e : ffffce09`aa524000 ffffde0e`80667aa0 00000000`00000000 00000000`00000000 : nt!WheapReportLiveDump+0x7b
ffffde0e`806673f0 fffff806`0e24eb95 : 00000000`00000001 ffffde0e`80667aa0 00000000`00000000 00000000`00000000 : nt!WheapReportDeferredLiveDumps+0x7a
ffffde0e`80667420 fffff806`0e14fca1 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff806`113ba22c : nt!WheaCrashDumpInitializationComplete+0x59
ffffde0e`80667450 fffff806`0de2bce5 : ffffce09`ae44d080 00000000`00000000 00000000`0000022c 00000000`00000001 : nt!NtSetSystemInformation+0x971
ffffde0e`80667a20 00007ffb`93792a84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000ed`371ff508 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`93792a84


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

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

0: kd> !errec ffffce09aa524020
errec is not extension gallery command
No export errec found
0: kd> !errrec ffffce09aa524020
===============================================================================
Common Platform Error Record @ ffffce09aa524020
-------------------------------------------------------------------------------
Record Id : 01da7139d43e6cec
Severity : Fatal (1)
Length : 28896
Creator : Microsoft
Notify Type : BOOT Error Record
Timestamp : 3/8/2024 9:20:16 (UTC)
Flags : 0x00000002 PreviousError

===============================================================================
Section 0 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffce09aa5240a0
Section @ ffffce09aa5242e0
Offset : 704
Length : 2592
Flags : 0x00000000
Severity : Fatal


===============================================================================
Section 1 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffce09aa5240e8
Section @ ffffce09aa524d00
Offset : 3296
Length : 544
Flags : 0x00000000
Severity : Fatal


===============================================================================
Section 2 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffce09aa524130
Section @ ffffce09aa524f20
Offset : 3840
Length : 72
Flags : 0x00000000
Severity : Fatal

And this is what it looks like when I try to run gpumemtest with this card (it works with the 1050Ti):

 

[Satan-IR]

That smss.exe is a Windows/system file. The problem won't be caused by that file rather a driver that's trying to access memory that it shouldn't at high priority. That's why I recommended you run the sfc /scannow as it is the builtin process that scans all protected system files. Just to make sure.

Also when I tried testing the RX 6600 witch gpumemtest, it didn't recognized the card, but it did the 1050 ti.

And this is what it looks like when I try to run gpumemtest with this card (it works with the 1050Ti):

These could also indicate a problem with the card or the driver I think. If possible/available, I would check that card on another system and also check your system with another known good/working PSU of equal or higher capacity.


Also might not be a bad idea to check your RAM with MemTest86. One stick at a time if it's more than one stick.

 

[scorz18]

That smss.exe is a Windows/system file. The problem won't be caused by that file rather a driver that's trying to access memory that it shouldn't at high priority. That's why I recommended you run the sfc /scannow as it is the builtin process that scans all protected system files. Just to make sure.




These could also indicate a problem with the card or the driver I think. If possible/available, I would check that card on another system and also check your system with another known good/working PSU of equal or higher capacity.


Also might not be a bad idea to check your RAM with MemTest86. One stick at a time if it's more than one stick.

Sadly I can't test my system with another PSU, but I think I'm gonna take the card tomorrow to a local PC Store, see if they can test it.

Also, tests I ran this far:

• Furmark (no errors on the 1050Ti, crash on the 6600)
• OCCT tests (no errors)
• corecycler (no errors)
• Prime95 (no errors)
• TestMem5 (no errors)
• HCI MemTest (no errors)
• Y-cruncher (no error)
• Intel Processor Diagnostic Tool (no errors)

I think thats all, hadn't run memtest86+ yet, but I think im gonna give it a go for a couple of hours while I'm at work. Also all the voltages and temps in hwinfo64 seems ok, don't know how accurate or relevant they are tho.

Thanks

 

[scorz18]

That smss.exe is a Windows/system file. The problem won't be caused by that file rather a driver that's trying to access memory that it shouldn't at high priority. That's why I recommended you run the sfc /scannow as it is the builtin process that scans all protected system files. Just to make sure.




These could also indicate a problem with the card or the driver I think. If possible/available, I would check that card on another system and also check your system with another known good/working PSU of equal or higher capacity.


Also might not be a bad idea to check your RAM with MemTest86. One stick at a time if it's more than one stick.

The result of memtest86+

 

[Satan-IR]

The result of memtest86+

Looks like both RAM sticks were plugged on the motherboard when you did the MemTest.

What I meant by "Also might not be a bad idea to check your RAM with MemTest86. One stick at a time if it's more than one stick." was take both out. Plug one RAM stick in slot A2. Boot with MemTest86 bootable. Run maximum passes. Note if RAM is bad or throws errors. Turn PC off. Put other RAM stick in A2. Run MemTest86 maximum passes.

Also the two 8GB RAM sticks came as a pack, right? You didn't buy them at different times by any chance?

I'm sorry if I didn't make that clear.

 

[scorz18]

Yes, they came in a kit. And I'm sorry for not following your instructions, I did understood what you wrote. I just thought that I'm gonna test them together first, and if I get any errors, i'll test them again separately. Probably it was bad thinking on my end, but i'm like 95% sure the RAMs are OK. Since I ran multiple tests, all without any errors. Also I took the GPU today to a local store, they said it's 90%-95% the GPU's faulty.