Solved Windows 11 nightmare - Randomly crashing on new-build

TCWindows · Mar 8, 2022

PROBLEMS/SYMPTOMS: Windows 11 randomly crashing just prior to login screen and sometimes on Wake-Up - Shows black screen and no response. The monitor then goes into sleep-mode.

Windows and Hardware Specs
Edition Windows 11 Pro
Version 21H2
Installed on ‎10/‎12/‎2021
OS build 22000.493
Experience Windows Feature Experience Pack 1000.22000.493.0

AMD Ryzen 5 5600G 3.9GHz Hexa Core
AM4 CPU Cooler Master Hyper 212 RGB Black Edition
MSI B550M PRO-VDH WIFI mATX Motherboard
Corsair CX650F RGB, 80 PLUS Bronze Fully Modular ATX Power Supply
Samsung 980 1 TB PCIe 3.0 (up to 3.500 MB/s) NVMe M.2
Crucial Ballistix RGB BL2K8G32C16U4BL 3200 MHz, DDR4, DRAM (32GB)
DEEPCOOL MACUBE 310, White, Mid Tower Chassis w/ Tempered Glass Window
CF120 PLUS 3-in-1 120mm 18 A-R
HP x34 Ultrawide Screen Monitor

Hello everyone,

Thank you for a great forum. This is my first post, so please forgive me if I miss anything out, but I will do my utmost to provide as much info as possible to help you to assist me.

I have build the above spec pc and installed Windows 11 Pro. Additionally, I also kept my old Microsoft keyboard, mouse and 2 hdds (3tb seagate and 500gb crucial ssd).

Most of the time my PC works fine. I never have any issues such as crashes whilst it's in use. However, once every 5-10 reboots, Windows loads up to the point where it's supposed to show the login screen, but instead I'm shown a black screen + monitor eventually goes to sleep mode and I can't do anything other than to manually reset the PC. The other issue is that once every 5-10 times when I put the pc to sleep, it doesn't wake-up. Again I'm faced with a black screen and I can't do anything other than to manually reset the PC.

One other problem I have noticed is that some websites are showing corrupt banners and or video, like this one here:

As part of my diagnosis and a process of elimination, I have done the following already:-

Removed all old devices and hard drives.
Changed HDMI/Display cables.
Updated Windows
Updated AMD video card drivers via either MSI website or AMD's website.
Updated MSI BIOS to latest version.

My suspicion is that the problem is with corrupt or incompatible drivers of the integrated video card, but I've already tried factory-resetting and reinstalling the drivers, but this has not helped at all I can't seem to fix it, so I'm hoping an expert can give me any tips.

Reliability Monitor:

I have attached LOG OUTPUT to this thread.

Thanks for your help in advance.

philc43 · Mar 8, 2022

Do you still get these crashes if you restart in safe mode?

Boot to Safe Mode in Windows 11

This tutorial will show you how to boot Windows 11 into normal mode, Safe Mode, Safe Mode with Networking, or Safe Mode with Command Prompt. Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default...

www.elevenforum.com

philc43 · Mar 8, 2022

There are no BSOD crash dumps created which is not surprising when the crashes seem to occur so soon in the boot process.

What I do see are lots of live kernel dumps

Code:

