BSOD when trying to boot in safe mode - Windows 7 x86

The Netgear wireless adapter is unrelated to the BSOD and inability to get the CDROM drive to work - I switched over to a wireless connection in just the past few days. I believe the CDROM issue came from uninstalling Roxio, while the BSOD could be Roxio and/or Acronis. The Hard drive still has Sonic Solutions (Roxio) drivers which I haven't been able to get rid of. I'd like to resolve the problems in this order:

1.) Get the CDROM drive working again without having to reinstall Roxio;
2.) Get the Sonic (Roxio) drivers removed from my hard drive driver list;
3.) Remove the Acronis software

It's possible the BSOD might go away after step 2, but I'd like to know that before proceeding to step 3.
 
You could try revo uninstaller or similar programs (glarysoft absolute uninstaller, wise program uninstaller, GeekUninstaller, YourUninstaller, and so forth).
 
Revo didn't seem to help much, but I can see it's usefulness, and I'll keep it around for a while.

I went into the registry and deleted all references to Pxhelp20.sys because Windows system log was giving these warnings:

The driver \Driver\PxHelp20 failed to load for the device IDE\CdRomATAPI_iHAS124___B_______________________AL0H____\5&33e30520&0&1.0.0.

The driver \Driver\PxHelp20 failed to load for the device SCSI\CdRom&Ven_ROXIO&Prod_DVD-ROM_EMULATOR&Rev_2.00\1&2afd7d61&0&000000.

I uninstalled the CDROM and then told Windows to scan for hardware changes. The CDROM is now working, but still includes ROXIO DVD-ROM EMULATOR SCSI CdRom Device under its properties. It says it is:

Driver Provider: Microsoft
Driver Date: 6/21/2006
Driver Version: 6.1.7601.17514
Digital Signer: Microsoft Windows

I also recall that I had a similar CDROM not working because of GEARAspiWDM.sys which has reappeared most likely from an ITunes update, but I haven't tried removing it again since the CDROM is working.

Hopefully I can move forward to resolving the BSOD.
 
As suggested, I've removed Roxio as best I can from my system, but I haven't found a way to uninstall the following Sonic Solutions (Roxio) driver that is listed for my hard drive:

sahdia32.sys

I'd like to remove this as a possible source of my safe mode BSOD before I try uninstalling my backup software. Anyone have a suggestion on how I can remove the driver manually? Thanks!

BTW, even though I've uninstalled Roxio and cleaned up as best I can using various tools, a search of my registry still contains numerous entries for Roxio. Anyone know a good way to clean these apparent leftovers from the registry?

Tom
 
I wouldn't want to be shot ( :wink11a: ), but there are many registry cleaners: piriform CCleaner, wise registry cleaner, regseeker, auslogics registry cleaner, and so forth.
I'd just remove the Roxio entries, ignore all the other entries.
As usual, before the changes: registry backup, system restore point and a backup of the system partition (at least)...
 
I wouldn't want to be shot ( :wink11a: ), but there are many registry cleaners: piriform CCleaner, wise registry cleaner, regseeker, auslogics registry cleaner, and so forth.
I'd just remove the Roxio entries, ignore all the other entries.
As usual, before the changes: registry backup, system restore point and a backup of the system partition (at least)...

Yes, I reinstalled Auslogic and tried to see if it would remove the leftover Roxio entries but it didn't. Earlier in this thread it was recommended that I remove it, so I did, and probably will uninstall it again as was previously recommended. I was hoping to find a relatively safe and effective tool.

Any thought on how to deal with the sahdia32.sys driver still loaded for my hard drive? It was identified as a possible cause of my safe mode BSOD.
 
Do you still have these files?
c:\windows\System32\Drivers\SahdIa32.sys
c:\windows\System32\Drivers\SaibIa32.sys
c:\windows\System32\Drivers\pxhelp20.sys

Post the results here for the following commands; same suggestion: registry backup, system restore point and system partition backup always (new and) ready!.
Let's try to be as safe as possible; run these commands from an elevated command prompt:
sc enumdepend sahdia32 && sc enumdepend saibia32 && sc enumdepend pxhelp
If each one shows:
[SC] EnumDependentServices: entriesread = 0
Then run:
sc config sahdia32 start= disabled && sc config saibia32 start= disabled && sc config pxhelp20 start= disabled

c:\windows\system32\regsvr32 /u sahdia32.sys && c:\windows\system32\regsvr32 /u saibia32.sys && c:\windows\system32\regsvr32 /u pxhelp20.sys

c:\windows\syswow64\regsvr32 /u sahdia32.sys && c:\windows\syswow64\regsvr32 /u saibia32.sys && c:\windows\syswow64\regsvr32 /u pxhelp20.sys
 
Do you still have these files?
c:\windows\System32\Drivers\SahdIa32.sys
c:\windows\System32\Drivers\SaibIa32.sys
c:\windows\System32\Drivers\pxhelp20.sys

