Oh and except for the screen blanking out during the ATI install, it has been stable so far. AlienFX lost it's theme somehow and I had to reconfigure but otherwise ok.
So I got this "your order has shipped" email today, while yesterday I got the email "we regret your order has been delayed ... with estimated ship date Jan 22". I ordered the PC at New Year's Eve and the initial ship date was supposed to be Jan 12. By checking the order status page, it is still "in production - Your order has been received and entered into Dell's Order Management System."
I just hope this latest email is true to its words!
My order includes HD 4870X2 graphics card. Is it recommended that I uninstall the driver after updating windows vista to its most recent service pack? Is my system going to be more unstable if I install the most recent ATI catalyst driver without uninstalling the OEM driver first?
Can someone please provide me with the general instruction to safely uninstall/reinstall the vid card driver? And should I go with the "omega" driver rather than the official driver?
Thank you all in advance.
I have confirmed that if you hold the reset button on the rear of the computer, then press and hold the start button on the front of the computer (make sure you are stilling pushing the reset), then release the reset button first while still pushing the power button, then release the power button, the computer will turn on, off, reset itself and turn on again and will normally boot to the OS. Dell Tech Support has to figure out why this combination works. Is it bypassing circuits, adding additional voltage, I don't know. However, this is a clue that brings me back to a CMOS/BIOS, Motherboard, Power Supply problem and not the programs running on the OS. The reason why are the programs never start, it will not even boot to the POST, which is the first thing after start up that the computer has to do prior to transferring the booting command to the OS, which then will load the OS and the programs. Still haven't received the second computer yet. I will keep the forum posted of what occurs, and I will be pricing out my Falcon Mach V.
So far, mine has been stable. I think my TrendMicro is causing an issue or Dell Remote Acces, Windows kept throwing errors about advanced networking which was resolved after uninstalling DRA. Also, updated X-fi software using the Creative update utility. **After installing the latest ATI drivers, upon restarting I got an information box about Crossfire and it was enabled automatically. So far I've played Red Alert 3 for a few hours with no issue and beautiful graphics! I would expect a bios update soon to resolve some of these erratic issues. I'm thinking the rebooting problem may have something to do with the power supply. We use Dell at work and I've had to replace 8 motherboards over the past year, so I'm thinking they're having some issues with quality control. Considering they test these machines, I would imagine it involves some sort of burn-in and you'd think they'd catch this right away. Those of you having issues, I would start would replacing the power supply - have Dell ship you a replacement overnight. On that note, if this has been a repeat problem I'd expect a Dell gift card or something of that nature at the minimum. We spend a lot of money on these brand name systems for high performance when we could be spending our money custom building one elsewhere. Chris - Is there an XPS support group we can call for support who are tracking these issues? Let's make some progress here, and some happy customers!
I don't know if this is where im suppose to post this but i have the xps 730x and it just gave me a problem...
i need help on how to solve this problem, its a "BOSD" blue screen of death or whatever they call it
and here is what it showed me after i debugg the minidump file
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffffa60017d8180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
fffffa60`14dea3a8 fffff800`020b3321 : 00000000`00000101 00000000`00000019 00000000`00000000 fffffa60`017d8180 : nt!KeBugCheckEx
fffffa60`14dea3b0 fffff800`0205de7a : fffff800`025543c0 fffffa60`14dea4d0 fffffa60`14dea520 fffff800`025543c0 : nt! ?? ::FNODOBFM::`string'+0x34b4
fffffa60`14dea3f0 fffff800`02531d74 : 00000000`00000000 00000022`0bc328ad 00000000`00000000 00000022`0bc36096 : nt!KeUpdateSystemTime+0xea
fffffa60`14dea420 fffff800`02065aed : 00000000`1cc797b6 fffffa60`14dea648 fffffa80`066c01a0 fffff980`23b72058 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`14dea450 fffff800`02071b41 : fffff980`090401f8 fffff980`09040260 fffff980`090402c8 fffff980`09040338 : nt!KiInterruptDispatchNoLock+0x14d
fffffa60`14dea5e0 fffffa60`007d264b : fffffa80`0ed544f0 fffff980`09040500 fffff980`09040580 fffff980`090405f0 : nt!KxWaitForLockOwnerShip+0x31
fffffa60`14dea610 fffff800`0252b4ef : 00000000`00000000 fffffa80`0ed54590 00000000`00001000 00000000`00000000 : ataport!IdeStartIoCallBack+0xb3
fffffa60`14dea730 fffffa60`009ba0d3 : fffffa80`0ed544f0 fffffa60`009ba12c fffffa60`01843180 fffffa60`018b5180 : hal!HalBuildScatterGatherList+0x203
fffffa60`14dea7a0 fffffa60`007d2566 : fffffa80`0ed544f0 fffffa80`0ed544f0 fffffa80`066c01a0 00000000`00000000 : PCIIDEX!BmSetup+0x6b
fffffa60`14dea800 fffffa60`007d1788 : 00000000`00000001 fffff800`02139736 00000000`00000000 fffffa80`0658f980 : ataport!IdeDispatchChannelRequest+0x106
fffffa60`14dea830 fffffa60`007d1680 : 00000000`00000001 00000000`00000002 fffffa80`0658f6e0 fffffa80`0ed544f0 : ataport!IdeStartChannelRequest+0xd8
fffffa60`14dea880 fffffa60`007d2434 : fffffa80`06e00bd0 00000000`00000103 fffffa80`06eb6610 fffffa60`00900fa2 : ataport!IdeStartDeviceRequest+0x234
fffffa60`14dea8f0 fffffa60`007ced85 : fffffa80`06e00bd0 fffffa80`0ed544f0 fffffa80`0658b520 fffffa80`06e00bd0 : ataport!IdePortPdoDispatch+0xac
fffffa60`14dea920 fffffa60`008faffc : fffffa80`06e00bd0 fffffa80`06e00bd0 fffffa80`06e00bd0 fffff880`105d30a8 : ataport!IdePortDispatch+0x25
fffffa60`14dea950 fffffa60`00903155 : fffffa60`00924b60 fffffa60`010cdd9b fffffa80`00010000 fffff880`08395010 : acpi!ACPIDispatchForwardIrp+0x38
fffffa60`14dea980 fffffa60`008fb297 : fffffa60`00924b60 fffffa80`05907010 fffff880`08395100 fffffa60`00dc509c : acpi!ACPIIrpDispatchDeviceControl+0x75
fffffa60`14dea9b0 fffffa60`00dc4b40 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : acpi!ACPIDispatchIrp+0x12b
fffffa60`14deaa30 fffffa60`00dc4d6e : fffffa80`00000000 fffffa80`0658b520 00000000`00020000 fffffa60`00000000 : CLASSPNP!ServiceTransferRequest+0x350
fffffa60`14deaad0 fffffa60`0098a0b4 : fffffa80`07d70010 fffffa80`082e0190 fffffa80`07d70290 fffffa80`08cc2680 : CLASSPNP!ClassReadWrite+0xce
fffffa60`14deab20 fffffa60`011d85a5 : fffffa80`082dc810 fffffa80`07d70010 00000000`00000000 fffffa60`00fb1520 : partmgr!PmReadWrite+0x84
fffffa60`14deab50 fffffa80`082dc810 : fffffa80`07d70010 00000000`00000000 fffffa60`00fb1520 fffffa80`082dc6c0 : SiRemFil+0x15a5
fffffa60`14deab58 fffffa80`07d70010 : 00000000`00000000 fffffa60`00fb1520 fffffa80`082dc6c0 fffffa60`0099f18b : 0xfffffa80`082dc810
fffffa60`14deab60 00000000`00000000 : fffffa60`00fb1520 fffffa80`082dc6c0 fffffa60`0099f18b fffffa80`082dc810 : 0xfffffa80`07d70010
fffffa60`14deab68 fffffa60`00fb1520 : fffffa80`082dc6c0 fffffa60`0099f18b fffffa80`082dc810 fffffa80`07d70010 : 0x0
fffffa60`14deab70 fffffa60`00faa22e : 00000000`00000000 fffffa80`07d70010 00000000`00000000 fffffa80`07d70010 : ecache!EcDeviceIoCallLowerDriver+0x12c
fffffa60`14deabb0 fffffa60`0118f70a : fffffa80`07d70000 fffffa80`083731b0 00000000`00000000 00000000`00000000 : ecache!EcDispatchReadWrite+0x8a6
fffffa60`14deace0 fffffa60`01020616 : 00000000`00000002 fffffa80`0c6a0b00 fffffa80`06c43800 fffffa80`0c6a0b01 : volsnap! ?? ::FNODOBFM::`string'+0xf9e
fffffa60`14dead30 fffff800`0205e637 : fffffa60`12fc3370 00000000`01ec6fd8 00000000`77722f00 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x16
fffffa60`14dead60 fffff800`0205e5ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffffa60`0c96b3f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
Is there a way to not get this stopped error?
Can one purchase the base model with the 2.66 i7 and then overclock it in ROM to maybe 3.2?
Also is there is an upgrade program the we should be entitled to the extreme Core i7 for free considering the QX9770 (£1000) is worth more then the extreme version of the Core i7 (£850)?
What I do not understand is that the Dell Canada site will let you configure a XPS 730X with the H2C (for $500 Canadian) as an option with any configuration, yet the US site only allows the configuraton on the most expensive Core i7. Why would they have a better configuration options?
* No idea. Those are two different marketing teams.
What sound card does it actually come with? I see XFI Titanium in my email receipt, I see XFI extremegamer on my online receipt. It of course said XFI Titanium as I was making the order. Which is it
* It should be the F333J PCIe Sound Blaster X-Fi Titanium Fatal1ty Pro. I dded the X-Fi because I had it laying around.
What power supply brand and model is it that it comes with?
* U662D HiPro
* UR006 Delta
That brings up a question I have. Do they do any type of testing prior to shipping to make sure it works? I mean in my opinion for gaming machines like these I would imagine they would do somet type of testing. Run a game, run applications. let it run for at least 24 hours type thing. I am not sure Dell does this but I know a lot of niche computer companies do a gammut of testing to their enthusiast boxes.
* Yes. I am on that beta team. I get to test many games on the XPS desktops before they go on sale. Right now I have the XPS 730x, XPS 730, and XPS 630 at the house.
One would hope that Dell does some testing, but you'll never hear an answer from any Dell personnel monitoring this forum. It appears they are absent or have no time to bother with us.
* No, I am here. I have to monitor all of the Desktop boards.
I think what I said was misunderstood, I know he cant answer the order questions BUT he can answer the tech questions like:
Do they run tests on every machine to make sure its going to work out of the box?
* The factory runs a whole assortment of burn in testing.
How is it overclocked? The factory level 1. Is it overclocked via the QPI or multipler on the core i7 965?
CPU Configuration Screen
XD Bit Capability = Enabled
SpeedStep = Enabled
C-STATE Tech = Enabled
C State package Limit = C6
Frequency/Voltage Control Screen
QPI Frequency = Auto
Memory Ratio = Auto
XMP Support = Disabled
H2C 3.72GHz CPU Core (Non-turbo) Ratio = 28
Air 3.45GHz CPU Core (Non-turbo) Ratio = 24
Overclock Configuration Screen
Adjust CPUBC1k (MHz) = 133
Spread Spectrum = Enabled
Adjust PCI Frequency (MHz) = Auto
Adjust PCI-E Frequency (MHz) = 100
Intel TurboMode Tech = Enabled
H2C 3.72GHz 1 - 4 core turbo speed limit = 28 (28x133=3.72Ghz)
H2C 3.72GHz Tdc = 180
H2C 3.72GHz Tdp = 200
Air 3.45GHz 1 - 4 core turbo speed limit = 26 (26x133=3.45GHz)
Air 3.45GHz Tdc = 160
Air 3.45GHz Tdp = 180
Overvoltage Configuration Screen
H2C 3.72GHz Dynamic CPU Vcore Offset = +120mv
Air 3.45GHz Dynamic CPU Vcore Offset = +80mv
DDR3 Memory Voltage = Auto
I0H Voltage = 1.10V
QPI and Uncore Voltage = Default
Noise is absolutely no factor, except at boot/reboot time when it ramps up like a hair dryer for about 10 seconds max. After that, it's as quiet as can be. Haven't been able to find a way to stop it yet.
* That is normal.