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
1187114 2011-03-18 23:29:00 ok tried bluescrren viewer, it's just empty so I guess there is no blue screen data since my last install, been at least 4 crashes though.

I tried another hard drive and installed XP pro x64 on it, crashed while trying to install anti virus software, crashed while installing updates, Gave up and went back to 7. (I had intended to move 7 onto another drive also but the repair disk refuses to look on the drive where I stored the image so I have to move it and try again).

I just moved the hard drive onto a diff sata port and cable (yeah I know 2 things at once again) and am waiting to see if it crashes again, I also have prime 95 running in the background at the moment.

On a weird possibly related note, If I use the XMP in the bios it correctly sets my RAM to the 1600 8 8 8 24 2T 1.5 settings it's rated at and memtest works fine but on boot the BIOS insists that windows has failed to boot due to overclocking and sets it back to 1333 9 9 9 24 as per the SPD. I'm wondering if this is just it noticing that it has failed to start in the past and making assumptions or if something weird is going on. 		dugimodo (138)
1187115 2011-03-18 23:39:00 Are the dmp files in the default folder?? You didnt move them did you? Speedy Gonzales (78)
1187116 2011-03-19 02:07:00 no moved nothing, there are no dump files. As I said it's only actually bluescreened once and I've reinstalled windows since then. It just completely freezes as opposed to bluescreening. dugimodo (138)
1187117 2011-03-19 02:34:00 Well obviously it wont be there, if you formatted after :p Speedy Gonzales (78)
1187118 2011-03-19 05:17:00 running 9 hours today and no crashes, fingers crossed. Is it possible the SATA 3 ports don't work well with older drives ? these are the ones that were NOT part of the sandybridge problem and this board is the updated version anyway.

All I've done is swapped the cables from the system drive and one of the data drives and it seems to be stable. Will take days to be sure though as it initially ran 3 days ok.

Maybe the cable wasn't seated properly? I dont know but it's a new cable of the locking type that came with the board. 		dugimodo (138)
1187119 2011-03-20 01:09:00 ok so no joy, going to send it back to CL.

I turned off all the power management so it wouldn't sleep and left it idiling overnight, according to task manager I left running and onscreen it locked up after 4.5 hours. (frozen but I can read what was on the screen at the time)

This morning after reboot it locks up much more frequently, maybe something is gradually warming up but in any case a pc that can't sit idle without locking up is no good to anyone. 		dugimodo (138)
1187120 2011-03-20 22:03:00 PC lockups are usually memory related, check memory is on the compatibility sheet for the Mobo.
As for the P67 bug, that is SATA2 related and the issue is a I/O degrade of throughput, nothing else... 		SolMiester (139)
1187121 2011-03-21 19:09:00 Thanks but I've given up and am sending it back. Memtest ran for 6.5 hours without problem and if the memory isn't compatible that's computer lounges fault as I paid them the $50 to precheck for compatibility etc.

In the end I discovered if I disable windows power management and leave it idling it locks up at some point, leaving task manager running let me see how long - usually within a couple hours. This leads me to believe it's not stress or heat related. 		dugimodo (138)
1187122 2011-03-27 20:19:00 OK update: CL replaced the motherboard, very good service. Now however I'm feeling guilty because it hasn't fixed the problem :(

SO starting over I removed all but 1 hard drive - an older seagate 500 that's been very reliable, installed an ATI HD4850 to eliminate the graphics card, and started from scratch.

Installed and updated XP home which then ran for approx 12 hours with no crashes.
Spent all day sunday installing and updating XP pro x64, then 64 bit Windows 7 - no crashes during this process.
Left Win 7 running overnight - 9.5 hours later it crashed the same as before !! :( :(

I'm thinking it's a driver or windows update causing the freezes but I'm at a loss as to how to prove it, my theory that it was the Nvidia driver was blown out of the water as it is now running an ATI card on a clean install.

I haven't changed the PSU so I guess I should try that too, but it was stable on the previous build and it certainly isn't being loaded any more on this one.

Would it be worth disabling the onboard sound, could that be the culprit for system freezes ?

I'm also planning on trying memtest again, it did run error free overnight but as the PC freezes so randomly it could take a very long time to show up. 		dugimodo (138)
1187123 2011-03-27 20:50:00 One long way to tell if its a updated driver issue - its a PITA way, but it should work -- Reinstall the OS fron scratch - DONT install any drivers other than the ones that come within windows - dont go on the internet -- leave it running - If its hardware, it will freeze again, if its drivers it shouldn't.

OR start the PC in safe mode and leave it running. Safe mode will only load in the default drivers in windows.

You can also try Burnin Test (www.passmark.com) - start the PC normally, install and under the configuration or test options (cant rember off hand the exact location)/ Test Configuration and Duty Cycles - untick items not required, set everything to max - this will really give the System Hell for about 15 minutes. It may weed out any problems. See Bottom Screen shot for options (www.passmark.com) 		wainuitech (129)
1 2 3 4 5 6 7