Question Multiple bluescreens for the past 6 months

Qsirp · Jun 3, 2020

Hi,
I made my own pc about 9 months ago and everything worked perfectly, after a month or so I started getting a BSOD, with the stop code 'IRQL_NOT_LESS_OR_EQUAL.
Then after that came the BSOD'S: System thread exception not handled and kmode exception not handled.

Now more then 6 months further and I'm still getting bluescreens, I feel like I've tried everything. Installed new ram, new SSD, updated all my driver, fresh windows install and searched on so many websites to try and find a fix. Now finally I've come here to ask help from anyone who maybe has any clue to what it could be.

System:
Motherboard: MSI X570 Carbon wifi
GPU: RTX 2070 super
CPU: Ryzen 5 3600
Ram: 32 GB Corsair Vengeance 3000 mhz XMP profile with 15 cas latency
Storage: adata xpg sx8200 pro (m.2 SSD) 3TB Toshiba harddrive.
Cooling: Cooler Master Masterliquid 240L
Power supply: Cooler Master MWE Gold 750W Full Modular.
Case: Thermaltake Level 20 MT (for whatever reason anyone might wanna know)

Dump files:
https://drive.google.com/drive/folders/1cMADfZ2YIbDsLn_1Arkb52VldNNNpQYM?usp=sharing

These are only a few crashes I've had. Most of them disappeared because of fresh windows installs.

Crash List

Created by using BlueScreenView

��

Dump File	Crash Time	Bug Check String	Bug Check Code	Parameter 1	Parameter 2	Parameter 3	Parameter 4	Company	File Version	Stack Address 3	Computer Name	Full Path	Processors Count	Major Version	Minor Version
060220-12250-01.dmp	6/2/2020 5:35:01 PM		0x00000139	00000000`00000003[/TD] [TD]fffff588`c9c378a0	fffff588`c9c377f8[/TD] [TD]00000000`00000000	ntoskrnl.exe	ntoskrnl.exe+1c2390	x64	ntoskrnl.exe+1c2390	C:\Windows\Minidump\060220-12250-01.dmp	12	15	18362	761,597	6/2/2020 5:35:40 PM
060220-11859-01.dmp	6/2/2020 6:29:34 PM	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000`00000000[/TD] [TD]00000000`000000ff	00000000`00000000[/TD] [TD]fffff801`3b14980b	ntoskrnl.exe	ntoskrnl.exe+1c2390	x64	ntoskrnl.exe+1c2390	C:\Windows\Minidump\060220-11859-01.dmp	12	15	18362	737,575	6/2/2020 6:30:13 PM
060320-12500-01.dmp	6/3/2020 12:25:24 PM	KMODE_EXCEPTION_NOT_HANDLED	0x0000001e	ffffffff`c0000005[/TD] [TD]00000000`00000000	00000000`00000008[/TD] [TD]00000000`00000000	ntoskrnl.exe	ntoskrnl.exe+1c2390	x64	ntoskrnl.exe+1c2390	C:\Windows\Minidump\060320-12500-01.dmp	12	15	18362	1,388,209	6/3/2020 12:26:09 PM
060320-12062-01.dmp	6/3/2020 4:08:43 PM	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000`000001f0[/TD] [TD]00000000`000000ff	00000000`000000cb[/TD] [TD]fffff805`152bed64	ntoskrnl.exe	ntoskrnl.exe+1c2390	x64	ntoskrnl.exe+1c2390	C:\Windows\Minidump\060320-12062-01.dmp	12	15	18362	1,675,699	6/3/2020 4:09:26 PM
060320-12250-01.dmp	6/3/2020 5:00:00 PM	IRQL_NOT_LESS_OR_EQUAL	0x0000000a	00000000`0000028c[/TD] [TD]00000000`00000002	00000000`00000000[/TD] [TD]fffff801`7f82e198	ntoskrnl.exe	ntoskrnl.exe+1c2390	x64	ntoskrnl.exe+1c2390	C:\Windows\Minidump\060320-12250-01.dmp	12	15	18362	703,591	6/3/2020 5:00:45 PM

I hope I've provided enough information and it would be amazing if anyone will be able to help me solve this issue.

Qsirp · Jun 8, 2020

Colif said:
8192MB 3000MHz Unknown CMK16GX4M2D3000C16
8192MB 3000MHz Unknown CMK16GX4M2B3000C15
8192MB 3000MHz Unknown CMK16GX4M2D3000C16
8192MB 3000MHz Unknown CMK16GX4M2B3000C15

