[bennystylee]

after you have run chkdsk ...
go to Event Viewer...Application...scroll to find Entry called winlogon.. double click on that you'll get a Summary...tell us what the fist part of the report about how many and what kind of errors...
the proper thing to do is keep running chkdsk until it does not correct any more errors...
since you lost so much hair when this first happened I highly suggest you back up your data to cd/dvd's as insurance on the possibility that the drive is on its last legs...this should be done as a normal part of your backup strategy

Will do - I am fully backed up

The event viewer errors from the other site is showing controller issues.
I did not read the other thread but if your having controller issues...try reinstalling your chipset drivers

Just reinstalled chipset drivers (VIA_HyperionPro_V524A) I am now going to chkdsk will post back the results when I have them

Thanks

[Advertisements]

New data cable installed?
If problem still happens then it may be the controller.

[rshaffer61]

New data cable installed?
If problem still happens then it may be the controller.

[123Runner]

will do - i got a new data cable with the new hard drive last week as also thought this may of been an issue - but that didn't fix it..

I have run out of ideas.
Looking like a controller on the board.

[bennystylee]

after you have run chkdsk ...
go to Event Viewer...Application...scroll to find Entry called winlogon.. double click on that you'll get a Summary...tell us what the fist part of the report about how many and what kind of errors...
the proper thing to do is keep running chkdsk until it does not correct any more errors...

Ok chkdsk has just done and is ok

