0xc2 - 0x7 BSOD die plotseling optreed Bad pool caller

[marco282]

Hallo,

Sinds vandaag word ik geplaagt door random BSOD's, in eerste instantie dacht ik aan mijn nieuwe werkgeheugen wat ik er gister in gedaan heb, maar ik heb er echter vandaag pas last van. Heb ook vandaag wat gedaan met drivers voor Storage controllers enzo ennog wat dingen.

Maar helaas verhelpt dat mijn probleem niet.
Ik heb de minidump gecheckt en daar staat dit bij

[I]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: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffffa801b7c1b70, Address of the block of pool being deallocated



ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002e0f000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

POOL_ADDRESS:  fffffa801b7c1b70 

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fb260e to fffff80002e7f700

STACK_TEXT:  
fffff880`0afc7ec8 fffff800`02fb260e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00000000 : nt+0x70700
fffff880`0afc7ed0 00000000`000000c2 : 00000000`00000007 00000000`00001097 00000000`00000000 fffffa80`1b7c1b70 : nt+0x1a360e
fffff880`0afc7ed8 00000000`00000007 : 00000000`00001097 00000000`00000000 fffffa80`1b7c1b70 fffffa80`0aa28b40 : 0xc2
fffff880`0afc7ee0 00000000`00001097 : 00000000`00000000 fffffa80`1b7c1b70 fffffa80`0aa28b40 00000003`00000004 : 0x7
fffff880`0afc7ee8 00000000`00000000 : fffffa80`1b7c1b70 fffffa80`0aa28b40 00000003`00000004 fffff800`0b6ba301 : 0x1097


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt+70700
fffff800`02e7f700 48894c2408      mov     qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt+70700

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntoskrnl.exe

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner[/I]


Echter krijg ik niet alle info van debug tracker want ik krijg veel errors hiervan 



[I]
 Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***             [/I]

Heeft iemand ergens ervaring hiermee? want hij zegt dat het door de nt kernel word veroorzaakt en niet door een driver, dus beetje vreemd.

 

[Mik Zjegger]

Hoi,
lees dit even over jouw Bug_Check_Code.
Meer nuttige info:
http://support.microsoft.com/kb/265879
Doe een sfc /scannow How To