BSOD error 0x000000d1

[ThokeB]

I still got BSODS, but only when Driver Verifier is enabled and Windows is booting.

I see 3 drivers from an unknown manufacturer in Driver Verifier: bdfwfpf.sys, dump_dumpfve.sys and dump_iastor.sys.
Bdfwfpf.sys seems to be related to Bitdefender firewall, so I should keep it checked.
Dump_iastor.sys.is apparently Intel Sata driver for harddisk, so it should be checked too (I guess?)

I found this about dump_dumpfve.sys:

dump_dumpfve.sys

%SysDir%\Drivers\DUMP_DUMPFVE.SYS is related to Microsoft Windows Vista.
DUMP_DUMPFVE.SYS is a Full Volume Encryption Crashdump Hibernate Filter Driver.
DUMPFVE.SYS is a part of Microsoft® Windows® Vista Operating System.

I'll attach the newest dumps if you want to have a look at them.

I'll be in touch after testing this computer a few days. Let's hope the problem is gone!

EDIT: Hold on, this still might not be because of dump_dumpfve.sys... I'll test some more.

It seems BSODs still occur despite Driver Verifier not stress-testing dump_dumpfve.sys.
I have no idea what exactly causes these crashes, but I do know they are related to Driver Verifier. There are no crashes when Driver Verifier is disabled.

 

[Dave76]

The drivers with the 'dump' prefix are drivers created to provide disk access during crash dump file generation.
You can uncheck these.
1. Then uncheck half of the remaining drivers, run Driver Verifier and see if it still crashes.

2. Then you can check the drivers from the last test and uncheck the others. Run Driver Verifier again.

This way we can either get a Driver Verifier generated crash that will name a driver or rule out some of the drivers.

bdfwfpf.sys is from Bitdefender.

What Anti Virus are you using?

All three of the new crashes are the same.

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
read operation which referenced memory
FAILURE_BUCKET_ID:  X64_0xA_nt!ViPendingCompleteAfterWait+49

These are not Driver Verifier generated crashes, and they don't give much info.

Other driver info.
Update your Logitech SetPoint driver/program - 17.6.2009 - out of date.

 

[ThokeB]

I did as you said, and got a load of different kind of crashes.
Driver Verifier had these checked:
View attachment 232034

View attachment 232035

I'll check other drivers now.

EDIT: I also managed to get ntbtlog. It should show all the booted drivers before the crash.

 

[Dave76]

The two new crash dumps are the same as the last ones and not any help.

Your laptop should run with Driver Verifier turned on, it will crash only if there is a driver problem.
In your case the driver is crashing the system when it's trying to boot.

Uncheck about half of the drivers, all the Atheros drivers and the ones above it, then reboot see if it crashes.
Remember the bdfwfpf.sys is from Bitdefender, keep it with the second group.

Then check all the drivers you unchecked and test all the other drivers.

If it boots and runs then it is one of the unchecked drivers causing the problems.

 

[ThokeB]

I checked all the Bitdefender drivers (including the unknown Bitdefender driver), and booted the computer 4 times. There was no crashes.

Next I'll check all the Atheros drivers and after that all the rest.

I did the test with Atheros drivers and I got BSOD right away when booting. Now it's stuck in "initializing disk for crash dump..." and the fan noise is very high.

I'm writing this from other computer

So there's something wrong with Atheros drivers, what should I do to them?

 

[Dave76]

Good news.

Let me know the results.

Edit: just saw your 'Edit'

 

[ThokeB]

Now I'm pinpointing the exact Atheros driver that causes problems. Here's the latest BSOD info so far (if it's of any use at all).

 

[ThokeB]

Found the driver!

btath_lwflt.sys
"Atheros FILTER driver"

I'll reinstall the factory version of the driver (I may need to reinstall all the Atheros drivers).

I'm now checking other drivers. I had also other BSODs than 0x0000000A ones.

I'm also attaching the newest BSOD info as this time it even didn't get stuck in "initializing disk for crash dump" phase in the BSOD screen.

 

[Dave76]

Yes, reinstall all the Atheros drivers.

Both zip file dumps were all the same as the last several crashes.

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Arg1: fffff9800a976ba8, memory referenced
FAILURE_BUCKET_ID:  X64_0xA_nt!ViPendingCompleteAfterWait+49

Not much help and not Driver Verifier induced crashes.


Haven't had much luck deciphering the Event Logs as they are in Finnish.
The last System Event Logs are stopping on Date: 2012-09-08.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.
Check if you are getting new System Event Logs.

If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.

Let me know the progress.