-
win7 boot stops at disk.sys
From
Ogg@VERT/CAPCITY2 to
All on Thursday, March 20, 2025 22:25:00
I've been tasked to investigate a win7 32bit system that is
failing to load. It's an Acer Aspire 7715Z
I tried using a windows repair disk (created with another win 7
32bit system) ..but it doesn't get past the "select
language:US"
I can enter the Advanced Boot Options menu (via repeated F8
hits until it pops up).
I can select "Disable Restart" from that list and the system
enters BSOD with STOP code 0x000000ed
I've researched that stop code and the common strategy is to
get to the point where one can run CHKDSK /X /R /F ..but "Safe
Mode with command line) doesn't take me there either - the
system just stalls for a while, and then restarts. The last
driver loaded/reported is "disk.sys".
Selecting "Enable bootlogging" doesn't seem to write to the
ntbtlog.txt file in \Windows\System32 like it should.
Does anyone here have experience in sorting out this issue?
I can boot the pc with a linux live-cd (the Acer supports
64bit, so I chose antiX x64 Base) ...and that looks great.
fdisk -l lists the partitions fine. /dev/sda1 /dev/sda2 and
/dev/sda3 look good.
sudo mount /dev/sda3 /mnt ..works great and allows me to look
around on the Windows partition.
The driver files in /mnt/Windows/System32/drivers are viewable.
Should I just place all the matching driver files with the ones
from my good win7 32bit system?
Or.. should I only replace disk.sys first?
Common wisdom seems to indicate that the problem driver is
usually the one *after* disk.sys. But.. I can't be sure what
that next driver it was trying to load. If I could be sure
what that one is, maybe I could rename it so that it wouldn't
load?
If I look at \Windows\System32\ntbtlog.txt from my good win7
32bit machine, the next file after disk.sys is Classpnp.sys
So.. any ideas on how to resolve this mystery? Appreciated.
--
../|ug
--- OpenXP 5.0.64
* Origin: Ogg's Dovenet Point (723:320/1.9)
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
-
From
MRO@VERT/BBSESINF to
Ogg on Friday, March 21, 2025 00:20:50
Re: win7 boot stops at disk.sys
By: Ogg to All on Thu Mar 20 2025 10:25 pm
> I've been tasked to investigate a win7 32bit system that is
> failing to load. It's an Acer Aspire 7715Z
>
> I tried using a windows repair disk (created with another win 7
> 32bit system) ..but it doesn't get past the "select
> language:US"
>
> I can enter the Advanced Boot Options menu (via repeated F8
> hits until it pops up).
>
> I can select "Disable Restart" from that list and the system
> enters BSOD with STOP code 0x000000ed
>
> I've researched that stop code and the common strategy is to
> get to the point where one can run CHKDSK /X /R /F ..but "Safe
> Mode with command line) doesn't take me there either - the
> system just stalls for a while, and then restarts. The last
> driver loaded/reported is "disk.sys".
>
> Selecting "Enable bootlogging" doesn't seem to write to the
> ntbtlog.txt file in \Windows\System32 like it should.
>
> Does anyone here have experience in sorting out this issue?
>
> I can boot the pc with a linux live-cd (the Acer supports
> 64bit, so I chose antiX x64 Base) ...and that looks great.
>
> fdisk -l lists the partitions fine. /dev/sda1 /dev/sda2 and
> /dev/sda3 look good.
>
> sudo mount /dev/sda3 /mnt ..works great and allows me to look
> around on the Windows partition.
>
> The driver files in /mnt/Windows/System32/drivers are viewable.
>
> Should I just place all the matching driver files with the ones
> from my good win7 32bit system?
>
> Or.. should I only replace disk.sys first?
>
> Common wisdom seems to indicate that the problem driver is
> usually the one *after* disk.sys. But.. I can't be sure what
> that next driver it was trying to load. If I could be sure
> what that one is, maybe I could rename it so that it wouldn't
> load?
>
> If I look at \Windows\System32\ntbtlog.txt from my good win7
> 32bit machine, the next file after disk.sys is Classpnp.sys
>
> So.. any ideas on how to resolve this mystery? Appreciated.
Reinstall windows keeping the file system intact.
your windows directory and your files will be moved to a windows.old dir
dont waste your time playing detective and splicing in files that might not even be the correct versions.
BEFOREHAND, make sure you backup any important files using your linux boot cd.
---
þ Synchronet þ ::: BBSES.info - free BBS services :::
-
From
Exodus@VERT/PHARCYDE to
Ogg on Friday, March 21, 2025 10:20:19
O> I've been tasked to investigate a win7 32bit system that is
O> failing to load. It's an Acer Aspire 7715Z
Format and reinstall windows. Driver issue somewhere. I had an XP instance
on a machine NOT install because there was a stick of ram failing. Other OSes
installed and ran fine, but not windows.
... I would strongly oppose apathy, if I cared...
--- Renegade v1.35/DOS
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (723:1/4)
þ Synchronet þ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
-
From
MRO@VERT/BBSESINF to
Exodus on Saturday, March 22, 2025 13:25:51
Re: Re: win7 boot stops at disk.sys
By: Exodus to Ogg on Fri Mar 21 2025 10:20 am
> O> I've been tasked to investigate a win7 32bit system that is
> O> failing to load. It's an Acer Aspire 7715Z
>
> Format and reinstall windows. Driver issue somewhere. I had an XP instance
> on a machine NOT install because there was a stick of ram failing. Other
> OSes installed and ran fine, but not windows.
>
well they could just keep the file system intact and copy over the appdata shit later. sometimes it's useful to have those files for when you reinstall your browser and other programs.
---
þ Synchronet þ ::: BBSES.info - free BBS services :::