Dell XPS M1730 Owner's Lounge, Take 2

Vista 64-bit. Is it possible that the reason I get the symbol error message is that I interrupted the memory dump when I ctrl+alt+del'ed?

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`01e01000 PsLoadedModuleList = 0xfffff800`01fc5dd0
Debug session time: Tue Jun 23 18:31:48.753 2009 (GMT-5)
System Uptime: 0 days 0:28:40.444
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols

Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80001e6b940, 0, ffffffffffffffff}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis.sys -
*** ERROR: Module load completed but symbols could not be loaded for NETw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : NETw5v64.sys ( NETw5v64+96cd )

Followup: MachineOwner
---------

 

create a directory on your c:\ called Symbols
in WinDbg put the below in the File | Symbol File Path

Code:

SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols

 

one more thing dont forget to type

Code:

!analyze -v

to examine the dmp file

 

@Zath:

Its cool to try to pin down the cause yourself, but in my opinion - don't even bother. Call them up and tell them you are having issues again (explain what you are seeing). They need to resolve this... If they can't resolve it use the unresolved issues link I mentioned and reference your last case# along with history of the issue and cite # of times items have been replaced.

 

True, the worst they can do is say put the machine back to factory default (like they did with me, I knew my video card was bad but they still needed to see if it was something I loaded) and see if that fixes it. Then maybe a depot repair. I would still be curious to see if it was something else causing the issue. But who am I to tell anyone what to do.

 

did they replace the graphics cards with refurbished or new graphics cards?

 

refurbished. (I think)

http://www.dslreports.com/forum/r21931316-Other-BSOD-NETw5v64sys

That thread is from another dell owner who has the same problem. Apparently the file is the driver for our wireless cards. I was in the middle of typing up a post when - surprise! - another BSOD! I'll post up the dump soon. btw, it said "IRQ_IF_LESS_THAN_EQUAL" or something to that effect on the blue screen...

 

With me I am on my 3rd 8800M GTX card. 1st one I purchased, went out less than a year. Replaced it and less than a month the SLI on the new card went bad (Would BSOD booting after enabling SLI). Then replaced that one and so far so good. The parts looked new, but as long as they replace them for the next 3 years I am ok with it.

 

Tried clicking on the link to use !analyze -v and got this:


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`01e46000 PsLoadedModuleList = 0xfffff800`0200add0
Debug session time: Tue Jun 23 19:36:31.053 2009 (GMT-5)
System Uptime: 0 days 1:03:10.420
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80001e02318}

*** ERROR: Module load completed but symbols could not be loaded for NETw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for Mpfp.sys
Page 97fd3 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Probably caused by : NETw5v64.sys ( NETw5v64+96cd )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001e02318, address which referenced memory

Debugging Details:
------------------

Page 97fd3 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

READ_ADDRESS: 0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalpDmaNextContiguousPiece+118
fffff800`01e02318 458b02 mov r8d,dword ptr [r10]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: uTorrent.exe

TRAP_FRAME: fffffa600e894bf0 -- (.trap 0xfffffa600e894bf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80043d0320 rbx=0000000000000000 rcx=00000000000005a8
rdx=00000000000004b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001e02318 rsp=fffffa600e894d88 rbp=0000000000000000
r8=00000000000005a8 r9=000000000001e092 r10=0000000000000000
r11=fffffa8005f035a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
hal!HalpDmaNextContiguousPiece+0x118:
fffff800`01e02318 458b02 mov r8d,dword ptr [r10] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001ea01ee to fffff80001ea0450

