Precision M6400 Owner's Lounge

3dmark 2003 appears to be working fine.

 

I ran 3dmark 2003 and 3dmark vantage back to back with orthos running in the background and it went through fine, it appears only in 3dmark 2k5 and 2k6 I get this issue, I played some UT99 and UT3 last night for a couple of hours and everything seem to be fine.

 

I've read all the posts since the beginning... WOW! Lots of information.

The configuration that I have in mind is X9300 Quad Core, 4 GB Ram, Nvidia 3700m, 64 GB SLC SSD, Bluetooth, Wireless, RGB LED. It will not be hooked up to external monitors or use a docking station because I have my T7400 Desktop for that stuff.

For all the people that had problems, are they fixed now or did you just give up on it for a different one completely (non-M6400)?

I've seen that the fingerprint reader had some issues but there was no follow-up.

The configuration says that there is 370 Bluetooth but people are using drivers for 410 Bluetooth. Is that still the case and if so what is the difference between the two?

Is there a difference in stability with a 32-bit and 64-bit Windows XP / Vista / 7 Beta?

Thanks in advance

 

1) There's been not a really bad problem with the M6400 for now (compared to the battery drain problem of the HP 8730w), so even if your M6400 will have a probleme, Dell will take care of it.

2) The 410 bluetooth card is actually a 370 BT card + a additional WUSB chip. The 410 is not available in some countries... for the 370 you only need the 370 driver (the 410 driver actually will only install the included 370 part).

3) 64bit XP had some driver issues, but now it should run fine. Due to better Multi-Core-Support I prefer Vista 64bit or even Windows 7 RC.

 

3dmark06 works fine for me (3700M).
maybe a driver issue?

 

It could be, which driver are you using??

 

I have that as well...any chance you've a quad in that machine,
If you go back a few pages you'll see my posts having the same issue.
It could work perfect one night and go blank 20 mins into games another night.
Video card was changed as were drivers but still get issue.
I reckon it could be thermal related although the gpu temp is fine the cpu temp is up in the 50's idling.
If you leave it long enough it should reboot and saying you just had a BSOD..could take about 10 mins though for this to happen.

 

fyi, I just posted a dock station in the classifieds...

 

I must seem to some to be the local nitwit but I assure you I am a full fledged halfwit, meaning I know lots of stuff but it doesn't all fit just right yet. What is the big danger in installing Windows 7 on your second hard drive? The warnings sound cataclysmic if you don't install it on a 'spare' computer. Turns out I do have a spare but it has stuff I'd rather not lose. Doing the F12 at startup shows reading my e-sata much partitioned external drive but does that count as a spare? Am anxious to see if 7 is just Vista service pack 2 or what. I don't think turning a 2.5 gig OS into a 14.5 OS can possibly be an improvement. Less is more seems the path of the better software. But back to the question, how dangerous is it to install Windows 7 on a partition of my D drive? I'm real fond of the way I have XP set up and running in C and want to take no chances at all. I installed and removed Vista from D with a few hassles with getting it off the boot menu but no big problem. Aren't drives exclusive of each other unless instructed otherwise?

________________________________
Precision M6400, QX9300, 4GB, 64GB Samsung SSD & 320GB Seagate along with all the standard Covet stuff. (It's Orange but it doesn't say Covet anywhere I can see.)

 

I had them swap out the video card and then ran 3dmark 2006 in a 10 session loop and all is well for now.