Blue Screen on RE Rescue Media


Author
Message
Frank Esposito
Frank Esposito
Advanced Member
Advanced Member (505 reputation)Advanced Member (505 reputation)Advanced Member (505 reputation)Advanced Member (505 reputation)Advanced Member (505 reputation)Advanced Member (505 reputation)Advanced Member (505 reputation)Advanced Member (505 reputation)Advanced Member (505 reputation)Advanced Member (505 reputation)
Group: Forum Members
Posts: 354, Visits: 909
Thanks for t the info --- that is  really  good news 

JL Arranz
JL Arranz
Talented Member
Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)
Group: Forum Members
Posts: 91, Visits: 237
I'm having this problem with v8.1.7675 but not with v8.1.7638 or previous versions. I prefer myself to not do complicated things, as staying at v7638 is acceptable for me. I'm up-to-date in MS patches.

Partial incompatibility: this system has Rivatuner v2.24 (a 2009 version) to get color control (more/less brightness/gamma/etc, I like dim screens for reading but I need lighter settings for photos and videos) through hotkeys, and Rivatuner Statistics Server (a 2021 version) to get OSD in games (in combination with MSI Afterburner and HWiNFO64, I have yet to write down how to get all this...). If Reflect v8.1.7675 is installed, an error message from one of the two Rivatuners is displayed during bootup (I don't recall which one but I'm sure it's one of the two, as I saw this message quite frequently while I was adjusting these things one year and a half ago; the message says something about missing D3D v9 files iirc, although the color hotkeys keep on working I believe, I have not tried games to see the OSD).

Besides this semi-incompatibility, the 7675 Rescue Media BSODs while booting like in the first post. 7638 and previous versions work fine here.

PS (after reading Dan Danz posted 9 October 2023 11:14 PM): then it seems that v7638 works here because, after failing with v7675, I returned to v7638 reusing the previously built Rescue Media iso (I use to build to iso files and conserve them quite a bit).

Reflecting Mirror
Reflecting Mirror
Advanced Member
Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)
Group: Forum Members
Posts: 248, Visits: 908
JL Arranz - 11 October 2023 9:42 PM
I'm having this problem with v8.1.7675 but not with v8.1.7638 or previous versions. I prefer myself to not do complicated things, as staying at v7638 is acceptable for me. I'm up-to-date in MS patches.

Partial incompatibility: this system has Rivatuner v2.24 (a 2009 version) to get color control (more/less brightness/gamma/etc, I like dim screens for reading but I need lighter settings for photos and videos) through hotkeys, and Rivatuner Statistics Server (a 2021 version) to get OSD in games (in combination with MSI Afterburner and HWiNFO64, I have yet to write down how to get all this...). If Reflect v8.1.7675 is installed, an error message from one of the two Rivatuners is displayed during bootup (I don't recall which one but I'm sure it's one of the two, as I saw this message quite frequently while I was adjusting these things one year and a half ago; the message says something about missing D3D v9 files iirc, although the color hotkeys keep on working I believe, I have not tried games to see the OSD).

Besides this semi-incompatibility, the 7675 Rescue Media BSODs while booting like in the first post. 7638 and previous versions work fine here.

PS (after reading Dan Danz posted 9 October 2023 11:14 PM): then it seems that v7638 works here because, after failing with v7675, I returned to v7638 reusing the previously built Rescue Media iso (I use to build to iso files and conserve them quite a bit).

As I discovered the hard way, the problem was not the version of Reflect software per se. The problem was Microsoft OS patches caused the problem with WinRE 10 on Windows 10 platforms for the Reflect Rescue Media builder.
 
For example, when I encountered the BSOD using the new Reflect Rescue Media when I upgraded from 8.1.7544 to 8.1.7638 on September 27th, I restored back to the working 8.1.7544 version using the old working Reflect Rescue Media.

The issue as others stated in this thread said that the problem was with Microsoft OS patches and not the newer Reflect versions.

Based on that knowledge, I experimented by performing a force rebuild of the WIM in the Reflect Rescue Media builder while using the "working version" of 8.1.7544 and I tested the new Rescue Media. I received the BSOD on the "working version" of Reflect.

The reason you encountered the problem after upgrading Reflect is that when you went to create a new Rescue Media, the Rescue Media builder automatically rebuilds the WIM due to you are using a newer version of Reflect that uses the flawed Microsoft OS changes from previous OS patching.

To summarize, I am guessing the Microsoft OS patches that broke Reflect Rescue Media WinRE 10 for Windows 10 platforms occurred sometime in August. You would only encounter this problem by performing one of the following:
  • You performed a force rebuild by holding down the Ctrl key and click on the down arrow on the Build button to select Force Rebuild in the Reflect Rescue Media builder of the WIM using WinRE 10 on Windows 10 platforms.
  • You upgraded your Reflect installation and built a new Rescue Media using WinRE 10 on Windows 10 platforms.

Edited 12 October 2023 12:38 AM by Reflecting Mirror
JL Arranz
JL Arranz
Talented Member
Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)
Group: Forum Members
Posts: 91, Visits: 237
Reflecting Mirror - 11 October 2023 11:49 PM