STACK_TEXT:
fffffa60`0e894aa8 fffff800`01ea01ee : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0e894ab0 fffff800`01e9f0cb : 00000000`00000000 00000000`00000000 fffffa80`0455f830 fffffa80`09f65088 : nt!KiBugCheckDispatch+0x6e
fffffa60`0e894bf0 fffff800`01e02318 : fffffa80`09f2ef40 fffffa80`04e4ab50 fffff800`01e023b4 fffffa80`09f65088 : nt!KiPageFault+0x20b
fffffa60`0e894d88 fffff800`01e023b4 : fffffa80`09f65088 fffffa80`05f035a0 fffffa80`043d0880 fffffa80`09f2ef40 : hal!HalpDmaNextContiguousPiece+0x118
fffffa60`0e894da0 fffff800`01e05399 : fffffa80`09f65088 fffffa80`05f035a0 fffffa80`09f2ef40 fffffa80`0a2364d0 : hal!HalpDmaMapScatterTransfer+0x34
fffffa60`0e894df0 fffff800`01e05312 : fffffa80`09f65088 fffffa80`09f65080 00000000`000005a8 00000000`00000001 : hal!HalpMapTransfer+0x79
fffffa60`0e894e70 fffff800`01e0480f : 00000000`00000000 fffff800`01e01eaa 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffffa60`0e894eb0 fffff800`01e049bd : fffffa80`061f8050 fffffa80`05f035a0 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffffa60`0e894f50 fffff800`01e04ff6 : fffffa80`05f035a0 00000000`00000000 fffffa80`05f03500 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffffa60`0e894f80 fffff800`01e045df : fffffa80`046d7320 00000000`00000050 fffffa80`05f035a0 fffffa80`0bfc3c20 : hal!HalAllocateAdapterChannel+0x11a
fffffa60`0e894fc0 fffffa60`01002818 : fffffa80`0b7aff40 fffffa80`0bfc3c60 00000000`000000a0 fffffa60`03a141d7 : hal!HalBuildScatterGatherList+0x2f3
fffffa60`0e895030 fffffa60`038166cd : fffffa80`061f81a0 fffffa60`03a13dd0 fffffa80`048ffaa0 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x108
fffffa60`0e8950d0 fffffa60`03819229 : fffffa60`03a86330 fffffa80`063f2800 fffff780`00000014 fffffa60`00000000 : NETw5v64+0x96cd
fffffa60`0e895110 fffffa60`03970920 : fffffa80`04840f58 fffffa80`04840f58 fffffa80`043eb6c0 0000000c`00000001 : NETw5v64+0xc229
fffffa60`0e895160 fffffa60`0380fd08 : fffffa80`05f884d0 00000000`00000000 fffffa80`097dfc60 00000000`00000000 : NETw5v64+0x163920
fffffa60`0e895210 fffffa60`01003122 : fffffa60`00000000 00000000`00000000 fffffa80`097dfc60 fffffa80`09020003 : NETw5v64+0x2d08
fffffa60`0e8952b0 fffffa60`0249e728 : 00000000`00000000 00000000`00000002 fffffa80`097ba860 00000000`00000002 : ndis!NdisFSendNetBufferLists+0xe2
fffffa60`0e895300 fffffa60`0249eabd : fffffa60`0e8957a0 fffffa80`00000000 fffffa60`0e895470 fffffa60`0e895680 : nwifi!Dot11TXCompletion+0x3c4
fffffa60`0e8953c0 fffffa60`024a2ebe : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`095c6010 : nwifi!Dot11FlushIntermediateSendQueue+0xb5
fffffa60`0e895680 fffffa60`024a7f1e : 00000000`0002ffff 00000000`00000000 fffffa80`097dfc60 fffffa80`0464d450 : nwifi!MP6SendNBLInternal+0x132
fffffa60`0e8956e0 fffffa60`0100315e : fffffa80`073708b0 fffff800`00000000 00000001`00002c04 00000000`00000000 : nwifi!FilterSendNetBufferLists+0x7e
fffffa60`0e895710 fffffa60`07406ea7 : fffffa80`04803030 00000000`00000000 00000000`00000001 fffffa80`061f81a0 : ndis!NdisFSendNetBufferLists+0x11e
fffffa60`0e895760 fffffa60`010031ae : fffffa80`071a3740 fffffa80`04803030 fffffa80`00000000 00000000`00000000 : pacer!PcFilterSendNetBufferLists+0x3b3
fffffa60`0e895860 fffffa60`011a5189 : ffff0000`09baf1b3 fffffa80`061f81a0 00000000`00000000 00000000`00000000 : ndis!ndisSendNBLToFilter+0x3e
fffffa60`0e8958a0 fffffa60`072737c4 : fffffa80`0962a010 00000000`0000000e fffffa60`0e895970 00000000`00000000 : ndis!NdisSendNetBufferLists+0x69
fffffa60`0e8958f0 fffffa60`07276ef8 : 00000000`00000000 00000000`00000800 00000000`00000001 fffffa60`07269d25 : tcpip!IppDispatchSendPacketHelper+0x414
fffffa60`0e8959f0 fffffa60`0727635a : 00000000`00000000 00000000`00000006 fffffa80`00000014 fffffa80`00000000 : tcpip!IppPacketizeDatagrams+0x2e8
fffffa60`0e895b20 fffffa60`0725de8e : fffffa80`0a457080 fffffa60`0726e3ed 00000000`00000000 fffffa80`04519d10 : tcpip!IppSendDatagramsCommon+0x77b
fffffa60`0e895f40 fffffa60`0726e090 : fffffa80`0a457080 00000000`00000000 fffffa60`00000003 fffffa80`04803030 : tcpip!IpNlpSendDatagrams+0x3e
fffffa60`0e895f80 fffffa60`07256f67 : 00000000`033f7414 fffffa60`0e896400 fffffa60`073c0000 fffffa80`03c8e240 : tcpip!TcpTcbSend+0x5c0
fffffa60`0e896140 fffffa60`07257185 : fffffa80`04519d10 00000000`00000000 fffffa80`04519d10 fffffa60`0e8961f8 : tcpip!TcpEnqueueTcbSendOlmNotifySendComplete+0xa7
fffffa60`0e896170 fffffa60`072574bb : fffffa60`072574a0 fffffa60`0e8962c0 fffffa80`043d7010 fffffa60`073b3000 : tcpip!TcpEnqueueTcbSend+0x175
fffffa60`0e8961e0 fffff800`01eb1de2 : fffffa80`0a223050 fffffa60`073c3777 fffffa80`0a2a2101 00000000`00000f4c : tcpip!TcpTlConnectionSendCalloutRoutine+0x1b
fffffa60`0e896210 fffffa60`0725c825 : fffffa60`0e896330 fffffa60`073c8f85 fffffa80`04519d10 fffffa80`0b0a1e00 : nt!KeExpandKernelStackAndCalloutEx+0xb2
fffffa60`0e896290 fffffa60`073df440 : fffffa80`0a2095e0 fffffa80`043d7010 fffffa60`073c8f85 00000000`00000000 : tcpip!TcpTlConnectionSend+0x55
fffffa60`0e8962f0 fffffa60`073df14f : fffffa80`0caba400 fffffa80`0a2a2170 fffffa60`0e896ca0 fffffa80`0a388680 : tdx!TdxSendConnection+0x2a0
fffffa60`0e8963e0 fffffa60`073b1759 : fffffa80`0a2a2170 fffffa80`043d7010 fffffa80`043d7170 fffffa60`0e896458 : tdx!TdxTdiDispatchInternalDeviceControl+0x1c3
fffffa60`0e896410 fffffa60`073a61f4 : fffffa80`0734d2e0 fffffa80`043d7010 00000d90`00000001 fffffa80`062fc600 : Mpfp+0xc759
fffffa60`0e8964b0 fffffa60`0717ee43 : fffffa80`0734d2e0 fffffa80`043d7010 00000000`000005b4 fffffa80`0b0a1e30 : Mpfp+0x11f4
fffffa60`0e896530 fffffa60`071593b1 : fffffa80`0b0a1e30 fffffa60`0e8968b0 fffffa80`000005b4 fffffa80`0a33a850 : afd! ?? ::GFJBLGFE::`string'+0x716b
fffffa60`0e8966b0 fffff800`021028ac : 00000000`000005b4 fffffa60`07159010 fffffa80`09ff1a60 00000000`00000101 : afd!AfdFastIoDeviceControl+0x3a1
fffffa60`0e896a10 fffff800`0210b586 : 00000000`000001b0 00000000`00000318 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x34c
fffffa60`0e896b40 fffff800`01e9fef3 : 00000000`00000000 fffffa60`0e896ca0 00000000`00000000 fffff800`0211bd84 : nt!NtDeviceIoControlFile+0x56
fffffa60`0e896bb0 00000000`74fe385e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`026ff0a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74fe385e