Post the results here for the following commands; same suggestion: registry backup, system restore point and system partition backup always (new and) ready!.
Let's try to be as safe as possible; run these commands from an elevated command prompt:
sc enumdepend sahdia32 && sc enumdepend saibia32 && sc enumdepend pxhelp
If each one shows:
[SC] EnumDependentServices: entriesread = 0
Then run:
sc config sahdia32 start= disabled && sc config saibia32 start= disabled && sc config pxhelp20 start= disabled

c:\windows\system32\regsvr32 /u sahdia32.sys && c:\windows\system32\regsvr32 /u saibia32.sys && c:\windows\system32\regsvr32 /u pxhelp20.sys

c:\windows\syswow64\regsvr32 /u sahdia32.sys && c:\windows\syswow64\regsvr32 /u saibia32.sys && c:\windows\syswow64\regsvr32 /u pxhelp20.sys

I took me a couple of days to get to try this. I had already gotten the pxhelp20.sys driver off my system and checking enumdepend for the other two drivers returned entrieread=0 so I proceeded to the next step.

Changing the start=disabled via sc config was successful so I proceeded to the next step. After changing to the drivers directory and entering the regsrvr32 command for each of the drivers returned the following error for each driver (substitute the second driver name in place of the first):

The module "sahdia32.sys" was loaded but the entry-point DllUnregisterServer was not found.

Make sure that "sahdia32.sys" is a valid DLL or OCX file and then try again.

Rebooting was unsuccessful with the drivers disabled (similar to earlier post(s)) and I did a system restore after booting from the Windows installation disk.
 
Interestingly, System Information is showing the following for my drives (drive 0 is a Seagate and drive 1 is a Western Digital):

Description Roxio Sahd
Manufacturer Roxio 32 bit
Model Disk drive
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 3
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 1.82 TB (2,000,396,321,280 bytes)
Total Cylinders 243,201
Total Sectors 3,907,024,065
Total Tracks 62,016,255
Tracks/Cylinder 255
Partition Disk #0, Partition #0
Partition Size 100.00 MB (104,857,600 bytes)
Partition Starting Offset 1,048,576 bytes
Partition Disk #0, Partition #1
Partition Size 931.33 GB (1,000,004,911,104 bytes)
Partition Starting Offset 105,906,176 bytes
Partition Disk #0, Partition #2
Partition Size 931.59 GB (1,000,284,880,896 bytes)
Partition Starting Offset 1,000,110,817,280 bytes

Description Roxio Sahd
Manufacturer Roxio 32 bit
Model Disk drive
Bytes/Sector 512
Media Loaded Yes
Media Type External hard disk media
Partitions 1
SCSI Bus Not Available
SCSI Logical Unit Not Available
SCSI Port Not Available
SCSI Target ID Not Available
Sectors/Track 63
Size 931.51 GB (1,000,202,273,280 bytes)
Total Cylinders 121,601
Total Sectors 1,953,520,065
Total Tracks 31,008,255
Tracks/Cylinder 255
Partition Disk #1, Partition #0
Partition Size 931.51 GB (1,000,202,043,392 bytes)
Partition Starting Offset 1,048,576 bytes



I don't know if this helps shed any light on my problem.
 
At least now it seems quite clear that those two drivers are the problem: when you try to boot in safe mode, those ones won't be loaded, hence the bsod/crash of safe mode happens.
 
At least now it seems quite clear that those two drivers are the problem: when you try to boot in safe mode, those ones won't be loaded, hence the bsod/crash of safe mode happens.

I'm assuming that merely deleting this registry key won't do it:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SahdIa32

That's the only place in the registry that references the driver. I know we've been looking at 2 drivers, but right now that driver appears for both my internal and external USB backup drive. I guess I can try it after creating the appropriate backups, but if it won't work I'd like to understand a bit more why. That may give me some insight into how to remove it.
 
I'd also appreciate any thoughts about possibly uninstalling the disk drive via device manager and then have Windows reinstall it via add new hardware. What pitfalls are there in using this approach? Should I allow the uninstall also delete the driver files, if that option is available? Thanks again for any help you can provide!
 
I found one more piece of information and I hope it may be helpful. Here's the contents of the file oem142.inf in the \windows\inf directory:

;/*++
;
;Copyright (c) 2007, Sonic Solutions. All rights reserved.
;
;Module Name:
;
; SAHDIA32.INF
;
;Abstract:
; INF file for installing Roxio Image Backup Kernel Driver
;
;--*/


[Version]
Signature = "$Windows NT$"
Class = DiskDrive
ClassGUID = {4d36e967-e325-11ce-bfc1-08002be10318}
Provider = %Roxio%
CatalogFile.NTx86=sahdia32.cat
DriverVer = 04/21/2009, 1.0.0.0

[DestinationDirs]
DefaultDestDir = 12

[SourceDisksNames.x86]
0=%Desc_x86%

