Eclipse Community

I have a Z590 Aorus Ultra and i9-11900K, but whenever I try to boot into Windows 7 (modded .iso I made with extra drivers or even regular), it freezes on the splash screen. When I decided I can do without UEFI, I made a BIOS intended USB, but when I tried booting into it, I got a 0xA5 bluescreen with the message: "The BIOS in this system is not fully ACPI compliant. Please contact your system vendor for an updated BIOS". I had an idea about using an acpi.sys file from Windows 8.1, which boots just fine and am using right now. I know people like Luumi installed custom BIOSes to get support for XP, 7, etc. so I was wondering if such a BIOS exists for my board. For now I settled with 8.1 + Classic Shell, but I plan on completely moving to 7 as soon as I fix this bluescreen issue. Once again it occurs right when the installer USB loads, and I am really not sure what to do to fix it.

Try this
https://www.wincert.net/forum/topic/18176-vistaw2k8-x64-on-modern-hardware/#comment-137330

It's meant for Vista, but it says it's the same as the patch for 7.

K4sum1 wrote: *

17 Feb 2022, 20:42

Try this
https://www.wincert.net/forum/topic/18176-vistaw2k8-x64-on-modern-hardware/#comment-137330

It's meant for Vista, but it says it's the same as the patch for 7.

How can I apply this patch? Is there a program I can use?

VictorTheVictor wrote: *

18 Feb 2022, 04:16

K4sum1 wrote: *

17 Feb 2022, 20:42

Try this
https://www.wincert.net/forum/topic/18176-vistaw2k8-x64-on-modern-hardware/#comment-137330

It's meant for Vista, but it says it's the same as the patch for 7.

How can I apply this patch? Is there a program I can use?

Any hex editor, I like HXD.

K4sum1 wrote: *

18 Feb 2022, 04:28

VictorTheVictor wrote: *

18 Feb 2022, 04:16

K4sum1 wrote: *

17 Feb 2022, 20:42

Try this
https://www.wincert.net/forum/topic/18176-vistaw2k8-x64-on-modern-hardware/#comment-137330

It's meant for Vista, but it says it's the same as the patch for 7.

How can I apply this patch? Is there a program I can use?

Any hex editor, I like HXD.

So, I did just that, but it tells me acpi.sys is corrupt. I made sure to ONLY change the two lines that were needed, nothing else. Any way to get around this?

VictorTheVictor wrote: *

18 Feb 2022, 07:16

K4sum1 wrote: *

18 Feb 2022, 04:28

VictorTheVictor wrote: *

18 Feb 2022, 04:16

How can I apply this patch? Is there a program I can use?

Any hex editor, I like HXD.

So, I did just that, but it tells me acpi.sys is corrupt. I made sure to ONLY change the two lines that were needed, nothing else. Any way to get around this?

I'll look at it tomorrow, I think it may be a checksum problem. You can try rebuilding the checksum with CFF explorer.

K4sum1 wrote: *

18 Feb 2022, 08:52

VictorTheVictor wrote: *

18 Feb 2022, 07:16

K4sum1 wrote: *

18 Feb 2022, 04:28

Any hex editor, I like HXD.

So, I did just that, but it tells me acpi.sys is corrupt. I made sure to ONLY change the two lines that were needed, nothing else. Any way to get around this?

I'll look at it tomorrow, I think it may be a checksum problem. You can try rebuilding the checksum with CFF explorer.

Okay, how would I do that? Where is the checksum file? I just edited the data and moved the patched acpi.sys into NTLite's extracted image folder.

VictorTheVictor wrote: *

18 Feb 2022, 20:38

K4sum1 wrote: *

18 Feb 2022, 08:52

VictorTheVictor wrote: *

18 Feb 2022, 07:16

So, I did just that, but it tells me acpi.sys is corrupt. I made sure to ONLY change the two lines that were needed, nothing else. Any way to get around this?

I'll look at it tomorrow, I think it may be a checksum problem. You can try rebuilding the checksum with CFF explorer.

Okay, how would I do that? Where is the checksum file? I just edited the data and moved the patched acpi.sys into NTLite's extracted image folder.

K4sum1 wrote: *

18 Feb 2022, 22:10

VictorTheVictor wrote: *

18 Feb 2022, 20:38

K4sum1 wrote: *

18 Feb 2022, 08:52

I'll look at it tomorrow, I think it may be a checksum problem. You can try rebuilding the checksum with CFF explorer.

Okay, how would I do that? Where is the checksum file? I just edited the data and moved the patched acpi.sys into NTLite's extracted image folder.

acpi.zip

