Sniper_Merc
[H]ard|Gawd
- Joined
- Mar 25, 2004
- Messages
- 1,037
Well, after having built a box for a friend with one I decided to break down and replace my Shuttle AN35 N 400 board with a DFI NFII Ultra Infinity. I really liked the CMOS reloaded function and I also intend to add in a pair of 36.7 gig raptors some time later this year so the onboard SATA will come in handy.
After initial startup with the board I wound up with one BSOD saying something along the lines of ***Hardware Failure ** ***Contact your hardware vendor for support**. I personally had never seen windows give a message like that so it made me wonder if it was the board actually producing the message. At any rate it wound up being the only BSOD I had experienced during the day so I ignored it.
Later on that night just as I was about to head for bed it happend again, and again, and again, and again. This was after managing to OC my Mobile 2600+ up to 2600 MHz on air at 200 FSB Synced with my ram which was also overclocked to 200 MHz (crucial pc 2700) Dropping the speed down to even bios defaults which picks up the CPU at 800 MHz failed to solve the problem, after two hours i got frustrated and went to bed.
Next morning (afternoon i guess) come out, turn it on set to 2600 MHz and run all damn day with it like that (go figure) no BSOD, not even an indication that there was a problem, after benching and playing Mech 4 Mercs all day I figured maybe it was just a fluke. Well right up untill I tried to go to bed (yes the fuckin gremlins were waiting for that point ). Same damn shit started happening, could barely get into wiindows, and when I did it was only for a few seconds. After 4 or 5 more hours of dicking with it, pullin cards, swapin ram ETC ETC, I was at the fuck it stage it's goin back tomorrow . That was yesterday morning about 5 AM.
Get up at around 1 PM flip the puter on, runs perfectly for another 2 hours decided fuck it didnt want to dick with it again, took it back and got another one.
After some Initial problems with the latest Nforce IDE driver causing winders not to boot I finally get it running good at about 3 AM this morning, and getting all my stuff reinstalled. Fixed the lock on boot by just uninstalling only the Nforce IDE driver (4.24) and going back to the 3.13 driver.
So far im back up to 2500 MHz 166/166 @1.75 Vcore x15 multi 2.7 V on the ram and all is smooth.
Considering this is the first motherboard in 5 years of building my own computers that I had go bad right off the bat, I guess I should count myself lucky, but it certainly is a frustrating thing to have happen.
Going to cross post this on my site Snipershide And eventually I'll post up a review on the board. Pics some hardware info and other things on the site for your enjoyment as well
After initial startup with the board I wound up with one BSOD saying something along the lines of ***Hardware Failure ** ***Contact your hardware vendor for support**. I personally had never seen windows give a message like that so it made me wonder if it was the board actually producing the message. At any rate it wound up being the only BSOD I had experienced during the day so I ignored it.
Later on that night just as I was about to head for bed it happend again, and again, and again, and again. This was after managing to OC my Mobile 2600+ up to 2600 MHz on air at 200 FSB Synced with my ram which was also overclocked to 200 MHz (crucial pc 2700) Dropping the speed down to even bios defaults which picks up the CPU at 800 MHz failed to solve the problem, after two hours i got frustrated and went to bed.
Next morning (afternoon i guess) come out, turn it on set to 2600 MHz and run all damn day with it like that (go figure) no BSOD, not even an indication that there was a problem, after benching and playing Mech 4 Mercs all day I figured maybe it was just a fluke. Well right up untill I tried to go to bed (yes the fuckin gremlins were waiting for that point ). Same damn shit started happening, could barely get into wiindows, and when I did it was only for a few seconds. After 4 or 5 more hours of dicking with it, pullin cards, swapin ram ETC ETC, I was at the fuck it stage it's goin back tomorrow . That was yesterday morning about 5 AM.
Get up at around 1 PM flip the puter on, runs perfectly for another 2 hours decided fuck it didnt want to dick with it again, took it back and got another one.
After some Initial problems with the latest Nforce IDE driver causing winders not to boot I finally get it running good at about 3 AM this morning, and getting all my stuff reinstalled. Fixed the lock on boot by just uninstalling only the Nforce IDE driver (4.24) and going back to the 3.13 driver.
So far im back up to 2500 MHz 166/166 @1.75 Vcore x15 multi 2.7 V on the ram and all is smooth.
Considering this is the first motherboard in 5 years of building my own computers that I had go bad right off the bat, I guess I should count myself lucky, but it certainly is a frustrating thing to have happen.
Going to cross post this on my site Snipershide And eventually I'll post up a review on the board. Pics some hardware info and other things on the site for your enjoyment as well