Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Crashing Issues


  • Please log in to reply
7 replies to this topic

#1 chased

chased

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 04 November 2007 - 01:10 AM

This might be a common and annoying problem, but their must be somebody who knows..My computer keeps crashing and showing the blue screen. The one that says "bad_pool_id" or something like that. A little bit about my computer. It is a custom PC and I have no friggin idea where it came from, but I believe these are the specs based on what Everest pulls up:

OS: Windows XP professional SP 2
CPU: Intel Pentium IIIE, 800MHz (6 x 133)
Motherboard: MSI 815E(P)T Pro (MS-6337 v5.x) / MS-6337 LE5
Motherboard Chipset: Intel Solano i815E
Memory: 512MB (PC133 SDRAM)
BIOS Type: Award Modular (07/09/01)
Anti-virus program: Panta Antivirus 2008
Firewall: Outpost free firewall

..I can pull up more information if needed. A little more background on the problem. It started about a month ago, and after trying everything possible on the internet to fix it, it never got fixed. So I reinstalled windows (the option that keeps all your files), and sure enough the problem did not go away. So I decided to reinstall windows again, this time instead of installing it from the C drive, I installed it from the disk, enabling me to completely wipe out the C drive and reformat a new drive without keeping any of my files. The installation worked and for an hour or so I thought it actually solved the problem. But sure enough the problem returned. Now, whenever the blue screen appears, I restart and I get a message saying "The system has recovered from a fatal error."
Here are the screenshots of the error details. It identifies two files as the causing trouble, but when I try to browse to those files they don't even exist. Weird.



[attachment=2562:error.jpg]





[attachment=2563:error2.jpg]

BC AdBot (Login to Remove)

 


#2 4ward_tristan

4ward_tristan

  • Members
  • 211 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:beachmere qld aus
  • Local time:05:27 AM

Posted 04 November 2007 - 04:02 AM

what haardware have you tested in your machine???

firstly, create a memtest bootcd and run that for a good 6+ passes - www.memtest.org

next, test your hdd with your manufactures diagnostic utility (post here with brand+model for a link, or check on the manufactures website)

goodluck
=)

#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,271 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:27 PM

Posted 04 November 2007 - 08:14 AM

Can you go into Event Viewer and see if there is more detail on the error message?

I find nothing for bad pool ID either by googling or by going to the MS website. The preponderance of error messages indicate "bad pool caller".

http://search.microsoft.com/results.aspx?q...amp;PageType=99

Louis

#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:03:27 PM

Posted 04 November 2007 - 10:50 AM

Bad Pool Header: http://aumha.org/a/stop.php#0x19
Bad Pool Caller: http://aumha.org/a/stop.php#0xc2

Both are most commonly caused by corrupted device drivers, less often by memory problems Both of these are generally errors with the driver accessing the memory in an unacceptable manner

More about memory allocation here: http://msdn2.microsoft.com/en-us/library/aa489507.aspx

Search your hard drive for files ending in .dmp or .mdmp. If you find them, then analyze them using this link and post the results here for us to have a look at.

http://forums.majorgeeks.com/showthread.php?t=35246

Edited by usasma, 04 November 2007 - 10:52 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 chased

chased
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 04 November 2007 - 01:46 PM

what haardware have you tested in your machine???

firstly, create a memtest bootcd and run that for a good 6+ passes - www.memtest.org

next, test your hdd with your manufactures diagnostic utility (post here with brand+model for a link, or check on the manufactures website)

goodluck


I haven't tested anything yet, but I will run a memtest today to see what it pulls up.

Hdd: Quantum Fireballp AS40.0 (39GB, 7200RPM, Ultra-ATA/100)

I'll check for that Hdd diagnostic utility as well

thanks

#6 chased

chased
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 04 November 2007 - 01:52 PM

Can you go into Event Viewer and see if there is more detail on the error message?

I find nothing for bad pool ID either by googling or by going to the MS website. The preponderance of error messages indicate "bad pool caller".

http://search.microsoft.com/results.aspx?q...amp;PageType=99

Louis


Yes, you are right, it is "bad pool caller." I have some screen shots of the error messages, but for some reason I couldn't figure out how to attach them in a post, I will try to attach them again, but I didn't do it right in my first post.
This is the one error message that I think is the most important:

"The following files will be included in this error report:
C:\DOCUME~1\CHASED~1\LOCALS~1\Temp\WERd61f.dir00\Mini110307-04.dmp
C:\DOCUME~1\CHASED~1\LOCALS~1\Temp\WERd61f.dir00\sysdata.xml"