seems your sets weren't exactly the same after all. their latency is difference (C15 vs C16).
Rest of codes can change over time, but the C is a constant.

Running 16 cas ram at 15 in XMP is going to cause errors
Do you change bios settings when running the sticks in different slots? It should work for the old sticks though?

They may not entire problem but it doesn't help trying to get both working together. None of the dumps mention any drivers though, even the IRQ errors which should.

Oh wow, I didn’t expect that. So what should i do? Just remove one pair of sticks and just run 1 pair?

Qsirp · Jun 8, 2020

gardenman said:
I wasn't notified there was new replies in this thread or I would have got to this sooner. I ran the dump files through the debugger and got the following information: https://appellatemalayancivet.htmlpasta.com/

File information: 060320-12500-01.dmp (Jun 3 2020 - 06:25:24)
Bugcheck: KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by: ntkrnlmp.exe (Process: steam.exe)
Uptime: 0 Day(s), 16 Hour(s), 23 Min(s), and 30 Sec(s)

File information: 060320-12250-01.dmp (Jun 3 2020 - 11:00:00)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: memory_corruption (Process: LEDKeeper2.exe)
Uptime: 0 Day(s), 0 Hour(s), 50 Min(s), and 43 Sec(s)

File information: 060320-12062-01.dmp (Jun 3 2020 - 10:08:43)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 3 Hour(s), 42 Min(s), and 43 Sec(s)

File information: 060220-12250-01.dmp (Jun 2 2020 - 11:35:01)
Bugcheck: KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 06 Min(s), and 12 Sec(s)

File information: 060220-11859-01.dmp (Jun 2 2020 - 12:29:34)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 54 Min(s), and 04 Sec(s)

Comment: 2 or more types of RAM are installed.

Comment: The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner or other MSI software)

Possible Motherboard page: https://www.msi.com/Motherboard/MPG-X570-GAMING-PRO-CARBON-WIFI
You are using the latest BIOS already, version 1.72 BETA.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Thank you for looking into all this, i hope this will help myself and other people find out what’s the problem

Colif · Jun 8, 2020

i would run just 1 pair, which is up to you but make sure they are matching set.

i think both sets should work with motherboard. I already found the one set on MB list and CMK16GX4M2C3000C16 is on the listing from Gigabyte and only difference between yours at it is the C before 3000 is a D on your ram, same ram family, newer year.

They just may not work well together

Qsirp · Jun 8, 2020

Colif said:
i would run just 1 pair, which is up to you but make sure they are matching set.

i think both sets should work with motherboard. I already found the one set on MB list and CMK16GX4M2C3000C16 is on the listing from Gigabyte and only difference between yours at it is the C before 3000 is a D on your ram, same ram family, newer year.

They just may not work well together

I have put in the one pair of ram sticks, hope a few bluescreens go away now. The dumb part about all this, is that I've had bluescreens before I even bought the second pair of ram sticks, so it's probably not over yet

Colif · Jun 8, 2020

perhaps not but we may get less unexplainable ones (can always hope)

Qsirp · Jun 9, 2020

Update:
I have some new bluescreens with some new causes like: Win32kbase.sys and win32kfull.sys. Maybe something new to look at.
https://drive.google.com/drive/folders/1qNOiGCpB61Lpqy3xMPfKvGZNGe3Y9a1C?usp=sharing

Colif · Jun 9, 2020

both drivers are part of windows kernel.

I wonder if its the GPU drives (he says, knowing Nvidia drivers are always a possibility), you do have April drivers, there are May ones but they aren't much better. You would think Nvidia could get drivers to work with a 2070

I often see win32kfull.sys crash with GPU drivers. One of these days I will work out what the name means.

I should wait and see

gardenman · Jun 9, 2020

I ran the dump files through the debugger and got the following information: https://milliaryirishsetter.htmlpasta.com/

File information:	060920-8921-01.dmp (Jun 9 2020 - 07:02:25)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	ntkrnlmp.exe (Process: LEDKeeper2.exe)
Uptime:	0 Day(s), 13 Hour(s), 52 Min(s), and 10 Sec(s)

File information:	060820-9031-01.dmp (Jun 8 2020 - 17:09:39)
Bugcheck:	APC_INDEX_MISMATCH (1)
Probably caused by:	ntkrnlmp.exe (Process: nvsphelper64.e)
Uptime:	0 Day(s), 3 Hour(s), 18 Min(s), and 15 Sec(s)

File information:	060820-8937-01.dmp (Jun 8 2020 - 10:21:04)
Bugcheck:	BAD_OBJECT_HEADER (189)
Probably caused by:	ntkrnlmp.exe (Process: VoiceControlEn)
Uptime:	0 Day(s), 1 Hour(s), 14 Min(s), and 10 Sec(s)

File information:	060720-9296-01.dmp (Jun 7 2020 - 09:43:59)
Bugcheck:	KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
Probably caused by:	win32kbase.sys (Process: Taskmgr.exe)
Uptime:	0 Day(s), 0 Hour(s), 12 Min(s), and 31 Sec(s)

File information:	060720-9109-01.dmp (Jun 7 2020 - 09:30:58)
Bugcheck:	APC_INDEX_MISMATCH (1)
Probably caused by:	ntkrnlmp.exe (Process: MRT.exe)
Uptime:	0 Day(s), 1 Hour(s), 31 Min(s), and 55 Sec(s)

For some reason my software still flagged these dumps as having 2 different types of RAM. It might be because some of the crashes happened while they different types of RAM were installed, then they were removed for other crashes.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Qsirp · Jun 9, 2020

Another update:

Just uninstalled GPU drivers using ddu, and installed new drivers, for now the new drivers are the latest version, If the bsod's continue i'll try using an older version. But for now no problems still.

Qsirp · Jun 9, 2020

gardenman said:
I ran the dump files through the debugger and got the following information: https://milliaryirishsetter.htmlpasta.com/

File information: 060920-8921-01.dmp (Jun 9 2020 - 07:02:25)
Bugcheck: DPC_WATCHDOG_VIOLATION (133)
Probably caused by: ntkrnlmp.exe (Process: LEDKeeper2.exe)
Uptime: 0 Day(s), 13 Hour(s), 52 Min(s), and 10 Sec(s)

File information: 060820-9031-01.dmp (Jun 8 2020 - 17:09:39)
Bugcheck: APC_INDEX_MISMATCH (1)
Probably caused by: ntkrnlmp.exe (Process: nvsphelper64.e)
Uptime: 0 Day(s), 3 Hour(s), 18 Min(s), and 15 Sec(s)

File information: 060820-8937-01.dmp (Jun 8 2020 - 10:21:04)
Bugcheck: BAD_OBJECT_HEADER (189)
Probably caused by: ntkrnlmp.exe (Process: VoiceControlEn)
Uptime: 0 Day(s), 1 Hour(s), 14 Min(s), and 10 Sec(s)

File information: 060720-9296-01.dmp (Jun 7 2020 - 09:43:59)
Bugcheck: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
Probably caused by: win32kbase.sys (Process: Taskmgr.exe)
Uptime: 0 Day(s), 0 Hour(s), 12 Min(s), and 31 Sec(s)

File information: 060720-9109-01.dmp (Jun 7 2020 - 09:30:58)
Bugcheck: APC_INDEX_MISMATCH (1)
Probably caused by: ntkrnlmp.exe (Process: MRT.exe)
Uptime: 0 Day(s), 1 Hour(s), 31 Min(s), and 55 Sec(s)

For some reason my software still flagged these dumps as having 2 different types of RAM. It might be because some of the crashes happened while they different types of RAM were installed, then they were removed for other crashes.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

If I recall correctly, LEDKeeper2.exe is a program from the MSI Dragon Center for the RGB in my system.

nvsphelper64.exe is the nvidia shadowplay helper, It should fix this error by installing new graphics drivers and not installing geforce experience, so i should not get this error anymore.

the VoiceControlEn process could also be the MSI Dragon Center because that has a function to use my voice to set a certain RGB color, It is turned off though in MSI Dragon Center so that's weird.

taskmgr.exe is well, the taskmanager from windows, no clue why that's the process that caused my pc to bluescreen.

MRT.exe is the microsoft removal tool, also have no clue why that is the process that caused the bluescreen.

While making this post my pc bluescreened once again, this time the bugcheck was: Kernel_Lock_Entry_Leaked_On_Thread_Termination. From my research this bluescreen is caused by

