BSOD on PC launch

[CalPet]

Hello,

I've been experiencing BSOD everytime when I first start my pc during the day. After the pc restarts I have no more BSOD. I'm able to play games normally without issue, except for one hard crash that occured while playing valheim which left no BSOD or crash file, that occured two weeks ago and has been the only time that has happened. I've disabled fast startup which seemed to help for one day but that introduced a new BSOD which came with error code 0xc0000221. Sometimes on first startup Im able to log in but then if I click on anything it will just BSOD. But after it relaunches I can go on without further issues.

SysnativeFileCollectionApp.zip

Case
PCS LUMIN ARGB MID TOWER CASE (PWM)
Processor (CPU)
AMD Ryzen 7 7800X3D Eight Core CPU (4.2GHz-5.0GHz/104MB w/3D V-CACHE/AM5)
Motherboard
ASUS® PRIME X670-P-CSM (AM5, DDR5, PCIe 4.0)
Memory (RAM)
32GB Corsair VENGEANCE DDR5 5600MHz (2 x 16GB)
Graphics Card
16GB NVIDIA GEFORCE RTX 4080 SUPER - HDMI, DP, LHR
1st M.2 SSD Drive
2TB SAMSUNG 980 PRO M.2, PCIe NVMe (up to 7000MB/R, 5000MB/W)
DVD/BLU-RAY Drive
NOT REQUIRED
Power Supply
CORSAIR 850W RMx SERIES™ MODULAR 80 PLUS® GOLD, ULTRA QUIET
Power Cable
1 x 1.5 Metre UK Power Cable (Kettle Lead, 1.0mm Core)
Processor Cooling
PCS FrostFlow 240 Series ARGB High Performance Liquid Cooler
Thermal Paste
STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Sound Card
ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Network Card
ONBOARD 2.5Gbe LAN PORT
Wireless Network Card
WIRELESS INTEL® Wi-Fi 6E AX210 2,400Mbps/5GHz, 300Mbps/2.4GHz PCI-E CARD + BT 5.0
USB/Thunderbolt Options
MIN. 2 x USB 3.0 & 2 x USB 2.0 PORTS @ BACK PANEL + MIN. 2 FRONT PORTS
Operating System
Windows 11 Home 64 Bit - inc. Single Licence
Operating System Language
United Kingdom - English Language
Windows Recovery Media
Windows 10/11 Multi-Language Recovery Image - Unlimited Downloads from Online Account
Office Software
FREE 30 Day Trial of Microsoft 365® (Operating System Required)
Anti-Virus
NO ANTI-VIRUS SOFTWARE
Browser
Microsoft® Edge

 

[SpyderTracks]

