Page 1 of 1

BC_Bluetooth Verifier Fault BSOD

Posted: Thu Aug 19, 2010 8:57 pm
by hellosailor
I've been getting BSODs with that error message pretty regularly (not always, but often enough to be a problem now) when I print to an HP Photosmart printer that's on Bluetooth. (I use BT for the printer because my WiFi network connection sometimes is 2.5GHz, sometimes 5GHz, and the printer queues can't jump with that.)

PCDoctor says the hardware is good; the BT drivers, BIOS and OS are fully up to date, and Lenono is sending a new BT radio under warranty because "sometimes the diagnostics don't find all the problems." But, it really feels like a software issue, a driver conflict trouncing on memory in the usual BSOD way.

Anyone have any thoughts about chasing this down? I just don't expect a new BT radio to solve a "Verifier Fault" that sounds like a software process to me. Lenono weren't even interested in the minidump logs, I don't think they've got a clue as to what it means.

Re: BC_Bluetooth Verifier Fault BSOD

Posted: Thu Aug 19, 2010 9:49 pm
by Harryc

Re: BC_Bluetooth Verifier Fault BSOD

Posted: Fri Aug 20, 2010 3:06 pm
by hellosailor
Thanks, harry, I never knew a Verifier was in XP, much less that it is still here in Vista. Doesn't help me much yet--because I'll have to figure out the name and location of HP's BT drivers before I can run it on them.

But, I also found a thread about the same error message in the HP forums. An unapologetic HP rep was telling a victim, ergh, customer, to try installing new drivers, which is what I also did yesterday. this afternoon my BT radio was replaced under warranty (very generously, since the old one passed diagnostics!) so...I'm as updated as can be and we'll see what else breaks.

Just to add insult to injury, since I rarely shut my computer (I suspend it) it has decided to take FOREVER to shutdown now. As in, after five clocked minutes and no more drive activity, I, ahem, pulled the [censored] plugs. Five minutes is just about 4:30 beyond reasonable, wouldn't you say? For a machine with no active tasks and nothing to shut down?