Pxhlpa64.sys event log error - help please

Hi

I deleted this driver as it was one of the causes of several BSOD issues and it was identified by a member on this forum, and that I should delete it.

I am now getting errors in event log about this driver failing to start, is there any way that I can edit the service that is trying to start this driver?

The BSOD problem has been resolved and all is well generally with the system, just want to stop these errors on boot/start up.

-System
-Provider[ Name] Service Control Manager[ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}[ EventSourceName] Service Control Manager
-EventID7026[ Qualifiers] 49152
Version0Level2Task0Opcode0Keywords0x8080000000000000-TimeCreated[ SystemTime] 2012-04-06T17:16:04.047200000Z
EventRecordID202700Correlation-Execution[ ProcessID] 740[ ThreadID] 744
ChannelSystemComputerNOMADMAINPCSecurity
-EventData
param1PxHlpa64

Hi, I looked for it in services.msc, couldn't see it anywhere but then the driver isn't installed so it can't be running, but didn't check Msconfig.

The driver relates to SONIC software that I don't even have installed, should I be looking for ROXIO or SONIC entries rather than the driver itself?

Hi, I already knew how to do that, the driver is not for a device though so it is unlikely to be in there but thanks for trying.

Its giving two errors every time the machine boots up, one is code 7000, the other is code 7026, the 7026 is mentioned above in the initial post, this basically means "the driver failed to start because it isn't installed", it refers to PXHLPA64.SYS, as explained this is a ROXIO driver that isn't digitally signed and lots of people have had issues with it, so a tech guy on here told me to delete it after having BSOD issues.

Its not causing any problems as far as I am aware, just that for every boot up it is reporting two critical errors, I don't like that. It says it starts from services.exe.

There is nothing jumping out at me either in MSCONFIG or SERVICES.MSC that would automatically say that it is the process that it is trying to start that particular driver.

I just don't like having critical system errors all the time, who knows what it is actually affecting?

Thanks mate, that was brilliant, it has pointed me to the registry key where the file is trying to be started from!

EXCELLENT!!

REP ADDED!

THANKS!

Mate, that software is the SHIZNIT!! Cheers