That error code you posted can relate to either a problematic SSD (if it's not quite seated correctly) or suspect RAM

May be worth uninstalling the SSD, just clean the contacts with a lint free cloth and reinstall it.

Worth doing the same with the RAM Sticks.

Also, would be worth running a Memtest86 pass to scan the RAM: https://www.memtest86.com/

@ubuysa is the BSOD doctor, he'll be able to look at the logs when he's free, but those things may be worth doing in the meantime.

 

[CalPet]

That error code you posted can relate to either a problematic SSD (if it's not quite seated correctly) or suspect RAM

May be worth uninstalling the SSD, just clean the contacts with a lint free cloth and reinstall it.

Worth doing the same with the RAM Sticks.

Also, would be worth running a Memtest86 pass to scan the RAM: https://www.memtest86.com/

@ubuysa is the BSOD doctor, he'll be able to look at the logs when he's free, but those things may be worth doing in the meantime.

Thanks for the quick response! Im not all the comfortable taking the ssd and ram off, I did a memtest86 when I first recieved my pc and it came back normal. But I can do another one tomorrow probably. Appreciate the help.

 

[ubuysa]

I agree that the 0xC0000221 is possibly the system drive - it's an IMAGE_CHECKSUM_MISMATCH exception. You might also want to upload some detailed troubleshooting data...

Can you please download and run the SysnativeBSODCollectionApp and upload the resultant zip file to a cloud service with a link to it here. Be sure to make it public (so we don't have to login to download the zip file).

The SysnativeBSODCollectionApp does not collect any personally identifying information, it's perfectly safe, and it#s used by several respected Windows help forums. You can look at the files in the zip file, mostly they are txt files, but please don't change or delete anything. If you want to know what data these files contain there are full details here.

 

[SpyderTracks]

I agree that the 0xC0000221 is possibly the system drive - it's an IMAGE_CHECKSUM_MISMATCH exception. You might also want to upload some detailed troubleshooting data...

Can you please download and run the SysnativeBSODCollectionApp and upload the resultant zip file to a cloud service with a link to it here. Be sure to make it public (so we don't have to login to download the zip file).

The SysnativeBSODCollectionApp does not collect any personally identifying information, it's perfectly safe, and it#s used by several respected Windows help forums. You can look at the files in the zip file, mostly they are txt files, but please don't change or delete anything. If you want to know what data these files contain there are full details here.

The sys native results are linked in the first post, just before the specs, it's 620kb though which seems on the small side, but not sure what it includes.

 

[ubuysa]

There is one BSOD in the logs but no dump was uploaded, are you running any kind of disk cleanup tool?....

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          06/05/2024 14:54:32
Event ID:      1001
Task Category: None
Level:         Error
Keywords:    
User:          SYSTEM
Computer:      TheDevice
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffffadfffff7ff80, 0x0000000000000002, 0x0000000000000000, 0xfffff8022c0ff2ec). A dump was saved in: C:\WINDOWS\Minidump\050624-7437-01.dmp. Report Id: 18c0743c-dcba-4308-bb23-a29198350364.

A 0xA bugcheck is the classic IRQL_NOT_LESS_OR_EQUAL, which is most usually a bad third-party driver. In this case however, there are also a few disk errors, making it more lilely that this is a flaky drive...

Log Name:      System
Source:        disk
Date:          05/05/2024 15:55:26
Event ID:      51
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      TheDevice
Description:
An error was detected on device \Device\Harddisk1\DR3 during a paging operation.

I would download Samsung Magician and run the maximal diagnostic you can on that drive. Also post the SMART data for it here too. It's worth checking for firmware and/or driver updates for the drive too. That's in addition to removing and reseating it.

One other common error running through the logs is this one...

Log Name:      System
Source:        Microsoft-Windows-TPM-WMI
Date:          06/05/2024 14:54:34
Event ID:      1796
Task Category: None
Level:         Error
Keywords:    
User:          SYSTEM
Computer:      TheDevice
Description:
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931

This particular error (1796) indicates that a failure occurred updating a SecureBoot variable, which might also gel with there being a system drive error.

 

[CalPet]

There is one BSOD in the logs but no dump was uploaded, are you running any kind of disk cleanup tool?....

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          06/05/2024 14:54:32
Event ID:      1001
Task Category: None
Level:         Error
Keywords:   
User:          SYSTEM
Computer:      TheDevice
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffffadfffff7ff80, 0x0000000000000002, 0x0000000000000000, 0xfffff8022c0ff2ec). A dump was saved in: C:\WINDOWS\Minidump\050624-7437-01.dmp. Report Id: 18c0743c-dcba-4308-bb23-a29198350364.

A 0xA bugcheck is the classic IRQL_NOT_LESS_OR_EQUAL, which is most usually a bad third-party driver. In this case however, there are also a few disk errors, making it more lilely that this is a flaky drive...

Log Name:      System
Source:        disk
Date:          05/05/2024 15:55:26
Event ID:      51
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      TheDevice
Description:
An error was detected on device \Device\Harddisk1\DR3 during a paging operation.

I would download Samsung Magician and run the maximal diagnostic you can on that drive. Also post the SMART data for it here too. It's worth checking for firmware and/or driver updates for the drive too. That's in addition to removing and reseating it.

One other common error running through the logs is this one...

Log Name:      System
Source:        Microsoft-Windows-TPM-WMI
Date:          06/05/2024 14:54:34
Event ID:      1796
Task Category: None
Level:         Error
Keywords:   
User:          SYSTEM
Computer:      TheDevice
Description:
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931

This particular error (1796) indicates that a failure occurred updating a SecureBoot variable, which might also gel with there being a system drive error.

Ran the full samsung magician scan, came back clear and that ssd is in good health. I've linked below the full smart test I did. (I've ran previous tests as I had magician installed when I first recieved the pc.) I also found a minidump file (I hope!) Seems to be from todays bsod on launch. No disk cleanup tool is running so if they're settings I need to change to make sure minidump files are created let me know! Dont feel comfortable removing and reseating the ssd. I appreciate both of you helping.

Smart test file + one minidump file <---click me

 

[CalPet]

Ran the full samsung magician scan, came back clear and that ssd is in good health. I've linked below the full smart test I did. (I've ran previous tests as I had magician installed when I first recieved the pc.) I also found a minidump file (I hope!) Seems to be from todays bsod on launch. No disk cleanup tool is running so if they're settings I need to change to make sure minidump files are created let me know! Dont feel comfortable removing and reseating the ssd. I appreciate both of you helping.

Smart test file + one minidump file <---click me

Sorry realised that smart test file isnt the actual results (I believe?) Linked below should be the correct results from the s.m.a.r.t. test.

smart test <---click me

 

[ubuysa]