STACK_COMMAND: kb

FOLLOWUP_IP:
NETw5v64+96cd
fffffa60`038166cd 4084ff test dil,dil

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: NETw5v64+96cd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETw5v64

IMAGE_NAME: NETw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 492192c1

FAILURE_BUCKET_ID: X64_0xA_NETw5v64+96cd

BUCKET_ID: X64_0xA_NETw5v64+96cd

Followup: MachineOwner
---------

 

again points to network card.

Interestingly enough, it also points to utorrent.exe

I am in the process of downloading something - perhaps using that at the same time I'm using PlayStation Media Server is causing the problem. I have just turned off utorrent, as I'm streaming via PMS. With luck, that's all this is.

As for troubleshooting, I appreciate your suggestions on calling Dell. However at this time I'm not ready to sit on the phone again and deal with waiting for parts again. If this continues, however, then hell yeah I'm calling Dell. I have 3 more years of at home warranty + accidental (oops drove over it).

 

I was playing around in device manager and saw that the wireless adapter was allowing the computer to turn it off to save power. So I unchecked that option. Maybe that'll help, too? Let's hope so!

I have had utorrent and PMS running concurrently on thousands of occasions. SOmething must have changed when I updated to SP2 that made these two programs either not like each other or caused issues with power management in the Dell AGN card drivers.

 

After doing several tests over several days with many different NVIDIA/PhysX drivers I have come to the conclusion the AGEIA card is worthless to me. My laptop runs games and benchmarks either the same or better without it. Especially with the newer 18x series drivers. The biggest problem I had was just tyring to get the darn option to be available in the PhysX options with the newer versions. I even went through the hassle of installing versions in certain orders. I must have done 100 reboots, Ccleans and driver sweepers trying all different options.

None of the games I play really use the card and if so I have noticed 0 difference in them without it.

Someday there might be that one game that really uses it, but until then it will sit on my bench shelf.

Just my 2c on the subject of AGEIA cards.

 

Even if games start to 'really' use it, the card itself is useless. Your GPUs can now do exactly what the AGEIA Physx card does - rendering it useless =-(

 

ummm, yeah, very "refurbished"

i actually talked dell into sending me the gpu so i could replace it myself and it was in rough shape. the fins had a bunch of dings and it promptly failed again...

 

Yeah I don't think they even test their refurbs to be honest. As someone else mentioned to me previously, all the Dell refurb parts are crap. Took me 3 GPUs to finally get one that works.

 

Thanks didnt get to check back for a bit. Gunna throw those clocks, those sound familiar from ones i used to use when i first had the machine just forgot which ones i had stable. Lets see what happens. BTW did some testing with TF2 AFR2 is the best in FPS and no stuttering its pretty nice now..USe Single GPU for L4D though if you pickup nHancer you can get better performance with a custom AFR2 setup, dont remember it off the top of my head but if i saw the check list i could point it out. Caused some shadow probs though.

P.S. Eleron911 where did all the old ppl go. Have not seen Magnus72 and the old gang. Lotsa new m1730 owners lately it seems. That or i have been off here for a really long time =P

Cheers,

D_Sage

 

@DSage -

What FPS are you seeing with L4D and your setup? Any intermittent stuttering? Which driver are you running?

Thanks.

 

http://stores.shop.ebay.com/Noob-of-Hatfield__W0QQ_armrsZ1

lol?

 

A great buy if you're mentally handicapped.

 

I especially enjoyed the stickers...

 

I don't like them... M1730 is awesome even without "modding".

 

Has anyone ever sorted the problem with the M1730 not booting with external hard drives attached to it?

It gets to the Intel RAID screen and stops there. Its been a problem since day one for me. I've tried putting external usb storage devices down the list in the BIOS boot options but this doesn't help.

 

I'll try and putting the RAID as first boot device now... fingers crossed.

 

72 - what if you disable usb as boot device option too, I remember doing that but can't
Verify till I get home from work, but I do remember doing that too on mine.
I typing this and browsing the forum on my Blackberry Bold at work,
I do enjoy all my toys LOL!!!.

 

Hey,

I put RAID first and disabled USB booting. Funnily seems to work when I try a restart but not when I try a cold start.

I'm going to try another cold start now with just one of the two external USB hard drives attached. I've a feeling that the second one might be causing the problem.

EDIT: Ok worked with one ext HD from a cold boot, now going to connect the second ext HD and see what happens.

 

Man that is strange, since the day I made my changes I have not had this issue and
I use a usb drive and even while cold boot starting works ok on mine all the time.

 

Working fine now! Cheers and rep on its way to you. So glad this problem is fixed it bugged the cr^p outta me since I got the laptop.

EDIT: Oops, spoke to soon. As a final test I started the laptop up form a scheduled BIOS Start-Up with two ext HD's both not spinning. It wasn't able to handle this and again froze at the RAID page. I don't know if its a HD or M1730 specific problem but need less to say - its annoying! Anyways, I'll try a few more combo's to see if something works. Might try scheduled wake-up from sleep or something...

 

I would disagree, to some extent. Because a robust physx engine coupled with a robust graphics engine would eat up GPU resources, and no matter how good the GPUs are, they will have their limits. You are very correct in asserting that nVidia’s own PhysX on GPUs is working fine; the cards were designed to handle Ageia PhysX. However, there’s a reason why many desktop gamers with dual-GPU solutions are also adding in additional 8800s as dedicated PPU units, because robust gaming with Physx will require more head-room/FLOPs for the PhysX calculations. In this regard, if there was a game that say, took the best out of our cards, and had PhysX, the PPU could cover the overhead.

Do such titles exist? Hardly any. I’m still waiting for Ernstig to do the comparitive PhysX tests with Cryostasis set at 1680x1050, because that’s when his GPUs will be handling the real load. The 1280x800 tests told me something, but that was more about how badly my system needs to be formatted. The game’s graphics engine is still too simple and really doesn't push dual-video cards far enough; everyone knows that low resolutions bottle-neck the SLi feature anyway, and this could explain why Ernstig’s tests showed similar results with both Nvidia and Ageia-PPU PhysX. Up that resolution to around the 1600x1200 mark and you’ll see the GPU’s reaching their maximum to produce the visuals at acceptable frame rates - add in the PhysX sections of the game, and the frame-rate will collapse - they'll need additional help.

“But then why didn’t he get higher results when he had the Ageia card running the PhysX during his 1280x800 test?” Some might question. Well, I personally think the dual-cards were bottle necked due to the lower resolution and no demand for the 'physx' feature, seeing as all they were producing were visuals and no other demands such as the PhysX feature, which was being handled by the PPU (Note: The bulk of Cryostasis' performance hit comes from PhysX, and not the graphics engine). I know when I run the game with the PPU doing the physics and the GPUs doing the visuals at 1280x800, my SLi bar is dipping down to 60%. As soon as I up the resolution, the bar normalises, and the frame-rate stabilises at a medium-point instead of fluctuating high and low.

In a nut shell, from what I see on my own machine and from the comments I’ve read on PC gaming forums that focus on GPU-intensive PhysX applications, I can say the following. At a low resolution, the PPU wouldn’t yield any real benefits - it‘s useless. At a high resolution--when your cards are proving their worth and possibly at their limit--the PPU gives you that extra headroom. Whether this is useless or not is entirely contingent on the preferences and custom needs of each individual.

Link regarding a discussion of GPUs with PPUs compared againsst GPUs with additional GPU for 'PhysX' feature:
http://forums.overclockers.co.uk/showthread.php?p=13424979

The real question: Will PhysX even fly at the primary physics engine for a majority of titles? At the moment, Havok is still the leading engine and I prefer Havok as it doesn't burden the CPU. But until and unless I don't see an nVidia level tech-demo, showing the Havok engine do what PhysX has been doing as of late, I'll go by the belief that nVidia and its 'PhysX' engine will eventually gain control.

Anyway, I hope I get something interesting out of Ernstig's test results.

 

@72hundred

Had the exact same problem. However, turning off booting from USB devices fixed the problem. I've never booted up with two external HDs attached tho. Is your BIOS up-to-date? Even if so, try to install it again. Also I assume that at least one of your external HDs is set as primary drive. Changing it to logical should fix it (you will need to format the hard drive). You can do that using Acronis Disk Director Suite.

 

If you upgrade your cpu to like a x9000, and your video card goes out....and you don't have the old cpu anymore....can you still have your videocard replaced? Is the warranty still good for things other than the CPU?

 

BIOS is up to date (I think) its A10.

I had a look at the second ext HD and lo and behold it was set-up as a primary! In the process now of moving 290Gb's - probably run it tonight.

Thanks for the catch RE primary drive - never would have thought of it! I remember I never formatted the drive when I got it because I wanted to use straight away.

 

LOL, I had my Ageia card allready removed. So I had to reinstall it for the 2nd time. I'm becoming a sort of handy in opening my beast.

I only ran in two issues:

• 
  I messed up the Ageia and the nVidia drivers. I did some different tests myself and now I seem not to get my Ageia card working anymore. In the device manager the Ageia PhysX card is enabled and in the nVidia control panel the nVidia PhysX is disabled. Am I missing something?
  I've to reinstall the drivers. What drivers I should use and in which order to install to get a clean comparison. I know I've to start with the Ageia drivers first.

• 
  My keyboard connector makes bad contact. Maybe I need my keyboard or the palm assembly to be replaced. When I replace my keyboard it looks like it doesn't slip in the connector right. I can see a narrow gap between the keyboard and the palm. Some num pad keys don't work at that moment. When I shove it a few times back and forth it starts to work after a while. Then I've to screw it tight quick to be shure it stays that way. Very annoying every time after opening this rig.

@Kade Storm
Can you tell me what drivers you're using. I want to get my Ageia working properly to finish that Cryostasis test.

 

First install v8.09.04. AFTER installing v8.09.04, install the current version. Once complete, install your GPU driver.

http://www.nvidia.com/object/physx_8.09.04_whql.html

 

Just extended my warranty another 3 years - $345.55! I would highly recommend it to other people. I have the full protection - the whole shebang: accidental damage; onsite coverage; phone support; free parts replacement.

Even if you're planning to switch brands in the next year and try something new, this is totally worth it, because when your motherboard kicks the bucket, Dell will send you a new computer from their current line, which is apparently the Alienware <-- definitely worth the $300.

 

great isn't it? Did you have to haggle them? or is that standard price?

 

I've warranty up till April '11. Did you confirm with the sales rep that you'd get a Alienware if the laptop died and they couldn't find the parts?

 

I think you will get a refurb M1730 with comparable specs as your's until there are no more M1730s that are comparable. After that you can ask for a comparable new system.

 

No haggling. I did ask about this extension a month ago on the online chat, and they quoted me some ludicrous figure over $500, so I was peeved for a while and didn't ask again until last night. At the beginning of the phone conversation, he told me something like $367, but by then end it had dropped to $345. It's obvious they cater and change the price dependent upon whose calling. They probably checked my file and saw what a nuisance to Dell I've been in the past three years (had my system/parts replaced numerous times probably totaling $6,000 over the last three years), so they gave me a discount so I wouldn't complain too much.

I've warranty up till April '11. Did you confirm with the sales rep that you'd get a Alienware if the laptop died and they couldn't find the parts?

Nope. Going on hearsay.

I think you will get a refurb M1730 with comparable specs as your's until there are no more M1730s that are comparable. After that you can ask for a comparable new system.

Well obviously. I was merely stating that in the long term [for current 1730 owners] that it'd be worth it alone to get the warranty because it pays for a whole new system when the m1730's are out of stock. $300 or $400 might seem like a lot for a warranty, but I get the most out of it, and I technically 'profted' the first time I had my graphics card replaced, considering at the time it was a $1200 part.

 

That's fair. I don't expect a new system from Alienware unless they can't offer me one through Dell.

 

That did it.
I think the first time testing I have missed something. I start all over again to get clean better results.
We'll see if the Ageia card will perform better in high resolutions.

 

I'd give it another year or two tops before they run out of m1730s. After that, warranty will pay itself off! Yay!

 

Does anyone have problems with their fans blowing. I can't seem to get my notebook to cool. I have a cooling pad and AC in the room. Dell has replaced the GPU's, heatsink, motherboard. Yet it still is overheating.

The only thing that bothers me is the lack of airflow from the back of the machine. There is nothing even when it is hot as 100C still no fans kick on. Any recommendations on what to do?

 

Monitor temps using HWMonitor and contact Dell ASAP and have them replace the GPUs again citing high temps and failure of fans turning on @ proper temps. Keep in mind the GPU fans should come on between 70-75c.

 

I just got my M1730 back, with the motherboard, heatsink, and fans replaced. Yet nothing has changed and it is still way too hot. At this rate Dell is going to have my machine more than I do.

I will download the HWMonitor software now and I am expecting Dell to call me back tomorrow. Thanks for the advice.

 

I take it you didn't opt for the on-site Next Business Day warranty? Sending the unit to the depot can be a hassle, but if its your only option I would do it.

You should look into updating your warranty with onsite NBD coverage. Check the Warranty Status link on support.dell.com. You'll have to supply your service tag and other relevant info but this is where you can access additional coverage options and cost.

 

Thanks, man.

If the game's running well, take the resolution up to the maximum of 1920x1200. Oh, and also keep the anti-aliasing and anisotropy-filtering activated along with everything else being at max.

By the way, do let me know your average FRAPS reading for the outdoor scenes with the snow-storm? Mine stutters and staggers at 15 FPS, which. . . sucks.

 

I have had my beast for about the weeks now and love it runs all my games at full everything no heat issues looks great playing blurays on my 52 inch plasma.thinking about upgrading cpu.overall love my BEAST.

 

hello:

Does anyone here have a link for the dell xps 1920x1200 wallpapers.
I know the link was posted here somewhere...(I cannot seem to find it even after searching).

thanks.

 

There are everywhere.

http://www.desktopnexus.com/search/XPS/

 

Thank you!!!!
That is the site I forgot to bookmark.