EWF BSOD
- From: "Dietmar" <dietmar.stoelting@xxxxxxxxxxx>
- Date: Mon, 21 Aug 2006 15:06:27 -0400
Hi all,
I "solved" the mystery of suddenly BSOD with EWF after (some) reboot:
Sometimes EWF induces a write to (new subkey in Volume)
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\STORAGE
This new entry causes the BSOD.
I found this by comparing two folders SYSTEM (exported as *.reg files
because only than they can be edited direct)
one working and the other direct after this BSOD with Beyond Compare 2
(wonderful tool).
So I reanimated a compi that, with EWF, always gives BSOD.
This type of BSOD happens through switching from EWF enabled
(writeprotect) to EWF disabled.
If you enable EWF after from outside, it is too late, because this extra
entry in
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\STORAGE\Volume
has been written. But you can give new live to your compi, deleting by
hand this extra entry.
I noticed, that you cant delete the whole key STORAGE by importing it
into another registry.
This is very strange to me. So you only can delete all values in the wrong
key.
You have all permissions to do everything in any registry, if you build a
minlogon macrocomponent from
Windows Embedded with component regedit.exe included, because this
minlogon doesnt know anything
about any permissions...hihi.
Nice to hear from you
Dietmar
PS: This behavior of XP, Vista... is reproduceible.
You see BSOD and BSOD gone with my methode.
I think it happens, because a wrong geometry of the protected Volume is
written there.
.
- Prev by Date: Re: Missing dependency MSHTML.DLL -> PSAPI.DLL
- Next by Date: Re: Removing items on control panel
- Previous by thread: Is that possible?
- Next by thread: Re: Removing items on control panel
- Index(es):
Relevant Pages
|
