Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: MoonStorm on January 14, 2012, 09:49:33 pm
-
I spent a week trying to solve BSODs in Windows 7 x64, memory errors in memtest and yellow marks in device manager for two SLI graphics cards on a board with auto settings loaded in BIOS.
All started after a BIOS update from F3 to F8. Loaded default settings. Windows was occasionally BSOD with no indication of the failure (using BlueScreenView) other than STOP errors (usually with a bug check code of IRQL_NOT_LESS_OR_EQUAL) in ntoskrnl.exe, which is rather unusual. Thought initially I had some problems in the drivers and activated the driver verifier. The driver verifier actually pointed to problems in the driver installed by the Gigabyte tools (that was expected to be honest) but in the end, after uninstalling them, I was still out of luck. It was erroring in the same place, sometimes in win32k.sys.
First of all, the memory problems. The tool here http://www.memtest86.com/ (http://www.memtest86.com/) (ver. 4.0) is not compatible with this setup. It'll blow up with CPU HALT errors, making me thing it was CPU/memory related. This one here however http://www.memtest.org/ (http://www.memtest.org/) (ver.4.20) seems to be working though, and initially it was giving memory erros in any DIMM configuration (even with one stick placed anywhere, with or without an XMP profile). Alright, I thought, no problem, large X4 mem kits usually are a challenge for a motherboard, even though it shouldn't be like that (considering the mobo specs) but hey, we're living in times where quality/testing comes as a second priority. So I started to up the voltage for the QPI/VTT and IMC to 1.2V, and in the end the DRAM voltage as well, but just slightly. The memtest succeeded and I was happy.
Next off however, I started seeing weird behaviour in the graphics card department. The "Enable SLI" option was either not active, or it was active and after activating it and a reboot, the cards would display a yellow mark icon in device manager and the resolution was lowered to a minimum. Reinstalling the drivers would solve the problem, but just for the current session. Imagine that happening on every single restart and you'll go mental too.
Now I was aware that I was kind of at the limit with the PSU (Thermaltake 700W old generation), giving lower amps on the rails comparing with the current generation, and I was just about to order one when....
... in desperation I short-circuited the Clear CMOS pins and great was my surprise that by loading defaults in BIOS I got a steady smooth running machine, even with the XMP profile turned on.
What gives Gigabyte? Do you like torturing your customers?
-
I'm still looking for the question !
Aussie Allan
-
I was just trying to help anyone else having the same problems that had searched like mad this forum and others, in an attempt to get their life back on track. It's also an alarm signal for Gigabyte. I've picked Gigabyte thinking all these types of problems would go away. I guess I was just fooling myself.
-
QUOTE ..... in desperation I short-circuited the Clear CMOS pins and great was my surprise that by loading defaults in BIOS I got a steady smooth running machine, even with the XMP profile turned on.
If you did this in the first place ..... you could have saved yourself a hell of a lot of typing :D
Aussie Allan
-
True, but I still believe there are some useful tips in there, don't you think?
-
Some ... but with your new found 20/20 hind sight ..... if you had the same day over again with the new knowledge ..... you would have a very different day and view.......would you not!
I call that experience 8)
Aussie Allan
UPDATE: .... I have no problems at all when people try and help others ..... that's why I'm here.......just leave the product assassination at the day job! ;)
-
Product assasination? Give it a rest Allan. It's QC that we should all be worried about. Have a look at this board specs and compare it with the official tested CPU and memory list on Gigabyte website. Do you see a 3930K proc in there? or any RAM above 8GB?
When you need to buy in haste hardware after an old machine died and you're making a living with it, and this happens, you'll look at things rather differently.
-
OK ....I'll bite ...... what's QC ? :)
Aussie Allan
-
Quality Control?
-
when you consider we're on a site that is really only visited by people with problems with there kit, ..... it does make our perception a bit jaded ..... I hope I'm correct in stating returns are about 0.1% tops if there (gigabyte) are in the average grouping......that's less than 1 in 1000 including the moron factor!
Ive had over 20 gigabyte boards in 16 yrs with not one RMA ..... must be just lucky ..... had an ASUS board once.....it died ;D
Aussie Allan
-
Product assasination? Give it a rest Allan. It's QC that we should all be worried about. Have a look at this board specs and compare it with the official tested CPU and memory list on Gigabyte website. Do you see a 3930K proc in there? or any RAM above 8GB?
When you need to buy in haste hardware after an old machine died and you're making a living with it, and this happens, you'll look at things rather differently.
???
3930K processor is on the list:
http://www.gigabyte.com/support-downloads/cpu-support-popup.aspx?pid=4050
Up to 16GB official GB X79 Memory Support List:
http://download.gigabyte.eu/FileList/Memory/mb_memory_ga-x79-ud3.pdf
Next time,do not flash your BIOS if you don't have proper knowledge.
Here is good tutorial:
http://forums.tweaktown.com/gigabyte/27576-bios-flashing-how-qflash-guide.html
Ive had over 20 gigabyte boards in 16 yrs with not one RMA ..... must be just lucky ..... had an ASUS board once.....it died ;D
Aussie Allan
Same as me,
last month bought new Maximus IV GENE-Z/GEN3 and sell after 3 days of nightmare (with stock setting). >:(
-
I would also like to point out to the OP that instead of a lot of typing regarding the BSOD the simple noting and posting of the STOP code would have been far easier and more useful. Just something for next time. ;)
-
Next time,do not flash your BIOS if you don't have proper knowledge.
Here is good tutorial:
http://forums.tweaktown.com/gigabyte/27576-bios-flashing-how-qflash-guide.html
ex58, reading through how I debugged the problem, you reckon I don't have the proper knowledge? What a lovely community this is...
Clearing CMOS shouldn't be needed after a successful BIOS flash, just loading defaults, but that's what solved my problem.
I'm certain that for the people who experience the same problems with a similar setup, even if the solution might not help in their case, the debugging steps will help greatly.
For the rest of the members on this forum, apparently outraged by my post, ignore this thread and move on.
-
Please don't get the wrong view of the forum MoonStorm as it is normally very friendly and helpful. In their defence I think you caught several members on a bad day, there were a couple of new members who were being downright rude and aggresive in their stance and winding up many normally very friendly forum helpers.
I am sure that many people actually were pleased to see your post and as you mentioned it might help others in future. Sorry for the short replies in general. They weren't meant I am sure.
-
Clearing CMOS shouldn't be needed after a successful BIOS flash, just loading defaults, but that's what solved my problem.
For the rest of the members on this forum, apparently outraged by my post, ignore this thread and move on.
Hi MoonStorm, ;)
Just to share with you that on Gigabyte motherboards, it is natural that we follow the following procedure:
Hi errfoil, ;)
About Flashing a Bios,
Use Q-Flash utilities. Pdf guide.
http://www.gigabyte.com/MicroSite/121/tech_qflash.htm
More infos on Forum here :
How Do I Update My BIOS?
http://forum.giga-byte.co.uk/index.php/topic,2441.0.html
====================================
About Flash Bios
Normaly a End Key is for Flash a Bios. When the post appears.
...
Use a QFlash to reflash BIOS ( Never use @BIOS, because is not good orIt is not the best ..)
More help about How Do I Update My BIOS? Read it, this is the best.
http://forum.giga-byte.co.uk/index.php/topic,2441.0.html
But Before AND after Flash a BIOS...
I do not know if you've done that ... but I invite you to do so.
I suggest you apply the following instructions (quote from Dark Mantis) ...
===================================================
Hi
...
Try clearing the CMOS before installing the GPU. follow these instructions exactly.
Remove the power cable from the mains supply and then press the power switch on the case for a few seconds just to drain any residual energy in the PSU capacitors.
Once done remove the motherboard battery for at least one hour before replacing it.
Next plug back into the mains supply and boot.
You will now need to enter the BIOS by pressing DEL and load Optimised BIOS Defaults.
Make any other changes to the BIOS settings to suit your self like disabling the floppy drive, disabling the full screen logo and making the HDD the primary boot device and then press F10 to save and exit.
And during a Flashing BIOS...
Hi
...
Try using QFlash to update the BIOS to the latest version and make sure that youi disable the "Keep DMI Data" on the QFlash homepage.
Remember that we can not guess what people know ... or like what they had experience and computer knowledge.
Unless expressly if they are written in their message or during a previous message on the forum.
For all people, including myself, we must not forget also to speak with civility greatly helps to reduce conflict and generate positive results in difficult situations in computer hardware.
However, it does not prevent you from using your knowledge and experience to resolve your situation.
I welcome you on the forum, despite the incident. ;)
Gloup_Gloup
-
MoonStorm
Dark Mantis beat me to the punch in an explanation .... It might be easier to explain briefly with a bit of FPS humor ....
About 72hrs ago .... the Forum came under a sustained frontal cyber assault at strength (2 or 3 people)
Half way through the fire fight , the left flank got hit as well, attacking gigabyte hardware and apps with heavy weapons.
Many hardened forum members came out and showed there support and added to the firefight ....two are still MIA
Unfortunately ;) several unknowing new members stuck there heads up... :o.....and had a fire mission put down on there position
This explanation is our/my way of saying sorry, twas the wrong time and place to say "I don't like the green on Gigabyte boards".... would have been enough to mark you as a possible enemy combatant and draw friendly fire.
Any and all constructive information , (mostly computer related) is welcome .... although the occasional lobster or crab recipe does not go astray.
Your opinions will be respected ..... but don't expect others to agree with you......respect other peoples opinions ;)
If we try and keep it constructive instead of destructive .....Gigabyte might just take us seriously and listen to our grievances and ideas.
And a Karma for you MoonStorm for the shot that passed your ear ;D
Aussie Allan
-
Hi Aussie Allan, ;)
After having read the log (Your previous post) of the ship of the fleet admiral Gigabyte on a mission to the UK, I am glad not participate in combat, already been weakened by other actual physical injury.
Thank you for the info AA. :P
Gloup_Gloup
-
The OP's blaming Gigabyte for pilot error was off-putting and set the tone.
Want to advise others? Here:
- You never, ever boot into your OS with known memory errors and you certainly do not go changing things, least of all drivers, with bad memory. If you have an object lodged in your windshield wiper scratching the window, you don't put the wipers on high!
- Make a backup of your BIOS settings when you finalise them. Either PrtScr with an LPT1 printer or take pictures of your BIOS screens and keep them on your phone/camera.
- Always clear CMOS settings and DMI data when updating BIOS.
- Always run basic function tests from a bootable disc, like memtest86+, after a BIOS update; you don't know what they've changed as everything isn't in the change log, which you've, no doubt, read before embarking on this endeavour.
;)