LastWriteTime       Size (MB) FullName                                                       
-------------       --------- --------                                                       
16/12/2021 16:01:46   4842.65 C:\Windows\LiveKernelReports\WATCHDOG-20211216-1601.dmp         
26/12/2021 16:20:06      0.25 C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20211226-1620.dmp 
13/02/2022 10:23:51      0.25 C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20220213-1023.dmp 
20/12/2021 16:11:21      0.25 C:\Windows\LiveKernelReports\USBXHCI\USBXHCI-20211220-1611.dmp 
13/12/2021 09:26:07      0.35 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211213-0926.dmp
13/12/2021 14:04:05      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211213-1404.dmp
14/12/2021 20:11:28      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211214-2011.dmp
16/12/2021 20:08:02      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211216-2008.dmp
16/12/2021 20:09:09      0.25 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211216-2009.dmp
17/12/2021 08:33:33      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211217-0833.dmp
19/12/2021 10:43:50      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211219-1043.dmp
19/12/2021 10:44:00      0.35 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211219-1044.dmp
19/12/2021 23:36:01      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211219-2336.dmp
20/12/2021 21:53:41      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211220-2153.dmp
20/12/2021 21:54:01      0.35 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211220-2154.dmp
20/12/2021 22:02:34      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211220-2202.dmp
25/12/2021 11:45:48      0.35 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211225-1145.dmp
26/12/2021 12:35:48      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211226-1235.dmp
28/12/2021 14:04:37      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211228-1404.dmp
28/12/2021 14:05:36      0.25 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211228-1405.dmp
28/12/2021 14:06:03      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211228-1406.dmp
29/12/2021 13:04:36      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211229-1304.dmp
30/12/2021 13:54:09      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211230-1354.dmp
30/12/2021 13:55:01      0.36 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211230-1355.dmp
02/01/2022 12:36:04      0.25 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220102-1236.dmp
09/01/2022 13:56:16      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220109-1356.dmp
10/01/2022 13:57:53      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220110-1357.dmp
15/01/2022 10:04:28      0.35 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220115-1004.dmp
17/01/2022 08:17:35      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220117-0817.dmp
17/01/2022 18:08:55      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220117-1808.dmp
17/01/2022 18:09:09      0.35 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220117-1809.dmp
19/01/2022 08:08:44      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220119-0808.dmp
20/01/2022 08:54:01      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220120-0854.dmp
30/01/2022 12:30:46      0.36 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220130-1230.dmp
30/01/2022 12:31:10      0.25 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220130-1231.dmp
31/01/2022 08:17:05      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220131-0817.dmp
03/02/2022 19:03:38      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220203-1903.dmp
08/02/2022 09:53:34      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220208-0953.dmp
08/02/2022 12:04:16      0.35 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220208-1204.dmp
20/02/2022 13:45:42      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220220-1345.dmp
21/02/2022 18:25:26      0.34 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220221-1825.dmp

Do you think you could copy the LiveKernelReports folder to your desktop, zip it and share it via OneDrive or Dropbox. These might give some clues as to what is going on.

philc43 · Mar 8, 2022

My other concern is that you may not have your memory inserted in the correct slots, all four are not identical and therefore it is important that the matched pairs are inserted correctly. Match one pair in slots 2 and 4, match the other pair in slots 1 and 3.

TCWindows · Mar 8, 2022

Hi @philc43.

Thank you so much for your prompt reply and help. I am very grateful for your advise.

I'm in the process of zipping and uploading the Livekernels folder, but it's almost 5gb, so allow me to get this uploaded and shared with you asap.

The issue is that I haven't been able to test this scenario in safe mode because when I go to safemode, it says I have no ethernet/wlan connections to use to be able to connect to the net. Also since the issue happens prior to logging in, would safemode make a difference?

Forgive me, I'm not sure how I've got the memory wrong because there are 4 x 8gb dimms (all are the same brand and spec), so how do I know which order they should to be in?

Thank you.

zbook · Mar 8, 2022

Was the disk drive troubleshooted or replaced in February?

Please run:

Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.

Gather_additional_dump_files.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.

Samsun Magician:

Samsung Magician Software Download | Samsung Semiconductor Global

Samsung Magician software is designed to help you manage your Samsung SSD with a simple, intuitive user interface. Download files & find supported models.

semiconductor.samsung.com

Post images or share links for results on these tabs:
a) Drive details
b) Update software /firmware
c) Diagnostic scan > full scan
d) Performance benchmark
e) Over provisioning
f) Performance optimization

Code:

Event[4469]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 821 operation 0 status c0000225.

Event[4470]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 762 operation 0 status c0000225.

Event[4471]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 24 operation 0 status c0000225.

Event[4472]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 81f operation 0 status c0000225.

Event[4473]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 33 operation 0 status c0000225.

Event[4474]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 33 operation 0 status c0000225.

Event[4475]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 33 operation 0 status c0000225.

Event[4476]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 73 operation 0 status c0000225.

Event[4477]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector b3 operation 0 status c0000225.

Event[4478]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector f3 operation 0 status c0000225.

Event[4479]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 133 operation 0 status c0000225.

