Printable View
Well, in a follow up tohttp://techzonez.com/forums/showthread.php?t=10244 - sorry about starting a new thread. It was an old thread and did not seem to generate much interest. Anyway, I run repair and when it reboots - it blue screens - even in safe mode. I want to fix this short of running True Image as the image is sort of old. Thanks.
0x0000007B (0xf7c4a640, 0xc0000034, 0X0000000, 0x00000000)
i use ghost i create a small fat32 partiton, then i get my sys cleaned with remaing space, and tweak it to my liings then i ghost it and make the file read only, making it hard to become corrupted, only that has kept my notebook in good running conditon since my tower died, this thing has no cd burner, lol, no cd drive to speak of making it ahrd to reinstall in case of failure or bsod, iv stayed away from winamp never bsod since,
So are you also getting the "Inaccessible Boot Device" message along with the BSOD?
I don't remember. Next time I see it..........I'm running AV's now.
I know how to fix it! :D Need I continue? :Peace:
no. Does mini PE not have a diagnostic repair unit? - sure conan, and lose all my work on the new theme, - :(Quote:
Originally Posted by rik
Don't you have a spare drive to backup files?Quote:
Originally Posted by lynchknot
True image is over a month old. I will lose everything new. I wish I could use just the files I need from true image rather than restoring the whole partition
Isn't there space to back up just your theme work without having to re-image?
How do I get to them? If I can get to them, then why can't I go to the BSOD store and replace the windows files that are corrupted.
**edit - could the fact that I am using WD hard drive for windows and MS does not have drivers in winxp CD?
Hold on let's backtrack a bit. You've got 2 hard drives right? Why can't you save your theme files on another drive to back-up your work? How do you get to them? Save them to the drive without Windows.Quote:
Originally Posted by lynchknot
Ok I already did that with one of the file viewers. Now if only I can back up everything but what is wrong. Just as bad is losing all my updated progs and configs.
Is this the second parameter? There are too many zeros thoughQuote:
The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:
* Disks or storage controllers that are failing, defective, or improperly configured.
* Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.
Quote:
0x0000007B (0xf7c4a640, 0xc0000034, 0X0000000, 0x00000000)
What the heck happened now ? thought you already had every PC problem and now you invented a new one :p
I think you had so many security apps running that you wore the ram out.
http://support.microsoft.com/default...b;en-us;324103
Take a look at that site if you haven't already.
I have had chkdsk /r fix that before but it is really dependant on whether it's HW or SW causing the issue. Unfortunately I know of no way to check that short of possibly d/l and running the appropriate diags for your drive from WD.
**edit - funny how this all happend exactly when Outpost time ran out:
**edit - "fixboot cannot find the system drive"Quote:
Serious problem with Outpost Firewall Pro?
Hi all, I am using the 30day trial of Outpost Firewall PRO and just now I got a blue screen on my computer saying some errors and my HDD just stopped working, I switched my PC off and on, the HDD didnt turn on for about 20 secs. When it did and when Windows XP loaded Windows said my system is recovering from a serious system error, and would I like to send an error report to help disgnose the problem. I clicked send error report, and my browser opened a page saying the following.
Solution Found: Contact Agnitum to obtain the update
Problem Description
Thank you for submitting an error report. The error was likely caused by Outpost Firewall Pro.
Problem Resolution
Outpost Firewall Pro was created by Agnitum . Agnitum informed Microsoft that they have a solution available for the problem you reported. To learn more about the solution, Agnitum recommends that you visit the following website:
Gohttp://www.agnitum.com/download/outpostpro.html
Additional Information
* Microsoft did not create, nor does it provide technical support for Outpost Firewall Pro.
* If you have trouble installing the fix or the problem you reported persists, please contact Agnitum and alert them of the problem.
The exact same thing happened on my other PC down stairs about 5 days after installing Outost. Could someone please tell me what exactly happened, surely this isnt good for my PC.
quick question did you change your mobo right before the problem started?
No I have changed nothing but installed latest Outpost firewall over previous. I used PE to rename Outpost but It did not work. This could also be related to adaware deleting files.
I had a boot right to blue screen problem a few weeks ago and i turns out windows doesnt like people to install entirely different motherboards. Your problem sounded like that but i guess not. Good Luck with your problem.
Thanks. I guess there is no immediate solution. I have copied "my documents" my desktop and application data (firefox) to the other drive. I'm going to use true image to restore.
Does it BSOD all the time, on every startup? Are you able to use regcleaner and delete the outpost entries, then re-install demo outpost -fooling it- and see if it works?
And did you visit the Agnitum site to see what they recommend?
In place install.
boot from xp disk - choose install.
finds old installation - asks if you want to fix ...erm yup. (press R)
gets rid of old install and rewrites system keeping all files and drivers intact.
You have to re-install all the patches and updates but you keep all your data - cool.
You should also make yourself a BART disk go to http://www.nu2.nu/pebuilder for instructions - everyone needs a bart disk and some modded plugins for it - this could be the start of a new thread.
Oh and that wsaupdate thing you should also edit out of the registry and remove the wsaupdate call so you can delete the cloned file.
I found this link in my MSDN flash newsletter... a new KB from 7th Jan 05, not sure if you've seen it...
http://support.microsoft.com/?kbid=891892&SD=tech
it might be useful.