Many different BSOD on Windows 11

Mick1010

Mick1010

Member
Joined
Jun 14, 2023
Posts
12
SysnativeFileCollectionApp in a Zip: SysnativeFileCollectionApp.zip

Hello folks,

Lately I've been having alot of issues with my PC and I can't get to the core of the problem.
I can't even be certain if it is the Windows or if it is the System because before all of this the System was functioning without any problem and I even reinstalled Windows 11 multiple times so for me that is out of option aswell, but you guys are the pro's so I am trusting in y'all.
First of all this is my specs, in case anyone needs them:

AMD Ryzen 5 7600x
Gigabyte X670 Gaming X AX
Gigabyte Eagle OC RTX 3070ti
Corsair Vengeance RGB 2x16 DDR5-6000MHz
750W Corsair 80+ Gold PSU

The problem is as the following:
Whenever I do anything on the PC, let it be regular gaming, working on something or literally just watching a YouTube video, there is a chance of me getting a BSOD straight to my face.
There is a variety of error codes such as:

Driver Overran Stack Buffer
Kernel Mode Heap Corruption
IRQL Not Less Or Equal
Faulty Hardware Corrupted Page
DPC Watchdog Violation
something connected to "ntoskrnl.exe"
something connected to "dxgmms2.sys"
something connected to "intelppm.sys"
System Service Exception
Reference By Pointer
and probably many more that I cant remember or havent Googled because it BSOD'd so fast I couldnt even read the code.

Due to the BSOD not always or basically never being the same, I am completely out of options.

I did the "sfc /scannow" in the CMD alongside the "chkdsk" command aswell as the "DISM.exe /Online /Cleanup-image /Restorehealth" with all of the commands coming back negative so Windows didnt find any fault in the System files, the disks nor the RAM as I have also done the integrated Memory Integrity Check.

I also reinstalled Windows 11 completely on a fresh SSD multiple times but still with no success. I swapped out RAM kits for completely fresh ones, I updated my BIOS to the latest release and tried older releases aswell, I installed every single driver I could possibly find for my System and I have reseated every component in my PC to ensure that there is no loose connection.

I have no idea what else I can do to fix this problem. I am loosing very worthy progress on my work and I don't even work on anything right now without saving literally every 5 minutes. But it wasnt always like this, when I upgraded to this PC, I had no issues at all and then it just randomly started happening.

This crashing sometimes happens after 10 hours of usage, sometimes couple minutes after booting the PC, sometimes it is in a loop where there is a BSOD and the computer restarts itself and not even 1 minute after another BSOD with a new error code occurs. And then it just keeps going until it doesn't and then it gives me peace for a couple minutes maybe an hour or 2. Depends on the mood of the PC I guess, lol.

I also have Minidumps saved that I can upload if needed, incase they can help you guys out in determining the root of the problem

Thanks alot for anyone that is willing to help me!
I am truly devastated with this problem.
 
Sorry, most people add the link at the end.

There are BSODs in your System log but no dumps were uploaded. Do you run a cleaning tool? If so, you'll need to stop it cleaning the dump files.

Also, your system language is not English and it's hard for us English speakers to read the messages in your system log. Could you change the language to English and run the Sysnative data collection app again please? Without any dumps however it's not going to be easy to diagnose this.
 
Oh sorry my bad didnt even think about the language!
No I am not running any cleaning tools, since I have reinstalled Windows completely, I just have some drivers, a browser (Opera GX), Steam alongside some games and Discord installed.
Funny enough I found out that Windows deletes my Minidumps for some reason, couple days ago I had like 7-8 in there, and now I only had 4.
I was able to fetch those tho and will attach them alongside the updated SysnativeFileCollectionApp.
Thanks alot!
 

Attachments

Wrench97 said:
You appear to running Driver Verifier, when you run verifier you must exclude all MicroSoft drivers or you will get false results.
See here> Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8

Check for updates on your AMD chipset drivers either from the Gigabyte site or the AMD Site.
Click to expand...
I found a similar thread with a user having similar problems like mine and they told him to use Driver Verifier so I gave it a shot.
I tried it out, selected only drivers that werent from Microsoft and the PC wouldnt even boot beyond Windows Logo and gave me straight BSOD.
In Safe Mode it worked but there I couldnt test anything because it uses barely anything in that mode so I disabled it again.
I dont know why it shows that it is still on tbh.

My PC just crashed again and I'll upload this fresh Minidump on this reply so maybe you guys can take a look at that aswell?
Thanks
 

Attachments

Mick1010 said:
I found a similar thread with a user having similar problems like mine and they told him to use Driver Verifier so I gave it a shot.
I tried it out, selected only drivers that werent from Microsoft and the PC wouldnt even boot beyond Windows Logo and gave me straight BSOD.
In Safe Mode it worked but there I couldnt test anything because it uses barely anything in that mode so I disabled it again.
I dont know why it shows that it is still on tbh.

