just curious as to why you would cut the power from the back of the psu itself when the system is already powered off?
just curious as to why you would cut the power from the back of the psu itself when the system is already powered off?
From the above description the system is borderline stable. When the system is powered on from complete power removal some non-user configurable chipset registers are programmed based on BIOS settings. In this instance the board is seeing more then one possible value as being valid for one of the registers. Kind of like sitting on top of a fence with the ground shaking. Equal chance of falling to either side.Quote:
Originally Posted by DemonEyez
Through trial and error will have to find the manual setting in the BIOS that is causing the issue, lock all settings that are on Auto to manual or make a voltage adjustment. Usually a voltage adjustment will solve this.
I never leave household- or other machines on 'standby'Quote:
Originally Posted by cantankerous
Plus, I'm still modding and adjusting my rig. I don't want any change of short circuit, that's way I want my PSU complete cut off from any power
Thank you for the very clear explanation :up: , now I know in which direction to search.Quote:
Originally Posted by Praz
I'll try as you suggested upping the voltages and setting things to manual and see if it helps. Thanx!
Golden rule of overclocking, never leave anything on auto.:D :up:Quote:
Originally Posted by DemonEyez
hey guys, im running the 2/14 bios and Vista X64 with SP1. I just changed my IDE based Pioneer DVR-112D to a SATA based DVR-212. The drive shows up in post np, it also shows up in Windows and burns and reads without issue. The problem? Sometimes it 'drops' or 'disappears' from the system out of no where. If I do a hardware scan in device manager it will come back up. If I reboot it will show up in post and in Windows again, that is until it 'disappears' again. The drive has the latest 1.24 firmware. Anyone have any ideas?
Perhaps it's some Vista-related problem again...
Do you have any other sata drives on the same channel as that 212D and is that your only optical drive, or perhaps you have put is as slave instead of master or something of that sort..
Sorry guys, one more thing. Anyone know why DFI isn't using the latest RAID ROM bios version 7.6.0.1011? Instead they are still using the older 7.5.0.1017. It may not mean anything but I always like to be completely up to date on everything I can. I am sure Intel have this updated ROM version for a reason. It may have nothing to do with my problem above but perhaps so? Anyone know a way to get the latest ROM onto my board?
Hi. The DVR-212 is the only SATA based Optical drive. I do however have 2 x 150gb Raptors and 1 X Hitachi 7K1000 1TB drive attached. The 3 hard drives do not ever disconnect however, it is only the Burner that does so.Quote:
Originally Posted by mad_skills
Then it would appear to be the burner. Change SATA ports around and switch cables and try and replicate the issue and we'll make some progress.Quote:
Originally Posted by cantankerous
Perhaps you can change sata ports or bring the original firmware.
What's the best bang for the buck memory to get for this board?
hmmm now i'm confused which temp should i really rely on... :shrug:
http://i116.photobucket.com/albums/o...mXtreem600.jpg
Probably none of them, its pretty difficult to get accurate absolute temps anyway. These programs are much better are measuring temp changes than they are at measureing the actual temps unfortunetly. I suppse though that these programs give us something close enough to what our hardware is running at.
hmmm .. can someone read my post and gimme an explanation please ... I read a lot and can't find why it did that ..
Post #3978
Thank you ...
regardless if the old ram passes memtest. If your new ram solves the issue then it's the old ram causing the BSOD. Request an RMA for your RAM.Quote:
Originally Posted by MacKaquE
I agree. I've also recently identified some faulty memory that consistently passes Memtest (and other DOS-based memory testing programs) but is unstable when running programs in WinXP that utilise DirectX graphics.Quote:
Originally Posted by GripS
Took me ages to work it out and I first thought it was the motherboard. However, it seems that Memtest is not a reliable method of confirming whether the RAM is good.
Corsair Dominator, Crucial Ballistix or some Team Xtreem ram probably...Quote:
Originally Posted by x6700
A heads up that 2/14 bios is now official on DFI's site.
Do you know if the UT bios can be used on the LT version of this board?
The bios revisions up to 24th December appear to be the same (LP35DC24), but the latest (LP35D214) is only shown on the UT download page.
I am 99% sure they are the same. Perhaps that page will be updated at a later time cause up to now it has been the same bios for both boards as they are identical besides the stock cooling.
In agreement with Cantankerous.
The page probably has not been upgraded.
I've been using the 2/14 on my LT without any issues.
Thanks for the quick response.
I also thought they were the same board with different cooling solutions, but wanted to be sure :).
Hey Carl, how are things going? I finally picked up some LN2 and am using the 2/14 bios. For some reason no matter which cpu I use I can get near a limit of the cpu/board and it'll just lock up. I can't get it to boot no matter how many times I clear the bios or which way I clear the bios. The only solution is to use a different cpu. That is a huge pain in the ass because I have to heat up the pot and remove everything. I wonder if it's just my board. I was thinking about picking up a 2nd one just to see.Quote:
Originally Posted by soundx98
UT P35 and LT P35 are basically identical, apart from the transpiper cooling.
I have T2RS and I noticed that some BIOS settings are different like how you ^ CPU voltage for example.