What do you do when your ASUS notebook corrupts your OS?

What do you do? Just use the stupid "repair" disk that just wipes ur partition clean?

Im getting sick of this happening says my registry is gone 0xc000000f... gettin sick of this happen every time it wants to do this.

So can a use a live linux cd and try to take a default reg file from the third partition? Or is it possible to use the registry backup files those anti spyware programs make? I think i got one a week old so any thoughts?

 

A more detailed explanation of your problem would result in a better suggestion from the masses.

If you're getting this problem a lot, there is a chance your drive is malfunctioning, but it could also be you are not shutting down properly.

I've seen thousands of computer errors, but not one ever said your registry has gone 0xc00000f.

You can restore your registry if needed from the c:\windows\repair directory or recovery points, if that is indeed what is happening, but that's a fairly rare thing to need to do.

 

Vista, ASus OEM OS. I can take the hdd though and pop it in my desktop.

I was just on the desktop about to open firefox but BSOD b4 i could even click the short cut. Didnt install anythign strange, ive had this happen so many times with little thoughts on how to fix it.
Ill take a pict of what it shows me.
Wow lots a smudges and prints

 

For an immediate fix, I suggest the following things to try:
a) Reboot Windows, press F8 at the splashscreen, select "Last Known Good Config".
b) Reboot in Safe Mode, assuming it boots, and restore the computer to a recent restore point.
c) Follow the instructions on the screen in your photo (Windows Recovery Console). You need a standalone WinXP CD.

For identifying the problem:
a) If it's always the same problem/error code, then I suspect software.
b) If they are different problems/error codes every time, I suspect HDD is malfunctioning.
(this is of course not certain)

If the former, you could do a clean install, and only install the stock drivers and most essential applications first. Run for a few days (or for a period larger than what you typically get between two consecutive instances the error pops up). If the error doesn't pop up, then you can assume the cause is some software you install later on.

Then you could start install software in batches, and let the computer run for the same interval between batches. This may allow you to identify with some confidence what software is causing the trouble.

This may or may not be possible, depending on how long it typically takes for the error to creep up.

 

bobasp1
I do not understand the title of your thread.
Notebook (ASUS or any other brand) can't corrupt OS

 

Sure it can. Depends what you include in your definition of "notebook".

 

Did you do a windows update before this happened? I remember reading that this happened to vista when system updates go awry. You'll probably need to do a fresh install. Or, better yet, install XP.

 

Asus has back disk and will reinstall back all the applications. However, if you change the hard drive, it may not work.

 

I do not include owner

 

most of the time, that error actually occurs because of ntfs corrupt.

It sounds like you don't have a Vista DVD, correct? If you cannot follow E.B.E.'s instructions, do the following


Step 1

download RC.iso from the following link:

http://www.thecomputerparamedic.com/rc.iso

You need to burn this image to a CD and boot your computer with it--this is different than burning a file to a CD. If you do not know how to burn an ISO image, then download the following program to another PC and install it.

make certain you download the proper installation for your version of windows. Open MY COMPUTER, choose HELP > ABOUT. Note the service pack and get the appropriate version of the iso burner power toy

http://isorecorder.alexfeinman.com/isorecorder.htm

After installation, reboot, then right click the RC.iso file you downloaded above and choose COPY IMAGE TO CD.

Then reboot your broken PC with that CD in the CD-ROM drive.

This will give you a recovery console to use to run

Insert the cd into the non-functioning PC



STEP 2

When boot begins, a windows setup will appear to start, but you will be taken to a recovery console.

You will need to select your windows installation by pressing a number, most likely 1

Windows will ask you for a password

If you have XP home, press enter...there is no password

If you have XP Pro or Vista, you need to enter the password you set when you installed your OS.

After entering the password, you will find yourself at a command prompt that looks like this

c:\windows

type
chkdsk /r
<enter>

follow the prompts, then when it is complete, remove the CD

type

EXIT

<enter>

the machine will reboot

Did that fix it?

 

A and B send me to that screen in picture.
C if i use the retail disk it basically wipes out my drivers which some cant be fixed with the drivers disk.

I was on the phone about asus many times over the past year. Basicly this happens once every 2 months. Ive seen it just crap out when im on the desktop trying to open the calculator, trying to listen to music, about to use Firefox.

I did a test to see if i could make it screw up with everything stock no extra programs or drivers just a clean reformat. It took about 3 weeks but I wanted to make sure wasn't an outside program I was using.

Ill try it out. Can I hook the hdd up to my desktop to chkdsk it or its best to use it on the laptop it self?

