Results 1 to 5 of 5

Thread: Possible cause to overclock instability?

  1. #1
    Senior Member mikeo01's Avatar
    Join Date
    Oct 2011
    Location
    Wales!
    Posts
    1,402
    Thanks
    294
    Thanked
    98 times in 88 posts
    • mikeo01's system
      • Motherboard:
      • MSI B85i Gaming
      • CPU:
      • Intel Xeon 1230V3
      • Memory:
      • G.Skill RipJaws 2133MHZ
      • Storage:
      • Plextor M5S 128GB
      • Graphics card(s):
      • VTX3D R9 290
      • PSU:
      • Coolermaster VS450
      • Case:
      • Corsair 250D
      • Operating System:
      • Windows 8 PRO, Ubuntu
      • Monitor(s):
      • LG 22" W2261VP

    Possible cause to overclock instability?

    I had my Phenom II x6 1045T overclocked for few months, stable and at great temperatures (48c). Last few months I haven't had the overclock set, but have moved my components to another case ready to start a mod project on my actual chassis.

    Since then I have also bought an SSD and an extra hard drive (Samsung HDD) so total of 3 storage media present. I have also attached this chassis' USB and head phone headers.

    Since my CPU is locked my overclock settings are bus only, so I am wondering could a hard drive cause instability?


    Errors - BSOD (pointing to USB.sys USBHUB.sys) and immediate reboot (no errors). It isn't heat related because the max it hits is 48c (same as before). I also use exactly the same hardware. There are no errors within Prime, I also used OCCT. 4 Hours in and the system reboot (instant).


    I am wondering if a new SSD and hard drive could cause this as such, since I now have 3 drives occupying the SATA ports instead of one.

    CPU is under a year old.



    Sure an OC is no big deal, but the performance boost I had with it is worth investigating
    "If at first you don't succeed; call it version 1.0" ||| "I'm not interrupting you, I'm putting our conversation in full-duplex mode" ||| "The problem with UDP joke: I don't get half of them"
    "I’d tell you the one about the CIDR block, but you’re too classy" ||| "There’s no place like 127.0.0.1" ||| "I made an NTP joke once. The timing was perfect."
    "In high society, TCP is more welcome than UDP. At least it knows a proper handshake."

  2. #2
    Banhammer in peace PeterB kalniel's Avatar
    Join Date
    Aug 2005
    Posts
    31,025
    Thanks
    1,871
    Thanked
    3,383 times in 2,720 posts
    • kalniel's system
      • Motherboard:
      • Gigabyte Z390 Aorus Ultra
      • CPU:
      • Intel i9 9900k
      • Memory:
      • 32GB DDR4 3200 CL16
      • Storage:
      • 1TB Samsung 970Evo+ NVMe
      • Graphics card(s):
      • nVidia GTX 1060 6GB
      • PSU:
      • Seasonic 600W
      • Case:
      • Cooler Master HAF 912
      • Operating System:
      • Win 10 Pro x64
      • Monitor(s):
      • Dell S2721DGF
      • Internet:
      • rubbish

    Re: Possible cause to overclock instability?

    Yes, but USB drivers and controllers are funk anyway so try different ones. Most cases/motherboards I've had have had some kind of issue with the ports - if you're not using the chasis ports then unplug the headers.

  3. Received thanks from:

    mikeo01 (10-08-2013)

  4. #3
    I'm Very Important
    Join Date
    Jul 2009
    Posts
    2,945
    Thanks
    321
    Thanked
    360 times in 318 posts
    • Domestic_Ginger's system
      • Motherboard:
      • Gigabyte GA-MA770-UD3
      • CPU:
      • Phenom II X2 550
      • Memory:
      • 4GB DDR2
      • Storage:
      • F3 500gb
      • Graphics card(s):
      • 5850
      • PSU:
      • Corsair 550vx
      • Case:
      • NZXT beta evo
      • Operating System:
      • W7
      • Monitor(s):
      • G2222HDL

    Re: Possible cause to overclock instability?

    Mike, by you've upped the fsb and I presume got the ram multiplayer under control but have you dialed back the HT-link to about 2k? May be worth a look if you haven't. I'm habit out on terminology re PIIs. The CPU-NB may be worth looking at although data seems to be connected to the SB.

  5. Received thanks from:

    mikeo01 (10-08-2013)

  6. #4
    Senior Member mikeo01's Avatar
    Join Date
    Oct 2011
    Location
    Wales!
    Posts
    1,402
    Thanks
    294
    Thanked
    98 times in 88 posts
    • mikeo01's system
      • Motherboard:
      • MSI B85i Gaming
      • CPU:
      • Intel Xeon 1230V3
      • Memory:
      • G.Skill RipJaws 2133MHZ
      • Storage:
      • Plextor M5S 128GB
      • Graphics card(s):
      • VTX3D R9 290
      • PSU:
      • Coolermaster VS450
      • Case:
      • Corsair 250D
      • Operating System:
      • Windows 8 PRO, Ubuntu
      • Monitor(s):
      • LG 22" W2261VP

    Re: Possible cause to overclock instability?

    Removed USB drivers and let Windows default have a go. Also reinstalled the SATA controllers just in case.

    RAMs fine, so is the HT link and CPU/NB. I have them close to 2000mhz now and also juiced up the voltage a bit, so ideally it should be OK with that.

    Will post back if this overclock seems stable. Lowered FSB from 296 to 293 now as my board fluctuates a bit, not sure if the extra hard drives are putting a little bit of pressure on the southbridge. Well I assume its that just because the overclock was fine before that.


    I used to have a cache drive and hard drive attached and it was fine, so not sure.

  7. #5
    Senior Member mikeo01's Avatar
    Join Date
    Oct 2011
    Location
    Wales!
    Posts
    1,402
    Thanks
    294
    Thanked
    98 times in 88 posts
    • mikeo01's system
      • Motherboard:
      • MSI B85i Gaming
      • CPU:
      • Intel Xeon 1230V3
      • Memory:
      • G.Skill RipJaws 2133MHZ
      • Storage:
      • Plextor M5S 128GB
      • Graphics card(s):
      • VTX3D R9 290
      • PSU:
      • Coolermaster VS450
      • Case:
      • Corsair 250D
      • Operating System:
      • Windows 8 PRO, Ubuntu
      • Monitor(s):
      • LG 22" W2261VP

    Re: Possible cause to overclock instability?

    Seems like maybe having an extra hard drive attached was causing the fuss. Maybe. I am also using a generic SATA cable which I always found in the past to cause a lot more trouble with random errors so I will keep an eye on it, hopefully it's just a dodgy SATA cable causing some odd issues.

    And also I found out what was causing my BSODs, wasn't a USB driver, it was my old friend, good old Creative Sound Blaster with their latest and greatest Windows 8 drivers that AutoUpdater installed, they do not work for me. How I love Creative

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •