Hey bazis … thank you for looking at this situation of mine … re the WINDOWSMinidump folder contents … I have the latest file for you (looks like AnyDVD’s driver is involved in the BSOD) but how do I send it? I don’t see a file attachment interface here (or via PM) on this board. Am I too junior for that functionality?
Up until last night, the Minidump file (and / or ‘MEMORY.DMP’ file [in WINDOWS]) was not being created for the current issue … even though the BSOD screens indicated the memory dumps were occurring to completion … by way of explanation, fairly recently I modified the System Properties > Advanced > Startup and Recovery – System failure – Write debugging information settings to ‘Kernel memory dump’ and had disabled ‘Overwrite any existing file’, however, I was still having trouble capturing a Miniaaaaaa-aa.dmp or MEMORY.DMP file following recent DRIVER_POWER_STATE_FAILURE BSODs, so, after reading your post last night, I re-enabled ‘Overwrite any existing file’ to see if that was the debugging file capture problem – it may have been as I did capture a file. Interestingly, the subject machine hung on the BSOD screen after the memory dump completed, even though ‘Automatically restart’ is enabled in the settings … as to the type of memory dump … for Vista Bus SP2, do you recommend the Small memory dump (64KB) over the Kernel memory dump? Any other thoughts on debugging settings?
… re the manual override procedure you outlined … I was already familiar with that and had already tried it … even though I follow through on the entire procedure, Vista won’t acknowledge the change. Is there something about an MDS/ISO file pair (created with ImgBurn 2.5.0.0 and AnyDVD 6.6.0.9 running) that would give your WinCDEmu trouble?
Right now, with ImgBurn assigned as the default program for both file types, on a right-click Context menu > Open with >
– for an ISO file, I get ImgBurn, Nero Burning ROM and Nero Express (Nero 7 Ultra Edition is installed) as Recommended Programs
– for an MDS file, I get ImgBurn and WinCDEmu Mounter as Recommended Programs
Also, is WinCDEmu limited to one virtual drive at a time?
Be advised I also have Nirsoft’s BlueScreenView v1.11 installed, and, have put the subject machine in Test Mode (as per the sysprogs.orgsigning page), the latter to see if driver signing was the issue – it seemingly wasn’t.
FFF
2221PST08JAN10 edit – interesting observations: when checking right-click Context menu > Open with >
– for an ISO file, the Nero Burning ROM Recommended Program icon says it is authored by ‘Bazis’ – not ‘Nero AG’ as expected
(after de-associating the ISO file type in Nero Product Setup, this incongruity is sorted out and ‘WinCDEmu Mounter’ authored by ‘Bazis’ appears)
For an MDS file, the Windows Explorer file Type is displayed as ‘Alcohol CD/DVD image’ … (?)
FYI – disabling AnyDVD Autostart (on system startup) doesn’t sort out the failure of WinCDEmu to create a virtual drive from a mounted image file that can be seen in Windows Explorer, however, a ‘CD-ROM Drive’ can be seen in Device Manager as a direct result.