I would tend to believe the
msg..it is put out by the makers.|
As you can see there is no mention of memory..is is the OS being
corrupt and in your case the boots disk as well..this would lead me
towards the fat table being messed up..a fsisk/mbr might have worked as
well. Fdisk is of course going to nuke it all down..if you just
re-installed the windows it says it might still be there. This would
tell me that the bug is not in I wonder but outside of windows
affecting boot and windows. I would have gone with the least and
quickest method ( fix windows) first. Then if it still was messed up I
would have gone with the fdisk and format.
The only part of this msg that bothers me is the "windows NT.."???
When a boot drive is inaccessible it usually means that the FAT is
messed up. Dos considers these tables to be so important that it will
make two of them, so that when one goes down the other can be put in
Do a search on them and read about them..Good stuff to know..Read about
low level formatting also..!
I went to google.com and did a search for "STOP: 0X000007B
INACCESSIBLE Boot Device", which is the error message I got on my
Windows 2000 unit (when it was sick) and google search revealed:
Boot Device" message when booting Windows NT.
Windows NT 3.5x
STOP message appears when you restart a computer with Windows NT: STOP:
0x0000007B Inaccessible Boot Device.
may caused by a boot sector virus. Check any disks for viruses that may
have been used in the computer since the last time you were able to
successfully restart it.
Solution If a virus has already infected the Windows NT computer,
and the virus cannot be removed, then the operating system will have to
be reloaded. If reinstalling the operating system will not remove the
virus, the disk drive will have to be low-level formatted.
Now, I am really confused. The computer repair
man told me the Windows 2000 operating system was corrupted due to
Service Pack 4 but the google search says a virus caused the error.
Who am I to believe?
Original Message -----
Wednesday, December 22, 2004 1:10 PM
[pcductape] Re: STOP error - Blue Screen
Carl I honestly don't
believe it was anything to do with memory chips. None of what you have
said would add up to anything doing with memory..
Debugging means it is fixing itself..so why do anything during that
you could use the ctrl-Alt-del. to stop it I suppose..
I would just let it run it's process. If it is going to mess it up
anyhow what is the difference..Pulling a plug in the middle of a
process is not what we want to do..
The key here is " Middle" or as in " already started" Then that would
still depend on what has started and if the computer can restore itself
after re-boot, assuming you can re-boot.
If you want to prove this out, I suppose you could mimmick the process
all over...Mess it all up again and see if the memory is where it is
at..or another way would be to research it thru yourself and see what
Now that your back up on line another thing you could do is punch the
error msg into the Internet and see what comes up.
Actually I was in Outlook Express and it was
in the process of "debuging" and would not shut down and that is why I
pulled the plug. Now, you think it was Service Patch 4?
Two lessons I've learned:
1- When a blue screen appears, pull the
memory chips myself,
2- Do not pull the plug when a program is