The raw value for 'unsafe shutdowns' is not zero. Whilst these don't damage the drive they can corrupt drive data so it's not impossible that you have a corrupted Windows system. Try running these two commands, one after the other...

dism /online /cleanup-image /restorehealth
sfc /scannow

They should correct any major problems with system files.

The dump shows that you're failing whilst cdd.dll and win32kfull.exe are writing to the screen, cdd.dll is the Windows Canonical Display Driver and win32kfull.exe is the Windows 32-bit kernel mode device driver root...

4: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff88f`bc41e098 fffff802`2c22e269     nt!KeBugCheckEx
01 fffff88f`bc41e0a0 fffff802`2c229705     nt!KiBugCheckDispatch+0x69
02 fffff88f`bc41e1e0 fffff802`2c0ff2ec     nt!KiPageFault+0x485
03 fffff88f`bc41e370 fffff802`2c032fca     nt!MiResolveProtoPteFault+0xcc
04 fffff88f`bc41e440 fffff802`2c030192     nt!MiDispatchFault+0x3ca
05 fffff88f`bc41e580 fffff802`2c2295fa     nt!MmAccessFault+0x152
06 fffff88f`bc41e6a0 ffffc2ca`8ac1dc5b     nt!KiPageFault+0x37a        <===== here's the failure
07 fffff88f`bc41e830 ffffc2ca`8abe532d     win32kfull!vSolidFillRect1+0x1bb
08 fffff88f`bc41e880 ffffc2ca`8abe4fc5     win32kfull!vDIBSolidBlt+0x10d
09 fffff88f`bc41eab0 ffffc2ca`8afa3399     win32kfull!EngBitBlt+0x165
0a fffff88f`bc41ec00 ffffc2ca`8af458f4     win32k!EngBitBlt+0x89
0b fffff88f`bc41ec70 ffffc2ca`8af4530e     cdd!ColorFillBitmap+0x4b4
0c fffff88f`bc41ee50 ffffc2ca`8af4522a     cdd!DrvBitBltInternal+0xce
0d fffff88f`bc41f090 ffffc2ca`8ac702a5     cdd!DrvBitBlt+0x6a
0e fffff88f`bc41f100 ffffc2ca`8ac6f67f     win32kfull!OffBitBlt+0x131
0f fffff88f`bc41f210 ffffc2ca`8abe4d26     win32kfull!SpBitBlt+0x38f
10 fffff88f`bc41f720 ffffc2ca`8abe489b     win32kfull!GrePatBltLockedDC+0x356
11 fffff88f`bc41f7d0 ffffc2ca`8abb4411     win32kfull!GrePolyPatBltInternal+0x2eb
12 fffff88f`bc41f950 ffffc2ca`8abb4324     win32kfull!GrePolyPatBlt+0xe1
13 fffff88f`bc41f9c0 ffffc2ca`8ab67b5e     win32kfull!FillRect+0x54
14 fffff88f`bc41fa20 ffffc2ca`8ac3cd1e     win32kfull!xxxPaintRect+0x7e
15 fffff88f`bc41fa50 ffffc2ca`8ac3ccae     win32kfull!xxxFillWindow+0x62
16 fffff88f`bc41fad0 ffffc2ca`8ac14475     win32kfull!xxxDWP_EraseBkgnd+0x52
17 fffff88f`bc41fb00 ffffc2ca`8ac13eed     win32kfull!xxxRealDefWindowProc+0x4b5
18 fffff88f`bc41fc40 ffffc2ca`8ac28e03     win32kfull!xxxWrapRealDefWindowProc+0x6d
19 fffff88f`bc41fc90 ffffc2ca`8ac20097     win32kfull!NtUserfnDWORD+0x83
1a fffff88f`bc41fcd0 ffffc2ca`8afa73f8     win32kfull!NtUserMessageCall+0x1d7
1b fffff88f`bc41fd60 fffff802`2c22d938     win32k!NtUserMessageCall+0x3c
1c fffff88f`bc41fdb0 00007ffe`bce11554     nt!KiSystemServiceCopyEnd+0x28
1d 00000000`004fcf28 00000000`00000000     0x00007ffe`bce11554

Note: you read this from the bottom up. If this dump was taken at boot (and it looks like it) then I doubt you're using the Nvidia graphics driver yet, but you will be using the graphics card - via the Windows cdd drivers. Try removing and re-seating the graphics card.

It's also worth checking to see whether it BSODs on boot in Safe Mode. Here's how to start Windows in Safe mode, you won't be able top do any work in Safe Mode and most devices (like your display) won't work properly because their third-party drivers are not loaded. What we want to see though, is whether it BSODs booting into Safe Mode, so try many reboots into Safe Mode and see....