I have not heard anything on the rev2 boards but should get an answer shortly. Penryn works in the boards but I have not been told about "official" support yet. As soon as I have some information I will get it posted.
well with penryn support at least that's some good news. Eventually plan to move on to a 45nm chip and move my E6600 for a HTPC.
Hello, there's some familiar faces here from around the place and other forums, with similar problems to what I have with my board, my dealer and I have been working together and copying / pasting all replies (including mine) to posts I have started asking for help for my motherboard in a fair few forums and we have been sending them to Gigabyte trying to get them to at least try to help or offer an exchange or refund so I can buy a decent board, after about a week and a half of doing this we finally got a reply this morning offering their beta bios update which I have already tried and got nowhere with. I'm at the stage now where I will never touch Gigabyte again (and this is my first motherboard through them), my last 3 where MSI, then previously ASUS and never had trouble. The worst thing is there is nothing we can do
Intel Core 2 Duo E6850 CPU
2 x Kingston Hyper 2 GB Kit memory 1066MHz
Gigabyte GA-N680SLI-DQ6 RV2 Mobo
Razer Barracuda AC-1 Digital Audio Card
XFX PCIe 8800GTX xXx Video card
Thermaltake 1000W Toughpower PSU
WD 250GB SataII HD
2 x WD 500GB SATAII HD
Compro T750 HDTV Dual Tuner PCI Card
Thermaltake Bigwater 745 water cooling
Samsung 226BW 22" monitor
Samsung Syncmaster 913 19" monitor
Silverstone TJ07 Tower
Logitech G9 mouse
Razer Copperhead mouse
Razer Tarantula keyboard
Intel Core 2 Duo E6850 CPU
2 x Kingston Hyper 2 GB Kit memory 1066MHz
Gigabyte GA-N680SLI-DQ6 RV2 Mobo
Razer Barracuda AC-1 Digital Audio Card
XFX PCIe 8800GTX xXx Video card
Thermaltake 1000W Toughpower PSU
WD 250GB SataII HD
2 x WD 500GB SATAII HD
Compro T750 HDTV Dual Tuner PCI Card
Thermaltake Bigwater 745 water cooling
Samsung 226BW 22" monitor
Samsung Syncmaster 913 19" monitor
Silverstone TJ07 Tower
Logitech G9 mouse
Razer Copperhead mouse
Razer Tarantula keyboard
Belveder,
I read your posts in the other thread and would like to make a suggestion. I see you are using Kingston 1066 memory. This memory requires 5,5,5,15 settings and 2.2 volts. Are you using those settings? Are you familiar with how to increase the voltage on the ram?
I read your posts in the other thread and would like to make a suggestion. I see you are using Kingston 1066 memory. This memory requires 5,5,5,15 settings and 2.2 volts. Are you using those settings? Are you familiar with how to increase the voltage on the ram?
Blazer7
Golden Member
- Jun 26, 2007
- 1,136
- 12
- 81
Mr belvedere,
Welcome to our thread. If my memory serves you had/have a mem compatibility issue when using 4 sticks. I?m sorry to hear that you are still plagued with it. I take it that the FBb was of no help to you also. Maybe the next official BIOS will resolve this problem but frankly I somehow don?t believe it will.
Have you tried running your mem @800 2.2V ?
Welcome to our thread. If my memory serves you had/have a mem compatibility issue when using 4 sticks. I?m sorry to hear that you are still plagued with it. I take it that the FBb was of no help to you also. Maybe the next official BIOS will resolve this problem but frankly I somehow don?t believe it will.
Have you tried running your mem @800 2.2V ?
yes Ozoneman have been through all the settings a number of times, Blazer7 has been a great help elsewhere, but nothing has worked.
Have you tried different ram? I don't know much about Kingston ram but I've always thought of that ram as value ram. You might want to try some better ram. The Gigabyte 680i board that we have running here is using Patriot PC6400 (2 2gig sticks). It works great!
Since there are a few bios experts here,I was wondering if any help could be had for the following. I have a ver.1 board with the F5B bios and all is well,except for this nagging bios screen that appears twice on boot up and it states the following
GIGABYTE Technology Corp. PCIE-to-SATAII/IDE RAID Controller Bios v1.06.65
Detect drives done , no any drive found
this comes up twice I suspect as I have 2 HD's installed. But I do not have raid enabled nor do I use raid.
Any way to disable this??????
GIGABYTE Technology Corp. PCIE-to-SATAII/IDE RAID Controller Bios v1.06.65
Detect drives done , no any drive found
this comes up twice I suspect as I have 2 HD's installed. But I do not have raid enabled nor do I use raid.
Any way to disable this??????
- Apr 5, 2005
- 508
- 0
- 0
Good Evening Mr. RaisinMan.
It sounds like your CMOS is "retaining" a false sensing of equipment. That has happened to me on a couple of occasions. May I suggest the following:
1. Download the F5e BIOS that Mr. Gary posted a number of pages ago (I think it's back in the 60's range).
2. Clear the CMOS, and remove the onboard battery for about 5 minutes, then clear the CMOS again, and replace the battery.
3. Fire up the PC and enter the Q-Flash utility (End key from boot, or F8 in setup routine).
4. In Q-Flash change the DMI retention option to "Disable."
5. Flash the CMOS with the F5e BIOS.
6. Shutdown the PC from the Q-Flash utility (F10).
7. Disconnect the power from the PC for 30 seconds, then reconnect the power and fire up the PC.
8. Enter the CMOS Setup Routine and Select "Optimized Defaults."
9. Set the various CMOS optional pages (be sure to activate Advanced Selections via Ctrl+F1). Be sure to carefully check any activation of the RAID related options in the CMOS setup pages.
10. Save the CMOS settings and restart.
11. Enter the CMOS Setup again, and check all your settings in Advanced Setup.
12. Restart the PC and see if that corrects the problem.
Best of luck, and let us know how you make out on this. Best regards. TheBeagle
:beer:
It sounds like your CMOS is "retaining" a false sensing of equipment. That has happened to me on a couple of occasions. May I suggest the following:
1. Download the F5e BIOS that Mr. Gary posted a number of pages ago (I think it's back in the 60's range).
2. Clear the CMOS, and remove the onboard battery for about 5 minutes, then clear the CMOS again, and replace the battery.
3. Fire up the PC and enter the Q-Flash utility (End key from boot, or F8 in setup routine).
4. In Q-Flash change the DMI retention option to "Disable."
5. Flash the CMOS with the F5e BIOS.
6. Shutdown the PC from the Q-Flash utility (F10).
7. Disconnect the power from the PC for 30 seconds, then reconnect the power and fire up the PC.
8. Enter the CMOS Setup Routine and Select "Optimized Defaults."
9. Set the various CMOS optional pages (be sure to activate Advanced Selections via Ctrl+F1). Be sure to carefully check any activation of the RAID related options in the CMOS setup pages.
10. Save the CMOS settings and restart.
11. Enter the CMOS Setup again, and check all your settings in Advanced Setup.
12. Restart the PC and see if that corrects the problem.
Best of luck, and let us know how you make out on this. Best regards. TheBeagle
:beer:Hi Folks,
first of all I wanted to thank you in advance for the dedication to this thread. There is a stack of good advice and you allshould be commended.
first my specs:
GA-N680SLI-DQ6 Rev 1
Intel E6600 cpu
BFG 8800 GTX 768mb gpu
4gig OXZ SLI PC2 8500 ram
2x WD 500gig HDD Raid 0
bios F3 then F4 then F3
I think I lost my mind when I decided to take a perfectly stable system and flash to Bios F4. In the process this tanked my Raid. I spent the last couple of days recovering my data off of the hdd's (thank goodness) and I got to the point where I thought that the hdd's were ruined.
I put them in my spare rig and using the WD Lifeguard tools, I was able to reformat them both. I've put them back into the Gigabyte rig, reset the drives to Raid 0 and went into Windows XP setup in order to reinstall the OS. Got to the point of Setup Is Starting and then BSOD error stating that there's something wrong with my HDD's and I need to run Chk Dsk on them.
I'm at a bit of a loss as the drives appear to be OK but the Raid configuration isn't.
Has anyone experienced this? I've put a different SATA drive in the gigabyte rig and successfully installed XP on it. I also put back all of the original drivers that came with the MB but still no joy with the Raid Drives..
Help?.. Question would be whether or not the F5b or e? bios would sort this out?
Many thanks.
NF
first of all I wanted to thank you in advance for the dedication to this thread. There is a stack of good advice and you allshould be commended.
first my specs:
GA-N680SLI-DQ6 Rev 1
Intel E6600 cpu
BFG 8800 GTX 768mb gpu
4gig OXZ SLI PC2 8500 ram
2x WD 500gig HDD Raid 0
bios F3 then F4
then F3I think I lost my mind when I decided to take a perfectly stable system and flash to Bios F4. In the process this tanked my Raid. I spent the last couple of days recovering my data off of the hdd's (thank goodness) and I got to the point where I thought that the hdd's were ruined.
I put them in my spare rig and using the WD Lifeguard tools, I was able to reformat them both. I've put them back into the Gigabyte rig, reset the drives to Raid 0 and went into Windows XP setup in order to reinstall the OS. Got to the point of Setup Is Starting and then BSOD error stating that there's something wrong with my HDD's and I need to run Chk Dsk on them.
I'm at a bit of a loss as the drives appear to be OK but the Raid configuration isn't.
Has anyone experienced this? I've put a different SATA drive in the gigabyte rig and successfully installed XP on it. I also put back all of the original drivers that came with the MB but still no joy with the Raid Drives..
Help?.. Question would be whether or not the F5b or e? bios would sort this out?
Many thanks.
NF
- Apr 5, 2005
- 508
- 0
- 0
Hello Mr. Ninja.
It is likely that you have some problems associated with the information that is written to the Master Boot Record (MBR) on your hard drives. When a hard drive is introduced into a RAID environment, and made part of an array, it has certain data written to the drive's inner disk surfaces that tell the drive that it should act as part of an array. However, that array designation data can get messed up in certain circumstances, and it sounds like you may have encountered such a situation.
First of all, I would strongly suggest that you flash the CMOS with BIOS revision 5Fe. Mr. Gary made that gem available to us a few months ago, and the link to it is at least back to Page 60 or so. BIOS F5e is the most stable RAID microcode, and you should not encounter problems associated with the level of BIOS revision if you use that version.
As has been mentioned several times previously in this Thread, IF you are going to use a RAID 0 array for your boot drive (or any important data drive), then you ought better have a fail-safe redundancy plan in place to cover your butt whenever your array runs into trouble. And believe me, the old saying about "if it can get screwed up, it will!" is solid gold advice when it comes to RAID 0 arrays. Having stated that, you can reasonably expect fairly good performance from a RAID 0 array, as long as the drives are suited for that use (i.e., "YS" drives from Western Digital that have the TLER function FULLY enabled).
If after you flash your CMOS with BIOS F5e, you still have a problem with your array, then a much more extensive remedial effort is indicated. First of all, you need to save all your important data on the RAID 0 hard drives to some other place, since what you're going to have to do is going to wipe out any and all data on those drives. You didn't indicate what operating system you are using going forward, so I'm going to presume you are going to stay with WinXP and that you have access to a WinXP install disk.
With that presumption, you are going to need to INDIVIDUALLY attach ONLY one (1) of the RAID 0 array hard drives to the PC, and initiate a WinXP operating system install routine. You know, the basic blue screen which you encounter when you are loading WinXP for the first time. Be sure to load any drivers that might be necessary to access that hard drive (F6) during the first few seconds of that routine. When you get to the portion of the install routine, after you acknowledge the ELUA (F8), you should see the hard drive listed. What you want to then accomplish is to wipe out any partitions on that physical drove, and then do a FULL format so that the MBR is wiped clean. Be sure to watch the format routine procedure as it progresses, and be prepared to stop the machine as soon as the MBR format is completed. Repeat this process for the other RAID 0 hard drive.
You should now have two completely freshened hard drives, and you can proceed to designate them as RAID 0 hard drives in a newly constructed array, utilizing the F5e BIOS as the controller, and you should be good to go from there. I know this procedure is a bit laborious, but you must effectively clear the "old" RAID designation from the drive, before you can be assured that you have a solid foundation for your PC.
I hope that helps. Let us know how you make out. Best regards. TheBeagle :beer:
It is likely that you have some problems associated with the information that is written to the Master Boot Record (MBR) on your hard drives. When a hard drive is introduced into a RAID environment, and made part of an array, it has certain data written to the drive's inner disk surfaces that tell the drive that it should act as part of an array. However, that array designation data can get messed up in certain circumstances, and it sounds like you may have encountered such a situation.
First of all, I would strongly suggest that you flash the CMOS with BIOS revision 5Fe. Mr. Gary made that gem available to us a few months ago, and the link to it is at least back to Page 60 or so. BIOS F5e is the most stable RAID microcode, and you should not encounter problems associated with the level of BIOS revision if you use that version.
As has been mentioned several times previously in this Thread, IF you are going to use a RAID 0 array for your boot drive (or any important data drive), then you ought better have a fail-safe redundancy plan in place to cover your butt whenever your array runs into trouble. And believe me, the old saying about "if it can get screwed up, it will!" is solid gold advice when it comes to RAID 0 arrays. Having stated that, you can reasonably expect fairly good performance from a RAID 0 array, as long as the drives are suited for that use (i.e., "YS" drives from Western Digital that have the TLER function FULLY enabled).
If after you flash your CMOS with BIOS F5e, you still have a problem with your array, then a much more extensive remedial effort is indicated. First of all, you need to save all your important data on the RAID 0 hard drives to some other place, since what you're going to have to do is going to wipe out any and all data on those drives. You didn't indicate what operating system you are using going forward, so I'm going to presume you are going to stay with WinXP and that you have access to a WinXP install disk.
With that presumption, you are going to need to INDIVIDUALLY attach ONLY one (1) of the RAID 0 array hard drives to the PC, and initiate a WinXP operating system install routine. You know, the basic blue screen which you encounter when you are loading WinXP for the first time. Be sure to load any drivers that might be necessary to access that hard drive (F6) during the first few seconds of that routine. When you get to the portion of the install routine, after you acknowledge the ELUA (F8), you should see the hard drive listed. What you want to then accomplish is to wipe out any partitions on that physical drove, and then do a FULL format so that the MBR is wiped clean. Be sure to watch the format routine procedure as it progresses, and be prepared to stop the machine as soon as the MBR format is completed. Repeat this process for the other RAID 0 hard drive.
You should now have two completely freshened hard drives, and you can proceed to designate them as RAID 0 hard drives in a newly constructed array, utilizing the F5e BIOS as the controller, and you should be good to go from there. I know this procedure is a bit laborious, but you must effectively clear the "old" RAID designation from the drive, before you can be assured that you have a solid foundation for your PC.
I hope that helps. Let us know how you make out. Best regards. TheBeagle
:beer:Originally posted by: TheBeagle
Good Evening Mr. RaisinMan.
It sounds like your CMOS is "retaining" a false sensing of equipment. That has happened to me on a couple of occasions. May I suggest the following:
1. Download the F5e BIOS that Mr. Gary posted a number of pages ago (I think it's back in the 60's range).
2. Clear the CMOS, and remove the onboard battery for about 5 minutes, then clear the CMOS again, and replace the battery.
3. Fire up the PC and enter the Q-Flash utility (End key from boot, or F8 in setup routine).
4. In Q-Flash change the DMI retention option to "Disable."
5. Flash the CMOS with the F5e BIOS.
6. Shutdown the PC from the Q-Flash utility (F10).
7. Disconnect the power from the PC for 30 seconds, then reconnect the power and fire up the PC.
8. Enter the CMOS Setup Routine and Select "Optimized Defaults."
9. Set the various CMOS optional pages (be sure to activate Advanced Selections via Ctrl+F1). Be sure to carefully check any activation of the RAID related options in the CMOS setup pages.
10. Save the CMOS settings and restart.
11. Enter the CMOS Setup again, and check all your settings in Advanced Setup.
12. Restart the PC and see if that corrects the problem.
Best of luck, and let us know how you make out on this. Best regards. TheBeagle
Thank you for the advice!
As soon as practicle I will do as you advise and report back with the findings!
Hi Mr. Beagle,
I've successfully flashed to F5e and tried what you suggested.
Unfortunately, even with 1 drive installed, I still get the BSOD error.
However, what I have done is put the drives in my spare rig, using the WD Lifeguard tools, recreated the partitions. I'm now in the process of formatting the drives in the spare rig. once this is done, I'll pop them back in the gigabyte rig and proceed from there.
Fingers crossed.
It is definately these drives and some kind of hangover from the previous raid. Worse case I guess I can always use them as individual drives and not a raid 0 setup. I am beginning to wonder if something on the MB itself has broken and perhaps I should try a different pair of raid slots to plug the SATA drives into..
I'll update you as soon as I can.
NF
I've successfully flashed to F5e and tried what you suggested.
Unfortunately, even with 1 drive installed, I still get the BSOD error.
However, what I have done is put the drives in my spare rig, using the WD Lifeguard tools, recreated the partitions. I'm now in the process of formatting the drives in the spare rig. once this is done, I'll pop them back in the gigabyte rig and proceed from there.
Fingers crossed.
It is definately these drives and some kind of hangover from the previous raid. Worse case I guess I can always use them as individual drives and not a raid 0 setup. I am beginning to wonder if something on the MB itself has broken and perhaps I should try a different pair of raid slots to plug the SATA drives into..
I'll update you as soon as I can.
NF
Blazer7
Golden Member
- Jun 26, 2007
- 1,136
- 12
- 81
Hello Mr Ninja.
I?ve been using 4 RAID 0 arrays from the early days of this board and never had any trouble. I?ve also updated from the F3 to the F4 some months ago and none of my arrays were affected. That said I?m not completely sure that your BIOS update was the sole reason for your problem. TheBeagles advise and comments on the MBR and BIOS are definitely correct and you did good updating your BIOS to the F5e as the F3 and F4 are junk.
Have you noticed anything different with the new BIOS ? Which controller are you using for your RAID array ? Please keep us posted on your progress.
I?ve been using 4 RAID 0 arrays from the early days of this board and never had any trouble. I?ve also updated from the F3 to the F4 some months ago and none of my arrays were affected. That said I?m not completely sure that your BIOS update was the sole reason for your problem. TheBeagles advise and comments on the MBR and BIOS are definitely correct and you did good updating your BIOS to the F5e as the F3 and F4 are junk.
Have you noticed anything different with the new BIOS ? Which controller are you using for your RAID array ? Please keep us posted on your progress.
Hello Mr ninja!
For chits and giggles try the purple SATA ports that are toward the rear of the board,make sure you Bios settings are properly adjusted for this setting. I had the same issues as you have mentioned after doing this I have never looked back. My board is a rev2 so you know.
My board is still in RMA heaven for other problems not associated with it, they just got it so they stated in an E-mail two to three Weeks now just to turn it around.
Mr. Belveder,
Sorry to see you still have issues, as someone suggested RMA them sticks of ram try different manufacturer, I have G-skill they work great. Avoid the "dominator" series from what I have read 2 another thread, hope this helps you. Good day to you all!
Mr blazer,
roflmao! You got me laughing so hard today, I thank you for that. Yeah the gigatech over at weak town. Is for the lack of a better word disarmed, and he is a she(but not a he she). She is from china or there abouts so you know, but hey please pay her a visit and see the "deer in the head lights" responses there great!!
You have a great sense of humar and with the problems with this board it's a good thing to have!
Cheers! to all!
P.S. i'll post back when and if mine ever returns from RMA vacation!
Well...
Unfortunately the process hasn't worked. I can set up the new array but it still gives me the BSOD ChkDsk error..
I took a chance and plugged the drives into the GRaid and then set up another raid array.
I went into windows (using the other drive) and ran the WD data lifeguard tools and created the array as a boot drive. Curiously enough it's copying the entire drive including system files onto the new array.. ?? Didn't expect it to do that but hey, not much to lose at this point is there?
At least Windows is recognizing the array as a drive now.. This is a real PITA and to be honest given that the only thing I did originally was to flash to a new Bios as provided by Gigabyte, I should really look to RMA this puppy as I think the raid is somehow broken..
I'll let you know if I can boot from the new array or not.
NF
Unfortunately the process hasn't worked. I can set up the new array but it still gives me the BSOD ChkDsk error..
I took a chance and plugged the drives into the GRaid and then set up another raid array.
I went into windows (using the other drive) and ran the WD data lifeguard tools and created the array as a boot drive. Curiously enough it's copying the entire drive including system files onto the new array.. ?? Didn't expect it to do that but hey, not much to lose at this point is there?
At least Windows is recognizing the array as a drive now.. This is a real PITA and to be honest given that the only thing I did originally was to flash to a new Bios as provided by Gigabyte, I should really look to RMA this puppy as I think the raid is somehow broken..
I'll let you know if I can boot from the new array or not.
NF
Hi Blazer
Just noticed this now..
I was successful in doing a full format of the hdd's but not within the windows setup process. It did work inside windows which I'm happy about. Unfortunately I still couldn't install windows on this array (once I set it up..)..
With respect to your question, outside of the fact that the system recognizes the bios in the initial post screen, it looks identical to F3 / F4.
With respect to the controller, the system shows that I'm using the GBB36X controller (purple one)
OK.. Update..
I'm seriously impressed by the WD Data Lifeguard tools.. I was able to boot from the array that was copied over from my original installation.
I'm now starting the long and exciting process of setting everything up again. I'm thrilled to bits that it's working but I'm still concerned about the main raid controller on the MB.
I've run a check disk and also a defrag and everything checks out OK..
What are your thoughts on RMA or testing the whether or not the raid controller on the MB is broken or not?
I'm seriously impressed by the WD Data Lifeguard tools.. I was able to boot from the array that was copied over from my original installation.
I'm now starting the long and exciting process of setting everything up again. I'm thrilled to bits that it's working but I'm still concerned about the main raid controller on the MB.
I've run a check disk and also a defrag and everything checks out OK..
What are your thoughts on RMA or testing the whether or not the raid controller on the MB is broken or not?
Blazer7
Golden Member
- Jun 26, 2007
- 1,136
- 12
- 81
ok Mr Ninja,
My thoughts were that since you had your RAID up and running you should load it with junk and then defrag it to see whether it brakes down or not but you beat me to that. Great job. :thumbsup:
If you want to test nVidia's controller you'll have to do it the hard way. This means setting up a RAID again. Are you interested ? I'm running 3 RAID 0 arrays from nVidia's controller and the 4th from the 2nd Gigabyte. nVidia's is definitely better but setting up a RAID from scratch is time consuming especially if it is your boot drive.
Before jumping the gun have in mind that RAID 0 is not exactly RAID as there is no redundancy. This means that if one disk fails the whole RAID collapses. The more disks you use in a RAID 0 the greater the risk. It is almost insane not to have a backup when dealing with RAID 0. I'm using Norton Ghost for my backup and I strongly recommend it to anybody that uses RAID 0 especially as a boot drive.
If you understand all this and you still wanna give it a shot then we are here to help as much as we can.
PS
Of course there is that old saying ... if it ain't broken leave it alone and right now your rig is going. Your call.
My thoughts were that since you had your RAID up and running you should load it with junk and then defrag it to see whether it brakes down or not but you beat me to that. Great job. :thumbsup:
If you want to test nVidia's controller you'll have to do it the hard way. This means setting up a RAID again. Are you interested ? I'm running 3 RAID 0 arrays from nVidia's controller and the 4th from the 2nd Gigabyte. nVidia's is definitely better but setting up a RAID from scratch is time consuming especially if it is your boot drive.
Before jumping the gun have in mind that RAID 0 is not exactly RAID as there is no redundancy. This means that if one disk fails the whole RAID collapses. The more disks you use in a RAID 0 the greater the risk. It is almost insane not to have a backup when dealing with RAID 0. I'm using Norton Ghost for my backup and I strongly recommend it to anybody that uses RAID 0 especially as a boot drive.
If you understand all this and you still wanna give it a shot then we are here to help as much as we can.
PS
Of course there is that old saying ... if it ain't broken leave it alone and right now your rig is going. Your call.
Fallen Kell
Diamond Member
- Oct 9, 1999
- 6,180
- 519
- 126
This is why I personally don't run my OS partition on a RAID disk. Too many headaches between Windows and drivers and hardware... RAID is great for data disks, but almost always causes problems with Windows.
Hey guys i know this is a bit side tracked but what kind of 3dmark Scores are u getting i Have a GA N680 SLI DQ6 rev1, Intel QX6700, 2 X XFX 8800 GTX XXX and corsair Dominator 8500 C5D....i only get 12751 with 3dmark06 ???? this is with the latest drivers from nvidia....i dont know if its just me but that seems kinda low and also for windows rating index i only get 5.1 which is because of my RAM ????? =S i payed alot for this ram and i only get 5.1 ???? ive seen loads of ppl get 5.9 anyway tell me what you guys think thanx
Rob
Rob
eklock2000
Senior member
- Jan 11, 2007
- 292
- 0
- 0
I'm gettin' about 10,700 in 3DMark06. I feel like it's low too, but I've got no litmus test cuz my old computer was so slow. Also, heard it's CPU limited and I'm not overclocking. Does 3DMark take into account multi-cores?
Peace,
EK2K
GA-N680iSLI-DQ6, Rev. 1, F5b
Intel E6600 w/ Zalman 9700
eVGA 8800GTX w/ 163.71 forceware
2Gb - Crucial Ballistix PC2-8000 (BL2KIT12864AA1005)
Corsair CMPSU 620HX
Antec900
WinXP SP2
Peace,
EK2K
GA-N680iSLI-DQ6, Rev. 1, F5b
Intel E6600 w/ Zalman 9700
eVGA 8800GTX w/ 163.71 forceware
2Gb - Crucial Ballistix PC2-8000 (BL2KIT12864AA1005)
Corsair CMPSU 620HX
Antec900
WinXP SP2
Yes, the CPUtest in 3DMark06 is multi-threaded so it takes advantage of Multi-core processors. rt182, I don't know what is going on with your PC. We have almost the same setup and I am scoring a lot higher than you (not to rub it in) I did overclock my CPU to 3.43 gHz and I flashed both my video card Bios's to be super overclocked. Check out my specs.
Hi guys,
Another problem... in windows both of the Network Controllers from the nForce disappeared, but the Marvell Yukon ones are still here.... I am a loss to explain this. They're not showing in Device Manager, nor in the Network Connections. THis is happening on both Vista Ultimate x64 and Server 2003 x64
Another problem... in windows both of the Network Controllers from the nForce disappeared, but the Marvell Yukon ones are still here.... I am a loss to explain this. They're not showing in Device Manager, nor in the Network Connections. THis is happening on both Vista Ultimate x64 and Server 2003 x64
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter