Windows 10: BSOD from netbt.sys

Hi

I think I may have a problem.

Ive had a few BSOD's while I was still testing the TP builds. Still on the insider program but on the slow ring so my build is 10240.

But now I seem to be having more frequent BSODs. I didnt pay attention to what caused them before but the last 2 (the day after each other) have had the same message at the bottom - driver irql not less or equal (netbt.sys).

I downloaded the file mentioned in the post about posting BSOD posts but I dont understand how to save the info that it collects.

Nick

:)

 

Windows 10 start-up

When I start my laptop I get an error message. "PC ran into a problem. Windows is checking and needs to shut down. You PC will start automatically(netbt.sys)". Another time I will get the same error message but this time it will end with "(amdpps,sys)".
Could someone please explain what these error messages are and how to get rid of them? I have a HP Pavillion g6 running Windows 10. Thanks.

 

Driver Verifier BSOD diagnosis opinions?

Thank you very much for looking at this.

I followed the directions for uninstalling the drivers, and attempted to install new ones that I

downloaded from my motherboard maker, ASUS. Unfortunately, they don't provide audio drivers for anything past Win 7 64 bit, but even though I'm running Win 10, I tried them. The computer would still crash when I ran driver verifier at startup and I had
to use a restore point.

When I checked which drivers were installed, however, it seemed to still be reverting to the original ones that initially caused the problem. So, I did some research on my own and used the Windows Show or Hide Updates program to make sure VIA wasn't auto-updating,
but the issues persisted. So, as a last resort, I simply went to device manager and updated the audio drivers to Win 10 provided by Microsoft, but I'm still getting the driver verifier crash before the system starts. My computer is presently in this state.
As long as I don't use driver verifier, it doesn't crash at startup, but I bet it will after normal sustained use.

The new dump files are here from the trials above. I'm curious if they're all still pointing to the audio driver, and if so/not,
what other steps you might recommend?

 

Hi Nickynoo,

Welcome to the 10forums.
The tool creates a zip file with the necessary files for debugging the BSOD.
The zip file created by the tool needs to be uploaded, please read How to upload files

 

Please upload a new zip file, the attached zip file is empty

 

I am running the BSOD tool again, but I do notice when i start it that it looks for *.dmp in C:\windows\minidump - I have no files in that folder. Then it carries on with its tasks. Problem?

Here is the newly generated zip file

Nick

 

That is a problem.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial

 

So you will not be able to help me with my problem? I guess Ill have to wait until it happens again.

Thanks anyway

 

Using the thread that you gave me I did option 1 (control panel) - it leads to settings under startup and recovery - however the settings that say "Write an event to the system log" and "Automatically restart" were already checked. Do the 3 options in the thread accomplish the same thing? Do I need to check that the other types of memory dumps are working, if so how, point me in the right direction please.

Nick

 

How is the 'write debugging information' set?
That setting is what it is mainly about.

 

It was set on kernel memory dump and now Ive changed it to small mini dump

 

Please use the tool and upload the zip file when you have a bluescreen.
Prefered after a few bluescreens for a better analyse.