Agreed. Very poor product support on Intel's part. The likely result of which - for me, at least - is the combined failure of Intel's board and Windows 7. Win7 simply crashes without warning every hour to three hours. Having looked at all other possibilities, I now believe this is rooted in Intel's poor support of the board. It's probably the on-board RAID controller, the P35 chipset, or the (lack of) MEI. Impossible to say at this point...
I'm thinking about buying an new board, but I would have to buy an old technique, namely the P45-Chipset (maybe an Asus P5Q Pro Turbo or something like that), because of my RAM an CPU. It's fast enough for me, and I don't want to buy a i5 or i7 + board + DDR3-RAM.
I'm also thinking about changing to AMD, because I'm so disappointed about the poor support of Intel.
Could it be, that your RAM or disks have problems? Such crashes sound to me like a hardware-problem. Have you checked the temperatures of ICH and MCH. My system crashed for a while, because those temperatures were very high and I had to optimize the airflow of the case. The coolers are not well placed.
Sure could be. It could be entirely coincidental that these crashes started soon after the upgrade to Win7. I've run the memory, hard disks, etc. through a broad series of tests. All seems to be well. I'm actually now wondering if this could be something as simple as a failing PSU.
There are three drivers for Win7x64:
No IDT-drivers, no tools, no Dolby Control Center, no Management Engine Driver.
The drivers above work with all boards with P35-chipset or ICH 9/10.
..and the available IDT audio drivers fail to install on the rc 64bit ?
What does that question mean? There are no Win7x64-IDT-drivers.
there are 64bit drivers for vista and xp. never tried them? that's the first thing i did
Maybe there are some drivers, but I bought a board and I bought support for that board.
And I bought it one year ago.
And if the Vista64-drivers work with Win7x64, why not call them Win7x64-drivers?
What? They are not tested under Win7x64?
Well, I'm not a tester, I'm a customer.
Maybe it's fun for you to work with some kind of patchwork, but not for me.
we are all customers, i believe
post the link to the page saying "dp35dp comes with full support for all future versions of MS Windows", if you find one...
use whatever works if you need it, or accept the alternative. it's that simple.
So you would say, if Intel stops support one month after they started selling it, it's OK?
It the same argument. One could buy another board, sure. And another and another and another.
They just cost 50 Cent and the production doesn't cost hundreds of MW/h and endless ressources...
they didn't stop the support for operating systems the listed "supported" at the time of release.
from the product guide page 10:
The Desktop Board supports the following operating systems:
• Microsoft Windows Vista* Ultimate
• Microsoft Windows Vista Enterprise
• Microsoft Windows Vista Business
• Microsoft Windows Vista Home Premium
• Microsoft Windows Vista Home Basic
• Microsoft Windows Vista Ultimate 64-bit edition
• Microsoft Windows Vista Enterprise 64-bit edition
• Microsoft Windows Vista Business 64-bit edition
• Microsoft Windows Vista Home Premium 64-bit edition
• Microsoft Windows Vista Home Basic 64-bit edition
• Microsoft Windows* XP Media Center Edition 2005
• Microsoft Windows XP Professional
• Microsoft Windows XP Professional x64 Edition
• Microsoft Windows XP Home
Thanks for your reply, suryanm. I did indeed install all Win7 drivers provided by Intel. Notably, Intel has yet to provide the MEI driver. The Vista driver seems to work - but really, Intel should be providing an updated driver here, rather than having customers go fishing around to troubleshoot an error in Device Manager. In my case, however, the issue has turned out to be one of hardware failure. We are not clear yet as to whether it is the processor or the motherboard - but it has been determined to be one of these two. Unfortunately, Intel's poor support of the dp35dp led me to believe I had a driver issue initially, wasting a nice chunk of my time, rather than proceeding straight to the hardware failure conclusion.