Question Can you please help me to find BSOD cause on my new PC?

[mosssi]

Hello guys.
I've built a new PC and I installed Windows 11 on it. From then I face BSOD mutiple times a day. Sometimes when my system awake from sleep mode or during the working state.
This is my system info:

https://drive.google.com/file/d/18vBKP6K7FRUhCp0a6DPT1TdIjVttODpB/view?usp=drive_link

These are the dump files summery:
https://drive.google.com/file/d/134qCD5eEzcmWqfIzRAy-Kv3ENTZz8jWA/view?usp=drive_link

Things I did to fix the problem:
- Updated the nvidia driver to latest version
- Used Driver verifier according to This Thread
+ I got BSOD at startup but I couldn't find the faulty driver
- Ran my mainboard Memtest with no errors

Can you please help me to find the reason? Thanks

 

[helpstar]

which PSU are you using?
update BIOS of the motherboard

to have a look what the problem could be:
run userbenchmark.com and post the http link of your result, e.g. https://www.userbenchmark.com/UserRun/28977730


check windows integrity
open the command prompt as administrator and type DISM /Online /Cleanup-Image /RestoreHealth
https://www.lifewire.com/how-to-open-an-elevated-command-prompt-2618088
https://answers.microsoft.com/en-us...em-files/bc609315-da1f-4775-812c-695b60477a93


clean boot
https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows


check the hard drive for errors with its manufacturer´s tool and if available, update the firmware

use ddu uninstaller and reinstall the latest graphics driver

 

[mosssi]

My PSU is:
Asus Rog strix 1000W Aura Edition
Also BIOS is uptodate.

This is the Userbenchmark result:
https://www.userbenchmark.com/UserRun/67084063

I tried "sfc /scannow" and it saied:
Windows Resource Protection found corrupt files and repaired them (a good thing)

I installed Samsung Magcian and I updated all the framwares.

Also I reinstalled Nvidia driver using DDU.

I can confirm that I use XMP profile with my memory sticks. I fear if it's a high frequency memory problem.

Now I'm wating for a new BSOD to report.

PS:
Still having the problem.
ntoskrnl.exe ntoskrnl.exe+4b341d fffff806`48000000 fffff806`49047000 0x01047000 0x16b96037

 

[ubuysa]

The 'dump files' you have uploaded are pointless. ALWAYS upload the actual dump files. BSOD analysis is way more complex than just analyze -v. What you uploaded looks like BlueScreenView output - which is utterly useless for BSOD analysis!

 

[mosssi]

Good point. These are the actual dmp files:

https://drive.google.com/file/d/1B5gvJl2cw3ENggYj28lT_7Qh_PtN6r_A/view?usp=drive_link

https://drive.google.com/file/d/1JQ7arkfAUGXaIvXtrZic98q3Ne6FUDa6/view?usp=drive_link

https://drive.google.com/file/d/1rOJUtNDrbx1l0qzlLI6lvyEuP5cJ8PVy/view?usp=drive_link

https://drive.google.com/file/d/1AO-OUOVa6FN3DhZOUum5cosYIEYPrOrR/view?usp=drive_link

https://drive.google.com/file/d/1PFK713QpOZ1_s0GkpbXH0j4wGHvIZx-b/view?usp=drive_link

 

[mosssi]

I used verifier and there is a crash related to igovsd.sys driver. It seems its an asus audio driver. Do you know what should I do to cconfirm if this is the cause of the BSOD?

 

[ubuysa]

Only one of those five dumps have Driver Verifier enabled, and that did indeed flag igovsd.sys in the dump (I'm guessing you used BlueScreenView to deduce that?). That is probably not your problem however, you have to look at all five dumps in the round to realise that you almost certainly have a RAM problem.

Of the other four dumps (which do not have Driver Verifier enabled), three are 0x1E bugchecks with a 0xC0000005 exception code - that's a memory access violation. The call stacks in these dumps also show unusual addresses, and non-canonical in a couple, which is characteristic of a RAM issue. The other dump fails with a 0x50 bugcheck but also has unusual addresses on the call stack. Even the Driver Verifier BSOD (0xC4) fails because of a memory pool type failure, which could also be caused by bad RAM.

I suggest you run a thorough memory test on your RAM - that's going to take a long time on 64GB of RAM but you have little choice really, your RAM needs to be tested...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86, and do another four iterations.
4. Even a single error is a failure.

Let us know how that goes.

 

[mosssi]

Only one of those five dumps have Driver Verifier enabled, and that did indeed flag igovsd.sys in the dump (I'm guessing you used BlueScreenView to deduce that?).

Actually I used WinDbg to see the issue.

I suggest you run a thorough memory test on your RAM

I tested my ram with Memtest on the Asus mainboard BIOS. It didn't failed but I try to use the standalone app and recheck it.

Also what do you think on the XMP profile and the 5600Hz Ram? Someone mentioned to me which higher frequency RAMs can lead to unstablity of the system.

 

[ubuysa]

Also what do you think on the XMP profile and the 5600Hz Ram? Someone mentioned to me which higher frequency RAMs can lead to unstablity of the system.

When you're getting BSODs always remove any overclocks, so please remove the XMP overclock - even if the RAM is certified at the overclock frequency.

 

[mosssi]

I had many errors in Test 10 on one of my memory sticks. I will change the ram and repoert the result later.

 

[ubuysa]

RAM really needs to be in matched pairs (or quads) so if you exchange one stick be CERTAIN that the replacement has EXACTLY the same part number. If that's not possible then I strongly suggest that you scrap both sticks and buy a pack of matched RAM.