Event[4480]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 173 operation 0 status c0000225.

Event[4481]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 1b3 operation 0 status c0000225.

Event[4482]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 1f3 operation 0 status c0000225.

Event[4483]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 233 operation 0 status c0000225.

Event[4484]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 273 operation 0 status c0000225.

Event[4485]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 2b3 operation 0 status c0000225.

Event[4486]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 2f3 operation 0 status c0000225.

Event[4487]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 333 operation 0 status c0000225.

Event[4488]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 373 operation 0 status c0000225.

Event[4489]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 3b3 operation 0 status c0000225.

Event[4490]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 3f3 operation 0 status c0000225.

Event[4491]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 433 operation 0 status c0000225.

Event[4492]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 473 operation 0 status c0000225.

Event[4493]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 4b3 operation 0 status c0000225.

Event[4494]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 4f3 operation 0 status c0000225.

Event[4495]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 533 operation 0 status c0000225.

Event[4496]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 573 operation 0 status c0000225.

Event[4497]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 5b3 operation 0 status c0000225.

Event[4498]
  Log Name: System
  Source: volmgr
  Date: 2022-02-13T10:23:24.9280000Z
  Event ID: 2
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: RGB-DESKTOP-PC
  Description:
Failed to read KSR data - disk 0 sector 5f3 operation 0 status c0000225.

TCWindows · Mar 8, 2022

Hi @zbook and thank you for helping me. What disk drive are you referring to?

Just to be clear, for diagnosis purposes, I have removed all old drives and I'm only using the Samsung 1tb nvme which is brand-new.

philc43 · Mar 8, 2022

You could leave out the live kernel dump dated 16/12/21 - that will reduce the size dramatically.

The RAM modules are listed as follows:

Code:

Location     : DIMM 0
BankLabel    : P0 CHANNEL A
Manufacturer : Unknown
MemoryType   : DDR4
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 3200
Serial       : E5FB50B5
PartNumber   : BL8G32C16U4BL.8FE
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Location     : DIMM 1
BankLabel    : P0 CHANNEL A
Manufacturer : Unknown
MemoryType   : DDR4
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 3200
Serial       : E5EDED39
PartNumber   : BL8G32C16U4BL.M8FE
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Location     : DIMM 0
BankLabel    : P0 CHANNEL B
Manufacturer : Unknown
MemoryType   : DDR4
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 3200
Serial       : E5EDF32E
PartNumber   : BL8G32C16U4BL.M8FE
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Location     : DIMM 1
BankLabel    : P0 CHANNEL B
Manufacturer : Unknown
MemoryType   : DDR4
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 3200
Serial       : E5FB5BC4
PartNumber   : BL8G32C16U4BL.8FE
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Based on the part numbers I would suggest they might be very slightly different. I would swap slots 3 and 4 over to see if it makes a difference.

TCWindows · Mar 8, 2022

philc43 said:

You could leave out the live kernel dump dated 16/12/21 - that will reduce the size dramatically.

The RAM modules are listed as follows:

Code:

Location     : DIMM 0
BankLabel    : P0 CHANNEL A
Manufacturer : Unknown
MemoryType   : DDR4
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 3200
Serial       : E5FB50B5
PartNumber   : BL8G32C16U4BL.8FE
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Location     : DIMM 1
BankLabel    : P0 CHANNEL A
Manufacturer : Unknown
MemoryType   : DDR4
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 3200
Serial       : E5EDED39
PartNumber   : BL8G32C16U4BL.M8FE
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Location     : DIMM 0
BankLabel    : P0 CHANNEL B
Manufacturer : Unknown
MemoryType   : DDR4
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 3200
Serial       : E5EDF32E
PartNumber   : BL8G32C16U4BL.M8FE
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Location     : DIMM 1
BankLabel    : P0 CHANNEL B
Manufacturer : Unknown
MemoryType   : DDR4
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 3200
Serial       : E5FB5BC4
PartNumber   : BL8G32C16U4BL.8FE
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Based on the part numbers I would suggest they might be very slightly different. I would swap slots 3 and 4 over to see if it makes a difference.

Right, will do, thanks @philc43.

As per your request, I have uploaded the compressed Livekernel file (includes everything). You can find it HERE

