Aller au contenu principal

tdrpm258.sys seeems to cause BSOD BAD_POOL_HEADER STOP:0x19(0x20

Thread needs solution

I was getting BSOD BAD_POOL_HEADER STOP:0x19(0x20,0x85ECBDE0....and have eventually tracked it down to ATI HOME 2010 7046. After installing the ADD Home 2011 these BSOD's increased.

Looking at the mini-dumps it referred to an error with "tdrpm258.sys"

Uninstalled both acronis programs and the BSOD's seemed to have stopped. Is there a way of installing these acronis products without the offending" tdrpm258.sys" (i believe is try and decide).

0 Users found this helpful

Steve,

To confirm it is the T&D file that is causing the problem, it can be disabled in Services.msc (Win + R button - type in services.msc.

Have you checked out this post and see if it also works for you?

Hi Colin, I couldn't find the service? I just thought it was part of a main acronis services? Maybe that was the problem it wasn't installed properly.

What is t&d 's service name. I will reinstall tomorrow.

Hi All, reinstalled both acronis products. ADD Home 2011 had a problem installing (acronis monitor was running) but installed after clicking continue.
NEW BSOD when closing ADD:
##########################################################################
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

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

Symbol search path is: C:\symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e01000 PsLoadedModuleList = 0x82f49810
Debug session time: Thu Sep 16 10:34:01.879 2010 (UTC + 1:00)
System Uptime: 0 days 0:13:05.923
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
......
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00001001, Verifier predicted potential deadlock.
Arg2: adf94fe0, Lock address.
Arg3: 90badbe0, Verifier internal data.
Arg4: 00000000

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

*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys

BUGCHECK_STR: 0xc4_1001

DRIVER_DEADLOCK: Deadlock detection not initialized

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 83135f1f to 82eddd10

STACK_TEXT:
8a5aaac4 83135f1f 000000c4 00001001 adf94fe0 nt!KeBugCheckEx+0x1e
8a5aaae4 83141522 adf94fe0 83146d40 00000000 nt!VerifierBugCheckIfAppropriate+0x30
8a5aaaf8 831406ca 90badbe0 00000000 90badbe0 nt!ViDeadlockReportIssue+0x2f
8a5aab1c 83140db6 adf94fe0 00000001 00000001 nt!ViDeadlockAnalyze+0x1cb
8a5aabac 8313ce95 adf94fe0 00000001 8b8a4388 nt!VfDeadlockAcquireResource+0x2da
8a5aabd4 8313b9e9 00000001 8a5aac04 00000000 nt!ViKeObjectAcquired+0x3e
8a5aabfc 8671373b adf94fe0 00000000 00000000 nt!VerifierKeWaitForSingleObject+0x118
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 snapman+0x1673b

STACK_COMMAND: kb

FOLLOWUP_IP:
snapman+1673b
8671373b ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: snapman+1673b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: snapman

IMAGE_NAME: snapman.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4bc041fb

FAILURE_BUCKET_ID: 0xc4_1001_VRF_snapman+1673b

BUCKET_ID: 0xc4_1001_VRF_snapman+1673b

Followup: MachineOwner

####################################################################
Haven't had this so far, since reinstall, but i seem to recall having to fix for the above error from acronis fix. To do with running ADD 2011 and ATI 2010 together.

#######################################################################

OLD BSOD:

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

Symbol search path is: C:\symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e45000 PsLoadedModuleList = 0x82f8d810
Debug session time: Tue Sep 14 17:03:52.340 2010 (UTC + 1:00)
System Uptime: 0 days 6:33:05.385
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
........
1: 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: 9245c8b8, The pool entry we were looking for within the page.
Arg3: 9245c8f8, The next pool entry.
Arg4: 08080008, (reserved)

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

*** WARNING: Unable to verify timestamp for tdrpm258.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm258.sys

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 82fad718
Unable to read MiSystemVaType memory at 82f8d160
9245c8b8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: msnmsgr.exe ######NOTE: this has been many different processes inc "searchindexer"

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 85f240d5 to 82f641b6

STACK_TEXT:
ad4dbb08 85f240d5 9245c8c0 00676e65 ad4dbb2c nt!ExFreePoolWithTag+0x1b1
WARNING: Stack unwind information not available. Following frames may be wrong.
ad4dbb18 85f24563 9245c8c0 00000029 9245c8c0 CBUFS+0x10d5
ad4dbb2c 85f2eb1e ad4dbb5c 9b85c534 8ecad320 CBUFS+0x1563
ad4dbb60 85f2f5fd 8ecad320 9b85c528 ad4dbb84 CBUFS+0xbb1e
ad4dbb90 831746c3 8b8c0508 c685eb78 8bf14f20 CBUFS+0xc5fd
ad4dbbb4 82e81473 00000000 86623628 8b8c0508 nt!IovCallDriver+0x258
ad4dbbc8 8662c1be 8664d67c 8b8c0508 c685eb78 nt!IofCallDriver+0x1b
ad4dbc68 82e81473 00000000 00000000 8b91b278 tdrpm258+0xa1be
ad4dbc7c 8309597f 9f73ad19 00000c30 0017efa8 nt!IofCallDriver+0x1b
ad4dbd18 82e8844a 00000c30 0017f0a8 039fb528 nt!NtSetInformationFile+0xa3f
ad4dbd18 770264f4 00000c30 0017f0a8 039fb528 nt!KiFastCallEntry+0x12a
0017f310 00000000 00000000 00000000 00000000 0x770264f4

STACK_COMMAND: kb

FOLLOWUP_IP:
CBUFS+10d5
85f240d5 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: CBUFS+10d5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CBUFS

IMAGE_NAME: CBUFS.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b461b02

FAILURE_BUCKET_ID: 0x19_20_VRF_CBUFS+10d5

BUCKET_ID: 0x19_20_VRF_CBUFS+10d5

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

###########################################################################

OS windows 7 pro

Steve,

Do you have Visual Studio or Delphi installed as the debugging tracker or are you using the W7 debugger?

I was wrong about the T&D Service - must have been thinking of a previous version.

I suggest uninstalling both programs for the moment and only re-install one of them until you can get it working.

It looks from one of your debug reports that there is a problem on your system with the Snapman driver.

If possible make a disk backup using the rescue CD, or as you are having difficulty runningTI, download the ISO version burn it to disk, and make sure you can boot your PC with it and see al your drives.

So uninstall both programs then;

1. Open up Device Manager (Win button + Pause Break) \Device Manager.

2. Check to see if the Acronis backup entry still exists if it does delete it.

3. Make sure there are no running Acronis entries in Services or in MSConfig\startup - untick or disable them and then reboot the PC.

4. Install DD11 - reboot and make sure it works.

5. Assuming it does and no BSOD's install TI 2010 - reboot. Make sure DD11 still works, then try opening TI.

6. If you still get BSOD's and the debug file still mentions Snapapi - then this link might be of use snapapi545

Thanks Colin i will try.
I am using the "debugging tools for windows (86)\ wndbg" from the performance toolkit .
BTW : No6 was the fix i had to apply before.

Ok Uninstalled both acronis products completely. Checked for rogue services left behind.

1.Installed ADD Home 2011...opened quicker than normal. But BSOD on closing 0xc4 snapman.
2.Thought i better update with the snapapi fix. But BSOD on closing 0xc4 snapman.
3. Uninstalled ADD Home 2011

My PC seems to be running better without these products so, i will wait for acronis, maybe the next builds will work. Seeing there's a new version of AIT out, there will not be an update for that one, but i am not spending anymore money on acronis products (they used to be good with xp pc's).

It could be my hard drive, but i am yet to find a fault with it. And again i am not spending money just to get acronis products to work on my PC.

At least i found the cause of the first BSOD 0x19 bad_pool_error, it was driving me nuts.

I apologise to Acronis...grovel, grovel.

I ran the windows verifier system tool. Found a driver that was very old called secdrv.sys (2006). I have removed and everything stable again(so far). Could acronis confirm this driver causes problems with their software?

Macrovision SECDRV.SYS Driver Part Of SafeDisc Copy Protection

To remove "secdrv.sys" , type the following in cmd with administrator privilege:

sc stop secdrv
sc delete secdrv
del c:\windows\system32\drivers\secdrv.sys

That's interesting, is SafeDisc a utility that came with your PC or a component of some other software?

Hi Colin, To be honest i am not sure. Seems to be to do with Games but i don't play games so could be remnants of a virus?? Microsoft Security Advisory

Not sure why a driver for security on cd drives would cause Harddrive software to complain?? But since the removal Acronis working fine.

Burning Software.... NERO??? I will soon find out next time i try and burn a disc.

Hello all,

Thank you very much for all of your posts Please accept my apologies for not replying earlier.

Colin, I really appreciate your help!

Steve, I will definitely assist you.

After analyzing the dumps that you posted here, it is very possible that the issue is related to Microsoft driver verifier blocking access to Acronis drivers. Please check this article for a solution and if you need additional assistance or have any other questions, please let me know.

Thank you.

Hello Anton, Better late than never:)

I have not seen a BSOD since i removed the above driver. So trying to use the Microsoft driver verifier to troubleshoot the BSOD caused another problem. It pointed to the Acronis module instead of the actual culprit, who would have thought that, hey?

I basically did the workaround by just asking the verifier to show all the unsigned drivers and checking the dates. Investigated the eldest drivers one by one. Anything before the release of Windows Vista must be a suspect for crashing windows 7.

I still don't know how this driver got on the PC?

Oh what fun i had. Anyway its sorted now.

Regards
Steve