Bug #42656 Windows Stop Error
Submitted: 6 Feb 2009 17:32 Modified: 13 Feb 2009 22:05
Reporter: Jaco Eygelaar Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.1.31 OS:Microsoft Windows (Server 2003 x64)
Assigned to: CPU Architecture:Any
Tags: blue screen, stop error

[6 Feb 2009 17:32] Jaco Eygelaar
Description:
Our production server runs under very high CPU usage. We get 3 to 6 blue screens per day.

SERVER MODEL: HP Proliant DL360 G5
OPERATING SYSTEM:  Windows Server 2003 Standard x64
PROCESSOR:  Intel Xeon E5405 Quad-Core (10Ghz)
MEMORY:          4 GB RAM
HARDDRIVE:    2 x 73GB SAS HDD RAID 1

Using WinDBG, MEMORY.DMP shows the following:

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 000000000000121a, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffffadfffac0010, Address of the block of pool being deallocated

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

Page cc404 not present in the dump file. Type ".hh dbgerr004" for details
Page cc592 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffde018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffde018).  Type ".hh dbgerr001" for details

POOL_ADDRESS:  fffffadfffac0010 Nonpaged pool expansion

BUGCHECK_STR:  0xc2_7

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  mysqld.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800011a9769 to fffff8000102e890

STACK_TEXT:  
fffffadf`8cacf948 fffff800`011a9769 : 00000000`000000c2 00000000`00000007 00000000`0000121a 00000000`00000000 : nt!KeBugCheckEx
fffffadf`8cacf950 fffff800`0107877a : fffffadf`9ca8b8f0 fffffadf`968178e0 fffffadf`ffac0010 00000000`00000004 : nt!ExFreePoolWithTag+0x401
fffffadf`8cacfa10 fffff800`0127ef5a : fffffadf`96816fe0 fffffadf`8cacfcf0 00000000`00000000 fffffadf`ffb3f330 : nt!IopAllocateIrpPrivate+0x13e
fffffadf`8cacfa70 fffff800`0127ec16 : 00000000`00000000 00000000`00295e9c 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x6fe
fffffadf`8cacfb90 fffff800`0102e33d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffffadf`8cacfc00 00000000`77ef0a5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`5653f8f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ef0a5a

STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePoolWithTag+401
fffff800`011a9769 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExFreePoolWithTag+401

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  48a2ca8c

FAILURE_BUCKET_ID:  X64_0xc2_7_nt!ExFreePoolWithTag+401

BUCKET_ID:  X64_0xc2_7_nt!ExFreePoolWithTag+401

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

How to repeat:
In our case, this happens by itself at seemingly random intervals.  I cannot trigger it specifically.
[6 Feb 2009 17:40] Miguel Solorzano
Thank you for the bug report. Could you please print here the contents of log err file after a crash?. Thanks in advance.
[6 Feb 2009 17:50] Jaco Eygelaar
Thanks for the quick response.

I cannot find an .err file.  Ive done a quick google and cannot find a HOSTNAME.err file, and also not a folder called data, where its supposed to be.

Can you point me in the right direction please.
[6 Feb 2009 18:14] Vladislav Vaintroub
Actually, user mode code which is MySQL cannot be reason for a blue screen.
I'd first suspect a buggy driver then Windows itself.
[6 Feb 2009 18:19] Vladislav Vaintroub
After reading "analyze -v" with a bit  more attention, found

DEFAULT_BUCKET_ID:  DRIVER_FAULT

I guess HP can help more then MySQL here.
[6 Feb 2009 18:27] Jaco Eygelaar
Ok thanks for the help.  I will contact HP, and check driver versions.
[6 Feb 2009 19:03] Miguel Solorzano
Thank you for the feedback. Please re-open this bug report when you have information about your hardware. Thanks in advance.
[13 Feb 2009 21:49] Jaco Eygelaar
Just some quick feedback.  All drivers and other HP software was updated and the server is now stable.  Unfortunately I cannot pinpoint exactly what was causing the problem.  (Its a managed server and their tech staff did all the updates at once)

Thanks for the help and quick response.  Much appreciated.
[13 Feb 2009 22:05] Miguel Solorzano
Thank you for the feedback. According last comment closing this bug report.