BSoD(BAD_POOL_HEADER) - Program Accelerator (System Mechanic Pro)

Good afternoon. Some time ago, I have been using a program called System Mechanic Pro. The program had not given me problems before. A few days ago came the latest update of the program. I was testing it and when I used the Program Accelerator, about half an hour later, gave BSoD. I tested a few more times and kept giving BSoD. What will? Attached is the zip file that request. Thank you.

Note: I'm Brazilian. Sorry for the bad english.

Welcome.

You should uninstall/stop using this software and see the problem occurs again.

I would if it were my PC.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff8a00eaae5b0, fffff8a00eaae5f0, 5040303}

*** WARNING: Unable to verify timestamp for ampse.sys
*** ERROR: Module load completed but symbols could not be loaded for ampse.sys
Probably caused by : ampse.sys ( ampse+12d1aa )

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

3: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a00eaae5b0, The pool entry we were looking for within the page.
Arg3: fffff8a00eaae5f0, The next pool entry.
Arg4: 0000000005040303, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c0100
GetUlongFromAddress: unable to read from fffff800034c01c0
 fffff8a00eaae5b0 Paged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  SysMech.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033bbcae to fffff80003290fc0

STACK_TEXT:  
fffff880`0cd82c18 fffff800`033bbcae : 00000000`00000019 00000000`00000020 fffff8a0`0eaae5b0 fffff8a0`0eaae5f0 : nt!KeBugCheckEx
fffff880`0cd82c20 fffff880`0817b1aa : 00000000`00000000 fffff8a0`1067b090 00000000`624c6553 fffff880`0cd82dd0 : nt!ExDeferredFreePool+0x12da
fffff880`0cd82cd0 00000000`00000000 : fffff8a0`1067b090 00000000`624c6553 fffff880`0cd82dd0 fffff8a0`0eaae5c0 : ampse+0x12d1aa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ampse+12d1aa
fffff880`0817b1aa ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ampse+12d1aa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ampse

IMAGE_NAME:  ampse.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5037dd1f

FAILURE_BUCKET_ID:  X64_0x19_20_ampse+12d1aa

BUCKET_ID:  X64_0x19_20_ampse+12d1aa

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

3: kd> lmvm ampse
start             end                 module name
fffff880`0804e000 fffff880`081c1000   ampse    T (no symbols)           
    Loaded symbol image file: ampse.sys
    Image path: ampse.sys
    Image name: ampse.sys
    Timestamp:        Sat Aug 25 01:59:27 2012 (5037DD1F)
    CheckSum:         001761DD
    ImageSize:        00173000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table

Use the free version of Revo Uninstaller. *Uninstall in Advanced Mode*

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Thanks for responding, koolkat77. But I guess I did not explain right. The BSoD occurs while the Program Accelerator is in use. Are you talking to me uninstall System Mechanic Pro and stop using it? Or to uninstall and reinstall it again? In other words, I would like to continue using the program, but without giving BSoD while running the Program Accelerator.

These programs can be a cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner but make sure you back up the registry before making letting ccleaner delete anything.

Uninstall and reinstall the program. See if that helps. If it doesn't, you shouldn't be using it.

Sorry for the delay in responding. I uninstalled and installed the program again, but continued giving BSoD. I got to format the Windows to see if it solved. That did not solve. I used the diagnostic programs Memtest86 + and looked for hard disk errors. With that, I detected that there is no error in both. I believe my last chance is something on the Driver Verifier. koolkat77, do you think I should try to resolve the error or not I do anything else? Thank you.

It is best to leave things as they are. Before format it, I remember having used the Driver Verifier. And in this case, the computer has BSoD soon as Windows started. But now, after formatting, let the Driver Verifier turned on for about 12 hours and did not give any error. Now, I'm definitely lost. Most likely, the BSoD came program update. I'll wait an update to correct this or even stop using it. Thank you for your help, koolkat77. Problem solved.

Note: Before formatting, had also given errors in memory and hard drive. After formatting, no error in memory or on the hard disk. I no longer understand anything.