outdated windows version (I have no pending windows updates so can't be it)
outdated drivers (this seems to be a recurring factor in all the bluescreens I've had)
Malware (Can't be the problem because of fresh windows installs)
Malfunction of third party app (possibility)
Corrupt hard drive (quite sure this isn't the case because I've not had any problems with my hard drive and I even bought a new one because I thought at first it was my hard drive that had broken.)
fault in system files (which it probably isn't because of the multiple fresh windows installs)

I'm just trying to pinpoint what is the problem here. Hope you guys may have some input on this.

Colif · Jun 9, 2020

You are looking at what crashed in those cases, perhaps not cause (apart from Nvidia one which shows my guess was right)
BSOD always says what crashed in that header, only rarely does it show the actual driver name

nvidia caused 2, and 4
it could all be Nvidia, as the other 3 aren't so obvious

running a beta bios, living on the edge
chipset drivers here seem newer than whats installed - https://www.msi.com/Motherboard/support/MPG-X570-GAMING-PRO-CARBON-WIFI#down-driver&Win10 64 though maybe its right, the difference is only 2 weeks

what pc thinks are overclocking drivers are just the update drivers for Dragon Centre. I am not sure what would cause dragon centre to crash either. Curiously Dragon Centre was updated yesterday - its on utility tab of above. Probably won't help but you never know.

Colif · Jun 9, 2020

gardenman said:
For some reason my software still flagged these dumps as having 2 different types of RAM. It might be because some of the crashes happened while they different types of RAM were installed, then they were removed for other crashes.

That is odd then as if I look at https://milliaryirishsetter.htmlpasta.com/# its only showing 2 sticks of the same type (as it should be) CMK16GX4M2B3000C15 so the problem might be your end?

that is one cute dangerous dog that link brings to mind

gardenman · Jun 9, 2020

I just looked and it was as I suspected. The first crash (Dump #5) happened when both types of RAM were still installed. The same for Dump #4.

Dumps are listed from newest to oldest.

Part of BIOS info for Dump #5:

[Memory Device (Type 17) - Length 40 - Handle 001ah]
Physical Memory Array Handle 000fh
Memory Error Info Handle 0019h
Total Width 64 bits
Data Width 64 bits
Size 8192MB
Form Factor 09h - DIMM
Device Locator DIMM 1
Bank Locator P0 CHANNEL A
Memory Type 1ah - Specification Reserved
Type Detail 4080h - Synchronous
Speed 3000MHz
Manufacturer Unknown
Part Number CMK16GX4M2B3000C15
...
[Memory Device (Type 17) - Length 40 - Handle 001dh]
Physical Memory Array Handle 000fh
Memory Error Info Handle 001ch
Total Width 64 bits
Data Width 64 bits
Size 8192MB
Form Factor 09h - DIMM
Device Locator DIMM 0
Bank Locator P0 CHANNEL B
Memory Type 1ah - Specification Reserved
Type Detail 4080h - Synchronous
Speed 3000MHz
Manufacturer Unknown
Part Number CMK16GX4M2D3000C16

Two different part numbers.

Colif · Jun 10, 2020

Now I can't tell if he had right ram in at any stage. What dump normally creates the system info screen?

How many of those crashes happened after I showed you that 2 sticks were wrong. By my calculation all of them except last one should have 4 sticks in them, not 2. I didn't tell you about the 2 different sets until just after the 2nd BSOD above happened.

Its not normal for the ram sticks to change between crashes so it isn't something the program is set up to check for. Almost need the system info to show for each dump? or maybe a note?

I don't actually get why dump 5 only showed 2 sticks as I hadn't told op to remove 2 at that stage?

because of confusion I have about sticks, I don't know if Nvidia are to blame for some of them or not.

Qsirp · Jun 10, 2020

Colif said:
How many of those crashes happened after I showed you that 2 sticks were wrong. By my calculation all of them except last one should have 4 sticks in them, not 2. I didn't tell you about the 2 different sets until just after the 2nd BSOD above happened.

I think 2 or 3 of them were after I put just the one pair of ram sticks in.

Qsirp · Jun 10, 2020

I just got a bluescreen saying Driver_Irql_not_less_or_equal with the bsod telling me what crashed. the program that crashed was wdf01000.sys. Here is the link to that dumpfile:
https://drive.google.com/drive/folders/1LUpbjufRjSQdV9Pfv_dYlE9UGLPGR8ov?usp=sharing

Qsirp · Jun 10, 2020

The bluescreens didn't stop after uninstalling gpu drivers using ddu, and updating drivers. Anything i should do next?

gardenman · Jun 10, 2020

Colif said:
What dump normally creates the system info screen?

I'll have to look into that... it's been a while since I've done the programming. But I would think that it looks through any/all BIOS sections for RAM info that is shown in the System Info page. The reason for this is that not every dump has a BIOS section, so if I look only at the newest dump, it may not have BIOS info then there would be no System Info for all of the remaining dumps. Anyway, always look at the BIOS info from the top/most dump on the page.

Colif said:
I don't actually get why dump 5 only showed 2 sticks as I hadn't told op to remove 2 at that stage?

In the previous dump readings, Dumps 1, 2, and 3 only had 1 set of RAM modules. Dumps 4 and 5 (the older ones) had both sets of RAM.

Results for new dump file: https://wackierrubber.htmlpasta.com/

File information:	061020-9015-01.dmp (Jun 10 2020 - 09:02:31)
Bugcheck:	DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Probably caused by:	memory_corruption (Process: steam.exe)
Uptime:	0 Day(s), 0 Hour(s), 43 Min(s), and 02 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Colif · Jun 11, 2020

Wdf01000 = windows driver framework (https://en.wikipedia.org/wiki/Windows_Driver_Frameworks )
XINPUT filter driver for HID by Microsoft Corporation (HID = Human Interface devices) - this seems to be a HID Non user input filter driver... mystery deepens

only 2 "drivers" that show in stack text but both are parts of windows. I don't know what it was doing at time? I had to look up xinput, sounds like its for a button press?

Xbox controller? https://docs.microsoft.com/en-us/windows/win32/xinput/xinput-versions

Xbox controller drivers built into win 10, explains lack of drivers showing.

So why did Xbox controller cause steam to crash ¿?

what does the MSI gaming app do?

Did you run this?
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

as maybe running 2 different types of ram has corrupted some files.

Qsirp · Jun 11, 2020

Colif said:
So why did Xbox controller cause steam to crash ¿?

Maybe it was because I was playing a steam game with my Xbox controller, but it's weird because I have never had any BSOD's while playing games, only after I play and stop or while I'm on the internet.

Qsirp · Jun 11, 2020

Colif said:
Did you run this?
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

I only ran that command via cmd not windows powershell, I'm trying that right now!

Colif · Jun 11, 2020

according to the last IRQ error it crashed Steam.

its the same thing, I only showed power shell as in most win 10, powershell replaced CMD in that menu.

Qsirp · Jun 11, 2020

Colif said:
according to the last IRQ error it crashed Steam.

its the same thing, I only showed power shell as in most win 10, powershell replaced CMD in that menu.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6 PS C:\WINDOWS\system32> SFC /scannow Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> Repair-WindowsImage -Online -RestoreHealth

Path :
Online : True
ImageHealthState : Healthy
RestartNeeded : False

This is the outcome of the sfc scan and the restore health, I believe it didn't do much.

Colif · Jun 11, 2020

Well, it thinks the files are okay.

Guess we wait for next BSOD as see if it is more helpful.

Qsirp · Jun 11, 2020

Colif said:
Well, it thinks the files are okay.

Guess we wait for next BSOD as see if it is more helpful.

I've put you guys up to quite the challenge haven't I? xD

8192MB	3000MHz	Unknown	CMK16GX4M2D3000C16
8192MB	3000MHz	Unknown	CMK16GX4M2B3000C15
8192MB	3000MHz	Unknown	CMK16GX4M2D3000C16
8192MB	3000MHz	Unknown	CMK16GX4M2B3000C15

File information:	060320-12500-01.dmp (Jun 3 2020 - 06:25:24)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	ntkrnlmp.exe (Process: steam.exe)
Uptime:	0 Day(s), 16 Hour(s), 23 Min(s), and 30 Sec(s)

File information:	060320-12250-01.dmp (Jun 3 2020 - 11:00:00)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: LEDKeeper2.exe)
Uptime:	0 Day(s), 0 Hour(s), 50 Min(s), and 43 Sec(s)

File information:	060320-12062-01.dmp (Jun 3 2020 - 10:08:43)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 3 Hour(s), 42 Min(s), and 43 Sec(s)

File information:	060220-12250-01.dmp (Jun 2 2020 - 11:35:01)
Bugcheck:	KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:	ntkrnlmp.exe (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 06 Min(s), and 12 Sec(s)

File information:	060220-11859-01.dmp (Jun 2 2020 - 12:29:34)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 54 Min(s), and 04 Sec(s)

Question Multiple bluescreens for the past 6 months

Commendable

Commendable

Commendable

Win 11 Master

Commendable

Win 11 Master

Commendable

Win 11 Master

Splendid

Commendable

Commendable

Win 11 Master

Win 11 Master

Splendid

Win 11 Master

Commendable

Commendable

Commendable

Splendid

Win 11 Master

Commendable

Commendable

Win 11 Master

Commendable

Win 11 Master

Commendable

Share this page