Vista BSOD when opening a movie file

**Epsilonn** · 23-02-2009

Hi all, I'm confused about something. I haven't had any problems with my computer for a year now having in consideration that it is just one year old http://forums.techarena.in/images/smilies/rolleyes.gif. However, today, when i just opened a movie file, i received a BSOD. Afther debugging it with Windbg, i got the following report:

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000b, type of pool violation the caller is guilty of.
Arg2: fffff8800e2c8190
Arg3: 00000000050c0119
Arg4: fffff8800e2c81d0

Debugging Details:
------------------

BUGCHECK_STR: 0xc2_b

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002745052 to fffff80002665350

STACK_TEXT:
fffffa60`06346618 fffff800`02745052 : 00000000`000000c2 00000000`0000000b fffff880`0e2c8190 00000000`050c0119 : nt!KeBugCheckEx
fffffa60`06346620 fffffa60`03829663 : fffff880`0b379ae0 00000000`00000000 fffffa80`05f8d000 fffffa80`0884f7e0 : nt!ExFreePool+0x520
fffffa60`063466d0 fffff880`0b379ae0 : 00000000`00000000 fffffa80`05f8d000 fffffa80`0884f7e0 00000000`00000002 : atikmdag+0x26663
fffffa60`063466d8 00000000`00000000 : fffffa80`05f8d000 fffffa80`0884f7e0 00000000`00000002 fffffa60`0380b6b6 : 0xfffff880`0b379ae0

STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+26663
fffffa60`03829663 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: atikmdag+26663

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 496d7660

FAILURE_BUCKET_ID: X64_0xc2_b_atikmdag+26663

BUCKET_ID: X64_0xc2_b_atikmdag+26663

Followup: MachineOwner
---------

1: kd> lmvm atikmdag
start end module name
fffffa60`03803000 fffffa60`03d32000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Wed Jan 14 07:21:36 2009 (496D7660)
CheckSum: 004E33B4
ImageSize: 0052F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

The drivers and all my programs are updated.
I would like to understand this things within the report.
P.S. I have Vista x64, Q6600, Sapphire Ati HD4870, 2xST3500320AS RAID 0, Foxconn P35a-s, 4x1 Gb OCZ@667 Gold Edition.
Thanks in advance.

**Kirtikumar** · 24-02-2009

BAD_POOL_CALLER means bad RAM in my experience - try downloading memtest and test each stick of RAM individually.

It can also mean bad drivers, but since it's happening from the windows boot CD, I don't think that's the problem.

Once you can get past that, you can check this instruction http://support.microsoft.com/?kbid=307545

Config/system is a registry file, so the above instructions should work to recover it.
also go through this
http://support.microsoft.com/kb/310527
http://support.microsoft.com/kb/258069

**Solomon** · 24-02-2009

All four of your minidumps are C2 errors where a kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.

Over and over your minidumps read various modules were started but symbols could not beloaded for a slew of your processes.

Three of your four minidumps cited a347bus.sys. Do your have Alcohol 120% installed? This driver is a plug and play BIOS extension and it is noted for causing conflicts.

If you have corrupted memory as kimsland suspects then there is little wonder you are having so many BSODs. It will wreack havoc.

**RichiRich** · 24-02-2009

This is a hard one.

To resolve this problem provide some information about your system.

What SP version do you use?
What EWF QFE's do you use?
What BIOS, platform, processor?
What third-party drivers do you use?

Regards

**Epsilonn** · 24-02-2009

Thanks for the replies but someone in other forum wrote that there could be a conflict between dwm.exe and the ati driver. But I have had Catalyst 9.1 for three weeks with no problem and now I am curious why this BSOD occured only once in all this time providing the fact that I just opened a movie file right before the BSOD occurence. What do you think about this?
BTW, I use Vista SP1 and all my drivers including bios are updated.