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

BAD SPOOL HEADER


  • Please log in to reply
3 replies to this topic

#1 JR5

JR5

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 10 January 2010 - 01:18 PM

Hello. I read with great interest the post listed on 10/23/08 from usasma about how to receive help diagnosing Blue Srceens and Window crashes. I have been receiving the BSOD every time I reformat a DVD. The message I get is a BAD_SPOOL_ERROR. I followed the advice on the aforementioned post and downloaded and ran the Microsfot Debugging Tool for Windows which is shown below. As usasma notes in the post, I have pasted the Debugging Tools window below. My system is as follows:

Dell 8400 MCE
Windows XP Media Center 2005 Edition
NEC 16x CD/DVD ROM

I would like any information on how to correct this BSOD so I can burn DVD'd after reformatting them. Thanks.

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


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

WARNING: Whitespace at end of path element
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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sat Jan 2 17:18:35.078 2010 (GMT-5)
System Uptime: 0 days 9:44:12.792
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
............................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 85822ef0, 85822f08, 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+1c783 )

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

0: 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: 85822ef0, The pool entry we were looking for within the page.
Arg3: 85822f08, The next pool entry.
Arg4: 1a030001, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 85822ef0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: tfswctrl.exe

IRP_ADDRESS: 86e107c0

LAST_CONTROL_TRANSFER: from 80551fc5 to 8053767a

STACK_TEXT:
ab0495d0 80551fc5 00000019 00000020 85822ef0 nt!KeBugCheckEx+0x1b
ab049620 804f2a9f 85822ef8 00000000 00000103 nt!ExFreePoolWithTag+0x2c1
ab049678 805707d9 86e10800 ab0496bc ab0496a8 nt!IopCompleteRequest+0xf4
ab0496a0 8057ca50 868a95b8 80000005 84a57028 nt!IopSynchronousServiceTail+0xb8
ab049728 804dd99f 8000123c ab049828 e3a96a58 nt!NtQueryVolumeInformationFile+0x3b8
ab049728 804e408f 8000123c ab049828 e3a96a58 nt!KiFastCallEntry+0xfc
ab0497b4 f76ce50f 8000123c ab049828 e3a96a58 nt!ZwQueryVolumeInformationFile+0x11
ab0497d4 aa047783 8000123c ab049828 e3a96a58 fltmgr!FltQueryVolumeInformation+0x2f
WARNING: Stack unwind information not available. Following frames may be wrong.
ab04983c aa04fb5c e3626540 00000003 00000000 SRTSP+0x1c783
ab049880 f76c68ff ab04989c 00000005 00000003 SRTSP+0x24b5c
ab0498b4 f76c6e86 84865938 00000005 80551005 fltmgr!FltpDoInstanceSetupNotification+0x4b
ab049914 f76c7211 8483aa48 84534c28 00000005 fltmgr!FltpInitInstance+0x272
ab049984 f76c731c 8483aa48 84534c28 00000005 fltmgr!FltpCreateInstanceFromName+0x295
ab0499ec f76ce342 8483aa48 84534c28 00000005 fltmgr!FltpEnumerateRegistryInstances+0xf4
ab049a3c f76c56da 84534c28 87368d80 84404460 fltmgr!FltpDoFilterNotificationForNewVolume+0xe4
ab049a70 804e13d9 868a95b8 84404450 84404450 fltmgr!FltpCreate+0x1f0
ab049a80 8057bbed 872de510 87361c24 ab049c18 nt!IopfCallDriver+0x31
ab049b60 8056d03b 872de528 00000000 87361b80 nt!IopParseDevice+0xa12
ab049bd8 80570358 00000000 ab049c18 00000040 nt!ObpLookupObjectName+0x53c
ab049c2c 8057c246 00000000 00000000 000ec001 nt!ObOpenObjectByName+0xea
ab049ca8 8057c315 0012de28 00100001 0012ddd8 nt!IopCreateFile+0x407
ab049d04 8057c4c3 0012de28 00100001 0012ddd8 nt!IoCreateFile+0x8e
ab049d44 804dd99f 0012de28 00100001 0012ddd8 nt!NtOpenFile+0x27
ab049d44 7c90e514 0012de28 00100001 0012ddd8 nt!KiFastCallEntry+0xfc
0012de44 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
SRTSP+1c783
aa047783 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: SRTSP+1c783

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SRTSP

IMAGE_NAME: SRTSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a8e43f0

FAILURE_BUCKET_ID: 0x19_20_SRTSP+1c783

BUCKET_ID: 0x19_20_SRTSP+1c783

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

0: kd> lmvm SRTSP
start end module name
aa02b000 aa082000 SRTSP T (no symbols)
Loaded symbol image file: SRTSP.SYS
Image path: SRTSP.SYS
Image name: SRTSP.SYS
Timestamp: Fri Aug 21 02:51:28 2009 (4A8E43F0)
CheckSum: 0005D30F
ImageSize: 00057000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm SRTSP
start end module name
aa02b000 aa082000 SRTSP T (no symbols)
Loaded symbol image file: SRTSP.SYS
Image path: SRTSP.SYS
Image name: SRTSP.SYS
Timestamp: Fri Aug 21 02:51:28 2009 (4A8E43F0)
CheckSum: 0005D30F
ImageSize: 00057000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm SRTSP
start end module name
aa02b000 aa082000 SRTSP T (no symbols)
Loaded symbol image file: SRTSP.SYS
Image path: SRTSP.SYS
Image name: SRTSP.SYS
Timestamp: Fri Aug 21 02:51:28 2009 (4A8E43F0)
CheckSum: 0005D30F
ImageSize: 00057000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

BC AdBot (Login to Remove)

 


#2 OldGrumpyBastard

OldGrumpyBastard

  • Members
  • 781 posts
  • OFFLINE
  •  
  • Location:"Way South of 'da Bridge"
  • Local time:03:48 AM

Posted 10 January 2010 - 01:52 PM

Bug Check points to Symatec Anti-Virus Driver as the probable cause:

SRTSP.SYS http://www.greatis.com/appdata/a/s/srtsp.sys.htm

Process involved CD Packet writing software:

tfswctrl.exe http://www.glaryutilities.com/startuplibra...swctrl.exe.html
Does this look like an OldGrumpyBastard or what?

#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,558 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:48 AM

Posted 10 January 2010 - 02:32 PM

I would uninstall...then reinstall/update the Symantec software.

Have you experienced any problem burning disks?

Louis

#4 JR5

JR5
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 10 January 2010 - 04:12 PM

Thank you both. I will uninstall and reinstall the Symantec Anti-Virus software. I just updated it about a month ago so maybe that is the problem.

I am not having any trouble burning disks.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users