Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with AMD processors => Topic started by: smallfrycel on February 07, 2011, 07:51:06 pm
-
hi guys,
My boyfriend has come to some major computer trouble and neither of us can figure out whats wrong. And I mean like at all.
He woke up for work and turned his computer on and it didnt turn on. So he presumed his power supply had crapped itself. He went and bought a new one that day (AMD Phenom II) and also picked up a new motherboard (Gigabyte GA-MA77OT-UD3). Two 4g sticks of Ram and a new video card, a Radeon HD 5770.
SO everything is brand new. He's running windows Vista Pro version.
The computer turns on, boots up and then about 10 or 15 minutes later it just s***s itself and blue screens. What the heck is going on? Please please please, does anyone have ANY idea what the problem is?
-
Hi and welcome to the Gigabyte Forum.
Well it could be any number of things at the moment. Probably topmost on hte list would be memory. Either it isn't compatible or faulty.
Did he check to make sure they are compatible before purchase ?
Are they in the right slots ?
Is the processor supported by the BIOS ?
Is the PSU a decent make/model and large enough ?
Probably a good idea if you could list all your hardware please.
-
Power supply - Antec Earthwatts EA-650
He checked all the ram today and its completely fine. Ram is Cosair 2x 4gb sticks.
The processor is supported by the BIOS. He's updated it to the latest thingy.
He can boot the computer and run in BIOS mode and it doesnt die.
It blue screens randomly just out of no where.
-
the blue screen error is apparently " IRQ L not less or equal" thats the most common one anyways.
If its a hardward error how can you reset to BIOS and it still be working? It doesnt freeze completely. How can it be in the BIOS and it be there for hours and as soon as it goes to windows it just dies after minutes.
Also the CPU temperature only gets to 41 degrees.
It seems to stay up without specific drivers loaded from gigabyte.
Man what the heck is going on with it, i just dont get it.
-
It might well be that the memory is compatible but not set correctly.
Can you give me the stop code from the BSOD ?
-
Hi,
You say it has been tested but that doesn't always mean the RAM is fine.
Did you run MemTest on each stick individually for at least 10 passes with the RAM Module inserted in slot DDR3_1?
Have you tried to Manually set the RAM timings and Voltage?
What Corsair RAM are you actually running? (voltage, timings etc.)
-
he just told me that he's ran the memtest on each stick for the 10 phases and all was fine.
BSOD is "IRQ L not less or equal" its not on screen long enough to read the rest
-
Well it seems to point to a memory error so assuming that I'm right please list all the memory settings and the voltage. It will be something like 9-9-9-24 1.65v
Also if you check in the BIOS it should tell you the memory multiplier etc
-
All the memory, everything is on/set to 'Auto'. the Gigabyte motherboard is running everything.
It doesnt crash in the bios at all.
It only bluescreens in windows.
The memory is Corsair 2x 4gb XMS3 DDR3
He's now formatted the harddrive and re-installing Windows.
he thinks its the sounds card - because when he first set it up it didnt crash all night. he then installed the Gigabyte drivers and thats when the problems started. it started blue screening.
he's installing windows now and hes going to test with just the windows default drivers
-
Has he disabled the onboard sound capability ?
What speed is the memory running at ?
Just because it is on Auto in the BIOS doesn't mean that is the best settings for the memory though.
-
What settings do you think the memory should be on?
the thing is the BSOD is completely random.
-
I don't know what settings it should be on because you won't tell me!! ;D
There should be a sticker on the side of the modules with the numbers on it.
-
hey :P dont shoot the messenger :P im the one with a working computer LOL! so im passing on what im told. Ok I got the box here. it says Corsair 4gb XMS3 PC3-10666MHz
is that what you're after?! :D ???
-
OK messenger, you're safe! ;)
Thats only part of the data. The modules themselves, not the box should have the timings printed on a sticker along with the default voltage.
-
ok so he's just reinstalled windows, and then restarted because one of his hard drives has disappeared completely.
its just restarted and it randomly made the tv out the "main" screen for some reason. Also the missing harddrive is still missing - ok edit the missing hard drive its back now - it had lost the driver.
i'll get back to you on the memory thingo
-
http://www.scan.co.uk/products/4gb-corsair-xms3-ddr3-pc3-10666-%281333%29-non-ecc-unbuffered-cas-9-9-9-24-150v
its that one ;D so this i think
CMX4GX3M1A1333C9 - 4GB Corsair XMS3, DDR3 PC3-10666 (1333), Non-ECC Unbuffered, CAS 9-9-9-24, 1.50V
-
Right make sure the memory is set to unganged and 1.5v in the BIOS. This you will have to set manually. The timings are as you have given me, 9-9-9-24 that's the first four lines which should start with CAS Latency. Leave it at the default speed.
When he has finished just F10 to save and exit.
We will than see what if any difference that makes.
Also follow this when you get to Windows.
First thing I would advise you to do would be to go to Control Panel/System Properties/Advanced System Settings/Advanced tab/Startup and Recovery/Settings and untick the box marked Automatically restart and then OK.
That will stop the system rebooting before you can see what the BSOD says.
-
:D have passed on your message and he's nodding his head. I will get back to you if anything crashes god forbid! :-[ he's missed work for the last 3 days because of this eeek!
currently running playing a video with the windows drivers for audio and so far its fine - *knock on wood* but its only been 10 minutes.
-
Well at least he's dedicated! That's what it takes sometimes when these types of things happen. The only good thing is that this is when you really learn about your system not when the build goes easilly! ;)
-
hes just changed that setting you said then. said he will look at the memory setting thing when he restarts.
he's just installing a couple of drivers on it now.
-
It is always best to install one at a time and then reboot and make sure it is working ok before installing the next one.
-
he's just changed the memory thing and said that you cant change the voltage setting because theres no setting for it.
he's running a hardware test thing. still no video card drivers or anything installed yet.
-
There should be but I'm afraid it will have to wait until the morning now as I have been on here for about fifteen hours and I'm knackered. I will be back tomorrow if he still needs help. ;)
-
i just hope its ok for him to work tomorrow.
thanks for your help tonight. muchly appreciated. i will let you know what happens.
also with the voltage thing, it did say 1.5 already so im presuming thats ok?
-
Yes no problem for the voltage.
-
annnnnd BSOD!
IRQL_NOT_LESS OR_EQUAL
*** STOP 0x0000000A
GRRRRRRRR! Seriously wtf! It was completely fine before and then what an hour after it crashed!
10:05pm its fine and then BLAH big fat Blue screen of DEATH at a random point when not doing anything at 11:46pm
As I said random, and everything was running fine. and that's it.
-
hello mate,
best program i have found by far is intel burn in test ...i've used memtest loads of times and got passes then system still random blue screens .. then i found out about Intel burn in test which is supposed to be the test intel uses, dont quote me on that though lol ... anyway that tests ram and cpu always finds fault where memtest passes , test ram 1 stick at a time using intel burn in and set the sofware to us max ram .. even if ram timming are correct this software will find any probs if there are any with cpu or ram
-
annnnnd BSOD!
IRQL_NOT_LESS OR_EQUAL
*** STOP 0x0000000A
GRRRRRRRR! Seriously wtf! It was completely fine before and then what an hour after it crashed!
10:05pm its fine and then BLAH big fat Blue screen of DEATH at a random point when not doing anything at 11:46pm
As I said random, and everything was running fine. and that's it.
just to make ya mate feel better i bet its ram , i have had exact same problem the only way it could be fixed for me was change'n ram for kingston KVR ram 1333mhz cheap as cheaps ram to so i bought 16gig 4x4gig and me pc pass intel burn test and no more random blue screens :D crucial ram is good too never had any issues with therecheap stuff to
-
hello mate,
best program i have found by far is intel burn in test ...i've used memtest loads of times and got passes then system still random blue screens .. then i found out about Intel burn in test which is supposed to be the test intel uses, dont quote me on that though lol ... anyway that tests ram and cpu always finds fault where memtest passes , test ram 1 stick at a time using intel burn in and set the sofware to us max ram .. even if ram timming are correct this software will find any probs if there are any with cpu or ram
where do i get this intel program thing? can it boot off a usb stick or do you have to run it from windows?
-
also, how am i supposed to run the program if it keeps BSOD?! :'( windows wont stay up long enough to test it knowing my luck
-
serrrrrriously dont know what the heck is wrong with this AT ALL!
How can I determine what the problem is?
How do I know if one of the parts what we bought is faulty or not? - Could it possibly be the motherboard thats causing the problems? Could it be the CPU?
this is the 4th day we've been trying to figure out wtf is wrong with this machine. I just don't understand what would cause the machine to BSOD completely randomly if everything is new, and compatible with everything.
Could there be a virus somewhere?
I'm clutching at straws, I just want the thing to work!
If there's nothing wrong with the RAM then what else could it be, and why can't we or anybody for that matter find it?
:'( feel like I'm pounding my head against a brick wall! If I take the parts back to the shop, what do I say, and will they give me replacements?
-
Hi again,
Just wanted to check that when you bought the modules they were purchased as a matched kit not two seperate modules weren't they ?
and you have installed them in DDR3_1 and DDR3_2
You can download the Intel Burn Test here:
http://downloads.guru3d.com/IntelBurnTest-v2.3-download-2047.html
Most of these tests don't need Windows to run so you don't have to worry about that.
Do watch the tempertures with this test though. They don't call it Burn Test for nothing!
To be honest I don't find it any better than Memtest for the memory but you can try it if you want.
-
serrrrrriously dont know what the heck is wrong with this AT ALL!
How can I determine what the problem is?
:'( feel like I'm pounding my head against a brick wall! If I take the parts back to the shop, what do I say, and will they give me replacements?
I understand your frustration and facing these kind of issues can be a real nightmare. The fact that everything seems to be OK in BIOS but once into the operating system you are getting these BSOD's would point to a driver problem of some sort.
This STOP error can occur during startup or at any other time. The 8 digit hexadecimal number 0x0000000A translates to the bug check code “IRQL_NOT_LESS_OR_EQUAL” which may be caused by the following:
A kernel-level application or device driver running in kernel mode tried to read or write to a memory location that had restricted permissions. The code IRQL_NOT_LESS_OR_EQUAL indicates that the interrupt request level (IRQL) was higher than the number that was expected. A process running in kernel mode cannot access a process that has an IRQL which is greater than its own.
Components of the hardware may have failed such as the memory chip, the processor or motherboard. It may also indicate problems in video or disk adapters or device driver incompatibility issues.
Computer Hardware may not be OS compatible.
This STOP error usually results from the faulty installation of System Services, BIOS firmware or device drivers.
It can also be caused by incompatible virus scanners or backup tools.
Sometimes viruses or the anti-virus software that is running on the computer may cause problems.
A full list of the hardware being used would help but without that information my best guess would be either Audio or Graphic drivers being the main culprit.
-
Ok so last night we got to bed around 4 am.
We've changed two things and it hasn't BSOD in 14 hours.
There was a serial ATA cable attached to the board and not connected to anything else, which has now been removed.
And we've also removed one of the memory sticks.
I think after he's finished work (which will be late due to not working for the past 3 days) he's going to test it with the other memory stick in and see if it was just the cable that was there, or infact it is the memory stick.
He's been playing videos and sound almost all day and its been fine.
A kernel-level application or device driver running in kernel mode tried to read or write to a memory location that had restricted permissions.
could this be caused by the serial ATA cable that was attached to the motherboard and nothing else? Would have this been why it was BSOD? Or would it not even make a difference?
thanks for all your help guys, really appreciate it!
-
Having a SATA cable attached to the motherboard and not to anything else shouldn't cause the kind of problems you've been facing. I actually have a couple of unconnected SATA cables in my own PC as I tend to swap HDDs a LOT and they have never cause a problem.
-
its been on for almost 15 hours now
ok he just turned it off and put the other ram stick in went to turn it on and now the bootmng is missing :-[ ???
he can boot from the vista dvd but wtf now caused that?
-
As absic said there is no chance the unused SATA cable had anything to do with it. In fact I have one attached now to my machine but it doesn't make any difference.
It has to be the memory, one way or another.
-
As absic said there is no chance the unused SATA cable had anything to do with it. In fact I have one attached now to my machine but it doesn't make any difference.
It has to be the memory, one way or another.
but would the memory cause the bootmng to disappear?
if he pulls out the ram stick technically if thats the problem it should all work fine again for another 15 hours? or will this bootmng thing go missing every time he shuts down and restarts or turns it on ?
or is this a motherboard problem again now? ......... man this is doing my head in
-
Missing bootmngr is the message you get when Windows can't find the drive to boot from. This would indicate that there is something wrong with the drive-cable-controller setup. Obviously the easiest one to check is the cable so I would suggest swapping the SATA cable with another one. While he is there swap the power cable to the drive too. It is quite possible that when swapping the memory over he just moved the cable etc enough to disturb the connection.
-
he just said he didnt touch the cables because theyre clipped in securly so that you cant move them. well you can but you have to unclip it
so would that mean that if the controller's gone, then it would be the motherboard thats the problem?
-
This code "IRQL_NOT_LESS_OR_EQUAL" used to be seen quite regularly when installing windows, (from 98 to xp). I have seen it many times and the solution , excluding a hardware problem, was to strip back the comp to the basics. That is 1 stick of ram, 1 h/d and 1 optical drive. (Obviously you need graphics card, k/b, mouse and monitor). With this basic setup install the O/S. Then let it run and install all the drivers required for the mobo, graphics. Install one at a time. When the system becomes stable you can then install anything else you might have including the 2nd stick of ram. All of the above will work assuming that none of the components are faulty. I have however only come across this problem one or twice with Vista, but failing everything else and the advice given in previous posts it might be worth a try.
-
he just said he didnt touch the cables because theyre clipped in securly so that you cant move them. well you can but you have to unclip it
so would that mean that if the controller's gone, then it would be the motherboard thats the problem?
When I said moved the cable I only meant a fraction as in if there was a bad connection. Any slight movement of the board etc could be enough. But as I said it could be any of the three components, if we are to revert to guessing then yours is as good as mine. :-\
-
When I said moved the cable I only meant a fraction as in if there was a bad connection. Any slight movement of the board etc could be enough. But as I said it could be any of the three components, if we are to revert to guessing then yours is as good as mine. :-\
i soooo completely just dont understand why this isnt working as it should. the parts weren't exactly cheap and now what do I do with it all. It seems like we have tried everything, even taking everything out and putting it all back in one by one, starting from scratch with formatting the hard drives and installing windows vista again.
Does it have something to do with the harddrives on the system? He has 3. one of them is partitioned with windows on it. Its all running the default drivers that come with windows. I know last night when he tried to install the drivers for the graphics card it BSOD. The only thing I can think is that the motherboard (rev 1.5) isn't actually 1.5. Its on the latest F 8 - however im noticing that the rev 1.4 versions of the motherboard have F 10. And how come theres not much information about the rev 1.5 version?
The Gigabyte site clearly says that the motherboard supports the CPU - but does it really? we have a Phenom II x6 - even though the actual motherboard box only says x4............. is this the actual problem?
http://www.gigabyte.com/products/product-page.aspx?pid=3621#ov
we can get it up and running, but its only a matter of time before it BSOD or when its powered down and then can no longer start or has a problem when it starts again.
A new motherboard, a new CPU, a new power supply, new ram and a new graphics card. Not exactly cheap like I said, and none of it seems to be working together.
I just wanna take it all back to bloody Scan. If I take all the parts back tomorrow what do I say, "It just doesnt work?!" I want replacements. Is it worth me even trying to take it back, and will they allow it? Now he's looking at taking it back and getting something which actually says it supports x6
( http://event.asus.com/mb/2010/m4_6cores/ ) If we get a new board, what if that doesnt fix it.
I've read and re-read sooooooo much information about this I actually get a headache trying to find information atleast which is even similar to what the problems are with this. It seems we have tried everything. and no we're going round in circles, because nothing seems to be solving the problem.
What do you suggest I do from this point on?
Dark Mantis, youve been great helping me from the start, what do you think? If i take the parts back, and say they're faulty do I get the same or something different? Or do I just not bother? and spend another almost £300 on another lot - what do I do with what I've got then?
-
Well I do understand your predicament and can imagine how you must be feeling at the moment.
There is no compatibility issue between the motherboard and your processor for sure.
You have two choices really. You can take the components back to Scan and they will probably want to check them before replacing any faulty parts but I don't know how long that will take them. The obvious benefit is that they might find a problem.
The other option as I see it is to start at the beginning and follow my instructions to the letter. This is important because I am not there to see what is happening and so need to know that what I say is being followed exactly.
You must consider your options and then post back.
-
Hi there,
when faced with this particular kind of problem DM is quite correct. The best thing to do is step back and start over again until you can find exactly what is causing the system to be unstable.
You still haven't posted a complete list of your hardware, despite being asked to and it really would help, as there may be something else that is causing these issues other than the obvious things like RAM.
-
Gigabyte MA-770T-UD3 Motherboard, Revision 1.5
AMD Phenom II X6 1075T CPU with stock cooler (retail)
8GB (2x4GB Corsair XMS3 DDR3 sticks in DDR3 slots 0-1)
ATI Radeon HD 5770 1GB video card (PCI-E)
Antec Earthwatts 650Watt PSU
1 500 GB SATA Seagate HD (Windows Boot Drive)
1 650 GB SATA Western Digital HD
1 250 GB IDE Seagate HD (About to be replaced once backed up)
1 Sony SATA DVD-RW
Antec P180 case with back fan and top fan running for extra cooling
Sound and LAN are onboard the Gigabyte motherboard (RealTek)
I've disconnected all drives apart from the 500GB SATA Seagate and the 250GB IDE Seagate and switched the SATA cable. Prior to doing this the bootmgr would suddenly go missing from the Windows drive when powered down and back up again. Since disconnecting the 650GB WD HD it hasn't repeated this process and has been fully shut down and powered up 3-4 times without a problem.
Also since removing the SATA cable that wasn't actually connected to a drive and was merely there for later convenience I haven't had the blue screen of death at all. For instance right now it has been running for over 5 hours with no problems.
I don't see how the WD HD would be corrupting the bootmgr though? Any advice on how to solve that would be good.
Thanks guys ( boyfriend of smallfry ;) lol)
-
Hi there,
well the only thing that jumps out at me about your specs is the IDE HDD as sometimes running IDE and SATA drives at the same time can cause a problem. I would suggest backing up the IDE drive as soon as possible and removing it from the system.
The problem with the missing BOOT MGR is most probably due to your reconfiguring the system HDD's when you have been playing with the SATA cables rather than the WD drive but, as a matter of interest what model is the WD 650 GB Hard drive? I'm not aware of any specific problems but it could be that the drive needs a firmware update.
If you are confident that the RAM Modules are fine then you could try them in slots 3&4 rather than 1&2 and see if that makes a difference. It shouldn't really but we are talking about a computer here.
-
Hi again,
The only time I've modified the SATA setup is when I took that one spare (not attached to a HD or DVD drive etc) out of the board, which for some bizarre reason has stopped the BSOD not less or equal error entirely. When it was shut down and powered back up again, nothing had changed hardware wise but the bootmgr had gone missing on the main drive. Windows Recovery (Windows 7) allowed me to fix that and it was all fine again until the next complete shut down and power up.
As I say, with the 650GB WD hard drive unattached the problem hasn't resurfaced and it has been shut down quite a few times since. I severely doubt there's a fault with the WD drive as it's only 2 years (at best) old while the Seagate IDE drive is at least 5 years old. I have every intention of backing up the data on that drive and moving to a complete SATA setup in the v.near future as the vibrations from the IDE drive are too annoying, lol.
PS : The Western Digital drive is a Caviar Blue.
-
Hi again,
if you installed the OS with several hard drives installed you can find that the BOOT MGR is actually put on a different drive to the one you would expect it to go on ie the C:/ drive. It is always best to Install the OS with only one Hard drive installed as this will prevent anything being written where it shouldn't be, especially if you are installing Windows.
The fact that the BSOD's have stopped since removing this drive could point to it being faulty or to a problem with the original install of Windows Vista. Although your WD 650GB HDD is only 2 years old doesn't mean it can't be playing up. Have you tried running the WD Lifeguard Diagnostic software ( you can download from here: http://support.wdc.com/product/download.asp?groupid=606&lang=en ) to check that your HDD is OK?
-
The BSOD stopped appearing after disconnecting a cable that was attached to the motherboard but NOT attached to any drives. On removing that SATA cable the blue screen completely stopped occuring and the only problem has been this with the bootmgr. At no stage did removing a connected hard drive stop the BSOD from occuring.
Last night I disconnected all drives, used the Windows Recovery system to recreate the bootmgr and booted into Windows. I then plugged the hard drives back in and so far it has booted up fine without corrupting the Bootmgr after several shut down Windows and power cycles of the machine. For some reason the problems seem to have utterly vanished. ???
I'll try the WD software just to be double sure about that drive though.
PS: This is a Windows 7 install, though fundamentally similar to Windows Vista I need to mention that just so everyone is on the same page.
-
just change the ram mate thats your best bet