AT2k Design BBS Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Computer Support/Help/Discussion...  <--  <--- Return to Home Page
   Networked Database  Computer Support/Help/Discussion...   [1807 / 1834] RSS
 From   To   Subject   Date/Time 
Message   August Abolins    All   win7 boot stops at disk.sys   March 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.







-- 
  ../|ug

--- OpenXP 5.0.64
 * Origin: (} Pointy McPointface (618:250/1.9)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Computer Support/Help/Discussion...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0172 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2025 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.1.250224