philc43 · Mar 8, 2022

Thank you for the live kernel dumps - they are showing that there are a lot of graphics related issues - the watchdog series are all pointing to the graphics driver:

7: kd> lmvm amdkmdag
Browse full module list
start end module name
fffff805`66ca0000 fffff805`6b9bf000 amdkmdag T (no symbols)
Loaded symbol image file: amdkmdag.sys
Image path: amdkmdag.sys
Image name: amdkmdag.sys
Browse all global symbols functions data
Timestamp: Tue Oct 19 04:03:31 2021 (616E3583)
CheckSum: 04CD7064
ImageSize: 04D1F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0373652.INF_AMD64_97D024528A122D1A\B372726\AMDKMDAG.SYS (30.0.13023.1012, 76.81 MB (80,538,504 bytes), 12/11/2021 11:56)

Have you recently updated the graphics drivers? The bold date above indicates the last time the driver was updated on your system. I would think there might be some more recent ones from AMD. You may also find that Windows Update has some optional drivers for the graphics system that you can install.

TCWindows · Mar 8, 2022

philc43 said:
Thank you for the live kernel dumps - they are showing that there are a lot of graphics related issues - the watchdog series are all pointing to the graphics driver:

7: kd> lmvm amdkmdag
Browse full module list
start end module name
fffff805`66ca0000 fffff805`6b9bf000 amdkmdag T (no symbols)
Loaded symbol image file: amdkmdag.sys
Image path: amdkmdag.sys
Image name: amdkmdag.sys
Browse all global symbols functions data
Timestamp: Tue Oct 19 04:03:31 2021 (616E3583)
CheckSum: 04CD7064
ImageSize: 04D1F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0373652.INF_AMD64_97D024528A122D1A\B372726\AMDKMDAG.SYS (30.0.13023.1012, 76.81 MB (80,538,504 bytes), 12/11/2021 11:56)

Have you recently updated the graphics drivers? The bold date above indicates the last time the driver was updated on your system. I would think there might be some more recent ones from AMD. You may also find that Windows Update has some optional drivers for the graphics system that you can install.

Thanks so much phil. Yes, I've also been suspecting that it's something related to graphics. That date 12/11/2021 can't be right because I've updated my graphics drivers multiple times since that date. In fact only today Windows 11 did an update for the AMD drivers, although this hasn't made a difference:

I've even tried uninstalling, resetting drivers, installing from MSI, AMD websites, but no difference.

zbook · Mar 8, 2022

TCWindows said:
Hi @zbook and thank you for helping me. What disk drive are you referring to?

Just to be clear, for diagnosis purposes, I have removed all old drives and I'm only using the Samsung 1tb nvme which is brand-new.

The disk errors were reported on or before 2/13/2022.

With drive replacement that should no longer be important.

Open administrative command prompt and type or copy and paste:
powercfg -h off

Hibernation can be restarted after the troubleshooting has completed using:

powercfg -h on

Consider running Windows Driver Verifier (WDV) to rule in / out misbehaving drivers.

Code:

Event[27293]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2022-03-03T09:36:15.7800000Z
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: RGB-DESKTOP-PC
  Description:
Windows failed to resume from hibernate with error status 0xC0000411.

Code:

Event[7174]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2022-02-14T10:24:13.7680000Z
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: RGB-DESKTOP-PC
  Description:
Windows failed fast startup with error status 0xC00000D4.

TCWindows · Mar 8, 2022

zbook said:
The disk errors were reported on or before 2/13/2022.

With drive replacement that should no longer be important.

Open administrative command prompt and type or copy and paste:
powercfg -h off

Hibernation can be restarted after the troubleshooting has completed using:

powercfg -h on

Consider running Windows Driver Verifier (WDV) to rule in / out misbehaving drivers.

Code:

Event[27293] Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2022-03-03T09:36:15.7800000Z Event ID: 16 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: RGB-DESKTOP-PC Description: Windows failed to resume from hibernate with error status 0xC0000411.

Code:

Event[7174] Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2022-02-14T10:24:13.7680000Z Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: RGB-DESKTOP-PC Description: Windows failed fast startup with error status 0xC00000D4.

