Client has a Macbook, running bootcamp with Windows Vista, SP2. Client is using eSet NOD, versions as follows:

Nod 32 version 4.2.58.3. It also says installed components are:
Virus signature database: 5921 (20110302)
Update module: 1031 (20091029)
Antivirus and antispyware scanner module: 1296 (20110301)
Advanced heuristics module: 1115 (20101116)
Archive support module: 1125 (20110202)
Cleaner module: 1050 (20101207)
Anti-Stealth support module: 1024 (20101227)
SysInspector module: 1217 (20100907)
Self-defense support module : 1018 (20100812)
Real-time file system protection module: 1004 (20100727)

The computer is randomly generating BSODs, and the Bugcheck event in the event log is 0x000000d1. Windows Error Lookup Tool reports this as follows:

C:\err\Err>err 0xd1
# for hex 0xd1 / decimal 209 :
  DRIVER_IRQL_NOT_LESS_OR_EQUAL                                 bugcodes.h
  SQL_209_severity_16                                           sql_err
# Ambiguous column name '%.*ls'.
  ERROR_INVALID_SIGNAL_NUMBER                                   winerror.h
# The signal being posted is not correct.
# 3 matches found for "0xd1"

We know that it's not a SQL Error, because there is no SQL components on this computer. That left me with Driver_IRQL_Not_LesS_Or_Equal.

A dive into the dump file reports the faulting driver as EAMONM.SYS - more research reports this as belonging to eSet NOD. Research has immediately turned up suggestions that it is related to Windows Vista SP2, with some versions of eSet NOD.

• Install an updated version of NOD (to 4.2.71)
• Ensure all hardware drivers are up to date

The BSOD was resolved by upgrading NOD to the most recent version.

My post on WildersSecurity about this