[pcductape] Re: STOP error - Blue Screen

  • From: "Carl" <ctm007@xxxxxxxxxxxxxx>
  • To: <pcductape@xxxxxxxxxxxxx>
  • Date: Wed, 22 Dec 2004 13:32:10 -0600

Hey Trapper,

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:
"  "STOP:0x000007B Inaccessible Boot Device" message when booting Windows NT.

Microsoft Windows NT 3.5x 

The following STOP message appears when you restart a computer with Windows NT: 
STOP: 0x0000007B Inaccessible Boot Device. 

This problem 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 ----- 
  From: trapper 
  To: pcductape@xxxxxxxxxxxxx 
  Sent: Wednesday, December 22, 2004 1:10 PM
  Subject: [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 happens.
  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.

  Carl wrote: 
    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 "debuging".


GIF image

Other related posts: