UNSOLVED

tzouvar

updated

9 years ago

T

tzouvar

12 Posts

0

1745

April 28th, 2017 04:00

BSOD

Hello, I am getting very often blue screens with the code BAD_POOL_CALLER

any ideas please?

  • speedstep

    11 Legend

    •

    46969 Posts

    1105

    0

    Posted April 28th, 2017 04:00

    BAD_POOL_CALLER bug check has a value of 0x000000C2

     In particular, for situations with memory pool corruption, run the Windows Memory Diagnostics tool, to try and isolate the physical memory as a cause.

    If its not bad ram its a driver. For more information, see Driver Verifier.

    BAD_POOL_CALLER Parameters

    Parameter 1 indicates the type of violation.

    Parameter 1 Parameter 2 Parameter 3 Parameter 4 Cause of Error

    0x00

    0

    Pool type

    Pool tag

    The current thread requested a zero-byte pool allocation.

    0x01,

    0x02,

    0x04

    Pointer to pool header

    First part of pool header contents

    0

    The pool header has been corrupted.

    0x06

    Reserved

    Pointer to pool header

    Pool header contents

    The current thread attempted to free the pool, which was already freed.

    0x07

    Reserved

    Pool header contents

    Address of the block of pool being freed

    The current thread attempted to free the pool, which was already freed.

    0x08

    Current IRQL

    Pool type

    Size of allocation, in bytes

    The current thread attempted to allocate the pool at an invalid IRQL.

    0x09

    Current IRQL

    Pool type

    Address of pool

    The current thread attempted to free the pool at an invalid IRQL.

    0x0A

    Address of pool

    Allocator's tag

    Tag being used in the attempted free

    The current thread attempted to free pool memory by using the wrong tag.

    (The memory might belong to another component.)

    0x0B,

    0x0C,

    or 0x0D

    Address of pool

    Pool allocation's tag

    Bad quota process pointer

    The current thread attempted to release a quota on a corrupted pool allocation.

    0x40

    Starting address

    Start of system address space

    0

    The current thread attempted to free the kernel pool at a user-mode address.

    0x41

    Starting address

    Physical page frame

    Highest physical page frame

    The current thread attempted to free a non-allocated nonpaged pool address.

    0x42

    or 0x43

    Address being freed

    0

    0

    The current thread attempted to free a virtual address that was never in any pool.

    0x44

    Starting address

    Reserved

    0

    The current thread attempted to free a non-allocated nonpaged pool address.

    0x46

    Starting address

    0

    0

    The current thread attempted to free an invalid pool address.

    0x47

    Starting address

    Physical page frame

    Highest physical page frame

    The current thread attempted to free a non-allocated nonpaged pool address.

    0x48

    Starting address

    Reserved

    Reserved

    The current thread attempted to free a non-allocated paged pool address.

    0x50

    Starting address

    Start offset, in pages, from beginning of paged pool

    Size of paged pool, in bytes

    The current thread attempted to free a non-allocated paged pool address.

    0x60

    Starting address

    0

    0

    The current thread attempted to free an invalid contiguous memory address.

    (The caller of MmFreeContiguousMemory is passing a bad pointer.)

    0x99

    Address that is being freed

    0

    0

    The current thread attempted to free pool with an invalid address.

    (This code can also indicate corruption in the pool header.)

    0x9A

    Pool type

    Number of bytes requested

    Pool tag

    The current thread marked an allocation request MUST_SUCCEED.

    (This pool type is no longer supported.)

    0x9B

    Pool type

    Number of bytes requested

    Caller's address

    The current thread attempted to allocate a pool with a tag of 0

    (This would be untrackable, and possibly corrupt the existing tag tables.)

    0x9C

    Pool type

    Number of bytes requested

    Caller's address

    The current thread attempted to allocate a pool with a tag of "BIG".

    (This would be untrackable and could possibly corrupt the existing tag tables.)

    0x9D

    Incorrect pool tag used

    Pool type

    Caller's address

    The current thread attempted to allocate a pool with a tag that does not contain any letters or digits. Using such tags makes tracking pool issues difficult.

    0x41286

    Reserved

    Reserved

    Start offset from the beginning of the paged pool, in pages

    The current thread attempted to free a paged pool address in the middle of an allocation.

  • tzouvar

    12 Posts

    1123

    0

    Posted April 28th, 2017 05:00

    sorry i didn't mention that, I have the 15R3 i7700 with 1070

    diags did not show everything wrong

  • AAA737flyer

    2 Intern

    •

    757 Posts

    1105

    2

    Posted April 28th, 2017 05:00

    I'm going to take a wild guess that you have a laptop, maybe a R2?

    Select the link below and check the BSOD analyzer.

    http://www.dell.com/support/home/us/en/19/product-support/product/alienware-15-r2/diagnose

  • AAA737flyer

    2 Intern

    •

    757 Posts

    1123

    0

    Posted April 28th, 2017 06:00

    It would also help if you gave us a little background.

    What device did you recently install that may have created this issue or what software have you updated or installed. Have you attempted a restore point, etc...

    If you have attempted overclocking I would suggest you restore GPU and BIOS to defaults and check system stability. 

  • AAA737flyer

    2 Intern

    •

    757 Posts

    1123

    2

    Posted April 28th, 2017 06:00

    Also, if you are working with a HDD, schedule a "chkdsk". Also using administrator rights run sfc /scannow. (space between sfc and /scannow

  • tzouvar

    12 Posts

    1123

    0

    Posted April 28th, 2017 10:00

    no nothing like that, is a new machine. first bsod was at day one. sometimes I get blue screens whet I just scroll down at chrome, nothing much. 

  • AAA737flyer

    2 Intern

    •

    757 Posts

    1123

    2

    Posted April 28th, 2017 10:00

    did you run chkdsk an sfc /scannow..........

  • tzouvar

    12 Posts

    1123

    0

    Posted April 28th, 2017 11:00

    i did all system checks from support assist....nothing came up

  • AAA737flyer

    2 Intern

    •

    757 Posts

    1123

    0

    Posted April 28th, 2017 12:00

    chkdsk and sfc /scannow correct damaged sectors and repair Windows operating system. All of which can cause sporatic BSOD and freezes. Support Assist does not apply in this instance.

    Good luck.

  • tzouvar

    12 Posts

    334

    0

    Posted April 29th, 2017 03:00

    I did it...Now we wait and see... thank you!!