BSOD On New System Setup

Hello and thanks for taking the time to help me with my issue.

I recently upgraded my computer, firstly i changed the graphics card and everything was fine. Then after a week i also upgraded my cpu, motherboard and ram. The change was :

CPU old : Ryzen 9 3900X. New : Ryzen 7 7800X3D
Ram old : Corsair Vengeance 32GB DDR 3 3600MHz New : Corsair Vengeance DDR 5 32GB 6000MHz CL30 AMD EXPO
Motherboard old : ASUS ROG Strix B450-F New : Gigabyte B650 AORUS ELITE AX ATX
Powerpack old : Corsair RM850E New : RM1000X
Graphics old : RTX 3080TI New : RTX 4090.

Now I've reinstalled windows wiping my windows drive while maintaining the files on my other drives as this hasn't really caused an issue before. After the hardware changes i had a BSOD two times and i realised it was because of what i guesed were different things that i'd managed to figure out.

1. My drives had changed letters after my hardware change.
For this it didn't bother me to much as my C and D drives were the same. It had only swapped the E and F drives around but my games still worked.

2. When i'd logged back in to windows after the initial hardware change i had to put in a new windows 10 professional key due to the new hardware changes.
This went smoothly until i realised i was getting a BSOD in doing simple certain things like deleting a empy folder on a drive other than the C drive.

I found that the owner for all of the folders on every other drive other than the c drive was not under my ownership. I went through all the folders on the drives changing the ownership to my account with inheritance and it seems to have fixed the issue of getting a BSOD doing simple things.

The latest one i'm having trouble with is that it seems to be happening when i'm not around. I leave my pc in sleepmode throughout the night and it seems when i wake up it's crashed during the night. I only really seem to know this as wall paper engine pops up telling me it hadn't closed properly after waking my pc up. I'm getting this in event viewer : "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000096, 0xffffd204705183ae, 0x0000000000000000, 0x0000000000000000)"

I think I know where the mini dump is if it would be a good thing to attatch ? I'm thinking of backing up all my drives and formatting them to try to fix the issue but i'd like a little guide before hand to see if the problem is something else unrelated.

Some info :
Edition Windows 10 Pro
Version 22H2
Installed on ‎23/‎01/‎2024
OS build 19045.3996
Experience Windows Feature Experience Pack 1000.19053.1000.0

I've tried /sfc scannow and it was ok.
I did a memory diagnostic and it was ok.
CHKDSK always gets stuck at level 4 on my D drive. ( Makes me want to reformat. )


Thanks for your time.

Check disk won't finish on the D drive so i'm in the process of backing up it's files. I'm planning to format it after the back up and then run a check disk on it. I'm not sure what you mean by updates sorry. Thanks for the swift reply though.

Please see posting instructions:

BSOD - Posting Instructions

Thanks for your replies Zbook and Samuria.

I had a bsod today that said page fault in non paged area. I wiped all my drives but still weren't happy so i opted to create a media drive using the windows tool. It wouldn't let me install off the image from my computer with code (0x8007025D) so i had to use my laptop to make another and it worked. I think my windows install was a bit faulty.

Last night :
1. chkdsk completed on all drives without errors.
2. sfc /scannow worked without finding any problems.
3. dism also completed with no problems on the varying scan options.

I'm now installing program as i've double and triple checked all the windows updates are installed. It currently shows :

Edition Windows 10 Pro
Version 22H2
Installed on ‎28/‎01/‎2024
OS build 19045.3996
Experience Windows Feature Experience Pack 1000.19053.1000.0

I'm going to try playing some games and using the pc as i normally would today and seeing what it brings me. I'll make sure i use the tool to collect my next memory dump from a bsod and figure this out provided we haven't fixed it.

The only little problem i'm facing now is one of my internal drives is showing as a removable drive. When i used the command given here :
https://support.microsoft.com/en-us/...7-ce65a976c8dd
It just changes what drive is seen as a removable drive to another internal drive.

- - - Updated - - -

I found out how to get my hard drives to not show as ejectable. There was a setting in my bios named "Sata-Hot Plug" i disabled that and it's back to normal on that front. Most tests have gone pretty good so far. The final test will be if it starts up and responds ok tomorrow after a long session with the pc on sleep.

- - - Updated - - -

After deleting every system reserve and recover partition using the media creation tool method of installing windows my pc seems to be back to normal. Thanks to those who tried to help.

Hello and thanks for taking the time to try and help me.

I've recently been having some issues with a new build. I've done quite a lot of things and i have another thread with the things i've currently tried. The thread is here :

BSOD On New System Setup

I thought i'd resolved my issues but i just woke my pc up from sleep mode after using it ok for the morning and i had a BSOD with the message "Kernal Security Check Failure" I've used the V2 log tool and will be uploading my results with this post. The last thing i can really think on my end is the ram is bad and i should get it replaced.

Edition Windows 10 Pro
Version 22H2
Installed on ‎28/‎01/‎2024
OS build 19045.3996
Experience Windows Feature Experience Pack 1000.19053.1000.0

AMD Ryzen 7 7800X3D
Corsair Vengeance Pro 32GB DDR5-6000 / PC5-48000 DDR5 SDRAM UDIMM (Currently using AMD Expo in Bios for 6000mhz)
GIGABYTE B650 AORUS ELITE AX
Video Card: GIGABYTE GeForce RTX 4090 GAMING OC 24G
Windows is installed on a Samsung 850 Evo 250GB SSD.

Windows has recently been freshly installed twice, the last time from a fresh working pc on a fresh formatted usb stick.

Another reason my suspicion leads to ram is after browsing one or two topics where stuff seems similar, mainly the first thread :
[SOLVED] Please Help: Random reboots and crashes | HWiNFO Forum
gigabyte b650 aorus elite ax amd expo 7800x3d bsod - Google Suche

I'm getting closer and closer to thinking that it's either the ramr or the AMD Expo settings and i've landed with a bad CPU.

Some steps that you had performed may be repeated.

Make sure that images or share links are posted into this thread.


Please perform the following steps:


1) Run Tuneup plus > post a share link into this thread

https://www.tenforums.com/attachment...p_plus_log.bat

Batch files for use in BSOD debugging

Batch files for use in BSOD debugging


2) Run Sea Tools Long Generic test (all drives) > take pictures > post images or share link

https://www.seagate.com/content/dam/...00869623_B.pdf

https://www.seagate.com/content/dam/...sInstaller.exe


3) Run HD Tune (free or trial version) (all drives)
HD Tune website
Post images or share links for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


4) Run Chkdsk /b /v on all drives after completing the above drive tests

Use the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E:

Make sure that the chkdsk switches run on the Windows drive overnighr while sleeping.

C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y

Reboot as needed.


5) After completing all chkdsk tests run: chkdsk from event > post a share link

https://www.tenforums.com/attachment...kfromevent.bat

Batch files for use in BSOD debugging


6) These steps / tests can run overnight while sleeping:

a) Sea Tools Long Generic test
b) HD Tune Full error scan
c) Chkdsk /b /v


7) For any new BSOD post a new V2 share link into the newest post

It was AMD Expo on the DDR5 Ram. I had to make my own memory profile. It consisted of copying the original ram overclock profile and lowering the voltages so they never go over 1.25V.

When available please update the progress with the steps in post #8.