bugcheck 0xC2
in [Windows Servers]
|
From: Clint Bergman on 23 May 2007 12:40 Twice now in 2 months after 3 weeks+ of uptime my server has rebooted with bugcheck 0xC2. WinDebug gives me: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 121a, 0, e7e4b620} Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+477 ) Followup: MachineOwner --------- I'm not sure where to go from here...it's usually easy when the culprit is a driver or program, but what to do when NT kernel is fingered as the culprit? Any help is appreciated, thanks, ~Clint
From: John Toner [MVP] on 23 May 2007 16:17 From windbg help: Bug Check 0xC2: BAD_POOL_CALLER The BAD_POOL_CALLER bug check has a value of 0x000000C2. This indicates that the current thread is making a bad pool request. Cause An invalid pool request has been made by the current thread. Parameter 1 = 0x7 Parameter 2 = Reserved Parameter 3 = Pool header contents Parameter 4 = Address of the block of pool being freed Cause of Error = The current thread attempted to free the pool, which was already freed. Resolving the Problem Activate Driver Verifier to obtain more information about these errors. For details, see the Driver Verifier section of the Windows Driver Kit (WDK). So, if you enable Verifier, you might get have a better idea which driver is causing the issue. Regards, John Visit my blog: http://msmvps.com/blogs/jtoner "Clint Bergman" <clint(a)psd267.wednet.edu> wrote in message news:%23$hcdkVnHHA.3704(a)TK2MSFTNGP02.phx.gbl... Twice now in 2 months after 3 weeks+ of uptime my server has rebooted with bugcheck 0xC2. WinDebug gives me: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 121a, 0, e7e4b620} Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+477 ) Followup: MachineOwner --------- I'm not sure where to go from here...it's usually easy when the culprit is a driver or program, but what to do when NT kernel is fingered as the culprit? Any help is appreciated, thanks, ~Clint
|
Pages: 1 Prev: Windows Server 2000 MMC error Next: Help with a stop message |