BSOD while running Driver Verifier, probable reason netbt.sys

[didoto]

"Was there any other files with this .dmp file?" - What do you mean by that? I mean, if there are some other logs I should attach, lmk where to find them... I only look in the minidump folder...

 

[HonorGamer]

Well most of the time there is a folder something like "Windows_NT6_BSOD_(username)" or something close. But was that all that was in there was the dmp file?

 

[didoto]

Yes, that was all. Would the "Windows_NT6_BSOD_(username)" be located in the minidump folder too? If so, it's definitely not there hehe

 

[HonorGamer]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Go ahead and follow that again, and zip up and post the files from the tutorial that it tells you to.

 

[didoto]

Here you go...

 

[HonorGamer]

Here's the fun. Alright i will post back after i look at these.

 

[HonorGamer]

Alright the only thing that I can think of trying to do would be to do a clean install of windows. I can't find anything. I am going to ask someone to help me out though first. I will let you know if a clean install is what's going to happen.

 

[didoto]

Thanks

 

[writhziden]

You have a ton of programs loading on startup. That may contribute to some issues. See if you have problems after performing a clean startup: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Leave only Microsoft Security Client (MSC) checked in startup items.


Java:

I also noticed that you mentioned Java had some security problems. That is not uncommon if Java is not kept up to date. It is very susceptible to security breaches. I usually uninstall mine once every few weeks:

Start Menu -> Control Panel -> Uninstall a program -> Remove all Java software​

and then download a fresh version:

java.com: Java + You -> Downloads​

 

[didoto]

Removed Java and rebooted with a clean startup.

Will post if there's any development.

Thanks!

 

[didoto]

OK, the latest fashion is irql_not_less_or_equal 0x0a

I have attached the minidump just in case but (as long as I could see), it says nothing of value (ntoskrnl being the perp as usual)

I'm preparing for a clean re-installation now - I just hope this will solve the problem.

If not, I'll try a memory-stick change as a last resort (although, I doubt this is the problem).

Anyway, thanks everyone for your help!

 

[writhziden]

You still had Daemon Tools installed. Please refrain from installing it after you do your clean install.

For the clean install, follow the steps in http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164 to get your drivers and software installed optimally and test each driver and program to determine which may be the culprit.