This one is driving me crackers!..

Ashman UK

Ashman UK

Ashman UK

Associate
Joined
5 Jul 2004
Posts
371
Location
Gateshead, United Kingdom
Hi all.

Hope i can try to explain this problem thats just suddenly started happening with my vista os in the last few days best i can.

A few days ago after having vista run fine for months with all my usual stuff on it like nod32, diskeeper, games etc i decided to do a bit of a clean up as you do periodically with your pc.

With diskeepers boot-time defragmentor i set this to run which basically you can set chkdsk to run before it bootime defragments as per usual.

It re-booted went into doing the usual chkdsk as you can do aswell from right clicking on your hard drives icon in my computer and found that chkdsk found a corrupt file or two and began to repair them.

So i thought ok ill just it do its thing as its been awhile since i ran chkdsk either through diskeeper or the normal way and then found this message started coming up on the chkdsk screen.

"Replacing invalid security id with default security id for file xxxx"..and basically doing this for thousands of files for well over an hour.

So i let it complete and then found on rebooting vista that it gets past the green loading bar then the screen goes blank, does not log into vista at all and im left with just the mouse cursor on the screen and thats it!.

Over the last day and a half i have reformatted about six or seven times and systematically on my normal reformat routein installed a few drivers tried chkdsk to see if any of these cause the problem which then chkdsk runs fine with no errors and then with programs etc and all seems to be fine until i get literally everything installed again, run chkdsk from diskeeper, it finds errors and it does this all over again.:mad:

Ive googled about and searched on here and tried to find one or two articles on the net on "what" actually causes it.

Again, i can run chkdsk fine after the first few programs, drivers, windows updates, go on the system fine but again, it seems to just do it after a lot of stuff has been installed and i have done a hd error scan with hdtune aswell and cannot find any hd bad sectors.

Hope any of the above made sense and even any little suggestion would help.

Ive come across some problems before in my years of using a pc but this one tops the lot for me.!
 
Last edited:
Sounds like either bad ram or HDD, try running Memetest on the ram and look for HDD diag software on your drive manufactureres web site.
 
Sounds like Disk-keeper to me. Have you tried removing this and seeing what happens? If it works fine without it then there's your problem (if you really need it perhaps check to see if you have the latest version?)

Don't think it's HDD (as you've checked it) also don't think it's memory.



M.
 
Thanks for the replies chaps.

Im typing this on a "half installed" vista as in a few things i have installed and tested chkdsk via vista and so far no probs however i will try the suggestions above.

Will let ya know...
 
Well i got abit further into that install and after applying a lot of windows updates it then as usual re-booted then came up with the system did not shut down properly message and basically it went **** up again..

What im trying now is to scrap my raid array and install vista onto one of my raptors and repeat as above.

Awhile ago i had to send one of my raptors back to western digital as one of them was faulty and in a raid 0 configuration it would start throwing up random disk errors etc.

Clutching at straws maybe but ive nearly got all my stuff again on a single raptor and will try chkdsk after defragging again then connect the other raptor up then do a hdtune error slow scan on both drives, my os raptor and empty raptor, which were the two that made up my old raid array.

Luckily im using other half's older pc and we have a laptop here aswell for the interim but this is so bleeding time consuming when things go wrong. That i dont mind, its when you cant nail the cause of the problem that bugs the hell out of me.
 
Last edited:
Well got "everything" installed onto vista as i normally do and defargged using diskeeper then rebooted.

It fixed an error or two but it finished and then booted back into vista fine.

However...i installed a few last minor windows updates in, did another defrag with diskeeper and then rebooted to test chkdsk and lo behold when the green bar scrolls across the vista logo screen it blue screens for a fraction of a second and then reboots again and again.

I used the vista system start up repair of the disk it did this but now goes to a black screen at before vista logs on.

Really had enough of this and am contemplating just using other halfs pc and laptop to browse and sell stuff out of pc that i know works.

Sounds slightly drastic but it seems i have to waste 2 or 3hrs of my time before this problem rears its head.

Not good at all.
 
Thanks for the suggestion again mate.

Really frustrating as you can imagine.

Will keep plugging away as much as this is doing my head in, i want a reason and a conclusion to this stinking problem.

The overclock settings were the ones that were pre-set when i got this system from ocuk last june time and have used them since then up until a few days ago, orthos stress test included with no problems.

Ill try again with my raid array and this time not use diskeeper and just use another defragger and just use windows standard defragger.

Again, the worst thing is i can chkdsk(admittedly with diskeeper) everytime i install something like drivers windows updates but it seems to wait until i have got everything on till it decides to be a complete &^^%%!

One thing to note though is that this seems to occur "after" i have used diskeepers defragger then run chkdsk once i have got just about everything installed and after all windows updates are installed, including vista sp1.

Gonna try this time without diskeeper at all.

Im starting to narrow it down to either the one of hard drives being faulty, memory or or an incompatibility with diskeeper in some way.
 
Last edited:
Well its appears, as i have now done two or three chkdsk runs after installing "everything" and defragging, to be ok now.

The one thing thats different is that i am using a different defragmentor now "o and o defragger" and now touch wood all seems to be well.

Obviously my system and diskeeper dont like each other for some reason.

Fingers crossed, diskeeper was the problem and thats that for now.
 
Beats me why you want to chkdisk and defrag after every update etc...but it sure sounds like diskkeeper is giving you some serious grief.

my only other suggestion was going to be trying to install vista with 2gb of ram (or less) as I know it can be a pain if you install it with more than that installed on your motherboard.
 
Its diskeeper as i i had the same problem. its to do with the boot time defrag and the way vista has changed the security id tags for files. i did have some links with more info but there is at present no fix.
 
NorthstaNder said:
Beats me why you want to chkdisk and defrag after every update etc...but it sure sounds like diskkeeper is giving you some serious grief.

my only other suggestion was going to be trying to install vista with 2gb of ram (or less) as I know it can be a pain if you install it with more than that installed on your motherboard.
Click to expand...

Yeah its not so much i was doing this everytime i rebooted but as soon as the problem cropped up i had to keep testing it to narrow down the culprit and as bigboy has said below ya post and as i have now found out, its definetely diskeepers boot-time defragmentor "after" it appears with me when i ran the normal defragmentor in diskeeper "then" ran chkdsk "through" diskeeper.

Its funny because i used to use kaspersky antivirus but found using it, that it would not let diskeepers boottime defragger work so ditched kaspersky and moved onto nod32 which im using presently.

In hindsight i should have ditched diskeeper as thats twice now diskeeper has effectively caused me problems on this system.

System for a few days now with different defragmentor "o&o" is fine now and ive ran chkdsk a few times including just now and not a single problem.
 
Last edited:
if it's any assurance, i've been using o&o defrag since v6 (v6 had a memory leak issue) but its been fine since, never had any corruption with it
 
Yeah i like it.

It seems simple to use, you can defrag in a variety of ways and it does it very quick.

I dont wanna put others of using diskeeper cause it is a very good defragger but unfortunately it seems to have the odd serious system breaking issues as i have found out over 2 days this week.

Again thanks to all above posters for helping me narrow down and nail the problem, this one truly did my head in big time lol!.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom