| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 116733 | 2011-03-17 21:47:00 | Problems with new sandybridge build | dugimodo (138) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1187134 | 2011-03-28 21:41:00 | Not always but more often than not. Still, tell that to my Laptop, would randomly BSOD with all sorts of rubbish, replaced the RAM and it was fine. Whats worse, the bad RAM passed memtest without a problem..... |
Agent_24 (57) | ||
| 1187135 | 2011-03-28 22:35:00 | Not always. Got a PC here at the moment, lockes up every 5-10 minutes, it has buggered SATA ports on the board, the drive loses contact and the whole thing locks up solid - nothing to do with memory. If I put the HDD on a workshop PC it runs fine,(has the same Gigabyte board G31) cloned the drive to a IDE, and that runs fine on the customers board. A BSOD is caused by one of two things - Drivers or hardware faults - its a matter of finding which is causing the problem. Well yes, hardware fault is a given for a lockup, however MS Technet states 99% of software BSOD is driver related.. I was just trying to steer the issue from lock up or BSOD and what is the main cause of such issues. |
SolMiester (139) | ||
| 1187136 | 2011-03-28 22:38:00 | www.corsair.com is the RAM, no it's not on the list but the corsair site says it's compatible. It is one of my prime suspects though, and no I haven't tried a single RAM chip yet. Everything I try takes so bloody long to prove :( Safe mode ran 12 hours without crashing, not 100% proof but I stopped it there. XP hasn't crashed on me when I left it overnight but then it only addresses 3.xx G of RAM I have been googling all week, today a different search "sandy bridge windows 7 64 bit random freezes" found me dozens of threads from ASUS and Gigabyte and Intel users with identical isues, from there I have got a few hints so today I have: Disabled onboard LAN controller Disabled UBS3 Controller Bumped the memory Voltage from 1.5 to 1.56 (smallest step) So sitting idling using a wireless LAN adapter and we'll see what happens. If it's stable till tommorrow morning I'll try reversing these one by one. If not I'll try the RAM individually, yeah I know it probably should have been one of the first things but as memtest ran overnight without faulting I discounted RAM as a possibilty. |
dugimodo (138) | ||
| 1187137 | 2011-03-28 22:55:00 | I'm groping here but have you tried the memory tester in Win 7? | Snorkbox (15764) | ||
| 1187138 | 2011-03-28 23:02:00 | Personally I dont think its the RAM- reasoning being, its running OK in safe mode, so the RAM is still being used . (One possibility - the one you linked to, a single 8GB Module - Just checked Gigabytes memory listing and they all show 4 & 2 GB, no single 8GB ? ) Only way to find out, remove it and try another smaller DIMM . "usually" it would play up quickly, not wait several hours at idle though . I think its more of a driver issue (doesn't crash in safe mode) - did you install the Drivers from the DVD that came wth the board? If so you may want to try looking at gigabytes site, I have just had a gander, and there are a couple of latest drivers all around Feb this year - they may contain fixes, esp the chipset . |
wainuitech (129) | ||
| 1187139 | 2011-03-28 23:17:00 | It's not an 8GB chip it's a pair of 4GB in a dual channel kit Yes I have tried updating drivers and bios files from Gigabytes website, also tried a realtek sound driver from their site. The drivers on the CD is where I originally started from. Among things I plan to try is steal A 3GB triple channel set from my other PC and use 2G of it to see what happens. Some forum posts suggest the intel sata drivers so that's something else after my current tests.Trouble is of all the posts with identical issues there seems to be multiple fixes that work for some people. My suspicion is it's some kind of compatiblilty or timing issue between the sandybridge chipset and some other piece of hardware or RAM as the only common denominator in the threads I have read is the chipset. I bet it will quietly dissappear sometime in the future with a BIOS or driver release. In the mean time though I need to pin it down to a specific cause before I lose all my hair. |
dugimodo (138) | ||
| 1187140 | 2011-03-29 18:37:00 | As of this morning 20 hours uptime so touch wood it's looking good. Forgot to mention I also disabled onboard E-stata controller so I have 4 changes to undo one by one to see what caused it: E-sata LAN USB3 Mem Voltage Starting to think it might be the RAM after all, something I had forgotten was when I initially set it up I enabled XMP and it failed to boot and reset itself to default SPD values which means the RAM has been running at 1333, 9 9 9 24. However the values set by XMP - 1600, 8 8 8 23 are what the RAM is rated at and should have worked. |
dugimodo (138) | ||
| 1187141 | 2011-03-29 19:01:00 | Hmmm forgot to mention the RAM alterations - tisk tisk. One thing you should always do if theres a problem - go back to default settings. Its a bit like when people over clock to much and things go unstable and they wonder why. Looking at the list of changes to sort out, my pick is the Mem voltage first, put it back to what ever the default is. Reason being, if the other board you had did the same thing, unless its a bad batch, whats the chance the other items listed are faulty as well. |
wainuitech (129) | ||
| 1187142 | 2011-03-29 19:15:00 | I tend to agree, except XMP is a supported feature of both the MB and the RAM and I have been at default settings since well before I started this thread. Also the memory passes memtest at 1.5V which is the default so why it would need 1.56 to work in windows is a mystery, and overvolting it should not be necessary. I pretty much in desperation disabled everything in the BIOS I could live without, I don't think they are faulty but I do think it could be a driver issue with one of them and turning it off is easier than uninstalling / re-installing drivers. Leaving it running for at least 8 more hours, then I start reversing the changes. I guess I'll start with the memory Voltage. |
dugimodo (138) | ||
| 1187143 | 2011-03-29 21:25:00 | For some reason I have this idea that XMP\Overclocker RAM etc was designed to be run at high speed, and that if run at standard JEDEC timings it will be unstable? | Agent_24 (57) | ||
| 1 2 3 4 5 6 7 | |||||