Oh and Ive ran hdd tests to make sure its not a bad hdd. Also the vista updates were installed a few days before it happened it was just the stupid defender program. I didn't see any other vista updates after that. Personaly id like to see what caused it to BSOD because it did a memory dump so i can see what happened.

thanks for everyone's input

 

I think that chkdsk on the desktop will be just as well (and simpler) than gerryf19's method. Unless of course there is something in his post that I do not follow, but basically he covers a method to run chkdsk without a working Windows installation.

Given that you did those tests that you mentioned (e.g., running stock), I don't see what other option you have other than send it to ASUS, under the warranty. Explain to them that you ran stock and it did the same thing, and also that they won't see it as soon as they recover Windows, it takes a while before it develops. It will be up to them to decide what to change in that computer... I sure don't know what could be causing this.

 

They replaced the mobo twice actually because of faulty vga chip. G2S-A1 should of been fully tested b4 releasing the drivers and a better hardware check too.


Also heres what i got when i put in the RC disk it was about half way from botton the recovery menu thing. I never got to the part were i can chkdsk it so I just hooked it up to my desktop its XP. It found a few files but im not sure if its the ones i need.

 

If your desktop is vista, yes, you can run the command a
after mounting it as a second drive.

make sure you switch the drive, though, and if the desktop is VISTA run this command instead

chkdsk d: /b

(or whatever the drive letter assigned)

/b is a new switch with Vista that locates bad sectors, recovers information if possible and re-evaluate the bad sectors to see if they are "really" bad.

 

If you don't have VISTA on the desktop, use the /r switch

 

Just to clarify:

You can run it in XP as well on a second (or even USB) drive. The letter will depend on the partition setup on the desktop and laptop HDDs.

To the OP: if you are at the 3rd repair, you could request a complete replacement notebook, perhaps with a different model, instead of bothering about this problem any longer.

Not sure they'll agree, but you can ask at least.

 

Actually the chkdsk method worked this time. I've given up on using it most times because it normally doesn't help the issue.
I had it hooked up to an external sata drive took me 4 chkdsk trys before it actually finished it.

Normally the stock asus drivers and updated ones screw up the OS in a way that I have to reformat it or use a non OEM disk which actually screws it up more if i repair it. On top of that hardware issues have caused more problems. At the moment the mobo has been replaced multiple times, the screen was replaced because it started showing up with blue pixel lines *didn't hit or drop it and it showed up in the first few months*, and the dvd drive was replaced because it stopped reading dvds >_>. The things they didnt replace yet was the OLED display for the clock, the frame, the fans, the hdd, the media center play buttons.

The thing is I like asus support because they will get my laptop back to me in under 3 days from shipping to them to getting it at my house and that they will help you via chat almost 24 hours a day.
The bad thing is they seem to rush a lot of there stuff: poor drivers, quality checks on hardware, and other random crap.

Thx for all your help reps to everyone ^^

 

If chkdsk fixed the problem, then I think it's indeed a bad HDD. Either that, or a bad ATA controller.

 

Actually, the distinction I was trying to make at the time of the post was the the /r switch is a recovery console command, but that is actually incorrect....for some reason, I had it in my head that only /f was available outside the RC....goodness...the memory is failing me. It looks like my signature is more accurate than I thought.

 

4 runs does make me nervous.

During those runs, at the end, during the summary screen, can you tell me if you see anything in the line

?? KB in bad sectors?

If there is anything but 0 there, I am definitely leaning bad drive.

 

I got uhh i think they put a hitachi in it. I dl'd the software from there site and it showed up with 0 problems. I will paste the file it got the final time. It only got the summary once.

 

I think you're talking about the SMART test?

I think the previous poster wished you to copy-paste the result of chkdsk, with the bad-sectors switch.

To get that summary, type cmd in the runbox, then in the command line type:

chkdsk C: /f/r/x (these are WinXP switches)

you may want to replace the C: with D:, E: for all your partitions.

When the checkdisk completes, you get a summary readout, that should be copy pasted and posted here.

 

ill post when i get home i only did C i can do D though, but how do I do the hidden partition w/o using linux?

 

You can't, really, I'm not even sure it uses a filesystem that Windows knows how to read, but C: and D: should suffice for now.

 

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

F:\Documents and Settings\dan>chkdsk /r J:
The type of the file system is NTFS.
Volume label is VistaOS.

CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is recovering lost files.
Recovering orphaned file SYSTEM~1 (2373) into directory file 2370.
Recovering orphaned file systemprofile (2373) into directory file 2370.
Recovering orphaned file TxR (2395) into directory file 2370.
Recovering orphaned file SAM.LOG (25759) into directory file 2370.
Recovering orphaned file SECURITY.LOG (25760) into directory file 2370.
Recovering orphaned file SECURITY.SAV (25761) into directory file 2370.
Recovering orphaned file SOFTWARE.SAV (25762) into directory file 2370.
Recovering orphaned file SYSTEM.SAV (25763) into directory file 2370.
Recovering orphaned file SAM (63330) into directory file 2370.
Recovering orphaned file SAM.LOG1 (63331) into directory file 2370.
Recovering orphaned file SAM~1.LOG (63331) into directory file 2370.
Recovering orphaned file SECURITY (63332) into directory file 2370.
Recovering orphaned file SECURI~1.LOG (63333) into directory file 2370.
Recovering orphaned file SECURITY.LOG1 (63333) into directory file 2370.
Recovering orphaned file SOFTWARE (63334) into directory file 2370.
Recovering orphaned file SOFTWARE.LOG (63335) into directory file 2370.
Recovering orphaned file SOFTWA~1.LOG (63336) into directory file 2370.
Recovering orphaned file SOFTWARE.LOG1 (63336) into directory file 2370.
Recovering orphaned file SYSTEM (63337) into directory file 2370.
Recovering orphaned file SYSTEM.LOG (63338) into directory file 2370.
Recovering orphaned file SYSTEM.LOG1 (63339) into directory file 2370.
Recovering orphaned file SYSTEM~1.LOG (63339) into directory file 2370.
Recovering orphaned file SAM.LOG2 (65440) into directory file 2370.
Recovering orphaned file SAM~2.LOG (65440) into directory file 2370.
Recovering orphaned file SECURI~2.LOG (65441) into directory file 2370.
Recovering orphaned file SECURITY.LOG2 (65441) into directory file 2370.
Recovering orphaned file SOFTWA~2.LOG (65442) into directory file 2370.
Recovering orphaned file SOFTWARE.LOG2 (65442) into directory file 2370.
Recovering orphaned file SYSTEM.LOG2 (65443) into directory file 2370.
Recovering orphaned file SYSTEM~2.LOG (65443) into directory file 2370.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Windows replaced bad clusters in file 546
of name \pagefile.sys.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Correcting errors in the uppercase file.
Adding 1 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

90701823 KB total disk space.
78051512 KB in 123185 files.
86752 KB in 19080 indexes.
4 KB in bad sectors.
253455 KB in use by the system.
65536 KB occupied by the log file.
12310100 KB available on disk.

4096 bytes in each allocation unit.
22675455 total allocation units on disk.
3077525 allocation units available on disk.

160gig hdd 3 partitions 1 is about 88gigs the other about 58 and roughly 4-5 gigs is the recovery partition. Rest is what the index?
Also i got desktop hdd that basically screwed and id like to see if u got any advice on it but ill pm u the info.

I still think its Asus crapy untested drivers they decided to put in on this. Even after I got the updated ones it still does it.

 

I do think this is a bad HDD.

4 KB in bad sectors.

Plus all those errors; NTFS is a very robust filesystem and that amount of errors only happens in two situations (A) very bad OS crashes -- and rarely even then -- and (B) bad HDD.

I would suggest you try to get your HDD exchanged from warranty if possible, or else just buy an upgraded HDD.

And if you didn't already, backup all your data.

BTW, the index is a data structure used by the NTFS filesystem.

 

I would agree.

4kb is not a huge amount of bad disk, but if Windows is marking them bad, it means it has already exhausted the clusters it set aside during formatting.

Furthermore, the location of these bad clusters is not a good spot. Many of those recoverd orphans are actually part of the registry.

I've had drives last for years with 4kb in bad clusters, but I've also seen (twice last week in fact) drives quickly degrade to useless once bad clusters start showing up.

 

There is one thing that caught my attantion

Windows replaced bad clusters in file 546
of name \pagefile.sys.

 

lots of things creeped me out

That's some serious bad news...the OP was lucky to get it going

Add in
Adding 1 bad clusters to the Bad Clusters File and we know the situation is getting worse

 

Additionally, the firmware on the HDD also relocates sectors that go bad, transparently and on the fly, when it finds it has difficulty reading/writing them. So this problem is already past what the firmware can solve.

 

so should I contact asus about this problem? Well yeah I will... but id the hdd going bad or is the drivers screwing it up?

 

I would contact ASUS for a HDD replacement.

And yeah, the consensus seems to be that the HDD is going bad. We can't be sure of course, but at this point it's the most likely possibility.

You could do a SMART test on the HDD (for instance, check my Tips and Tricks, question "Has my HDD gone bad" for a way to do that; ignore the chkdsk part since you already did that). If the SMART test returns positive (i.e., SMART warning has been triggerred), then it's almost 100% the HDD.

 

i did it about 2 months ago and it came up clean

 

Do it again.