On 20 Mar 2025, August Abolins said the following...

 AA> Common wisdom seems to indicate that the problem driver is  
 AA> usually the one *after* disk.sys.   But.. I can't be sure what  
 AA> that next driver it was trying to load.

If you can boot into to a command prompt on that actual machine you can try
running the System File Checker utility:

sfc /scannow


If you can't get that machine booted into a command prompt, you can try taking
the HD out and mounting it into another Win 7 machine.  If the drive letter was
E: then you can run:

sfc /scannow /offbootdir=E:\ /offwindir E:\Windows

That'll check all of the Windows system files and replace any corrupted
versions.  Failing that booting to a Windows 7 CD/USB and doing an installation
repair could also work.


Jay

... Sure, I drink brake fluid. But I can stop anytime!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: Northern Realms (618:400/23)