To be honest iv not, cant see any potential benefit in doing it (but may very well be mistaken of course). Given id have to completely reassemble now, do you think itl be worth the effort?
PLEASE HELP!!! - installed new RAM, now comp wont boot with old or new???
- Thread starter aeb
- Start date
To be honest iv not, cant see any potential benefit in doing it (but may very well be mistaken of course). Given id have to completely reassemble now, do you think itl be worth the effort?
What do you guys think of
http://www.overclockers.co.uk/showproduct.php?prodid=MY-053-GS
its not on the QVL, do you think il have any luck Savvy (and others)?
http://www.overclockers.co.uk/showproduct.php?prodid=MY-053-GS
its not on the QVL, do you think il have any luck Savvy (and others)?
Associate
- Joined
- 3 Mar 2009
- Posts
- 120
- Location
- UK
just wondering if any of the motherboard contacts may be touching the case & shorting out. if youve reassembled eveything including the motherboard then maybe its not necessary
Cheers, u know what il actually give it a try, better than RMA'ing it and getting a charge i guess
EDIT: Would it be ok just to place it carefully on a desk....what precautions need to be taken when running outta the case?
Soldato
- Joined
- 10 Jun 2010
- Posts
- 5,158
- Location
- Scotland
I was going to suggest this a while back, but to be honest it's quite clear the RAM is at fault, indicated by the red light (correct me if I'm wrong)
If it wasn't booting for any other reason, then test it out the case.
If you really want to go ahead and try it. Just lay it ontop of the motherboard box. You will have to short the pins to power the system on, or just keep the case close enough. Maybe it will reach.
I really don't understand what the other guy was on about with corsair and geil not being compatible. They are
I was going to suggest this a while back, but to be honest it's quite clear the RAM is at fault, indicated by the red light (correct me if I'm wrong)
If it wasn't booting for any other reason, then test it out the case.
If you really want to go ahead and try it. Just lay it ontop of the motherboard box. You will have to short the pins to power the system on, or just keep the case close enough. Maybe it will reach.
I really don't understand what the other guy was on about with corsair and geil not being compatible. They are
Thank you Buchanan, u r vry trusted - lol but now im left really confused. To RMA the mobo or not the main question seems to be? There scheduled to pick it up tommorow, so id need to know tonight whether or not to cancel the return???
It is the RAM:
-Neither are on the QVL
-Savvy did say the mobo we are using is pretty picky
- mobo light & Beep code is for 'incompatible ram'
- Problem did start after inserting new RAM
On the other hand:
- Tech at ocuk said the Geil ram should be compatible
- mobo red light is also for 'no ram detected'
- the dominator ram worked fine for almost a week before the problems started.
So basically.....im confused
-Neither are on the QVL
-Savvy did say the mobo we are using is pretty picky
- mobo light & Beep code is for 'incompatible ram'
- Problem did start after inserting new RAM
On the other hand:
- Tech at ocuk said the Geil ram should be compatible
- mobo red light is also for 'no ram detected'
- the dominator ram worked fine for almost a week before the problems started.
So basically.....im confused
Soldato
- Joined
- 10 Jun 2010
- Posts
- 5,158
- Location
- Scotland
It is the RAM:
-Neither are on the QVL
-Savvy did say the mobo we are using is pretty picky
- mobo light & Beep code is for 'incompatible ram'
- Problem did start after inserting new RAM
On the other hand:
- Tech at ocuk said the Geil ram should be compatible
- mobo red light is also for 'no ram detected'
- the dominator ram worked fine for almost a week before the problems started.
So basically.....im confused
All of this is true. The Geil ram is definitely supported, so should the Corsair be. If it wasn't supported it definitely wouldn't have run for a week, that just doesn't happen. It's like putting petrol in a diesel car, it doesn't work for a week then decide to stop, it's pretty much instant.
Clutching at straws, I just can't get my head round why two sets of ram wont work. Take the cmos battery out and leave it at least until midnight, be sure to disconnect the atx power also. Just to be sure the cmos is definitely clearing.
Take a look at this section from the manual if you haven't already. It says to leave the jumper on for 5-10 seconds before moving back. Also read the part in the "Note" section. I don't know if that applies or not?
I must admit. If it was me, I wouldn't RMA the board just yet, of that's entirely your choice.
Buchanon confirm whether you run this board or other Asus board, from testing this board find 1333 runs best. QVL paints the memory not compatible this board is well proven for being picky.
List your entire spec, it may be related to set up
List your entire spec, it may be related to set up
Soldato
- Joined
- 10 Jun 2010
- Posts
- 5,158
- Location
- Scotland
It isn't
Hi all - Just an update
-Iv done a complete out of case barebones run
- Left it overnight without the battery and switched the jumpers on the mobo as per the manual to reset cmos
- Actually managed to get hold of some other RAM (not on QVL list but running at 1333 which iv been told has a better chance of working)
No Joy on any of them - so have a pick up for an RMA scheduled for tommorow.
Upon a magnifying glass analysis of the bottom of the mobo i find that there is an area under the RAM that has a slight damage/irregularity on it. It is literally tiny and might even be in my head but given iv tried absolutely everything i can think of im guessing its the problem.....im just hoping that if that is the case they dont try and pin it on me when i KNOW iv taken every possible precaution....we shall see i guess
Thanks a great deal for everyones help, il keep the thread updated if theres any updates or if its fixed - hopefully may be of use to someone else in the future.
-Iv done a complete out of case barebones run
- Left it overnight without the battery and switched the jumpers on the mobo as per the manual to reset cmos
- Actually managed to get hold of some other RAM (not on QVL list but running at 1333 which iv been told has a better chance of working)
No Joy on any of them - so have a pick up for an RMA scheduled for tommorow.
Upon a magnifying glass analysis of the bottom of the mobo i find that there is an area under the RAM that has a slight damage/irregularity on it. It is literally tiny and might even be in my head but given iv tried absolutely everything i can think of im guessing its the problem.....im just hoping that if that is the case they dont try and pin it on me when i KNOW iv taken every possible precaution....we shall see i guess
Thanks a great deal for everyones help, il keep the thread updated if theres any updates or if its fixed - hopefully may be of use to someone else in the future.
Associate
- Joined
- 8 Feb 2011
- Posts
- 5
Does anyone know if there was a resolution to this? I have near enough exactly the same problem - asus m4a89gtdpro, phenom x6, 2 x Cmx4gx3m2a1600c9 (on the qvl). Worked fine for a month or two, then lots of bsods. System only worked with one stick in (either of the two, but not both!). RMA'd one of the modules but same problems - no post, no display, no beeps with both sticks. I can see now from Internet searches that this is not uncommon... However, updated Bios to latest last night, rebooted ok and thought I'd give the two sticks a whirl - bad idea! Got the 'no memory' beep code. Went back to one stick that was working and... 'no memory' beep code! Aaaargh! Tried everything suggested but no joy.