My PC just crashed again and I'll upload this fresh Minidump on this reply so maybe you guys can take a look at that aswell?
Thanks
Click to expand...
Run Verifier following the instructions above, cut the non micro soft driver list in half, for example do drivers starting with A through M, if it starts and fine reset it to run drivers from N through Z.
Keep cutting the list until you narrow down the driver.
 
Wrench97 said:
Run Verifier following the instructions above, cut the non micro soft driver list in half, for example do drivers starting with A through M, if it starts and fine reset it to run drivers from N through Z.
Keep cutting the list until you narrow down the driver.
Click to expand...
Alright I will give that a try again just now.
I also installed Chipset drivers again but this time from AMD's site instead of Gigabytes, maybe that will help I dont know.
Thanks
 
The last one is a Nvida video card driver nvlddmkm.sys run verifier first lets see what it comes with.

Code: 
Debug session time: Thu Jun 15 16:48:55.859 2023 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061523-9453-01.dmp]
System Uptime: 0 days 1:20:35.448
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff801a375a8db, address which referenced memory
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
PROCESS_NAME:  System
Probably caused by: nvlddmkm.sys ( nvlddmkm+ea8db )
FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

*** 3rd PARTY DRIVER LIST ***
*** 3rd PARTY DRIVER LIST ***


Code: 
AmdTools64.sys                                Wed May 27 02:45:35 2020 (5ECE0C8F)
AtihdWT6.sys                                  Wed Jun 22 09:18:18 2022 (62B3169A)
CtiIo64.sys                                   Tue Apr 26 23:01:30 2022 (6268B20A)
MpKslDrv.sys                                  Thu Oct 25 14:41:58 2012 (508987F6)
NDivert.sys                                   Tue Jun 28 02:48:03 2022 (62BAA423)
NvModuleTracker.sys                           Fri May 13 09:38:38 2022 (627E5F5E)
RTKVHD64.sys                                  Tue Jun 28 06:09:39 2022 (62BAD363)
SteelSeries-Sonar-VAD.sys                     Tue Mar 14 06:54:34 2023 (6410526A)
UniFairy_x64.sys                              Thu Apr 14 00:30:07 2022 (6257A34F)
VirtualHID.sys                                Tue Dec 24 02:37:07 2019 (5E01C023)
amdfendr.sys                                  Tue Oct 11 14:57:43 2022 (6345BCA7)
amdfendrmgr.sys                               Tue Oct 11 14:58:10 2022 (6345BCC2)
amdgpio2.sys                                  Wed Mar 11 07:15:48 2020 (5E68C864)
amdi2c.sys                                    Tue Dec  6 01:53:41 2022 (638EE6F5)
amdkmpfd.sys                                  Thu Feb  4 10:55:29 2021 (601C18F1)
amdpsp.sys                                    Thu Feb 23 13:07:56 2023 (63F7AB7C)
amdxe.sys                                     Thu Jul 23 18:18:02 2020 (5F1A0C9A)
aow_drv_x64_ev.sys                            Mon Apr 24 01:05:58 2023 (64460E36)
gdrv3.sys                                     Tue Aug 23 23:08:05 2022 (63059615)
msquic.sys                                    Wed Nov 30 19:42:53 2022 (6387F88D)
mtkbtfilterx.sys                              Wed Mar 23 10:18:48 2022 (623B2C48)
nvhda64v.sys                                  Fri Jan 20 05:48:10 2023 (63CA716A)
nvlddmkm.sys                                  Wed May 24 09:08:28 2023 (646E0C4C)
nvvad64v.sys                                  Thu Sep 22 11:10:30 2022 (632C7AE6)
nvvhci.sys                                    Fri Apr 22 07:37:06 2022 (62629362)
rt25cx21x64.sys                               Mon Mar 20 11:58:43 2023 (641882B3)
ssdevfactory.sys                              Thu Mar  2 15:22:11 2023 (64010573)
sshid.sys                                     Thu Mar  2 15:22:11 2023 (64010573)
tapnordvpn.sys                                Thu May 31 05:50:28 2018 (5B0FC564)
unirsdt.sys                                   Thu Apr 14 00:43:04 2022 (6257A658)
wtd.sys                                       Thu Jul  4 17:49:45 2024 (668718F9)

Code:
 
Wrench97 said:
The last one is a Nvida video card driver nvlddmkm.sys run verifier first lets see what it comes with.

Code: 
Debug session time: Thu Jun 15 16:48:55.859 2023 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061523-9453-01.dmp]
System Uptime: 0 days 1:20:35.448
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff801a375a8db, address which referenced memory
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
PROCESS_NAME:  System
Probably caused by: nvlddmkm.sys ( nvlddmkm+ea8db )
FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

