Custom windows pe iso gives BSOD during boot after 1.0.97 bootloader update

[Smarty12345]

Official FAQ

• I have checked the official FAQ.

Ventoy Version

1.0.97

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

No. I didn't try these alternative boot modes.

BIOS Mode

UEFI Mode

Partition Style

MBR

Disk Capacity

32 or 64GB

Disk Manufacturer

Not sure/brand wore off

Image file checksum (if applicable)

None

Image file download link (if applicable)

No response

What happened?

I updated my usb drive, from 1.0.93 to 1.0.97 the other day, and did the same with my internal HDD on a laptop without an OS installed. After trying to boot off both drives, they all seem slow, and BSOD on boot of my custom built Windows PE image that worked before on 1.0.93.

For reference, a DIFFERENT USB drive, running 1.0.93 boots just fine

[steve6375]

Can you try 1.0.93 download and click update so it reverts to 93 and see if it then boots pe again?

[Smarty12345]

I will try that as soon as I get home, but since I don't have internet at home I don't know when I'll be able to give you the verdict as to whether it worked or not... Speaking of, can you take ventoy and do a nondestructive rollback, or would I have to format everything?

[steve6375]

Yes, I just told you, click update button on the app

[Smarty12345]

Thank you for clarifying, i figured that was the case, but wanted to be sure, as I've had issues nondestructively updating (or was that installing?) In the past... I'll try that as soon as I can and get back to you asap.

[Smarty12345]

I might have imagined the speed decrease, although I don't remember it being so slow, but after the downgrade to 1.0.93 the windows PE iso loaded just fine. I'll check back here when I can for more information on this issue

[steve6375]

Ok, certainly seems like it has problems with the latest version. What was the BSOD error exception number?

[Smarty12345]

I've re-upgraded the internal drive, and found that for whatever reason, it worked this time and loaded this time... I'm wondering if I hadn't explored the installer subdirectories and used the x64 version of the installer? If so, then that would be why it works now... I also just noticed the text file that says to move the files to the directory in which ventoy2disk resides, which could also be part of it...

Since it's working currently, let's just close this as I've likely figured out my issue, although if you want to know, I tried the USB drive I thought didn't work and it all of a sudden started working, and the only difference i could find between the internal and external drive is that the USB thumb drive was set for fat32 mode where the internal drive is set for ntfs mode, for hopefully obvious reasons(bigger filesize limit)...

Speaking of, is there ANY reason to actually use the 64bit version? I mean, is there any benefit over the 32 bit version?

[Smarty12345]

Oh, and for reference, the internal drive is still set as NTFS, in case that wasn't clear

[Smarty12345]

Oh f***... I got an error again now... I'll post the error code below...

0xc0000098

Also the file supposedly affected every time is below

/windows/system32/drivers/ADP80XX.sys

[steve6375]

I think that is a SCSI miniport driver issue. Maybe there is a problem with your internal drive or drive connector. Intermittent issue?

[Smarty12345]

I don't know if this helps your diagnosis of my issue, but I unfortunately spent forever trying to figure it out, and I only knew one thing until last night, and that was that it felt like it slowed down the loading of the PE image after updating to 1.0.97, when it did load... BUT!!! Last night I deleted the ISO after having trouble copying files from the mounted image, as well as errors doing the same with 7zip. After replacing the image with an uncorrupted copy it works again.

So, I guess this preliminarily solves my issue, but WHY was an image that was placed, then thereafter remained untouched except during loading of it, getting corruption errors? And aside from that, why were they errors that were supposedly undetectable by a diskcheck I ran that found ZERO issues needing fixed?

Is this a ventoy problem, or a "ME" problem?

[Smarty12345]

Oh... Also, the speed issue was also solved with the iso replacement

[steve6375]

Usb flash drives, especially cheap ones or fake ones often have such problems. After copying files to a usb drive you need to use 'safely remove drive' in windows or eject under Linux before unplugging the drive.
Cheap usb drives may have faulty memory cells and timeouts, error correction and retries can slow down read access performance.
I recommend SanDisk Extreme Pro usb 3 drives.
You can run chkdsk on the usb drive if you suspect a problem or simply try a different usb drive.
Millions of people use Ventoy, if it caused a problem on a good usb drive there would be thousands of complaints!

[Smarty12345]

Thanks for the information, but the drive I was having the main issue on was an internal drive, and as it's a cheaper 350$ hp notebook laptop, well, it's not good for much other than a PE system... Just saying...