[SourceDisksFiles.x86]
sahdia32.sys=0,,

[Manufacturer]
%ROXIOX86%=Roxio,NTx86

[Roxio.NTx86]
%SahdDesc%=Sahd_Inst.NTx86,GenDisk

[Sahd_Inst.NTx86]
CopyFiles = Sahd.Files.x86_01
Addreg = Sahd.HW.AddReg.x86

[Sahd_Inst.NTx86.Services]
AddService = sahdia32, ,Sahd_Service_Instx86,

[Sahd_Service_Instx86]
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_BOOT_START%
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceBinary = %12%\SAHDIA32.SYS
LoadOrderGroup = "Filter"

[Sahd.HW.AddReg.x86]
HKR,,"LowerFilters",0x00010008,"sahdia32"

[Sahd.Files.x86_01]
sahdia32.sys

[Strings]

; *******Localizable Strings*******
Roxio= "Roxio"
ROXIOX86="Roxio 32 bit"
Desc_x86= "Roxio Image Backup 32 bit Kernel Driver"
SahdDesc= "Roxio Sahd"

; *******Non Localizable Strings*******

SERVICE_BOOT_START = 0x0
SERVICE_SYSTEM_START = 0x1
SERVICE_AUTO_START = 0x2
SERVICE_DEMAND_START = 0x3
SERVICE_DISABLED = 0x4

SERVICE_KERNEL_DRIVER = 0x1
SERVICE_ERROR_IGNORE = 0x0
SERVICE_ERROR_NORMAL = 0x1
SERVICE_ERROR_SEVERE = 0x2
SERVICE_ERROR_CRITICAL = 0x3

REG_EXPAND_SZ = 0x00020000
REG_DWORD = 0x00010001
 
At least now it seems quite clear that those two drivers are the problem: when you try to boot in safe mode, those ones won't be loaded, hence the bsod/crash of safe mode happens.

I'm assuming that merely deleting this registry key won't do it:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SahdIa32

That's the only place in the registry that references the driver. I know we've been looking at 2 drivers, but right now that driver appears for both my internal and external USB backup drive. I guess I can try it after creating the appropriate backups, but if it won't work I'd like to understand a bit more why. That may give me some insight into how to remove it.


I just found a couple more registry entries:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}\0018
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}\0024
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\SahdIa32
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}\0018
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}\0024
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\SahdIa32
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}\0018
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}\0024
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SahdIa32

Don't know why I didn't find these before.
 
If your CD drive is currently working with PxHelp20 uninstalled, I would just focus on Acronis instead. If you're not on the latest version, try updating it, and past that, try uninstalling it. So long as Roxio isn't continuing to be the root cause of the Safe Mode BSoDs, which Acronis is known to cause, I would worry about the cleanup of that afterwards (if worthwhile at all).
 
I found this article (click) where there's this command:
RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection DefaultUninstall 132 path-to-uninstall-dir\infname.inf


Warning

I've never tried this one (not recently at least).

If you want to try it, it should be run from an elevated command prompt:
Read More:
I think I shouldn't recall you to be prepared at worst... (but I'm doing it! :embarrasment5:)
 
If your CD drive is currently working with PxHelp20 uninstalled, I would just focus on Acronis instead. If you're not on the latest version, try updating it, and past that, try uninstalling it. So long as Roxio isn't continuing to be the root cause of the Safe Mode BSoDs, which Acronis is known to cause, I would worry about the cleanup of that afterwards (if worthwhile at all).

No joy with uninstalling Acronis, still get a BSOD when trying to boot in safe mode. Here's a link to the memory dump:

MEMORY.zip - Google Drive

I'll upload the SysnativeBSODCollectionApp data when it's done running.
 
To me at least, it looks like this is related to the sector read error you saw when doing a backup (post #19). You may have just restored the corrupted NTFS volume's image. Did you ever try booting into safe mode after you were getting disk errors on your old drive, before replacing it?

Code:
0: kd> .bugcheck
Bugcheck code 00000050
Arguments [COLOR=#0000ff]80787000[/COLOR] 00000000 82afca62 00000000
Code:
0: kd> r @cr2
Last set context:cr2=[COLOR=#0000ff]80787000[/COLOR]
Code:
0: kd> !irql
Debugger saved IRQL for processor 0x0 -- 0 (LOW_LEVEL)
Code:
0: kd> !pte 80787000
                   VA [COLOR=#0000FF]80787000
[/COLOR]PDE at C0602018            PTE at C0403C38
contains 00000000D93D6863  contains 0000000000000000
pfn d93d6     ---DA--KWEV  [COLOR=#ff0000]not valid[/COLOR]


This is the same reference that was in the DMP from July 11th.

I know you've run sfc /scannow and bootrec commands before, did you ever do a check disk? If not, try running CHKDSK /R from an elevated command line and agree to restart if prompted.
 
Back
Top