BSOD 0x24 with WinPE ISO Builder

I have not seen this, unfortunately. Perhaps it would help to run a Repair installation of the Plus Pack. Everything for the tutorial was made using WinPE 2.0 on a Win XP SP3 machine with TI 2010 build 6053, and I have not seen this problem in any of dozens of runs. I always start the builder as a separate application - TI itself is not running at the time.

Hello,

Gary, you are correct, thanks for your help.

Max, as Gary suggested, please re-install Acronis Plus Pack completely and then try to create a WinPE ISO image once again. If your OS still crashes, please collect the following information and submit a support request:

• Windows Mini-Dumps
• AcronisInfo Utility output

We are looking forward to hearing back from you at your earliest convenience.

Thank you.

Thanks Gary.
I have done a bit more experimenting to see where it BSODs.
I took the precaution of shutting down real-time antivirus protection in case it was interfering some way.
A CHKDSK does not show any file or disk faults, Event Viewer shows nothing disk-related or 'IRPStackSize' amiss, so the finger appears to point to Acronis's tdrpm258.sys doing a bad call to NTFS and making NTFS fall off the end of the world accessing 0x04.

Like you I start ISO builder as a separate application and TI is not running at the time.
When the ISO builder is told to Proceed, it gets as far as "Updating WIM-file components" with the progress bar is about one-third complete.

A Windbg stack trace shows:
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from f7b79edc to f7b52736
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
aece24e0 f7b79edc aece25cc 88f27f90 aece251c Ntfs+0x736
aece2554 f7b7849c aece25cc 88ffd2d8 8ad43a80 Ntfs+0x27edc
aece25b8 f7b784d5 aece25cc 88ffd2d8 00000001 Ntfs+0x2649c
aece26dc 804e37f7 8ad65770 88ffd2d8 baf24628 Ntfs+0x264d5
aece26ec baf2d1be baf4e67c 8ad65770 88ffd2d8 nt!IopfCallDriver+0x31
aece2780 804e37f7 8ad65020 88ffd2d8 88ffd2d8 tdrpm258+0xa1be <<====
aece2790 f74b27a9 00000000 8a84a008 00000000 nt!IopfCallDriver+0x31
aece27bc f74b4d56 8ad65020 88f27f90 aece27e4 fltmgr!FltpQueryInformationFile+0x99
aece2804 f74b5329 8aaacc18 00000000 80552000 fltmgr!SetStreamListStandardInformationFlags+0x7e
aece2828 b0468ade 88f27f90 8a84a008 88eac6a0 fltmgr!FltIsDirectory+0x4b

The exception record is:
EXCEPTION_RECORD: aece2414 -- (.exr ffffffffaece2414)
ExceptionAddress: f7b52736 (Ntfs+0x00000736)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000004
Attempt to read from address 00000004

Max-

Another possible approach (once a reinstallation and/or repair of the Plus Pack is done) is to "manually" create the ISO as shown in the second part of the tutorial and see if this approach also fails. Perhaps uninstalling/reinstalling the WAIK might also be useful - perhaps there is corruption in some component. Also, WinPE 2.1 works with Win XP SP3, if you wanted to install this rather than WinPE 2.0.

One way to see if the WAIK might be the problem is to make a "base" WinPE ISO - don't add anything, just make the ISO from the existing boot.wim as installed by the WAIK. This takes the Acronis builder out of the picture. The bootable media will boot into the WinPE command line.

Thanks Gary - and to Ilya for his earlier post.
I have done a repair install of Plus Pack and rerun ISO Builder .... 0x24 again.
So following Ilya's suggestion, I have captured the Minidump, run AcronisInfo, zipped them together and raised a ticket.

I am now tied up for a few days, but when things ease up I will try your second suggestion (build a base ISO direct from WAIK) first. Based upon where the 0x24 occurred (while still gathering the components of the ISO and well before creation of the ISO), I would be surprised if this failed.

If I have no response from Acronis by then I will deinstall WAIK and download the PE2.1 version and try again.

Another thought would another install on a fresh download of the Plus Pack - make sure it is the same Plus Pack build as the TI build (6053 in your case). Perhaps something was not quite right with the downloaded file.

All that is needed to make a base WinPE ISO is to do the final command line in part 2 of the tutorial.

Thanks Gary.

I have now:
- installed a fresh download of up-to-date (build #7046) of TI 2010 and Plus Pack
- deinstalled the PE2.0 WAIK and downloaded and installed the PE2.1 version
Result: an 0x24 again in Acronis WinPE ISO builder when 'updating WIM-file contents'

I have rerun AcronisInfo and shipped its output this along with the Win minidump to Acronis on a ticket.

I also tried creating a 'base' Win PE ISO using WAIK alone (i.e. without Acronis WinPE ISO builder).
Result: success

Max-

I was wondering is there was any progress on this issue.

Also, I was wondering if you possibly have some kind of conflict with a built-in or attached card reader....
Or if any USB devices are attached at the time you are trying to run the ISO builder program.

If so, perhaps temporarily disabling any built-in card reader or detaching any USB devices may eliminate some driver collusion while the ISO builder is running.

No tangible progess...
I received several emails from Acronis asking for various things to be tried and telling how the problem was being escalated - and then silence.
In answer to your points, the PC concerned has no built in or attached card reader, and the only USB device attached (a printer) was off.
The odd thing is that it appears to 0x24 when it is still busy assembling the components for the updated WIM file rather than actually creating the ISO (or perhaps the ISO builder status window messages are misleading...), so it doesn't sound 'device driverish' if you see what I mean.
If I get any fix or workaround from Mr Acronis, I will post it here.
Thanks for your continued interest.