Sign In
Create Account
I'm running the GB board mentioned with an i72600k processor, Kingston Hyper X SSD, and 2 x 4gb GSkills Ripjaw RAM. Everything has been running perfect until I added 8gb more RAM (same manufacturer). Now the board won't even beep and keeps rebooting. Also, when I take the ram out, everything works perfect. Any ideas on where to start?
Thanks!
0
ga-z68x-ud3h-b3 RAM issue - need help
Started by Drsoggy, Sep 10 2012 11:53 PM
Ram Wont boot Ga-z68x-ud3h-b3
4 replies to this topic
#2
Posted 11 September 2012 - 12:15 AM
Gringo Vermelho
-
- Supervisors
-
- 4,877 posts
The Jan Bird fix
- Gender:Male
- Location:Brazil
Are you using a patched DSDT?
Upgrading RAM, CPU or doing other things to your PC such as adding or removing an expansion card can affect the location of some reserved memory spaces that are set in your DSDT: http://www.projectos...?showtopic=2416 As you can see, even though DSDT is said to be "fixed function" some things do change.
You can get intro trouble this way because your old /Extra/DSDT.aml no longer matches reality.
The solution is to re-extract and re-patch your DSDT.
If you still have an unmodified copy of your old DSDT (the one you patched) you can use a diff tool (diffmerge is fine) to compare it to the new, unpatched DSDT. Differences between the two will be automatically highlighted.
This way you can easily track down what has changed and apply these changes to the patched version of your old DSDT, and you won't have to re-patch the new one all over again. Hopefully that made sense.
EDIT, never mind, I read your post again.
The first thing I would do in your situation is a CMOS reset. Leave the new RAM in. Unplug the PSU from the mains, remove the motherboard battery and close the CMOS reset jumper for at least 30 seconds. Look in your motherboard manual for details.
Upgrading RAM, CPU or doing other things to your PC such as adding or removing an expansion card can affect the location of some reserved memory spaces that are set in your DSDT: http://www.projectos...?showtopic=2416 As you can see, even though DSDT is said to be "fixed function" some things do change.
You can get intro trouble this way because your old /Extra/DSDT.aml no longer matches reality.
The solution is to re-extract and re-patch your DSDT.
If you still have an unmodified copy of your old DSDT (the one you patched) you can use a diff tool (diffmerge is fine) to compare it to the new, unpatched DSDT. Differences between the two will be automatically highlighted.
This way you can easily track down what has changed and apply these changes to the patched version of your old DSDT, and you won't have to re-patch the new one all over again. Hopefully that made sense.
EDIT, never mind, I read your post again.
The first thing I would do in your situation is a CMOS reset. Leave the new RAM in. Unplug the PSU from the mains, remove the motherboard battery and close the CMOS reset jumper for at least 30 seconds. Look in your motherboard manual for details.
#3
Posted 11 September 2012 - 12:32 AM
Drsoggy
-
- Members
-
- 3 posts
InsanelyMac Protégé
#4
Posted 11 September 2012 - 12:35 AM
Gringo Vermelho
-
- Supervisors
-
- 4,877 posts
The Jan Bird fix
- Gender:Male
- Location:Brazil
I hadn't read your post properly when I wrote that. If your PC can't even POST, your issue has nothing to do with /Extra/DSDT.aml. See my edit.
#5
Posted 11 September 2012 - 03:30 AM
Drsoggy
-
- Members
-
- 3 posts
InsanelyMac Protégé
Got it. I will try that first.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users