My v7638 Rescue Media iso was built in September 6th and it's a good iso as said, but I believe I delayed some MS patches so I cannot assure that all August patches were already installed. Some time this summer I got the HATEFUL "installing patches and shutting down" when shutting down (sometimes you simply have to pull the plug at once if at all!!! such as if you're hurried to go out or the computer is in the bedroom and you already have to sleep), so I went to Settings -> Windows Update several "idle" times and I caught some patches that way, one or two from previous month, but I only semi-read what the patches are for (you are forced to install them sooner or later anyway).

PS This is my W10 patches history:

07-13 kb5028937 (2023-07)
07-13 kb5028166 (2023-07)
08-10 kb5028244 (2023-07)
08-11 kb5029244 (2023-08)
08-31 kb5029331 (2023-08)
09-01 kb5029847 (2023-08)
09-03 kb5029649 (2023-08)
09-06 ------------------------------------------------> v8.1.7638 Rescue Media iso that works
09-07 kb4023057 (2023-08) (it is kb "4" 023057)
09-13 kb5030180 (2023-09)
09-13 kb5030211 (2023-09)
10-08 kb5030300 (2023-09)
10-11 kb5031224 (2023-10)
10-11 kb5031356 (2023-10)
10-11 ------------------------------------------------> v8.1.7675 Rescue Media iso that does not work (*)
10-12 kb5001716 (2023-10)

(*) I have deleted this file, I believe it was built after kb5031224 and kb5031356, but not 100% sure. I'm sure yesterday (10-11) I installed 2 patches plus KB890830, so Idk how did kb5001716 install, for instance if it was "yesterday" after 0:00 or if it's been this morning, or under which pattern/option/setting/rule. I'm not sure which eligible by user automatic updates options do I have selected, or where to look. In Windows 7 and before I like seeing the systray icon when new patches are available, although I know MS prefers uniform Windows installs since Windows 10, so Windows Update settings are less flexible and (afaik) all patches are installed sooner or later and one or other way (you can for instance delay updates 7 days and extend it somewhat I believe, but not 7 years :p ).



Reflecting Mirror
Reflecting Mirror
Advanced Member
Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)
Group: Forum Members
Posts: 248, Visits: 908
My Windows 10 OS patches from October 10th that fixed the Rescue Media BSOD are shown below. I included the KB5001716 which installed on my system on 10/4/2023.



