[SOLVED] Multiple BSOD on new build (last one: ndis.sys - System_thread_exception_not_handled)

[nekiojam]

Hey guys.
I've built a new computer a month ago and I've had multiple issues with BSODs, although it did not happen much recently.
Last one happened while playing a game but it used to sometimes crash on idle or while rendering on Premiere Pro.

Here's the last (full) dump: https://drive.google.com/file/d/11jRkUfnJwqMGPv-PfuBTTYGHC-1kJnog/view?usp=sharing
And mini dump: https://drive.google.com/file/d/1fRMLr6yHVZqdsE_TyMDBMHKXBFt5V6VO/view?usp=sharing

Config:
i9-10900k
MSI MPG Z490
G.Skill Trident Z RGB - 4x8Gb 4266MHZ
ASUS Nvidia ROG 2080TI

If anyone can help, that would be wonderful since I've been struggling quite hard on this. Reinstalling Windows did not help.
I've also checked with Who Crashed and WinDbg but I'm no expert
Thanks a lot!

 

[PC Tailor]

Welcome to the forums my friend!

Downloading now but obviously full dump files are quite large. Do you happen to have minidumps to hand? If so, might be worth configuring these too just for a more online friendly format as minidumps are often enough to deduce from

 

[nekiojam]

Hey, my bad!
Here's the minidump: https://drive.google.com/file/d/1fRMLr6yHVZqdsE_TyMDBMHKXBFt5V6VO/view?usp=sharing

Updating the original post I've updated all my drivers since the crash too, just in case (I thought everything was up to date but guess it wasn't...)
Thanks!

 

[PC Tailor]

Thank you my friend! I did have time to get through the full dump, but the minidump helps for other users too.

"I have run the dump file(s) and you can see the full report(s) in the link below.
If you are prompted to ""Run only if trusted"" simply click play/run and the html will be viewed. This warning is always present."
Report: https://jsfiddle.net/buvetxry/show

Summary of findings:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
"This is typically driver based and therefore you should reference the third party modules loaded to check which ones may be misbehaving.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.

Check with your hardware vendor for any ACPI or other firmware updates. Hardware issues, such as system incompatibilities, memory conflicts, and IRQ conflicts can also generate this error. Confirm that any new hardware that is installed is compatible with the installed version of Windows.

You can also disable memory caching/shadowing of the BIOS to try to resolve the error. You should also run hardware diagnostics, that the system manufacturer supplies."

So some other things I could see:

STACK TEXT
ffff8289`59a17680 fffff804`4cea50bb : fffff804`34ba2b30 fffff804`34ba2b30 ffff8289`59a177d9 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0x104
ffff8289`59a17710 fffff804`4cdc6523 : fffff804`34ba2a70 fffff804`34ba2a70 00000000`00000000 ffffcc81`f6770000 : rt640x64+0xe50bb
ffff8289`59a17830 fffff804`4cea2377 : ffffcc81`f6770000 ffff8289`59a179a8 00000000`00000000 00000000`00000000 : rt640x64+0x6523
ffff8289`59a17890 fffff804`363363e9 : 00000000`00000001 ffffcc81`fa0dc000 00000000`00000000 ffffcc81`f5772740 : rt640x64+0xe2377
ffff8289`59a17910 fffff804`363368dc : ffffcc81`fa0dc5e8 00000000`0000000a 00000000`00000001 00000000`00000000 : ndis!ndisMiniportDpc+0xf1

rt640x64 is Realtek Ethernet Driver and is timestamped 12/02/2020. There is a newer version for your motherboard dated 2020-06-16 if i have gotten to correct system info and correct driver link. You can download it here: https://www.msi.com/Motherboard/support/MPG-Z490-GAMING-EDGE-WIFI#down-driver&Win10 64 - I believe this is indeed the same driver.

I'd start with that. Then look at other options. It could just be something else triggered it via the network driver but we'll have to find out.

Also how are you updating your drivers? Hopefully not using a driver updater app!

 

[nekiojam]

First of all, thanks a lot for the help! That's appreciated.

I've tried to update it to the new version but that's odd... It simply doesn't show the same version number. Here's what I get.

No driver updater, don't worry!

 

[PC Tailor]

First of all, thanks a lot for the help! That's appreciated.

No problem my friend. Stop errors are not an exact science, so it is a lot of trial and error. See what happens after this point. There could well be other things that just hide behind the RT Ethernet driver causing the issue, but it's taking it one step at a time and seeing.

If it does re-occur, some future minidumps might shed some more light.

Did the BSOD occur immediately after a fresh build or did they come on over time after building?

 

[nekiojam]

I'll keep an eye on it for sure and come back if any BSOD shows up.

I've had numerous BSOD after building that PC a month ago (and I cried, a lot ahaha) which I think were related to RAM or CPU configuration in the BIOS, but after some tweaking, it went smoothly.

Thanks again, let's cross fingers now!

 

[Colif]

I am more curious why WIn 10 update catalog thinks its the same number as a KIller driver

I don't get that one. I wonder if its mislabelled. You would think MS were more careful.

The 10.38.1118.2019 was released on 18th Nov last year.
10.42 is the latest installer on the Realtek Zoo page.

Drivers/installers aren't always the same thing. Many companies use older drivers and just change the date on the installer.

i wouldn't be surprised to find the release schedule for Realtek drivers closely follows Win 10.

 

[nekiojam]

Huh, thanks Colif, will try to download this driver.
Computer crashed again yesterday with BSOD, but no dump - it restarted instantly.

Also updated the BIOS before going to bed. Will try tonight with the new driver & BIOS.

 

[Colif]

could try running this and show zip here, PC should know how to read it... it might give a clue to yesterdays crash - https://www.sysnative.com/forums/pages/bsodcollectionapp/

 

[nekiojam]

Hey, got some updates.

Forgot to check the Event Viewer yesterday (which I did a lot when I had BSODs), and turns out the last one seems to be caused by HID Compliant headset. Already had this issue, my headset is a Razer Kraken V2.

Sysnative report here:
https://drive.google.com/file/d/1zuXjMZkrg2dFTFSraolCDSuuoX7lXgYf/view?usp=sharing

Updated the Realtek driver as you mentioned Colif will see how it goes.
Thanks!

 

[Colif]

serves me right for assuming it would be in English
I assume you know the Wireless BT is disabled

many of the programs crashing appear to be graphical in nature. Nvidia drivers aren't the best anymore.
Adobe Premier Pro sure likes to crash.

So the Headset is your kraken I guess.
wonders what RTX Voice is for. microphones.. wonder if that is cause of the event you looking at there. As I can see its crashed twice in the last few days.
if you look at System Information screen
in left column, click Software Environment and then Windows Error reporting, you will see the screen I am looking at

I can see your system info screen data as that is what the sysnative file collects.

 

[nekiojam]

Yes, disable BT just in case (I don't use it).
I guess it is my Kraken, I have no headset otherwise than this one… BUT, you're mentioning RTX Voice, and that might be a good hint indeed.

RTX Voice is a Nvidia software (it might still be in beta though) used to remove background noise from microphones using RTX tech. It generates a new mic input, but also adds an audio output. Didn't think about this software, I'll stop using it just in case too.

I'll check tonight for the screenshot and send it up. Thanks again Colif for the help

 

[Colif]

Oh I knew it was Nvidia, just didn't know its purpose.

Mixing Nvidia with Razer might be asking for troubles.