Oh thank you so much! It boots now. Though there is no mouse or keyboard input, which I believe is due to my xHCI drivers not working. I used "pure 64bit Win7 Intel USB 3.0+3.1 Drivers v5.0.4.43 WHQL with DPInst option" that I found on the Windows 7 subreddit. I integrated the drivers into the boot .wim and the Windows 7 Ultimate .wim. Did I do something wrong maybe?

VictorTheVictor wrote: *

19 Feb 2022, 01:19

K4sum1 wrote: *

18 Feb 2022, 22:10

VictorTheVictor wrote: *

18 Feb 2022, 20:38

Okay, how would I do that? Where is the checksum file? I just edited the data and moved the patched acpi.sys into NTLite's extracted image folder.

acpi.zip

Oh thank you so much! It boots now. Though there is no mouse or keyboard input, which I believe is due to my xHCI drivers not working. I used "pure 64bit Win7 Intel USB 3.0+3.1 Drivers v5.0.4.43 WHQL with DPInst option" that I found on the Windows 7 subreddit. I integrated the drivers into the boot .wim and the Windows 7 Ultimate .wim. Did I do something wrong maybe?

Try this
https://board.eclipse.cx/viewtopic.php?p=1957#p1957

K4sum1 wrote: *

19 Feb 2022, 01:23

VictorTheVictor wrote: *

19 Feb 2022, 01:19

K4sum1 wrote: *

18 Feb 2022, 22:10

acpi.zip

Oh thank you so much! It boots now. Though there is no mouse or keyboard input, which I believe is due to my xHCI drivers not working. I used "pure 64bit Win7 Intel USB 3.0+3.1 Drivers v5.0.4.43 WHQL with DPInst option" that I found on the Windows 7 subreddit. I integrated the drivers into the boot .wim and the Windows 7 Ultimate .wim. Did I do something wrong maybe?

Try this
https://board.eclipse.cx/viewtopic.php?p=1957#p1957

Thank you so much. Everything installed fine, though after the installation, it won't boot into the OS. It hangs on disk.sys, according to safe mode boot. Anything I can do now? I installed on my 500GB WD NVME SSD.

Oh wait was I supposed to use MBR? Because I tried GPT

VictorTheVictor wrote: *

19 Feb 2022, 03:01

K4sum1 wrote: *

19 Feb 2022, 01:23

VictorTheVictor wrote: *

19 Feb 2022, 01:19

Oh thank you so much! It boots now. Though there is no mouse or keyboard input, which I believe is due to my xHCI drivers not working. I used "pure 64bit Win7 Intel USB 3.0+3.1 Drivers v5.0.4.43 WHQL with DPInst option" that I found on the Windows 7 subreddit. I integrated the drivers into the boot .wim and the Windows 7 Ultimate .wim. Did I do something wrong maybe?

Try this
https://board.eclipse.cx/viewtopic.php?p=1957#p1957

Thank you so much. Everything installed fine, though after the installation, it won't boot into the OS. It hangs on disk.sys, according to safe mode boot. Anything I can do now? I installed on my 500GB WD NVME SSD.

You could try replacing the NVMe driver with the generic Samsung driver mod. I think you can find it on win-raid. I don't think GPT is the issue, but you can try MBR.

K4sum1 wrote: *

19 Feb 2022, 03:35

VictorTheVictor wrote: *

19 Feb 2022, 03:01

K4sum1 wrote: *

19 Feb 2022, 01:23

Try this
https://board.eclipse.cx/viewtopic.php?p=1957#p1957

Thank you so much. Everything installed fine, though after the installation, it won't boot into the OS. It hangs on disk.sys, according to safe mode boot. Anything I can do now? I installed on my 500GB WD NVME SSD.

You could try replacing the NVMe driver with the generic Samsung driver mod. I think you can find it on win-raid. I don't think GPT is the issue, but you can try MBR.

Where would I even go look for the WD NVME drivers? I have WD, not Samsung

Oh now I get a 0x80300024 error on MBR

Now that I went with MBR, it is giving me the same error for all the drives.

VictorTheVictor wrote: *

19 Feb 2022, 03:53

K4sum1 wrote: *

19 Feb 2022, 03:35

VictorTheVictor wrote: *

19 Feb 2022, 03:01

Thank you so much. Everything installed fine, though after the installation, it won't boot into the OS. It hangs on disk.sys, according to safe mode boot. Anything I can do now? I installed on my 500GB WD NVME SSD.

You could try replacing the NVMe driver with the generic Samsung driver mod. I think you can find it on win-raid. I don't think GPT is the issue, but you can try MBR.

Where would I even go look for the WD NVME drivers? I have WD, not Samsung