heres the reulst (from Event Viewer -> application -> (type-information, source-chkdsk)

Checking file system on F:
The type of the file system is NTFS.
Volume label is BackUp.
Read failure with status 0xc000003c at offset 0x228dff6000 for 0x1000 bytes.
The index buffer at VCN 0x0 of index $I30 in file 0x5574
cannot be read.
Correcting error in index $I30 for file 21876.
The index bitmap $I30 in file 0x5574 is incorrect.
Correcting error in index $I30 for file 21876.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 00 30 c4 44 f8 3e ca 01 ÿÿÿÿÿÿÿÿ.0.Dø>..
00 81 c5 c9 78 1e c5 01 34 56 d4 e1 18 49 ca 01 .�..x...4VÔá.I..
Sorting index $I30 in file 21876.
Read failure with status 0xc000003c at offset 0xc983a000 for 0x1000 bytes.
File record segment 155883 is unreadable.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file NEWTEX~1.TXT (21877) into directory file 21876.
Recovering orphaned file New Text Document.txt (21877) into directory file 21876.
Recovering orphaned file UNTITL~1.JPG (21878) into directory file 21876.
Recovering orphaned file Untitled-1.jpg (21878) into directory file 21876.
Recovering orphaned file 0409 (21879) into directory file 21876.
Cleaning up 28 unused index entries from index $SII of file 0x9.
Cleaning up 28 unused index entries from index $SDH of file 0x9.
Cleaning up 28 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

976760000 KB total disk space.
160303508 KB in 195296 files.
82128 KB in 33145 indexes.
0 KB in bad sectors.
324296 KB in use by the system.
65536 KB occupied by the log file.
816050068 KB available on disk.

4096 bytes in each allocation unit.
244190000 total allocation units on disk.
204012517 allocation units available on disk.


For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

[bennystylee]

My Event Viewer -> system log now has no errors or warnings! Not jumping to conclusions but it has been showing the errors on boot in the error log for previous days...I will attempt a days work on the system tomorrow and report back at the end of the day.

I am a little confused as to what has fixed this, surely its not as simple as reinstalling the via chipset drivers again? Did CCleaner really remove these from my system - hey whilst we are at it how long is the piece of string I am holding

Anyway thanks for all the help - I get the impression that if this doesnt work its curtains for the motherboard. I will report back tomorrow night.

Internet beers to all

[123Runner]

Did CCleaner really remove these from my system

Most likely not. It is a very good program when used properly. We do not recommend it anymore because of the registry repair section. When people use that part of it, they take the chance of destroying the registry and redering the computer useless.
We do not recommend any registry cleaners or optimizers.

[bennystylee]

Ok I started this morning (am on her now) it took 4 restarts to get her going and I saw a foxconn screen I have never seen before with what looked like controller errors!

Shame the board isnt available anywhere on the net (600A01-6lRS).

Darn

I am confused as to how I can sit on the machine and not have errors in my Event Viewer -> System - but still have a niggeling feeling there is a big problem. Controller problems arnt black and white?

Thanks

Edited by bennystylee, 19 October 2009 - 03:05 AM.

[bennystylee]

I have bought the bullet and am now off for a barebones machine!

Thanks for all the help guys

**Edit I have just ordered a new motherboard - and she arrives tomorrow.

Guys I can't say how much you have all helped thank you for turning voodoo into something I can understand.

Edited by bennystylee, 19 October 2009 - 03:05 AM.

[123Runner]

Please let us know how it goes after the new board is in.

[happyrock]

have you run chkdsk /r on all your drives...especially your OS drive
chkdsk was the one that got the drive errors sorted out and started things working right again...but because the errors came back quickly indicates a bad hard drive and since you have replaced them all I would have to agree its time to replace the mobo

[bennystylee]

have you run chkdsk /r on all your drives...especially your OS drive

only on the external drive, I am not going to do the OS drive as I will be reinstalling and reformatting after the new motherboard install tomorrow

chkdsk was the one that got the drive errors sorted out and started things working right again...but because the errors came back quickly indicates a bad hard drive

The error was a foxconn error just after the foxconn boot screen and before the xp spalsh - it halted the bootup and had controller errors with the same Event Id's as I place up yesterday on the other forum link

and since you have replaced them all I would have to agree its time to replace the mobo

The thing I dont get is how can I be working away and pushing the system quite hard (photoshop, flash, dreamweaver, outlook, firefox) all open now and it has controller errors? I am tempted to leave the new motherboard in its box until I get another WDF.

First time I have installed a new motherboard - very scared but have a very good print out on it.

Edited by bennystylee, 19 October 2009 - 06:51 AM.

[happyrock]

I would run chkdsk /r on the OS DRIVE ...IT COULD BE THE ONE CAUSING YOU THE GRIEF...
for the future...do not run the manufactures quick tests on the hard drives...they can pass but then when you run the long tests ...they can fail

[bennystylee]

I would run chkdsk /r on the OS DRIVE ...IT COULD BE THE ONE CAUSING YOU THE GRIEF...

Done - I am definately not changing motherboard until I have more errors - thanks and I will update once I have something to tell.

[happyrock]

post the chkdsk log after your done...

[bennystylee]

post the chkdsk log after your done...

Here you go

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 602 unused index entries from index $SII of file 0x9.
Cleaning up 602 unused index entries from index $SDH of file 0x9.
Cleaning up 602 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

102398278 KB total disk space.
25979248 KB in 136413 files.
49948 KB in 14273 indexes.
0 KB in bad sectors.
221846 KB in use by the system.
65536 KB occupied by the log file.
76147236 KB available on disk.

4096 bytes in each allocation unit.
25599569 total allocation units on disk.
19036809 allocation units available on disk.

Internal Info:
00 50 02 00 a8 4c 02 00 d4 9f 03 00 00 00 00 00 .P...L..........
08 01 00 00 06 00 00 00 c5 06 00 00 00 00 00 00 ................
b6 55 bf 02 00 00 00 00 18 5b 01 54 00 00 00 00 .U.......[.T....
b8 d5 96 12 00 00 00 00 f8 42 03 5b 02 00 00 00 .........B.[....
ee 92 e0 1e 02 00 00 00 1a b7 8f ea 04 00 00 00 ................
99 9e 36 00 00 00 00 00 a8 39 07 00 dd 14 02 00 ..6......9......
00 00 00 00 00 c0 a5 31 06 00 00 00 c1 37 00 00 .......1.....7..

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at http://go.microsoft....link/events.asp.