From: kipg on
hello. i run xp and in trying to boot up, the system shuts down and restarts
again and again. I have tried "last good config," but it makes no difference.
I try to access safe mode, but it won't let me get further than trying - it
too returns me to constant rebooting. i chose 'no reboot on failure,' and
got the following stop error: 0x0000007B (0x79BB528, 0xc0000000034,
0x00000000, 0x00000000)

i ran a scan disk and it revealed no disc problems and i installed the drive
as a slave and ran malware bytes and super antispy - they found nothing. i am
afraid my hd might have contracted a boot-sector virus. i do not know.

any ideas hoe to continue?

thanks.




From: glee on
You slaved the drive in another computer and ran MBAM and SAS but didn't
do a virus scan with the anti-virus app??

What was done on the computer just prior to the problem? Did you
install any drivers, updates, hardware, or did you change any settings?
--
Glen Ventura, MS MVP Oct. 2002 - Sept. 2009
A+
http://dts-l.net/


"kipg" <kipg(a)discussions.microsoft.com> wrote in message
news:D038A103-4167-435C-8E12-C17059F0A37E(a)microsoft.com...
> hello. i run xp and in trying to boot up, the system shuts down and
> restarts
> again and again. I have tried "last good config," but it makes no
> difference.
> I try to access safe mode, but it won't let me get further than
> trying - it
> too returns me to constant rebooting. i chose 'no reboot on
> failure,' and
> got the following stop error: 0x0000007B (0x79BB528, 0xc0000000034,
> 0x00000000, 0x00000000)
>
> i ran a scan disk and it revealed no disc problems and i installed the
> drive
> as a slave and ran malware bytes and super antispy - they found
> nothing. i am
> afraid my hd might have contracted a boot-sector virus. i do not know.
>
> any ideas hoe to continue?
>
> thanks.
>
>
>
>

From: kipg on
prior to the initial problem, i ran mcafee (nothing was found) and shut down
for the night. the next morning i rebooted and got my desktop - everything
seemed normal. i clicked onto a folder and accessed a word doc. when i went
to close it, everything froze - the doc, and visible desktop icons. i waited
for 10 min or so and decided to reboot. when the system restarted it got into
a reboot cycle. i tried to get into safe mode (as i mentioned) but the
rebooting cycle continued.. and here i am.

there was no updated drivers or new devices installed - no change in any
related settings. i will say that prior to this, i was not getting any audio,
but simply changed a setting in the sound and devices - and got my audio
back. this was after i ran the aforementioned apps and before i shut down for
the evening.

any ideas?

~k


"glee" wrote:

> You slaved the drive in another computer and ran MBAM and SAS but didn't
> do a virus scan with the anti-virus app??
>
> What was done on the computer just prior to the problem? Did you
> install any drivers, updates, hardware, or did you change any settings?
> --
> Glen Ventura, MS MVP Oct. 2002 - Sept. 2009
> A+
> http://dts-l.net/
>
From: Jose on
On Feb 19, 2:09 am, kipg <k...(a)discussions.microsoft.com> wrote:
> prior to the initial problem, i ran mcafee (nothing was found) and shut down
> for the night. the next morning i rebooted and got my desktop - everything
> seemed normal. i clicked onto a folder and accessed a word doc. when i went
> to close it, everything froze - the doc, and visible desktop icons. i waited
> for 10 min or so and decided to reboot. when the system restarted it got into
> a reboot cycle. i tried to get into safe mode (as i mentioned) but the
> rebooting cycle continued.. and here i am.
>
> there was no updated drivers or new devices installed - no change in any
> related settings. i will say that prior to this, i was not getting any audio,
> but simply  changed a setting in the sound and devices - and got my audio
> back. this was after i ran the aforementioned apps and before i shut down for
> the evening.
>
> any ideas?
>
> ~k
>
>
>
> "glee" wrote:
> > You slaved the drive in another computer and ran MBAM and SAS but didn't
> > do a virus scan with the anti-virus app??
>
> > What was done on the computer just prior to the problem?  Did you
> > install any drivers, updates, hardware, or did you change any settings?
> > --
> > Glen Ventura, MS MVP  Oct. 2002 - Sept. 2009
> > A+
> >http://dts-l.net/

After you waited 10 minutes or so and rebooted your frozen system. how
did you reboot?

Power button? Pull the plug? Other?

Does the BSOD screen also say INACCESSABLE_BOOT_DEVICE?

The 0xC000034 is an indication of XP being unable to access the hard
disk or unable to find what it needs, but I'm imagine you will see
some responses with Google links pointing to the places to read about
the message but not how to fix it. Generally the readings will say:

The Stop 0x7B message indicates that Windows XP has lost access to the
system partition or boot volume during the startup process.

Most people don't care what it means, they just need to fix it!

If you still have it in some other system where you can scan the
afflicted drive with MBAM and SAS that will not hurt.

I would then move everything in the original hardware configuration
and fix it there.

Boot your afflicted system with Recovery Console using either a
genuine bootable XP installation CD or a bootable Recovery Console
CD. This is not the same as any system recovery CDs that may have
come with your system. If you do not have a genuine bootable XP
installation CD, create a Recovery Console CD.

You can create a bootable XP Recovery Console CD when no XP media is
available:

http://www.bleepingcomputer.com/forums/topic276527.html

After you boot into the Recovery Console, for each of your hard disks,
you should then run:

chkdsk /r

For example, from the Recovery Console prompt, enter:

chkdsk c: /r

Let chkdsk finish and correct any problems it might find. It may take
a long time to complete or appear to be 'stuck'. Be patient. If the
HDD light is still flashing, it is doing something. Keep an eye on
the percentage amount to be sure it is still making progress.

Remove the CD and type 'exit' to leave the RC and restart the
computer.

Then we can continue.
From: John John - MVP on
An 0x7b error during startup means that Windows lost access to the
system partition, the second parameter (0xc0000034) usually indicates
that that the controller driver is missing or corrupt. You can try
booting to the Recovery Console and run a Chkdsk on the drive and see if
things change.

If chkdsk fails to fix things you can try to replace the driver by
copying it from the WINDOWS\system32\dllcache folder to the
WINDOWS\system32\drivers folder. Which driver is it? Well, that is the
$64,000 question. You're looking for a .sys file (a driver), for all
it's worth it won't hurt anything to copy all the .sys files from the
dllcache to the drivers folder.

John

kipg wrote:
> hello. i run xp and in trying to boot up, the system shuts down and restarts
> again and again. I have tried "last good config," but it makes no difference.
> I try to access safe mode, but it won't let me get further than trying - it
> too returns me to constant rebooting. i chose 'no reboot on failure,' and
> got the following stop error: 0x0000007B (0x79BB528, 0xc0000000034,
> 0x00000000, 0x00000000)
>
> i ran a scan disk and it revealed no disc problems and i installed the drive
> as a slave and ran malware bytes and super antispy - they found nothing. i am
> afraid my hd might have contracted a boot-sector virus. i do not know.
>
> any ideas hoe to continue?
>
> thanks.
>
>
>
>