Prev: Message at Shutdown regit.exe dllinitization failed
Next: icons refresh to much when close folders
From: glee on 19 Feb 2010 09:51
As the other respondents have already stated, you should run chkdsk with
the /r switch, from Recovery Console, once you have the drive back in
the original computer.
My only other comment is that you ran your virus scan prior to the
problem, from within Windows. I would run a virus scan of the drive
while it is slaved in the other computer, now.....that will help ensure
any virus or rootkit can be detected, while the affected drive is not
the boot drive.
Glen Ventura, MS MVP Oct. 2002 - Sept. 2009
"kipg" <kipg(a)discussions.microsoft.com> wrote in message
> 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 -
> seemed normal. i clicked onto a folder and accessed a word doc. when i
> to close it, everything froze - the doc, and visible desktop icons. i
> 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
> related settings. i will say that prior to this, i was not getting any
> but simply changed a setting in the sound and devices - and got my
> back. this was after i ran the aforementioned apps and before i shut
> down for
> the evening.
> any ideas?
> "glee" wrote:
>> You slaved the drive in another computer and ran MBAM and SAS but
>> 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
>> Glen Ventura, MS MVP Oct. 2002 - Sept. 2009
From: "db" databaseben at hotmail dot on 19 Feb 2010 11:48
boot looping can sometimes
be resolved by running the
command at the disk prompt:
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Veteran of the Armed Forces
- Microsoft Partner
~~~~~~~~~~"share the nirvana" - dbZen
"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?
From: kipg on 24 Feb 2010 03:08
I decided to start with the most simplest of your suggestions ("...replace
the driver by copying it from the WINDOWS\system32\dllcache folder to the
And I must say that this worked. I copied the file from another xp install
on another drive and pasted it on the problem drive - and my original desktop
appeared once I reconnected the drive. however it seems that the ATI drivers
my system utilizes were not found. so my dt looked like it was in some sort
of safe mode. but i re-installed those drivers and everything was pretty much
back to normal.
But now I have no internet connectivity. running an ie diagnosis the error
indicates that the "winsock catalog needs a reset." i found a fix, but it had
I might need to post another thread for this issue, but i thought i would
mention it. But thank you for the initial suggestion - at least i have access
to my docs/files/mp3s.
"John John - MVP" wrote:
> 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.
From: kipg on 24 Feb 2010 03:10
thanks for your suggestion, but John John - MVP offered a solution. you can
read about it if you wish.
> boot looping can sometimes
> be resolved by running the
> command at the disk prompt:
> DatabaseBen, Retired Professional
> - Systems Analyst
> - Database Developer
> - Accountancy
> - Veteran of the Armed Forces
> - Microsoft Partner
> - @hotmail.com
> ~~~~~~~~~~"share the nirvana" - dbZen
From: kipg on 24 Feb 2010 03:11
thanks for your suggestions, but John John - MVP offered a solution. you can
read about it if you wish.
> As the other respondents have already stated, you should run chkdsk with
> the /r switch, from Recovery Console, once you have the drive back in
> the original computer.
> My only other comment is that you ran your virus scan prior to the
> problem, from within Windows. I would run a virus scan of the drive
> while it is slaved in the other computer, now.....that will help ensure
> any virus or rootkit can be detected, while the affected drive is not
> the boot drive.
> Glen Ventura, MS MVP Oct. 2002 - Sept. 2009