Windows 7: Bad_pool_caller (BSOD)

LiPoUrR · 11 Aug 2010

Hi guys i have problem with my pc....

my pc shows bsod with message bad_pool_caller

i can use my pc but this bsod MUST happen every day! what to do

Tews · 11 Aug 2010

Blue Screen of Death (BSOD) Posting Instructions

LiPoUrR · 11 Aug 2010

is it ok now?

Tews · 11 Aug 2010

There were no .dmp files included ... please navigate to c:/windows/minidump and zip up the .dmp files and attach them to your next post..

LiPoUrR · 11 Aug 2010

omg -.- sry man.... here u go

ttran · 11 Aug 2010

First of all, ARE YOU OVERCLOCKING ANYTHING? If so, please go to BIOS and reset everything to optimal default setting please. The whole bunch of stop codes make me think about overclocking.

I suspect your graphic card because dxgmms1.sys and atikmdag.sys (graphic card drivers) was blamed in the DMP. First thing to try is to re-install the driver.When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

The chance that re-install driver fix the problem is very small, so in my experience, I would recommend you to see if you can borrow another graphic card and test on your system.

Also, please update this driver or remove it, it's too old and system can't run stably with its existence.

Code:

giveio   giveio.sys   Thu Apr 04 09:33:25 1996 (316334F5)

It is ADC Analyzer/SwiftForth/Disspy - ?SpeedFan?
Info only (½ way down page) - I/O Port Programming with Delphi and NT

Run a check disk please:
Disk Check

BUGCHECK SUMMARY:

Code:

BugCheck 1000007E, {c000001d, 82a33286, 8d117900, 8d1174e0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck 21, {0, 0, 400000, 1a9324}

Probably caused by : ntkrpamp.exe ( nt!PspReturnQuota+11f )

Followup: MachineOwner
---------
BugCheck 24, {1904fb, 8d0ca8cc, 8d0ca4b0, 8b03e9e7}

Probably caused by : Ntfs.sys ( Ntfs!NtfsUninitializeNtfsMcb+42 )

Followup: MachineOwner
---------
BugCheck 1000008E, {c0000005, 914b0af0, 8eb02618, 0}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : atikmdag.sys ( atikmdag+2a5af0 )

Followup: MachineOwner
---------
BugCheck 10E, {1f, 899f8008, 0, b145}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+de )

Followup: MachineOwner
---------
BugCheck 18, {0, 87a25f02, 2, ffffffff}

Probably caused by : ntkrpamp.exe ( nt!ObfDereferenceObjectWithTag+4b )

Followup: MachineOwner
---------
BugCheck 1000008E, {c0000005, 82c96593, 8c4dab44, 0}

GetPointerFromAddress: unable to read from 82bb9718
Unable to read MiSystemVaType memory at 82b99160
GetPointerFromAddress: unable to read from 82bb9718
Unable to read MiSystemVaType memory at 82b99160
GetPointerFromAddress: unable to read from 82bb9718
Unable to read MiSystemVaType memory at 82b99160
Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+28 )

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

Let us know if you need help

Tuan

Jonathan_King · 11 Aug 2010

If that doesn't work, please enable driver verifier: Driver Verifier - Enable and Disable

LiPoUrR · 11 Aug 2010

i did overclocked my cpu and gpu.... i reset it to default now, i will answer if i solve problem

can overheating cause this probem? i had 1 pc that shows bsod when he overheats! my cpu is 40-45c and gpu is 70-75c is that too much???

Jonathan_King · 11 Aug 2010

GPU may be a bit high, but it's probably okay.

Good thing you reset your GPU to stock speeds, overclocking can cause BSODs.

LiPoUrR · 11 Aug 2010

i had win xp, and i didnt had any problems with it.... but than i switched to win 7, and than bsod started appearing!!! i tried repair, but it didnt help!!! if nothing of this help, i will format my hdd, and install new os....

Windows 7: Bad_pool_caller (BSOD)

Bad_pool_caller (BSOD) problems?