JL Arranz
JL Arranz
Talented Member
Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)Talented Member (105 reputation)
Group: Forum Members
Posts: 91, Visits: 237
Fail here, even after kb5001716 (that had not been installed here before October 12th), same BSOD. I did 2 attempts with and without checking "prompt for key press to continue boot sequence", because I noticed that the prompt really appeared this time (take as 90% sure it wasn't appearing in v8.1.7638 and previous ones although I was building with the option checked, the rescue medias I tried worked all anyway) and that pressing the key sends the boot to the UEFI circuitry to say it so, instead of the BIOS circuitry that should be used with my configuration (this is an ancient computer with FX8350 on 970 chipset).

A positive difference is that Rivatuner isn't showing the error message of my first attempt with v8.1.7675, but I'll return to v7638 unless a fix appears.

Does WinPE 10 fix this? This rig is connected through WiFi (it's in an awkward place for a cable from the router), although I have never needed or used net to work with images.

PS: I've done the new attempts forcing the WIM rebuild with the Ctrl key etc, in my Windows 11 computer Reflect was keeping the v7675 iso even after a travel for v7638 to check things.

Edited 12 October 2023 11:27 PM by JL Arranz
Dan Danz
Dan Danz
Macrium Hero
Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)
Group: Forum Members
Posts: 1.2K, Visits: 9.5K
@JL Arranz  I've never been able to provoke the RM build problem IFF for Win 10 22H2 I either don't install either of two PREVIEW patches: KB5030310 and KB5030219 KB503300 and KB5029331 or if I uninstalled those patches.   I have never been able to fix the problem with changing the version of MR.  Nor do I know of anybody who has been able to fix it any other way.  {Corrected 2023-10-14 by Dan Danz}

HOWEVER some users reported experiences that were different from mine -- e.g., rebuilding with WIN PE 10 always worked,for me but building with WIN RE 10 always failed (with one of the bad patches present).  Others reported the problem with WIN PE 10, but could bypass it by using WIN RE 10 (the exact opposite of my expereinces).

If you never installed any of the Preview patchs mentioned in the first paragraph above, then I'm stumped.





L.W. (Dan) Danz, Overland Park KS
Reflect v8.1.7847+ on Windows 11 Home 23H2 22631.3085+ | Reflect v8.1.7853+ on Windows 10 Pro 22H2 19045.3996+
Reflect v8.1.7784+ on 2 systems Windows 10 Home 22H2 19045.3803+

Edited 14 October 2023 7:40 PM by Dan Danz
Dan Danz
Dan Danz
Macrium Hero
Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)Macrium Hero (2.7K reputation)
Group: Forum Members
Posts: 1.2K, Visits: 9.5K
NEW UPDATE FOR EVERYBODY FOLLOWING THIS TOPIC.

While I was hospitalized, Windows Update installed a "patch Tuesday" NON-PREVIEW patch on my problem Win 10 system. Since it was NON-Preview, I got no chance to refuse it.  Also NONE of the troublesome PREVIEW patches remained on the system. 

October 10, 2023—KB5031356 (OS Builds 19044.3570 and 19045.3570)
Windows 10 Enterprise and Education, version 21H2 More...

Release Date:10/10/2023
Version: OS Builds 19044.3570 and 19045.3570

Fearing ithat it contained the bad fix from the preview updates, when I got home I Installed MR v8.1.7675 and rebuilt WRBM.   Test booting WRBM was successful.
I've seen this with other NON-PREVIEW patchs released after I had the problem involving the preview patches.   Since we never learned what the exact cause of the RM build failure was, I don't think we can breathe easy..   It sure would be nice IF Reflect Support could pin down what was wrong with the problem builds.



L.W. (Dan) Danz, Overland Park KS
Reflect v8.1.7847+ on Windows 11 Home 23H2 22631.3085+ | Reflect v8.1.7853+ on Windows 10 Pro 22H2 19045.3996+
Reflect v8.1.7784+ on 2 systems Windows 10 Home 22H2 19045.3803+

Edited 13 October 2023 2:09 PM by Dan Danz
Joe Allen
Joe Allen
Macrium Representative
Macrium Representative (717 reputation)Macrium Representative (717 reputation)Macrium Representative (717 reputation)Macrium Representative (717 reputation)Macrium Representative (717 reputation)Macrium Representative (717 reputation)Macrium Representative (717 reputation)Macrium Representative (717 reputation)Macrium Representative (717 reputation)Macrium Representative (717 reputation)
Group: Administrators
Posts: 306, Visits: 3.3K
Hi All, 

I'm going to run my tests again locally in the event I have missed something. 

We pull WinRE through the Windows installation itself. Windows initially places the WinRE image file (winre.wim) in the Windows partition, in the \Windows\System32\Recovery folder.

I will report back to this forum thread on either Monday or Tuesday.

Kind Regards

Joe A

Macrium Support Team

Next Webinar

See our reviews on

Trustpilot Logo
Trustpilot Stars


Reflecting Mirror
Reflecting Mirror
Advanced Member
Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)Advanced Member (445 reputation)
Group: Forum Members
Posts: 248, Visits: 908
Just to add another data point in case it is relevant for Joe Allen's investigation, my PC is currently running after the October 10 Microsoft patches:

Windows 10 Pro 64-bit 22H2 OS Build 19045.3570 using Reflect Home Edition 8.1.7675 version and Rescue Media built from WinRE.

@DanDanz

I wish you a speedy recovery. Smile
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search