End of interactive (?!) support for DX38BT, says Intel on their page.
Oh well, guess it was about time. Haven't checked for DX48BT2 though, think not though since it's not discontinued yet I believe.
Printable View
End of interactive (?!) support for DX38BT, says Intel on their page.
Oh well, guess it was about time. Haven't checked for DX48BT2 though, think not though since it's not discontinued yet I believe.
Hello Manel.
End of interactive support for DX38BT and don't much time for DX48BT2 to be discontinued without IDT drivers to come out for Windows 7.
Unbelievable...
Hey guys,
Long time no posts (from me). :p:
I'm having some weird problems with my DX48BT2. I'm having some random reboots and I haven't figured out what it's causing it.
The crashes usually starts after power failures (which is every two days, for two hours).
While using the computer, the computer hangs up and I have to hard reset it or it just simply reboots it self (no BSOD or anything like it).
The PSU and Video Card are fine, I already tried with my friend's and keeps crashing the same (another HD4870 and the PSU was a 850w)
I haven't try with another memories 'cuz I don't have any DDR3 around that I could borrow but memtest keeps saying there's no error.
The system it's not overheating (which usually causes random reboots most of the time), CPU/RAM/PSU/VIDEO/CHIPSET temperatures are fine.
I have checked almost everything that could cause random reboots and nothing shows up.
This happened with Windows XP and now on Windows 7. All drivers are up2date.
The only error I have found so far is in Windows 7 Event Viewer, which shows critical errors indicating "Event 41 Kernel-Power", couldn't find anything useful @ Google about that error.
What's *strange* is that, the only way to "stop" this random reboots is resetting the BIOS and setting it again BUT the errors come back once there's another power failure so... (oh, It happens with all BIOS versions too, atm running latest BIOS), yes... That's why I think it could possibly be a motherboard error but that's how far I go, I can't think anymore what it could be, I'm just thinking on dropping this motherboard and buying a new one. >_<;
If you guys have any suggestion to troubleshoot this (or just a hammer), it will be appreciated.
Thanks in advance.
Q___Q;
Good to see other people still posting, maybe X38 is only dead for Intel.
BT, guess you're right, don't have much hope for new drivers or BIOS anymore.
tam, welcome back. I had the idea that this behaviour had been fixed in the past, guess not. I don't think I had this issue, not latelly at least. Power here doesn't go out that much, although not the cleanest. Still, last weekend there was some electric work being done and we lost power quite a few times, and for a long time. Still, the rig is running fine. I have problems with my Platinums though, errors come up while testing, guess it's RMA time.
Are you Ocing? Have you tried setting BIOS at defaults and see if it happens the same? Maybe also relaxing mem timings.
Mayve voltage usually is too low and the system (PSU) must shut down, if it's out of spec. Try reading voltage input with a multimeter, see if it's within the power company specification (plus minus limits of course). Maybe voltage is just to low to power your system.
System has been OCd since day one.Quote:
Originally Posted by Manel
I tried default BIOS settings and system restarts cuz of memory timings.
The memories are working at 1.9v, its the sweet spot for memtest errors and its OCZ recommended value, as for timings, its OCZ default timings, 7-6-6-24.
This problem started around 5 months ago, it used to work without problems, dunno what happened that is causing this.
Just my 2cents but what vid card (your friend's) did you try also? Was it an HD4xxx as well? Did you try an nVidia card? Maybe it's another of those AMD (I'm not an AMD hater nor an nVidia fanboy) cards issue. I believe there was such an issue a while back, solved with a BIOS update though.
Also, was it not after installing Windows 7 or something? Sorry, you said it happened with XP also.
Try removing for a while or changing the CMOS battery. I know this is just silly but maybe you just need to completelly drain power for a complete parameter reset. Can't think of anything else atm. Maybe using the internal jumper will help too.
Still have my DX48BT2 going strong.
Haven't been to the thread for a while, thought I'd check back in.
Tam,
Do you have drives in RAID? I know that with the newest intel rapid storage manager (or whatever it is called) version that i was having trouble with random reboots and pinned it down to the windows power option to turn off hard drives after xx time causing SMART errors and system reboots/crashes. If you are saying that the failures are happening just about every 2 hours, check to see how long windows waits to spin down your hard drives.
For me, having windows never turn off the drives fixed the problem.
On the other hand, overclocking does cause progressive component degredation, and after some time of running your system OC'd it is possible that the CPU, FSB, MCH and possibly the RAM may require a voltage increase to remain stable.
If you dont have drives in RAID, are not using the latest intel rapid storage technology, or telling windows to not spin down drives does not fix the problem, try either lowing your OC a little while keeping the voltages the same, or bump the voltages a little.
The voltage setting with the largest impact on overall system stability is the vFSB, so start there. if that doesnt work, bump the vMCH. increase the vCore next if the problem still exists. if that doesnt fix it, try the ram voltage.
Sean
Man, this is getting boring, nothing new from Intel for so long now...
It's sad but true Manel.Quote:
Originally Posted by Manel
Nothing news...
I should buy a new Sound Card :mad:
Yes BT, sad indeed. I can't imagine why Intel won't post newer audio drivers. IDT must have them for sure. Intel did stop using these codecs after our board, Realtek for the DX58SO I believe. Still, this is no reason to stop providing drivers for "older" boards.
Tam, did you solve your mem problem? I know that those Plats are rated 1.9V but you should try 1.8V instead. Tony once did a review of those and 1.9V wouldn't work for him too (with an Asus P5K3 though) and 1.8V worked like a charm. Try and play with mem voltage and see the sweet spot, these are speedy modules but sometimes picky.
Audio sucks for me too. Guess I'll have to re-install the drivers, always get question marks in the jacks in the rear panel in audio control panel, and the sound is lousy.
Also, Dolby never got an update.
Come on Intel, at least post some updated drivers. There must be newer ones for sure, with Win7 support at least.
INF 9.1.2.1007
Finally something new...
Sh*t, Intel released Dolby Control Center 2.2.3 and Realtek audio drivers for DX58 SO SmackOver, how about us? Are we dead yet?
I wonder if Dolby will work with our board? Or maybe it's specific for the Realtek codec. It's released for Vista and 7 (32 and 64bit).
Hello again manel.
After spending a long time, Intel releases new Chipset drivers' version, but IDT Audio drivers for Intel are absent.
I have a Notebook Hp with IDT Audio integrated solutions, and HP released these drivers, with DOLBY DIGITAL from a long time.
It is simply ridiculous.
I already have surrendered. I have ordered a Creative X-Fi Sound Card, to play games and listen music with Dolby Digital Live and DTS Connect.
Hi BT
Yes, I remember HP notebooks having IDT audio, and for a long time I saw them already with this new GUI (v2.0 I believe) while we still had the horrible looking older one for months. Only after a very long time they released drivers v20001 and that was it for us, no more drivers to date. I don't really believe these are not available, only Intel will not provide them. But why? At least DX48BT2 (and DX38BT being similar uses the same drivers, fortunatelly) hasn't reached EOL yet so support and updated drivers should still be provided. But I guess Intel can do as they please.
They also used to be regular updating LAN drivers and now it's been ages since v15.1.
Some newer drivers might not even bring changes to our boards (specifically) but at least you feel that they're working on their products, providing new features or enhancing/fixing existing ones.
Oh well, Intel will be Intel...
Just to re-inforce the driver (or lack of) update issue, there's a LAN 15.2 available already, just not in our dl page, yet. Released 29.04.20010, not exactly yesterday.
If they don't make their own drivers immediatelly available to us, how would they do it for third-party drivers, like IDT for audio?!
Intel is a giant, they can do as they please, for now...
DX58SO has had BIOS updates every month now, X58 is hi again. I don't expect this for our "old" board of course, waste of resources for an old product. But at least tweak a little, only a few things. We could start enumerating the changes we would like to see and maybe, just maybe, they'll listen.
RAID option ROM should be updated to the latest version. Also, one thing I believe should have been addressed already, mem voltage granularity, 0.4V is too much, we need 0.1V.
Come on guys, give your input.
Man, they heard me, again!! I'm starting to get suspicious... not really.
LAN drivers v15.3 out, just yesterday I could only find v15.2 but hey. Released on May 14th though, as usual a couple of weeks already.
Come on Intel, at least give us updated audio drivers, for Win7 is the least you can do (and I'm not even running 7). Maybe they'll listen.
I guess a new BIOS is out of the question, and IDCC as well (even version 769 is still beta, I guess it never come out of beta anyway). 5 series boards have had several IDCC versions latelly.
I ran into an interesting overclocking experience.
I found I couldn't break 3Ghz easily, as I use 8GB of Corsair XMS3 1333Ghz memory rated for 1.6V. On their own forum, when suggesting the configurations that should work well for overclocking, they'd list the vmem as 1.7v. I noted that when running at 1066, the vmem was 1.54v. So I undervolted when overclocking and stability was acheived.
Very strange!
So I'm now at 3.6Ghz on my Q6600
vcore 1.4
vFSB 1.325
vMCH 1.4
vMem 1.58
Multi: 9x
FSB: 400
Reference: 400
Mem freq: 1333
tCL = 9
tRCD = 9
tRP = 9
tRASmin = 24
tRFC = 80
tRRD = 4
tWR = 10
tWTR = 5
tRTP = 5
Command Rate: 2T
Totally amazing to me that I'd been going the wrong direction in voltages. It would POST with higer vMEM settings and pass several passes on Memtest, but was not stable for more than 15 to 30 minutes in Windows 7 x64.
Undervolting compared to the listed voltage worked in this instance. Has anyone else found that undervolting their memory yielded better results?
In any case, it feels like a whole new computer.
Hey HT, I've seen in the past people saying that in fact, some mem modules (depends on the specific chips they're made of) in fact like lower voltages rather than higher.
Not sure it was with Corsair sticks, though, I believe the chips were either Micron or Elpida.
Anyway, that's great news, you get the best of both worlds, lower voltages and temps, as well as a higher and more stable overclock. Cool!!
Do you have your Corsairs running @1333? Can't you get better timmings than 9-9-9-24? I believe those are the rated timmings for 1600, right? Maybe you can get CAS 7 or CAS 8? Still, with 8GB and all slots populated Intel doesn't support 1600. Maybe you can try this and confirm if it works, I was kinda wanting to go 8GB myself.
Corsair has chip types for their revisions of memory on their support forum http://forum.corsair.com/forums/showthread.php?t=68811
My memory modules have 2.1 listed as the version, so according to the list they are Elpida.
Coolbeans!
I'll do some testing in between all the other family activities this memorial day weekend and let you know next week.
I am not too sure if this is the right place to mention this, but the X38 chipset has a bug with the PCI-E 2.0 controller which prevents correct functioning of nVidia GT2xx and GF1xx GPU's. If you use these GPU's on an X38 based motherboard they will only operate at PCI-1.1 with drivers newer than April 2009.
The long running saga I had with ASUS finally ended today when I e-mailed nVidia and got a reply in a matter of hours.
G92 GPU's do not have P-states. So in theory they should (and it has been confirmed) run @ PCI-E 2.0 all of the time.Quote:
Hi John,
I am sorry however there is nothing we can do in this case. The Intel x38 chipset was Intel's first generation PCI-E 2.0 implementation and unfortunately has some PCI-E 2.0 bugs, one that causes the graphics card to hang when changing P states. The only Intel PCI-E 2.0 chipset which shows these bugs is the Intel x38 chipset. If you see any other Intel chipset reporting PCI-E 1.0 speeds with our GPUs, please let me know. The best way to check is to run a 3D program in the background as this will change the P state of the graphics card from PCI-E 1.0 to PCI-E 2.0. This throttling is done to conserve power when the user is running basic Windows tasks
I do not know how to proceed with this issue,
Could I request an RMA for an X48 board?
Or just bite the bullet and upgrade when I really do not need to or even want to at the moment
John
John, if it's only X38 you're ok since you're on X48. Unless they mean X48 also, since it's not too different from X38.
Still, they didn't mention Fermi as having or not the same issue, do you know if it's there too? I guess since the P states should exist there also.
I'm on G92 that's why I'm ok, I was waiting on GF104 but now I'm not sure anymore. Does ATI have this issue also?
How come they took so long to give a straight answer? If it's not even their fault?!
John, did you ask Intel regarding this bug? I guess, if the X48 has this issue fixed, those of us with the DX38BT should be able to RMA our boards and get a DX48BT2 at least.
How come drivers before April 2009 don't show this issue? Maybe they forced the throttling down in the drivers that support GT200 and above.
Any word on Fermi having P states as well? I guess it should have, so no upgrade anytime soon.
Man, Intel is so sloppy at times. Even their drivers, is it just me or those LAN drivers still use the same old font as it has been using for years?! Intel, come on, are you guys sleeping? Give it a welcome facelift, it needs for some time now.
On an unrelated note, I was amazed at the prompt replacement of my RMA'ed OCZ mem sticks. Those guys at OCZ worked fast. My Plats were showing lots of errors so I sent them to their European office in the Netherlands, on monday of last week. They got there on tuesday and on wednesday they shipped a DC kit of 4GB instead of my 2GB kit (great guys, thanks a lot, you rock.). Only thing funny (or not), when I was tracking the package with FedEx it showed leaving from Taiwan (what?! I said, not Taiwan please). Anyway, next monday it arrived and it in fact came from Taiwan and it was made in Taiwan. Come on guys, what happened to made in the US? My original kit didn't state where it was made, but I assumed the US, although everything these days is made in China or Taiwan. Still, that kinda disappointed me. But thanks you guys still. It's now happily running on my rig finally.
Now I have to install the x64 version of either Vista or 7. I was delaying it since I hate to see the Program Files (x86) there along with the regular one. Just a detail but still... I believe even 7 doesn't feel like a true 64 bit OS with all these things still there making it look like a patched thing. Maybe the next OS?! OSX does not have this distinction, does it? How I hate legacy stuff, it makes everything go forward so slow.
I think I'll stick to Vista, I hate the new task bar in 7, although you can almost tweak it to look like Vista's. Too bad MS won't make Vista lighter and snappier like 7.
Wow, this thread has 2349 posts and 94 pages!!! I don't have time to go through every one of them so I apologize in advance if this question has already been answered... I picked up a used X48 board with the latest bios. I make vcore changes in the bios, but cpuz and everest does not show them. Also, the amount of overclock I can make leads me to believe it's still at stock voltages. Are all these boards defective or am I missing something?