|
|
|
Stop error 0x0000007B
Showing all messages in thread #1250954701
Windows 2000 Annoyances Discussion Forum
The following are all of the messages in this thread (8 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
|
Stop error 0x0000007B
Saturday, August 22, 2009 at 8:25 am
Posted by R. Hinse
(4 messages posted)
After registry cleaning (Easy Registry) and defrag (Ausogics) I
cannot boot Win2K; stop error.
1. I cannot boot into Safe Mode - stop error
2. Ran Repair from install disk - no help
3. Ran last known good configuration from advanced menu - no good
4. Ran chkdsk from Recovery Console - no errors reported
5. Entered listsvc in Recovery Console to try to identify possible
bad IDE drivers - only use generic driver; atapi
6. Enabling boot logging produces no log since the stop error
apparently occurs before the session manager loads or before
it reaches the point where the log is written to disk. The stop
error occurs approximately 50-60% through the Starting Windows
graphical boot screen.
7. Also tried fixboot c: and fixmbr in Recovery Console - no help
I don't think this a hardware error because I can boot into
Recovery Console without the install disk; it is installed in the
boot menu. This is probably some sort of registry error but I have
no way to pinpoint it. A virus is unlikely as I have AVG installed and
have had no problems.
The following is the listsvc output only for boot or system:
Boot/ System Service Comment
B ACPI Microsoft ACPI driver
B AIC78xx
B AMDAGP AMD 1 G AGP Bus Filter
S Antiak AK Driver
B ATAPI Standard IDE/ESDI Hard Disk Controller
S AvgLdx86 AVG Free Loader Driver x86
S AvgMfx86 AVG Free On-access Scanner Minifilter Driver x86
S AvgTdix AVG Free Network Redirector
S Awlegacy
S Bantext Belarc SMBios access
S Beep
S CdAudio
S Cdn4_2k
S CDROM Cd-ROM Driver
B Diskperf
B Dmio Logical Disk Manager Driver
B Dmload
B Fltmgr
S Fs-Rec
B Ftdisk Volume Manager Driver
B Geruwa
S i8042prt i8042 Keyboard abd PS/2 Mouse Port Driver
S InCDPass
S InCDrec
S iNCDRM InCD Reader
B isapnp PnP ISA/EISA Bus Driver
S Kbdclass Keyboard Class Driver
S KbdHID Keyboard HID Driver
B KSecDD
S lbrtfdc
S mnmdd
S Mouclass Mouse Class Driver
B MountMgr
S MrxSmb MRXSMB
B Mup Mup
B NDIS NDIS System Driver
S NetBios NetBios Interface
S NetBT NetBios over TCP/IP
S Npfs
B ohci1394 NEC Firewire OHCI Compliant IEEE 1394 Host Controller
S Parport Parallel Port Driver
B PantMgr
B PCI PCI Bus Driver
S PCIDump
B PCIIde
S Rdbss
S redbook Digital CD Audio Playback Filter Driver
S PpcSs Remote Procedure Call
S Serial Serial Port Driver
S Sfloppy
S sglfb
B Snapman Acronis Snapshots Manager
S Tcpip TCP/IP Protocol Driver
B Teefer Teefer for NT
S tga
S VgaSave
These were listed as disabled but appeared on a list in another
forum indicating they should be active:
Abiosdsk
Atdisk
Fastfat
BusLogic
ultra66
I enabled these one at a time but their addition did not fix the
stop error.
Any further suggestions as to how I might solve this problem
would be appreciated. I really do not want to reinstall.
[Reply or follow-up to this message]
| |
re: Stop error 0x0000007B
Saturday, August 22, 2009 at 9:09 am
Posted by Steve
(23810 messages posted)
http://support.microsoft.com/kb/822052
[Reply or follow-up to this message]
|
re: Stop error 0x0000007B
Saturday, August 22, 2009 at 10:23 am
Posted by R. Hinse
(4 messages posted)
Yeah already read it; no help!
Any specific driver/service or registry fix?
On Saturday, August 22, 2009 at 9:09 am, Steve wrote:
>
>
>
>http://support.microsoft.com/kb/822052
[Reply or follow-up to this message]
|
re: Stop error 0x0000007B
Saturday, August 22, 2009 at 12:19 pm
Posted by druggas
(17 messages posted)
<<2. Ran Repair from install disk - no help>>
Just want to clarify this. Did you use the repair console, or go to setup first and
then do a repair?
Because you will want to boot up with your 2,000 cd and then go to setup and then
do a repair.
I can't imagine that it wouldn't fix your registry and get you up and running without
losing any of your data.
On Saturday, August 22, 2009 at 8:25 am, R. Hinse wrote:
>After registry cleaning (Easy Registry) and defrag (Ausogics) I
>cannot boot Win2K; stop error.
>
>1. I cannot boot into Safe Mode - stop error
>2. Ran Repair from install disk - no help
>3. Ran last known good configuration from advanced menu - no good
>4. Ran chkdsk from Recovery Console - no errors reported
>5. Entered listsvc in Recovery Console to try to identify possible
> bad IDE drivers - only use generic driver; atapi
>6. Enabling boot logging produces no log since the stop error
>apparently occurs before the session manager loads or before
>it reaches the point where the log is written to disk. The stop
>error occurs approximately 50-60% through the Starting Windows
>graphical boot screen.
>7. Also tried fixboot c: and fixmbr in Recovery Console - no help
>
>
>
>I don't think this a hardware error because I can boot into
>Recovery Console without the install disk; it is installed in the
>boot menu. This is probably some sort of registry error but I have
>no way to pinpoint it. A virus is unlikely as I have AVG installed and
>have had no problems.
>
>The following is the listsvc output only for boot or system:
>
>Boot/ System Service Comment
>B ACPI Microsoft ACPI driver
>B AIC78xx
>B AMDAGP AMD 1 G AGP Bus Filter
>S Antiak AK Driver
>B ATAPI Standard IDE/ESDI Hard Disk Controller
>S AvgLdx86 AVG Free Loader Driver x86
>S AvgMfx86 AVG Free On-access Scanner Minifilter Driver x86
>S AvgTdix AVG Free Network Redirector
>S Awlegacy
>S Bantext Belarc SMBios access
>S Beep
>S CdAudio
>S Cdn4_2k
>S CDROM Cd-ROM Driver
>B Diskperf
>B Dmio Logical Disk Manager Driver
>B Dmload
>B Fltmgr
>S Fs-Rec
>B Ftdisk Volume Manager Driver
>B Geruwa
>S i8042prt i8042 Keyboard abd PS/2 Mouse Port Driver
>S InCDPass
>S InCDrec
>S iNCDRM InCD Reader
>B isapnp PnP ISA/EISA Bus Driver
>S Kbdclass Keyboard Class Driver
>S KbdHID Keyboard HID Driver
>B KSecDD
>S lbrtfdc
>S mnmdd
>S Mouclass Mouse Class Driver
>B MountMgr
>S MrxSmb MRXSMB
>B Mup Mup
>B NDIS NDIS System Driver
>S NetBios NetBios Interface
>S NetBT NetBios over TCP/IP
>S Npfs
>B ohci1394 NEC Firewire OHCI Compliant IEEE 1394 Host Controller
>S Parport Parallel Port Driver
>B PantMgr
>B PCI PCI Bus Driver
>S PCIDump
>B PCIIde
>S Rdbss
>S redbook Digital CD Audio Playback Filter Driver
>S PpcSs Remote Procedure Call
>S Serial Serial Port Driver
>S Sfloppy
>S sglfb
>B Snapman Acronis Snapshots Manager
>S Tcpip TCP/IP Protocol Driver
>B Teefer Teefer for NT
>S tga
>S VgaSave
>
>These were listed as disabled but appeared on a list in another
>forum indicating they should be active:
>
>Abiosdsk
>Atdisk
>Fastfat
>BusLogic
>ultra66
>
>I enabled these one at a time but their addition did not fix the
>stop error.
>
>Any further suggestions as to how I might solve this problem
>would be appreciated. I really do not want to reinstall.
[Reply or follow-up to this message]
|
re: Stop error 0x0000007B
Saturday, August 22, 2009 at 8:36 pm
Posted by Steve
(23810 messages posted)
Probably screwed up the PC with the Registry Cleaner. If you made a backup of Registry
before the cleaning, then restore it, and see if that helps.
[Reply or follow-up to this message]
|
re: Stop error 0x0000007B
Saturday, August 22, 2009 at 8:47 pm
Posted by R. Hinse
(4 messages posted)
I don't mean to be insulting, but when I said install disk that can
mean only one thing. Yes, repair was run from the Setup menu
after booting from the Install disk. I don't think you can run repair
from any other media, certain not the Recovery Console
[Reply or follow-up to this message]
|
re: Stop error 0x0000007B
Sunday, August 23, 2009 at 3:37 pm
Posted by C K
(6910 messages posted)
There are multiple repairing options from the recovery console if you know all of
the possible commands, which few of the real experienced pro's even do. What he
was specifically asking was if you were doing a repair install on the current damaged
Windows system. If it completed successfully, were you able to boot into the repaired
system, which is actually a new fresh install, that has imported (hopefully) uncorrupted
data, applications, added drivers and program files and associated data and files?
If a repair install, (or repair reinstall as some put it) doesn't work, then you
have a registry that is so corrupt that when necessary entries are taken from the
old registry, you "infect" the new registry.
If this is happening, then you have no choice but to recover all the data that you
can, wipe the old install of Windows and install clean...
The big misconception is that registry cleaners will work miracles or speed up your
machine. Simply not true and many times, even the better ones will damage or destroy
your install. SOmetimes it may not be noticeable, sometimes it is catastrophic.
There is simply no way for any programmer of a registry cleaning app to anticipate
all possible scenerio's. The other misconception is that Windows loads the whole
registry into memory and the bigger it is, the slower Windows will run. Again not
true. Windows kernel loads what necessary, calls for what it needs, as will other
apps and processes. Cleaners also rarely fix any damage because many entries are
unique to a machine after a person starts using it. What may be a mistake or an
unkown in one machine, may be necessary in another machine. Many entries are unused
when Windows is installed, and you will see many vendors names in there whether you
have that software installed or not. The explanations is complicated on that, but
bottom line, they won't hurt your machine or slow it down.
Now remove something that Windows needs or has to go looking for and can't find,
now THAT slows your machine down, will crash/BSOD it, or destroy it. The registry
is the brains memory banks and operating instructions cache. Even a skilled neuro
surgeon can't gaurantee the outcome to 100% accuaracy everytime and can make a mistake
that can be fatal. Same can be said with registry cleaners and the one you used I
wouldn't touch. You aren't the only person that has posted here about that one and
it's fatal outcome when used.
The old timers here seldom use them, and when we do, we have complete images/backups
of the whole disc and the registry before we do anything to it. We've learned the
hard way!! Personally, working on thousands of machines, reg cleaning has made little
if any diff, other than making your pocket a little lighter (if you purchased it),
and you temper flair more often.......
Good Luck, you will spend more time trying to fix it than just swallowing hard and
starting over, unless you get really lucky IME.
[Reply or follow-up to this message]
|
re: Stop error 0x0000007B
Sunday, August 23, 2009 at 7:56 pm
Posted by R. Hinse
(4 messages posted)
Couldn't agree more. I am not a novice at correcting problems
like this but neither am I a pro. Maybe I have just been extremely
lucky in the past and things have not gotten so bad that fixing one
problem causes another. However, this time I may have hit the
proverbial brick wall and will probably have to reinstall (i.e. a
complete reinstall not just a repair).
I have not had problems with registry cleaners in the past but I
probably should have stuck to RegCure. You are so right about
registry cleaners and I am surprised I haven't had more problems.
In posting this problem, I was hoping that at least one person
might have had a particular experience or a flash of genius that
would remedy the problem with little or no effort. My hopes
dashed, I guess I'll just try to recover as much data as possible
before re-installing. I'm fortunate here in that I dual boot with a
Linux system which can mount and read my Fat32 system.
Maybe I should just stick with Linux. It doesn't seem to suffer
the same problems that the bloated Windows systems do.
Thanks for your comments.
[Reply or follow-up to this message]
| |
| |
Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
| |
Return to the Windows 2000 Discussion Forum
|
|
|
|
