BSOD while running Driver Verifier, probable reason netbt.sys

didoto · 19 Jul 2012

Hello,

I have been experiencing lots of BSODs lately, all at random and all showing different reasons.

At first, I thought that I had a memory problem - so, I removed one of the RAM modules and the laptop worked OK for a few days. However, today the BSODs started again.

I ran Driver Verifier for a few hours and started getting BSOD after BSOD.

I checked the minidump and (from what I saw), the reason is probably netbt.sys:

==================================================
Dump File : 071912-64475-01.dmp
Crash Time : 7/19/2012 1:34:55 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : fffffa80`29e73608
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`027b690d
Caused By Driver : netbt.sys
Caused By Address : netbt.sys+288bf608
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70040
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump1\071912-64475-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 301,811
==================================================

Before running Driver Verifier, I was getting a BAD_POOL_HEADER 0x19 BSODs.

I'm running Windows Home Premium x64 on a Toshiba Qosmio X500 laptop. The OS is OEM.

I have also attached the jcgriff + perfmon reports and the minidump txt export (just in case).

Thanks in advance for all the help you can provide me with

HonorGamer · 19 Jul 2012

I am not seeing the .dmp files in the files you have attached. Please attach that file also.

didoto · 19 Jul 2012

I apologize, I zipped it and attached it now.

HonorGamer · 19 Jul 2012

Try and update your Drivers - Download NVIDIA Drivers

Do you a Fingerprint USB device?

If so try removing that and uninstalling the drivers for it.

HonorGamer · 19 Jul 2012

Also do a windows update, and make sure you have the latest updates.

didoto · 19 Jul 2012

Yes, I have the fingerprint device, will remove it.

Windows is getting regularly updated, so this shouldn't be a problem.

Do you think that netbt.sys has actually something to do with the problem or it's more like a coincidence (or a false alarm)?

HonorGamer · 19 Jul 2012

Sometimes when a crash dump says: "probably caused by: (such an such file)" it isn't it. Just depends, but we are eliminating every possiblity so we can figure this out. I am actually new to BSOD analyzing so as we go I'm learning also.

Also try updating your Intel Storage Drivers

and Intel Processor drivers

And let me know from there.

didoto · 19 Jul 2012

Will do that now.

In the meantime, another BSOD happened - this time for a completely different reason.

I was in Safe mode, running a scan with MS Security Essentials (just in case).

I have attached the new minidump as well - might be helpful.

Thanks!

==================================================
Dump File : 071912-17877-01.dmp
Crash Time : 7/19/2012 3:35:19 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`027bf07a
Parameter 3 : fffff880`02389828
Parameter 4 : fffff880`02389090
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1a307a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17017 (win7_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+1a307a
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump1\071912-17877-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 270,627
==================================================

HonorGamer · 19 Jul 2012

This could be a hardware problem.

Try these following things and post back results:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).
Copy/paste the results into your next post.

HonorGamer · 19 Jul 2012

Also, please do a full virus scan either using avast! Free Antivirus | Download Antivirus Protection Software or Microsoft Security Essentials - Free Antivirus for Windows .

Then use Malwarebytes : Free anti-malware download to do a complete scan

Also remove ALL programs associated with Daemon Tools. They could be one cause of it.