I keep having issues with Vista. I either get bad_pooler_caller or an IRQ error. I reinstalled Vista and updated to service pack 1.



here is the newest error maybe I can get some help, been an on going issue.
I can post a dxdiag also if that will help.

oblem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Files that help describe the problem (some files may no longer be available)
Mini041009-01.dmp
sysdata.xml
Version.txt
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode: c2
BCP1: 0000000000000007
BCP2: 000000000000110B
BCP3: 0000000000000000
BCP4: FFFFFA8004D3F310
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Server information:

Originally Posted by pawdaw

I
Mini041009-01.dmp

You have to debug this file
How to read the small memory dump files that Windows creates for debugging

The better way will be if you pack this file and attache to post

Originally Posted by pawdaw

I keep having issues with Vista. I either get bad_pooler_caller or an IRQ error. I reinstalled Vista and updated to service pack 1.



here is the newest error maybe I can get some help, been an on going issue.
I can post a dxdiag also if that will help.

oblem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Files that help describe the problem (some files may no longer be available)
Mini041009-01.dmp
sysdata.xml
Version.txt
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode: c2
BCP1: 0000000000000007
BCP2: 000000000000110B
BCP3: 0000000000000000
BCP4: FFFFFA8004D3F310
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Server information:

0xC2, or BAD_POOL_CALLER is a driver error, and the first parameter
indicates an attempt to free memory that was already released. This usually
occurs when a driver file is corrupt or not compatible with the operating system.

Self Diagnostic:
ESET SysInspector

Free debugger tool:
Reading BSOD crash files

Looks like a AMD live Away driver was missing. I downloaded the driver, but can't confirm if it is working as intended.

Thanks for the help. I tired to do the stuff you told me to, but it is way over my head!