I know, but you can use the Samsung drivers for any system since they're universal. Also you could try deploying the wim to a MBR partition with DISM, create a MBR bootloader on that drive with EasyBCD, and boot from it.

Samsung driver mod: https://mega.nz/#!00pVkQLJ!NqJwjtrr_pRhyjaUB4jXXbxbgvhCaB62uGFGUfVOxek

Generic Phison: https://mega.nz/file/MlomEajC#vYNL1RJkrbAHxsCtCDdQ3NMwcG-xG1WAp16vQxaw-uE

Okay just tested this out on my laptop (10th gen, only NVME) and it works. Sort of. It installed and loaded but I get a black screen and screen artifacts on the top of it. I am assuming this is due to a lack of graphical drivers (10th gen Intel UHD).

VictorTheVictor wrote: *

20 Feb 2022, 04:32

Okay just tested this out on my laptop (10th gen, only NVME) and it works. Sort of. It installed and loaded but I get a black screen and screen artifacts on the top of it. I am assuming this is due to a lack of graphical drivers (10th gen Intel UHD).

I don't think so as Standard VGA Graphics Adapter should kick in. For the graphics, scour this thread and you should find some that work with your 10th Gen processor: https://www.win-raid.com/t4348f52-Intel-UHD-Graphics-Video-Driver-for-Win-x.html

Those do not currently work with 11th Generation Tiger Lake. I've tried modding them to work myself, but I can't figure out how to crack open igdklm64.sys (or whatever that file is call) in order to be able to, hopefully anyways, amend the file to get the driver to interpret 11th Gen Tiger Lake and other Intel such as 12th Gen Alder Lake and generational subsets of these such as Jasper Lake, Lake Field and so forth. Rather than bog down this thread, I'll open a new one with my issues.

Also, you said your touchpad wasn't working. That is due to it being an I2C HID Device meaning you need an I2C HID device for it to work. After that is installed, then you can use the touchpad and then install its driver. Most new BIOS do not include an option to change the touchpad between Advanced (I2C HID Device) or Basic (PS/2 Emulation) anymore, but if your BIOS has it then lucky you!

I installed the Samsung NVME drivers (now I only have the Samsung NVME, not the WD one) yet the same error occurs (disk.sys). Anything else I could do? Maybe something that will give us more information on the error? I am using regular Windows 7 GPT (I have CSM enabled too), but this exact iso worked on my laptop and got past the point where this one crashes, so I believe it is something to do with the chipset.

VictorTheVictor wrote: *

22 Feb 2022, 02:44

I installed the Samsung NVME drivers (now I only have the Samsung NVME, not the WD one) yet the same error occurs (disk.sys). Anything else I could do? Maybe something that will give us more information on the error? I am using regular Windows 7 GPT (I have CSM enabled too), but this exact iso worked on my laptop and got past the point where this one crashes, so I believe it is something to do with the chipset.

Try MBR.

https://media.discordapp.net/attachments/933570081059905577/946267609463136266/Screenshot_20220223-214817_Gallery.jpg
Same error, I even removed all other disks

And the same thing, disk.sys in safe mode

OH I figured it out! So the acpi.sys is unpatched in the install.wim, so that is why it won't boot. I simply had to patch that file, and I just have to rebuild the signature somehow. Any ideas how?

VictorTheVictor wrote: *

24 Feb 2022, 05:38

OH I figured it out! So the acpi.sys is unpatched in the install.wim, so that is why it won't boot. I simply had to patch that file, and I just have to rebuild the signature somehow. Any ideas how?

Using CFF Explorer, open the file and there should be an option somewhere that rebuilds the checksum. Rebuild it, save the file, and then integrate it into install.wim.

VictorTheVictor wrote: *

24 Feb 2022, 05:38

OH I figured it out! So the acpi.sys is unpatched in the install.wim, so that is why it won't boot. I simply had to patch that file, and I just have to rebuild the signature somehow. Any ideas how?

Use the same acpi.sys I gave you earlier.

Yeah I did that and it gets past that issue, though it freezes at the Windows loading logo finishing. I can't enter safe mode to debug the exact issue because when I press F7 I can only choose one option (I need to disable driver integrity because it notices acpi.sys was changed). Any way to make it always disable driver integrity check so I can do that and use the safe mode debugging?

Assuming Windows 7 is your default OS in the boot menu, enter this command from cmd from either another copy of Windows or the setup.

Code: Select all bcdedit.exe -set {default} TESTSIGNING ON

I would call this a huge success! Thank you so much for the help. The only odd thing I have noticed is everything seems laggy. Like I am running everything on a decade old integrated graphics card. From the UI to some games I tried, I am not sure why that is. I did install the latest 7 supported Radeon Pro graphics. Any way to debug this?