Jump to content

ganders75

Members
  • Content Count

    350
  • Joined

  • Last visited

Posts posted by ganders75


  1. You're going from single to dual core, so i'd probably:

    * uninstall the existing processor in Device Mgr, then ...

    * shutdown, switch processors, load optimised (maybe after CMOS clear if problems) and then enter your settings...

    * fire up windows and install the dual core driver (and hotfix etc)...

    then reboot and i think you'll be good to go...

     

    Right, all that said, i've got an opty 144 and an x2 4400 - whenever i'm changing between them i always rebuild windoze anyways... just a good chance for a clean start...


  2. You are running Memtest to test your settings, not just to ensure that the memory isn't defective. Did you follow the build guide posted here as a sticky? Even if you have built machines before, this info has helped countless people get up and running successfully.

     

    Most importantly, you should never attempt to install the OS until you are sure your machine is at least Memtest stable. Run 10+ tests of test 5 and 8, and then leave Memtest running overnight (8hrs+). It should still be running in the morning - and there should be no errors showing... Once that is done, you'll probably have to hose your OS partition and reinstall from scratch - it sounds like something has been messed up.

     

    One other question - what make/model is your PSU?


  3. Yep. This is a known issue with windoze that they have never bothered fixing. Unplug your IDE drives and the other stuff you don't need. Install windoze onto the drive. Then you can plug in the rest of the drives and stuff...

     

    my friend recently had this problem... for some reason if u have a SATA & PATA(IDE) device plugged in at same time, even though u may tell it to install to SATA, it puts boot files on IDE... the way he got around it (& it would seem the only way), is simply unplug all drives except the one u want windooze on...

  4. WinRar will open an ISO file and allow you to extract it.

     

    Is your system MemTest stable? You should be able to pass MemTest tests 5+8 for 10+ passes and then 12hrs+ overnight. Are you following the build guide posted on this site? Even if you've built machines before, you should read it and follow it. It has saved many, many people many, many hours of pain and frustration...

     

    EDIT: Also, you shouldn't really be attempting to install windows on an overclocked machine. If you've OC'd it - bringing it back to stock before attempting to install windows is always a safer plan...


  5. You should run MemTest after you make any memory related changes to test that the sticks are at least MemTest stable. You should also check them using Prime95 to ensure that your system is stable in Windows.

     

    Try sharps settings above - 4 sticks put alot more stress on the memory controller than 2 so you may need to back them off a little to get them stable... especially if you intend to overclock.


  6. You can either back off the FSB so that you run the faster sticks back at DDR400 - which will also mean you can tighten up alot of the SPD timings... or you can run them at their rated speed (DDR500, or whatever) and modify your multiplier to still give you a stable stock speed.

     

    You should always be sure you're stable at stock speeds before attempting to OC - otherwise you're just asking for trouble later on...

     

    Oh, and a second for the OC guide - it's one of the great references for overclocking available anywhere...


  7. Well, i read through this whole thing - and i have to agree with rgone and wevsspot... I run the Fortron FX600 and the only problems I have ever had were due to my own stupidity. I connected it all up without really thinking about what i was doing - it turns out I was loading one of the rails with most of the components in my system - and funnily enough it didn't really like that! ;o) I can't recommend them enough...


  8. Congrats ;o)

     

    One thought - did you follow the build guide? I guess you're up and running, so no point going back now ;o) but you should make sure that you run MemTest86+ from the BIOS - usually before you attempt to install the OS. If you aren't Memtest stable you may have corrupted some of the install files - which will lead to problems later on...


  9. Your PSU is underpowered for your rig. Do a search on here - and you'll see this is fairly common behaviour for a poor quality PSU attempting to drive these boards. You really should have one off the Recommended List. See the link in my sig...

     

    Also, I think you'll struggle mixing RAM like that - you'll definately have to run it single channel, and you may not be able to get it to run at all...


  10. I'd definately suggest that you use 2x1Gb sticks rather than 4x512. You'll have to run 2t with 4 sticks, and it puts a much greater load on the memory controller...

     

    Anywyas, can't really comment on others - but I'd definately recommend my Mushkins to anyone. If you're interested - you can get more info for settings, etc from the link in my sig.


  11. Are you running XP SP2? There has been a new "enhancement" added which limits your half open connections to something daft like 10. If you are running P2P software of any kind - you will definately pass this limit - which means your browser has to wait for one of these to expire before it can make a new connection...

     

    You'll see loads of Event 4226 errors in the event viewer. If you see them - then that is almost definately your problem.

     

    Your options?

    A: do nothing - it's working like MS want it to...

    B: fix it - use the Event 4226 patch and set it to something more sensible

×
×
  • Create New...