Jump to content

Enron x86

Members
  • Posts

    16
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Slovenia

OCC

  • Computer Specs
    CPU: Core i5 750
    MB: Asus P7P55D-E PRO
    Memory: 2 x 4GB Corsair DDR3 @ 1333 MHz
    Graphics: 2 x NVIDIA GeForce 9600GT SLI
    Sound Card: Creative Sound Blaster X-Fi XtremeMusic
    SSD: (OS): Samsung 830 64GB
    HDD: (OS): WD 80GB IDE
    HDD: (Programs): WD 320GB SATA2
    HDD: (Archive): WD 250GB SATA2
    PSU: LC 550W
    Case: Thermaltake Kandalf
    Monitor: Samsung Syncmaster 19MB (CRT)
    Keyboard: Logitech USB
    Mouse: Logitech PS/2

Enron x86's Achievements

Newbie

Newbie (1/14)

  1. No, not really:) It turns out it was most probably the tRCD timing. In BIOS, it's currently set to 3, but Aida64 reports it as 5. Works like a charm though. Also, the BIOS doesn't seem to know how to read the SPD timings properly, they're completely off, so I've set them manually. Oh, and another extra piece of advice for those of you who might want to get an older system up and running - WaybackMachine is your friend if you're looking for a BIOS for an old motherboard whose manufacturer and their website no longer exists:) Basically, the only reason I brough this zombie to life was to utilize a soundcard that uses both A3D1.0, EAX1.0/2.0 and DirectSound3D capabilities along with Sensaura's HRTF algorithms. Thief 1 sure sounds great now with headphones and it's real easy to tell where your opponents are.
  2. I'm baffled... The system is now running rock stable at even tighter BIOS and RAM settings than before, no sign of any errors. Ah well, lesson learned. If anyone experiences the same symptoms - namely, if you install some RAM into a machine and you're 100% certain that the RAM works, you might try running the BIOS with fail-safe defaults. BTW, I cleared the CMOS like three time before, but that always loads the optimized defaults.
  3. Mine's exactly the same. 8 gigs, running Chrome with about 10 tabs open and 2 small programs in the background. Windows 8 x64, uptime 31 days, 12 hrs, 6 mins.
  4. Great news, I seem to be getting somwhere! After loading the BIOS fail-safe defaults (instead of the optimized defaults), Prime95 has been running stable for half an hour now. Before, it would crash after about 5 mins. Time to zone-in on the BIOS setting that's causing this ... @Braegnok, I don't have any options like that, except for USB-keyboard support.
  5. Yes, same result. I know for a fact that at least 2 of the 4 RAM sticks work 100%, so I guess either the motherboard or the CPU is faulty. It seems weird, though, that all 3 RAM slots would fail ...
  6. Hello. I'm putting together a retro-gaming rig and I've encountered a problem. The motherboard is a QDI Kudoz 7x with 3 RAM slots + an AMD AthlonXP 2100+. The result of Memtest is always the same - it shows about 8 errors within the first few seconds of testing (so it's probably test 0 that fails), but after that it continues without any further errors. I have 4 sticks of DDR1 RAM (2 each from different manufacturers and different speeds). I've tried installing them individually into different slots. CMOS settings have been reset, I've tried manually adjusting memory timings etc., but the result is always the same. Is it possible that it's actully the CPU that's failing, say the L2 Cache? Thanks.
  7. Just found this topic at overclockers.com. It appears that nvidia nforce chipsets detect SATAIII SSDs as SATA1 and there's no way around it. BTW @wevsspot, you're right. My mobo uses the CK804 "chipset" or whatever that stands for. I've read over at Nforcehq that those are non-ahci. Anyways, I'm pretty satisfied with the numbrs and the performance I'm getting, so that's that. EDIT: It appears OCZ have managed to fix this problem in combination with nforce-based motherboards by updating the SSD's firmware. Damnit. Shout have bought a Vertex...
  8. Just booted into Windows XP and guess what... And here's proof that it CAN work if it's in the mood... At least it makes sense now. Time to switch some more cables. This is gonna be one long day...
  9. You're right, wevsspot, those are the only two options. Up until today I thought that RAID mode was some kind of equivalent to AHCI (it works even if no array is set; it uses different drivers). OK then, I'll try to get my hands on a copy of Windows 7. I believe my Windows XP has Fernando's modded nf4 drivers installed, he probably made them for W7 as well. So - first the default msahci drivers (probably have to be forced via regedit), and if that doesn't work, we'll use a modded driver. Any other good ones besides Fernando's?
  10. Don't have Windows 7, but there is a bootable copy of Windows XP on one of my HDDs. Should I run CrystalBenchmark from there?
  11. I am. It's not about sequential speeds anyway, it's the latency that matters. Still, though - the storage controller is operating at less than 50% of what it should be. I guees at the time these boards were made nobody thought such speeds will ever be reached, lazy DFI bums ...
  12. Hooray, success! Here's what it looked like before: NF4_SATA_PHY1: HDD NF4_SATA_PHY2: / NF4_SATA_PHY3: SAMSUNG SSD (not detected, not bootable) NF4_SATA_PHY4: DVD+-RW Switched some cables: NF4_SATA_PHY1: HDD NF4_SATA_PHY2: / NF4_SATA_PHY3: DVD+-RW NF4_SATA_PHY4: SAMSUNG SSD - fully detected and bootable! So, that takes care of the nasty single-drive-in-RAID business. Stonerboy779, I guess you were right, my CMOS is messed up, but I just don't feel like clearing it up today:) I'm almost completely satisfied now, only - does anyone have an idea, why my sequential read/write speeds are so low (checked it now; read:138 MB/s, write: 104 MB/s)? Will try the SIl3114 controller and see what the speeds are there. EDIT: Meh, the SIl3114 scores are even more pathetic - read 93 MB/s, write 62 MB/s. I guess I'll just have to work with what I've got, then. Thanks guys.
  13. @Stonerboy779, apparently you can. I was just reading it on the HardForum; this guy tried it and failed, but I somehow managed to do it. That is exactly what worries me, though. It should work without such "hacks". I'll try a few other things first, before clearing the CMOS.
  14. Hey Black64, it actually functions fine. It's just that SATA2 should enable higher speeds (up to 300 MB/s) - my SSD's declared read speed is over 500 MB/s, SATA2 (theoretically) limits that to 300 MB/s. I guess I'd be pleased with 200 MB/s or so. Also, I was wondering if anyone managed to boot an SSD on a nforce4 motherboard without putting it in RAID. I've actually never used RAID before and am clueless, whether using the SSD in RAID-STRIPE mode will have any adverse effects.
  15. OK guys, here's the deal. I have a DFI Lanparty UT NF4 SLI-DR Expert (socket 939). The board has two SATA controllers, one from NVIDIA (nforce4 - SATA2) and one from SiliconImage (SI3114 - SATA1). Today, my Samsung 830 64GB SSD arrived. I plugged it into the NF4 storage controller, since it's the fastest of the two. However, the drive was not detected in BIOS and during POST. When I booted into Windows (off my HDD), it got detected. Also, when attempting to do a fresh install of Windows 8 Consumer Preview, there was a yellow exclamation mark under the SSD, saying that "Windows can not be installed here, as this drive is not bootable". I then went into BIOS and enabled RAID-mode on the nForce4 storage controller, rebooted, pressed F10 and created a RAID-array (STRIPE) with just the SSD in it. The drive then bacame bootable and Windows installed just fine. However, CrystalDiskMark showed some underwhelming results - sequential read speed was about 120 MB/s, sequential write was about 104 MB/s. Anyway, I was just wondering if someone knows of a way to run the SSD natively (without RAID) and whether my current configuration is bad for the SSD. Also, Samsung SSD Magician reports that I'm not running in AHCI. Could that be the reason for the poor read/write results? EDIT: Just found out that in Windows 8, the "msahci" service is replaced by "storeahci". That could be why SSD Magician reports that AHCI is not running.
×
×
  • Create New...