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

DVD-R gives blue screen of death Bad_Pool_Header


  • Please log in to reply
4 replies to this topic

#1 HelpJules

HelpJules

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:49 AM

Posted 17 November 2010 - 04:09 PM

I have a Dell Dimension 4700 running Windows XP Professional 2002 SP3 with 512MB RAM. When I put a Maxell DVD-R of photos that a friend burned for me in I immediately get a blue screen of death with the words Bad_Pool_Header. When I turn off the computer it immediately reboots. I haven't had this problem before when inserting other discs or CD-ROMs. I downloaded Debugging Tools and the analysis report is below. Any help would be greatly appreciated.


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


Loading Dump File [C:\WINDOWS\Minidump\Mini111710-08.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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Nov 17 14:08:57.578 2010 (GMT-6)
System Uptime: 0 days 0:19:51.160
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 82f594e8, 82f59500, 1a030001}

Unable to load image SRTSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP.SYS
Probably caused by : SRTSP.SYS ( SRTSP+1c883 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 82f594e8, The pool entry we were looking for within the page.
Arg3: 82f59500, The next pool entry.
Arg4: 1a030001, (reserved)

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


OVERLAPPED_MODULE: Address regions for 'Udfs' and 'kmixer.sys' overlap

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 82f594e8

CUSTOMER_CRASH_COUNT: 8

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: svchost.exe

IRP_ADDRESS: 82c97790

LAST_CONTROL_TRANSFER: from 80551fc5 to 805376ba

STACK_TEXT:
ecccb5d0 80551fc5 00000019 00000020 82f594e8 nt!KeBugCheckEx+0x1b
ecccb620 804f2abf 82f594f0 00000000 00000103 nt!ExFreePoolWithTag+0x2c1
ecccb678 80573848 82c977d0 ecccb6bc ecccb6a8 nt!IopCompleteRequest+0xf4
ecccb6a0 8057a2a0 ffb2b058 80000005 83252cb0 nt!IopSynchronousServiceTail+0xb8
ecccb728 804dd99f 800005a0 ecccb828 e5417260 nt!NtQueryVolumeInformationFile+0x3b8
ecccb728 804e40af 800005a0 ecccb828 e5417260 nt!KiFastCallEntry+0xfc
ecccb7b4 f865750f 800005a0 ecccb828 e5417260 nt!ZwQueryVolumeInformationFile+0x11
ecccb7d4 ec199883 800005a0 ecccb828 e5417260 fltmgr!FltQueryVolumeInformation+0x2f
WARNING: Stack unwind information not available. Following frames may be wrong.
ecccb83c ec1a1c5c e31765f0 00000003 00000000 SRTSP+0x1c883
ecccb880 f864f8ff ecccb89c 00000005 00000003 SRTSP+0x24c5c
ecccb8b4 f864fe86 83301490 00000005 80551005 fltmgr!FltpDoInstanceSetupNotification+0x4b
ecccb914 f8650211 82521858 ffab8a50 00000005 fltmgr!FltpInitInstance+0x272
ecccb984 f865031c 82521858 ffab8a50 00000005 fltmgr!FltpCreateInstanceFromName+0x295
ecccb9ec f8657342 82521858 ffab8a50 00000005 fltmgr!FltpEnumerateRegistryInstances+0xf4
ecccba3c f864e6da ffab8a50 ffaeae50 ffabe018 fltmgr!FltpDoFilterNotificationForNewVolume+0xe4
ecccba70 804e13eb ffb2b058 ffabe008 ffabe008 fltmgr!FltpCreate+0x1f0
ecccba80 805794b6 83289618 825e30ac ecccbc18 nt!IopfCallDriver+0x31
ecccbb60 8056d03b 83289630 00000000 825e3008 nt!IopParseDevice+0xa12
ecccbbd8 805701e7 00000000 ecccbc18 00000040 nt!ObpLookupObjectName+0x53c
ecccbc2c 80579b12 00000000 00000000 bdfd5801 nt!ObOpenObjectByName+0xea
ecccbca8 80579be1 00bdfdb0 00100001 00bdfd60 nt!IopCreateFile+0x407
ecccbd04 80579d18 00bdfdb0 00100001 00bdfd60 nt!IoCreateFile+0x8e
ecccbd44 804dd99f 00bdfdb0 00100001 00bdfd60 nt!NtOpenFile+0x27
ecccbd44 7c90e514 00bdfdb0 00100001 00bdfd60 nt!KiFastCallEntry+0xfc
00bdfdcc 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
SRTSP+1c883
ec199883 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: SRTSP+1c883

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SRTSP

IMAGE_NAME: SRTSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4b85bc4b

FAILURE_BUCKET_ID: 0x19_20_SRTSP+1c883

BUCKET_ID: 0x19_20_SRTSP+1c883

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,230 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:49 AM

Posted 17 November 2010 - 05:20 PM

At first glance...appears to be caused by Symantec, http://www.symantec.com/connect/forums/srtspsys-causes-bsod

If you have the aforementioned product installed...you might try uninstalling it, then reinstalling it...then updating and running a thorough scan.

I tend to be suspicious of problems where it seems that the AV is at fault...I wonder what made it a probloem or what problem it encountered.

Louis

#3 HelpJules

HelpJules
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:49 AM

Posted 17 November 2010 - 10:30 PM

I don't have Symantec installed. I do have Norton. Any chance it could be caused by Norton? I have no idea what else could be causing this.

#4 frankp316

frankp316

  • Members
  • 2,677 posts
  • OFFLINE
  •  
  • Local time:07:49 AM

Posted 18 November 2010 - 05:55 AM

Same thing. Norton is the brand name for Symantec.

#5 HelpJules

HelpJules
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:49 AM

Posted 18 November 2010 - 12:49 PM

Thanks frankp316, I didn't know that. I'll try an uninstall and reinstall. I also tried inserting a CD-RW and didn't have any problems, so it could be the disc isn't compatible with my drive. I've had memory issues with my computer as well this year, so I'm sure it's coming time for an upgrade anyway.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users