Mikey Needs Your help

[{ESC}Mikey]

Could it just be you are getting a bit.....how should i say......

You may. hence you did And might be right Hehehehehe

[Don_Andos]

Thankx Don .... I did, and I did not have an answer for myself "I built it"

:esuprised: you build it self :esuprised:

[{ESC}Headcase]

You would be surprised how often things like this can spawn from nothing more than a .dll file that went bad in your OS.
I suggest DriveNuke, followed by WindowsXP.
XP will make everything go smoother, and even if installing XP doesn't fix it, XP is much easier to troubleshoot that 2K.

[AsToRoTh]

Ive also read about HDD spin up failures. Easy cure is to open your case and check the drives are spinning up quick... reason that came to mind is when you said about things running ok once in RAM. If that turns out to be the case then its either new HDDs or leave the case off.. open the HDD and give it a spin whenever you boot or need to access it LoL.

Does the pc take a long time to start reacting if power saving features are enabled? (theres an option to spin down drives if they are not accessed for a while)... just a thought.

[{ESC}Mikey]

Thank you AsToRoth

My drives do not power down "To many problems with that feature"
And they are both at speed.

And now more with this unusual problem ;

The system is back up and running find on two new 500gig drives
My two old 250gig drives still have the problem.
But if you add them to the system as drive 3 and 4 there is no problem with them, but as soon as you add them as only drives, problem is back DOH

Has to be something in Winblows its self :censored: :censored: windows!

All hardware checks out A OK :takethat:


Thank you all for your input " Mikey Likes it"