*** 3rd PARTY DRIVER LIST ***
*** 3rd PARTY DRIVER LIST ***


Code: 
AmdTools64.sys                                Wed May 27 02:45:35 2020 (5ECE0C8F)
AtihdWT6.sys                                  Wed Jun 22 09:18:18 2022 (62B3169A)
CtiIo64.sys                                   Tue Apr 26 23:01:30 2022 (6268B20A)
MpKslDrv.sys                                  Thu Oct 25 14:41:58 2012 (508987F6)
NDivert.sys                                   Tue Jun 28 02:48:03 2022 (62BAA423)
NvModuleTracker.sys                           Fri May 13 09:38:38 2022 (627E5F5E)
RTKVHD64.sys                                  Tue Jun 28 06:09:39 2022 (62BAD363)
SteelSeries-Sonar-VAD.sys                     Tue Mar 14 06:54:34 2023 (6410526A)
UniFairy_x64.sys                              Thu Apr 14 00:30:07 2022 (6257A34F)
VirtualHID.sys                                Tue Dec 24 02:37:07 2019 (5E01C023)
amdfendr.sys                                  Tue Oct 11 14:57:43 2022 (6345BCA7)
amdfendrmgr.sys                               Tue Oct 11 14:58:10 2022 (6345BCC2)
amdgpio2.sys                                  Wed Mar 11 07:15:48 2020 (5E68C864)
amdi2c.sys                                    Tue Dec  6 01:53:41 2022 (638EE6F5)
amdkmpfd.sys                                  Thu Feb  4 10:55:29 2021 (601C18F1)
amdpsp.sys                                    Thu Feb 23 13:07:56 2023 (63F7AB7C)
amdxe.sys                                     Thu Jul 23 18:18:02 2020 (5F1A0C9A)
aow_drv_x64_ev.sys                            Mon Apr 24 01:05:58 2023 (64460E36)
gdrv3.sys                                     Tue Aug 23 23:08:05 2022 (63059615)
msquic.sys                                    Wed Nov 30 19:42:53 2022 (6387F88D)
mtkbtfilterx.sys                              Wed Mar 23 10:18:48 2022 (623B2C48)
nvhda64v.sys                                  Fri Jan 20 05:48:10 2023 (63CA716A)
nvlddmkm.sys                                  Wed May 24 09:08:28 2023 (646E0C4C)
nvvad64v.sys                                  Thu Sep 22 11:10:30 2022 (632C7AE6)
nvvhci.sys                                    Fri Apr 22 07:37:06 2022 (62629362)
rt25cx21x64.sys                               Mon Mar 20 11:58:43 2023 (641882B3)
ssdevfactory.sys                              Thu Mar  2 15:22:11 2023 (64010573)
sshid.sys                                     Thu Mar  2 15:22:11 2023 (64010573)
tapnordvpn.sys                                Thu May 31 05:50:28 2018 (5B0FC564)
unirsdt.sys                                   Thu Apr 14 00:43:04 2022 (6257A658)
wtd.sys                                       Thu Jul  4 17:49:45 2024 (668718F9)

Code:
Click to expand...
What could that mean? I literally just installed new Nvidia drivers via clean install, but I have had that BSOD connected to the Nvidia drivers before and updated it back then aswell.
I am now currently running on driver verifier, I tried one half of the list, no problem booting, other half of the list, also no problem booting, now I am running the full list including the 4 microsoft drivers and now I am hoping for frequent crashes right? And then afterwards I should upload the Minidumps here and turn off driver verifier if I understood correctly?
I dont know why it works now and didnt work like 2 days ago, I am so confused.
 
No do run any Micro Soft drivers in verifier.
If you have the latest Nvidia driver drop back to a older driver.
How old is the video card?
Have you checked the temps of the video card?
If it BSOD's on older drivers I swap the card with a known good one to test.
 
Wrench97 said:
No do run any Micro Soft drivers in verifier.
If you have the latest Nvidia driver drop back to a older driver.
How old is the video card?
Have you checked the temps of the video card?
If it BSOD's on older drivers I swap the card with a known good one to test.
Click to expand...
Sorry couldnt quite understand your first sentence, should I now enable all or none? In the post that you linked it explicitly said to not select any microsoft drivers except 4 ones that they listed.
The card is just over 2 years old and the temps are not the best anymore.
Sometimes the hotspot reaches like 104°C with the memory sometimes reaching 95°C and thats just too much.
I have already assumed this so I ordered some thermal pads alongside thermal paste to replace everything and check back if that solves it, they should arrive tomorrow so I can disassemble it tomorrow.
Until you mentioned it, this card was a known good one but now that youve said it I cant be sure anymore...

Also, its already very late for me (3AM) and so far there hasnt been a BSOD even when I gamed pretty intensly.
Should I just leave the PC running over night to see if it crashes while doing nothing?
Or should I maybe open videos, leave games running etc?
 
ubuysa said:
Please run DV exactly as described in these instructions: Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8
Click to expand...
Will do, allthough in the instructions it doesnt really say if I should stress test it on games or heavy tasks or anything it just says to let it run for atleast 24 hours even if everything seems good or till it crashes.
I left my PC open for the night until like 1 hour ago so it was open for 16 hours+ without any crashes, I also did some gaming before I went to sleep to stress it a little bit.
Now as I came home I took out my GPU and replaced the thermal pads alongside the thermal paste and try to see if that fixes the case.
Im not too sure if GPU's overheating can cause a BSOD, I think it would rather just cause a PC freeze and after it cooled down it would just be as normal, or am I wrong here? Please correct my knowledge if I am wrong :D

This time I will let it run for 24 hours minimum and do as much stressing as I can do, the CPU is under heavier load even on idle which I blame the driver testing for, same with the gpu.
I hope I either get no crash and the GPU overheating somehow was the problem, or I get some crash with a dump that will help you guys analyze it.

Thanks alot again for all of your guys' time!
I really appreciate it.
 
This one looks like it was caused by a Steelseries process, what Steelseries hardware are you using?

Code: 
Debug session time: Sat Jun 17 02:53:53.889 2023 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061723-14031-01.dmp]
System Uptime: 0 days 13:59:33.533
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff802330150e6, Address of the instruction which caused the BugCheck
Arg3: ffffb80150934900, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
PROCESS_NAME:  SteelSeriesEng
Probably caused by: ucx01000.sys ( ucx01000+5570 )
FAILURE_BUCKET_ID:  AV_ucx01000!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
Notwithstanding the other advice you're getting I think it would be wise to run a RAM test at this point. That's based on the range of bugchecks you reported in your OP and the 0xC0000005 exception code in this one (that's a memory access violation).

Download Memtest86, use the extracted tool to make a bootable USB drive, then boot that USB drive. Memtest86 will start running as soon as it boots. If no errors are found after all four interations of the 13 different tests (which will take some hours on your 32GB of RAM) then restart Memtest86 and do another four iterations (for a total of 8).
 
Wrench97 said:
This one looks like it was caused by a Steelseries process, what Steelseries hardware are you using?

Code: 
Debug session time: Sat Jun 17 02:53:53.889 2023 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061723-14031-01.dmp]
System Uptime: 0 days 13:59:33.533
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff802330150e6, Address of the instruction which caused the BugCheck
Arg3: ffffb80150934900, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
PROCESS_NAME:  SteelSeriesEng
Probably caused by: ucx01000.sys ( ucx01000+5570 )
FAILURE_BUCKET_ID:  AV_ucx01000!unknown_function
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Click to expand...
Im using a Aerox 3 Wireless and its Software alongeside it which is called Steelseries GG.
Is there a chance that the mouse can malfunction over time and cause this?

Also what was funny is that the BSOD didnt shut the PC off, it completely froze and after 30 minutes ish I had to force the PC to quit via power button as it was not responding at all anymore.
I dont know what caused it, I was watching a YouTube video on my second monitor and played Diablo IV on my main monitor but I didnt use anything mouse related besides just moving the mouse around, so no macros, no updates and didnt even connect it via cable to charge so it is very confusing to me as to why this caused a BSOD.
ubuysa said:
Notwithstanding the other advice you're getting I think it would be wise to run a RAM test at this point. That's based on the range of bugchecks you reported in your OP and the 0xC0000005 exception code in this one (that's a memory access violation).

Download Memtest86, use the extracted tool to make a bootable USB drive, then boot that USB drive. Memtest86 will start running as soon as it boots. If no errors are found after all four interations of the 13 different tests (which will take some hours on your 32GB of RAM) then restart Memtest86 and do another four iterations (for a total of 8).
Click to expand...
Sorry if I am misunderstanding some stuff, my English isnt my main language and really isnt that great I sometimes have struggles understanding certain thing, so I apologize if I overlooked something or one of your advices.
I did the Memtest86 the day before I went into the driver verifier on your guys' recommendation, I let it run for 2 runs and it didnt show any error. I needed to use the PC for work and I read up online that after 2 succesful runs with 0 errors, that it is 99.9% safe. Also I originally had 2x2 sets of RAM sticks and I tried running the PC with both (used the first 2 in dual channel and then when the crashes occured, swapped them out for the other 2 but it just keeps on going).
Currently running with the latest 2 that I put in place of the others.

Thanks guys!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top