I've read in forums across the internet that some people just delted there minidump directory and it solved their problem. But these files are going into a directory that doesn't even exist. It must be that they are being deleted when the computer crashes, and when I restart the computer and try to navigate them, they have already been deleted.

#7 chased

chased
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 04 November 2007 - 02:08 PM

Bad Pool Header: http://aumha.org/a/stop.php#0x19
Bad Pool Caller: http://aumha.org/a/stop.php#0xc2

Both are most commonly caused by corrupted device drivers, less often by memory problems Both of these are generally errors with the driver accessing the memory in an unacceptable manner

More about memory allocation here: http://msdn2.microsoft.com/en-us/library/aa489507.aspx

Search your hard drive for files ending in .dmp or .mdmp. If you find them, then analyze them using this link and post the results here for us to have a look at.

http://forums.majorgeeks.com/showthread.php?t=35246


Results from the test on the today's minidump file:


Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini110407-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sun Nov 4 12:00:23.817 2007 (GMT-8)
System Uptime: 0 days 0:28:52.367
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000C5, {e8, 2, 1, 8054b907}



Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+156 )

Followup: Pool_corruption
---------

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 000000e8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8054b907, address which referenced memory

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




BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeferredFreePool+156
8054b907 8913 mov dword ptr [ebx],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8054ba1e to 8054b907

STACK_TEXT:
f8996a5c 8054ba1e 81ee2a40 00000000 f8996afc nt!ExDeferredFreePool+0x156
f8996a9c f83ab6ad 81ee28f0 00000000 f8996afc nt!ExFreePoolWithTag+0x489
f8996ab0 f83d8517 81ee28f0 82368260 e15cf918 Ntfs!NtfsFreeEresource+0x76
f8996ad4 f83ab57a 81d4a778 f8996afc f8996b07 Ntfs!NtfsDeleteFcb+0x67
f8996b20 f83ccd00 81d4a778 82368100 e1129cc8 Ntfs!NtfsTeardownFromLcb+0x1fd
f8996b78 f83a7759 81d4a778 e1129d90 e1129f28 Ntfs!NtfsTeardownStructures+0x125
f8996ba4 f83ca6eb 81d4a778 01129d90 e1129f28 Ntfs!NtfsDecrementCloseCounts+0x9e
f8996c28 f83ca48a 81d4a778 e1129d90 e1129cc8 Ntfs!NtfsCommonClose+0x397
f8996cc8 804e3d77 82368020 81d00e28 82374a58 Ntfs!NtfsFsdClose+0x21f
f8996cd8 f8449459 f8996d28 804e3d77 82343bc8 nt!IopfCallDriver+0x31
f8996ce0 804e3d77 82343bc8 81d00e28 81d00e28 sr!SrPassThrough+0x31
f8996cf0 8056afec 82236ba8 00000000 00000000 nt!IopfCallDriver+0x31
f8996d28 80563ff6 00236bc0 82236ba8 00000000 nt!IopDeleteFile+0x132
f8996d44 804e3c55 82236bc0 00000000 806ed03c nt!ObpRemoveObjectRoutine+0xdf
f8996d68 804f736e 8055f1b8 82236af8 806ed070 nt!ObfDereferenceObject+0x5f
f8996d8c 8050087f e2337e40 00000000 823c4520 nt!MiSegmentDelete+0xdd
f8996dac 8057dfed 00000000 00000000 00000000 nt!MiDereferenceSegmentThread+0x9e
f8996ddc 804fa477 805007e9 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+156
8054b907 8913 mov dword ptr [ebx],edx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExDeferredFreePool+156

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+156

BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+156

Followup: Pool_corruption
---------

#8 chased

chased
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:02:27 PM

Posted 04 November 2007 - 02:12 PM

what haardware have you tested in your machine???

firstly, create a memtest bootcd and run that for a good 6+ passes - www.memtest.org

next, test your hdd with your manufactures diagnostic utility (post here with brand+model for a link, or check on the manufactures website)

goodluck


I haven't tested anything yet, but I will run a memtest today to see what it pulls up.

Hdd: Quantum Fireballp AS40.0 (39GB, 7200RPM, Ultra-ATA/100)

I'll check for that Hdd diagnostic utility as well

thanks


I don't believe there is a test utility on the Quantum website, but is there another free program that I can use to test the Hdd?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users