View Full Version : P5E and Mushkin PC8500
Latest 702 bios, 2x2gb sticks of ram, which has passed hours of memtest. The site states the board supports 1066 and the option is in the bios, just that particular brand isn't listed.
It runs beautiful at 800mhz with 4-4-4-13, but even with timings at default 5-5-5-16, anything at all above 800mhz renders the board unbootable.
I thought I read somewhere it's supported as long as it's obtained through overclocking, but I don't want to overclock until I figure this out.
Any suggestions guys?
Thanks much in advance.
Try the 333 strap in bios. Also the Vdimm is off by .5v so if you want 2.1v set it to 2.04.
EDIT: try 9x400 3.6 / 400 strap and set the ram to 1066 5-5-5-15 |CPU @ 1.28 to 1.30 vcore | NB @ 1.4 | FSB @ Auto | SB @ Auto.
Try the 333 strap in bios. Also the Vdimm is off by .5v so if you want 2.1v set it to 2.04.
EDIT: try 9x400 3.6 / 400 strap and set the ram to 1066 5-5-5-15 |CPU @ 1.28 to 1.30 vcore | NB @ 1.4 | FSB @ Auto | SB @ Auto.
Awesome! Will do this after work today - Thanks mullet!
YVW, let us know how it goes dude. That should be a pretty solid 24/7 setup.
I'm at 365x9 right now and my vcore shows 1.32 in the bios HW monitor, 1.36 in cpuz, but I stilll have it in Auto. Is this normal? My P5K didn't raise vcore like that.
Even at 365x9 I can't get it stable. It has to be a vcore or vdimm issue.
365x9/DDR2 867 vdimm1.9/5-5-5-15
I tried with the vcore at the auto setting and lowered to 1.2.
I'll wait a bit, don't want to damage another one. :o
EDIT: Think I have it figured out. I was setting vcore way too low, even after you warned of the difference.
DiscipleDOC
05-28-08, 10:54 PM
Moved. ;)
Grey a lot of the time setting the CPU Vcore , NB and so on manually will put you in the ball park. Most of the time setting it to Auto will set it to high or to low. How far did you get?
Grey a lot of the time setting the CPU Vcore , NB and so on manually will put you in the ball park. Most of the time setting it to Auto will set it to high or to low. How far did you get?
I got to 375x9 fsb, 1.2 vcore (actual), 2.3 vdimm @ 10 something..don't remember exact, using your timings. I didn't touch the NB though, here's why..
I kind of panicked after several bsods and a couple no posts, reset everything to default and still got random bsods. I was thinking bad ram in spite of memtest and the fact it worked fine @ 250x12 on my P5K. But now I'm wondering if it's driver conflicts. I didn't reinstall Win after swapping boards, because according to [H] and..I think it was anand, the drivers Asus uses for both chipsets are identical.
I uninstalled all drivers/devices early this morning, registry editing and all, now I'm stable at default, using Orthos anyway. I think I may just break down and reinstall Win tonight to be sure...crapload of apps on there though :o .
EDIT: More bsod fun just surfing the web. Reinstall time. :(
Confirmed: This board does not like this Mushkin ram.
Time to order more.
This board likes G-skill and Corsair, I have run both. Vcore = cpu volts | Vdimm = ram volts.
This board likes G-skill and Corsair, I have run both. Vcore = cpu volts | Vdimm = ram volts.
Thanks again for all your help mullet. I've got 2 gigs of XMS2 6400 in there now and I have to lawlz at it. It's snappier with 2 gb of ram it likes than it was with 4gb of incompatible ram, even when it seemed to be doing good. :o :p
Cool, did you have 2x2 sticks ot 1x4 sticks of mushkainz.
Cool, did you have 2x2 sticks ot 1x4 sticks of mushkainz.
Yep, it's a pc 8500 line they discontinued a few months ago, 2.3 required. I wonder if this is why they discontinued it?
Right now I'm 2x1 sticks. I'm going to beat up on it for a couple of days just to make sure there isn't something else, then start overclocking again.
Just curious, is this the same as you have?
http://www.newegg.com/Product/Product.aspx?Item=N82E16820231166
EDIT: More frikken bsod with the XMS2 - My local mom and pop I got the mobo off of is telling me they are getting quite a few machines back that have Vista64 with SP1 that are blue screening. Uninstalling the SP fixes it. Rolling back now....
This is an adventure I didn't want.
Yes that is the exact ram I have. I am running Vista prem 64bit SP1 and I haven't had 1 BSOD. I would format the drive and download all the new Vista 64bit drivers as I did and do a clean install. I was running 500FSB with the old trusty E6600. I will help ya dude get this thing going I will post a full bios setup.
mullet - You da man :)
I did the format and reinstall and still got bsod with all the latest drivers, but Amuro pointed me to the win debugging tool in another thread and it pointed right to the ethernet driver. Even with the latest installed from the site I got bsods, so I'm trying the one listed in windows update now. I'm hoping like heck it's one of those "IF you experience a problem...." type fixes...
If I don't get anymore crashes by tomorrow I'll begin overclocking again.
Thanks again so much for your patience helping me out with this thing.
Appears solved at the moment. Vendor swapped out a new one for me.
I never bothered with Orthos because I couldn't get it stable without it, but I tried it this morning and it failed the ram within a minute several times, been running now about half an hour, stressing cpu with one instance, ram with the other.
Looking good so far.
EDIT: Calling it good, all night and no errors. :)
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.