Thanks zbook. I've disabled hibernate, but I remember trying the WDV a while ago and if I remember correctly, it crashed the system.

philc43 · Mar 8, 2022

TCWindows said:
Thanks so much phil. Yes, I've also been suspecting that it's something related to graphics. That date 12/11/2021 can't be right because I've updated my graphics drivers multiple times since that date. In fact only today Windows 11 did an update for the AMD drivers, although this hasn't made a difference:

View attachment 23735

I've even tried uninstalling, resetting drivers, installing from MSI, AMD websites, but no difference.

It looks like those updates have never in fact changed the graphics driver version - they have stayed the same: 30.0.13023.1012.

Here is AMDs latest (Windows Driver Store Version 30.0.14029.5006) : Latest AMD Radeon Graphics Driver for Windows 11

TCWindows · Mar 8, 2022

philc43 said:
It looks like those updates have never in fact changed the graphics driver version - they have stayed the same: 30.0.13023.1012.

Here is AMDs latest (Windows Driver Store Version 30.0.14029.5006) : Latest AMD Radeon Graphics Driver for Windows 11

Oh I see....that's very strange. Any suggestion how I can clear the old drivers and replace them in a fresh install with the new drivers?

philc43 · Mar 8, 2022

We recommend using DDU to uninstall all the old driver files.

www.wagnardsoft.com

Wagnardsoft: Computer PC Software tools. Home of Display Driver Uninstaller (DDU)

www.wagnardsoft.com

TCWindows · Mar 8, 2022

philc43 said:
We recommend using DDU to uninstall all the old driver files.

www.wagnardsoft.com

Wagnardsoft: Computer PC Software tools. Home of Display Driver Uninstaller (DDU)

www.wagnardsoft.com

Thank phil. I've followed the DDU instructions, rebooted in safe mode and ran DDU. Then I chose the recommended option which uninstalls the drivers and restarts the PC. On boot-up windows was on very low resolution, but after 30 seconds, it automatically switched to a higher resolution.

Then I've gone ahead and ran the radeon installer where I chose the 22.2.3. After install radeon is showing that I have updated to the following:

But that version does not match the one you posted: 30.0.14029.5006 and one of the website's graphics still shows a corrupted display.

philc43 · Mar 8, 2022

It is often a matter of trial and error until you find the right driver - the latest is not always the best but you have to go through the options available to you. I would also try the latest one on the motherboard website - 21.30.14

B550M PRO-VDH WIFI

Best AMD AM4 B550 MATX motherboard, lightning PCIe 4.0, lightning M.2, USB 3.2 Gen 1, M.2 heatsink, wifi AC, powerful overclocking, MSI PRO

www.msi.com

TCWindows · Mar 8, 2022

philc43 said:
It is often a matter of trial and error until you find the right driver - the latest is not always the best but you have to go through the options available to you. I would also try the latest one on the motherboard website - 21.30.14

B550M PRO-VDH WIFI

Best AMD AM4 B550 MATX motherboard, lightning PCIe 4.0, lightning M.2, USB 3.2 Gen 1, M.2 heatsink, wifi AC, powerful overclocking, MSI PRO

www.msi.com

Just allowed Windows to do it's direct update to 30.0.13023.4001, but display on some websites is still corrupt.

I'm now going to uninstall and try the MSI drivers instead. Will keep you posted.

TCWindows · Mar 8, 2022

So I've now uninstalled and fresh-installed the MSI drivers. I'm stilling having issues with a website display being corrupt, but I'm thinking it might be just that website, so I'm going to totally ignore that.

Having said that can you please tell me how I can check whether my drivers have now actually removed the old rubbish and are working correctly now? Where do I check?

Solved Windows 11 nightmare - Randomly crashing on new-build

Member

Attachments

My Computer

BSOD Analyst

My Computers

BSOD Analyst

My Computers

BSOD Analyst

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

BSOD Analyst

My Computers

Member

My Computer

BSOD Analyst

My Computers

Member

Attachments

My Computer

Well-known member

My Computer

Member

My Computer

BSOD Analyst

My Computers

Member

My Computer

BSOD Analyst

My Computers

Member

My Computer

BSOD Analyst

My Computers

Member

My Computer

Member

My Computer

Similar threads