New Dell XPS M1530, Need Some Help Pls!

Hey guys, got a problem...


Just got my new Dell XPS M1530 Laptop with Vista Home Premium day before yesterday. Besides few screen issues that Dell is handling I was quite happy with the purchase, until yesterday...

Every time I Restart or Shutdown the system, the damn thing gets a BSOD and once I perform a hard shutdown I loose all my saved files...


The STOP error is as follows:

STOP: 0xDEADDEAD (0x00000000, 0x00000000, 0x00000000, 0x00000000,)

Starting memory dump......Blah Blah


Now, the only hardware adjustment I made so far is add 4GB of Corsair Value Select DDR2 Ram instead of 1GB of Samsung it came with.

I ran the memory checker several times and it seems fine. I should also point out that while I'm using the system I experience no problems what so ever.

I've checked the System Logs a few times but don't see anything that would catch my eye, maybe you guys can point me in the right direction =)


After speaking with Dell XPS Support, I've seem to loose all hope. They basically said that they have no solution for my problem and that the only thing they suggest is to send me a replacement laptop since they already marked it DOA because of the grainy Samsung screen issue.

I still want try to find a solution to this annoying problem, I'm 75% convinced that it's probably related to Vista, or some software that's not getting along with it.

Everything I installed so far said that it was Vista compliant, and I made sure not to install any beta releases.


I know some of you might say go with XP, but I seem to really like the few Vista perks and staying very hopeful for the Service Pack 1...

Please help me with this, and let me know if you need any additional information.



Thanks in advance.

- Alex

 

I am no PC troubleshooter, but, If you really, really want to keep the laptop, I would do a system restore to a day or two before the problem happened, and take out the new memory.

But, frankly, the easiest, least time consuming and most reliable solution is to get the whole laptop replaced, especially since the screen is bad anyway. Replacing the screen alone may result in further damage. You are better off getting the whole laptop replaced.

 

When you get a BSOD, usually a crash dump is placed in C:\WINDOWS\Minidump. The error info on the BSOD can be confusing, and often reflects a process that occurred after the actual crash. To really know what happened, you can download windows debugging tools. Install the tool, then run it, but in vista you have to use the "Run as Administrator" (right click on WinDbg and select Run As Administrator) you will find this in the Debugging Tools for Windows in your Start -> All Programs menu. This tool needs a path to the microsoft website to get debugging symbols, you do this by selecting File -> Symbol File Path from the menu in WinDbg and pasting in this path:

Code:

SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Then open the latest crash dump by selecting File -> Open Crash Dump and point to the dump in C:\Windows\Minidump and double click on it. You need to be on the internet because the debugger will get symbols from the microsoft site. Wait for the symbols to load, then click on where it says i-analyze at the bottom of the screen. Wait a bit longer and you'll have a bunch of detailed info about the crash, most importantly WHICH process crashed and usually some indication of why. If you paste the results in here, we then have something to go on. The STOP CODE error 0xDEADDEAD that you posted means Manually Initiated Crash, which I suppose is misleading, hence the need to analyze the crash dump (if you really want to know, the tools are available) ...

 

Much thanks for the replies guys, especially you Proficio.

I've been on Maximum PC Forum and guys there are really helpful as well, but this is the first time someone is suggesting to use the "wonderful" windows debugging tools

Anyway, here's the most recent analyzed crash dump file:

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini012808-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Mon Jan 28 07:29:51.609 2008 (GMT-5)
System Uptime: 0 days 4:59:04.052
Loading Kernel Symbols
......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
........
Unable to load image \SystemRoot\system32\DRIVERS\NETw5v32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5v32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5v32.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DEADDEAD, {0, 0, 0, 0}



Probably caused by : NETw5v32.sys ( NETw5v32+efe87 )

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

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

MANUALLY_INITIATED_CRASH1 (deaddead)
The user manually initiated this crash dump.
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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




CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xDEADDEAD

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8fa54e87 to 818d8652

STACK_TEXT:
82e68ca0 8fa54e87 deaddead 85b2f2e8 87c4d240 nt!KeBugCheck+0x14
WARNING: Stack unwind information not available. Following frames may be wrong.
82e68cb4 8f96f626 87c440a0 85b2f2e8 86c21fe0 NETw5v32+0xefe87
82e68cd8 8f96f825 85b2f2e8 82e68d00 8f96f082 NETw5v32+0xa626
82e68ce4 8f96f082 85b2f2e8 86c21fe0 879ca828 NETw5v32+0xa825
82e68d00 8fa4df4a 87ad269c 00000013 00000000 NETw5v32+0xa082
82e68d20 816f0c32 879cae78 879ca850 82e68d44 NETw5v32+0xe8f4a
82e68d30 8198c85a 87835030 879ca850 8510e470 ndis!ndisDispatchIoWorkItem+0xf
82e68d44 81878fa0 879ca828 00000000 8510e470 nt!IopProcessWorkItem+0x23
82e68d7c 81a254e0 879ca828 82e63680 00000000 nt!ExpWorkerThread+0xfd
82e68dc0 8189159e 81878ea3 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
NETw5v32+efe87
8fa54e87 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NETw5v32+efe87

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETw5v32

IMAGE_NAME: NETw5v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 478f5db6

FAILURE_BUCKET_ID: 0xDEADDEAD_NETw5v32+efe87

BUCKET_ID: 0xDEADDEAD_NETw5v32+efe87

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


Again, very thankful for your help guys!

- Alex

 

Sounds like a problem with your replacement memory.

Remove the new memory and replace it with the original 1GB of Samsung memory carefully, does it still have problems??

If there are still problems when (only) your original memory is installed, it is a Dell problem, otherwise it is a problem with your new memory.

Good Luck

 

Ok I will give that a try and report back on here, the guys over at Maximum PC also suggested that having 4GB of ram in Vista 32-Bit is most likely the cause.

If that happens to be true, that means there is no way I can have more then 2GB running in true dual-channel mode, hence 3GB is not identical modules...



I'll report back after I switch out the memory, thanks.

- Alex

 

Wincrash Vista wrote

Wow that is one strange crash dump. First bit of strangeness is how it says "The user manually initiated this crash dump." Assuming that YOU did not, it must mean a "user space" program (driver) initiated this dump. Second bit of strangeness is that the crash occurred in driver NETw5v32.sys for which I can find no information anywhere. It is clearly a vista driver fault. If you follow the wincrash32 API calls hehe, it talks about NDIS, where it does ndisDispatchIoWorkItem. Kernel starts pspSystemThread, ExpWorkerThread, IopProcessThread, ndisDispatchIoWorkItem, then it gets into this driver NETw5v32 and this driver doesn't do exception handling properly, terminates the kernel. It gets to memory offset 0xefe87 in this NETw5v32 and crashes. The code that launches this appears to be related to NDIS which is Network Driver Interface Specification. The strange thing is how there is no info on the driver code NETw5v32.sys, and yet there are no symbols either, which usually means it is NOT part of vista. I doubt that this is a memory hardware problem. It is most likely some kind of driver bug. Since it appears to be network related, I'd suggest re-installing all network related drivers, check to make sure you have the most recent BIOS, and set the BIOS to default settings (boot pressing F2, look in Maintenance, set to default, press esc and save settings). Anything strange happening with networking?

Since there was recent memory change, boot pressing F12, choose boot to utility partition, it will run PSA (pre-boot assesment) then load diagnostic program, select custom and run the memory tests. The other suggestion of putting the original RAM in there is good too, but if the same DRIVER fails repeatedly that is not symptomatic of memory failure. A very small percentage of BSODs are caused by hardware, almost all are flaky drivers or application bugs. Check if there are more minidumps and if so run the same tool and see if it is always this same driver NETw5v32.sys appearing.

 

I lost you shortly after that...Lol

I went ahead and tested the memory multiple times prior to posting on this forum and it turned out without a single error. It is very strange indeed, I was not able to find any info what so ever while searching google for "NETw5v32.sys".

This is actually what made it so difficult to diagnose, but after I read Bbiddle's reply in regards to the memory being at fault, I decided to give it another shot and test the modules one by one. Long story short, I kept getting the STOP error regardless of the different configurations I was able to come up with, then finally a breakthrough... I completely removed the purchased Corsair Value Select memory and put in the 1GB Samsung that originally came with the laptop. So far 4 Reboots and 0 BSOD .

Kind off strange that with the right specs and Corsair being one of the leading memory manufacturers didn't get along with my friendly M1530

I'll gladly listen to any advice you might have in regards to upgrading with compatible memory.

Thanks for the help! Much apreciated!

- Alex

 

Scratch off the last thread I posted, just attempted to restart and got the same 0xDEADDEAD Stop error.........

Not sure what else to do at this point, unless anyone else can suggest something else, I guess I'll just wait until Dell sends me a replacement.

- Alex

 

You could try and reload windows vista.

 

I would start with a clean install of Vista.

 

It is most likely a software error. My suggestion is to make backups of your data and do a restore to factory image. After saving your data, put the vista disk in the drive, boot while pressing F12, select CD/DVD drive from the boot menu. Windows will load its setup program and have you choose language, keyboard, and time zone. After that look in the lower left corner for the option "Repair My Computer". This starts the windows recovery environment. After WinRE starts, select the command line option. When in the command prompt environment, type:

Code:

SET PATH = D:\Windows;D:\Windows\System32 [enter]
D: [enter]
cd Tools [enter]
PCRestore [enter]

You will get the factory image restore screen. Accept the warning about data loss, and the rest is automatic. Within about 10 minutes your machine is back the way it was.

Do some testing before making a bunch of software changes. Chances are if you do exactly the same thing you might get the same crash. Recall that the crash starts with NET and the dump showed entry into NDIS which is Network Device, so this appears to be related to networking in some way.

If you restore to factory image and still get the BSOD, try disabling network devices one by one in device manager (right click and disable), testing with each, remember you have LAN (ethernet), WIFI, and Bluetooth.

You should be accumulating minidumps in C:\Windows\Minidump, if they are all crashing in the same NET driver, then its either a driver bug or possibly hardware failure related to networking. Hence the disabling network drivers one by one to isolate.

 

Just before I had a chance to read this post, I decided to go back and try to trace back to Saturday late night, just when I got my first BSOD. The very first thing I wanted to check were the Windows Updates that I applied that same day. What do you know, as I took a closer look I saw that the driver for the friggin' WiFi failed to install twice... Hence making me realize that it probably did not install correctly. As I went into the driver properties, first thing I notice is the "NETw5v32.sys" that keeps showing up in the logs. Long story short, I unistalled the damn thing, rebooted the PC, and to be safe cleaned out the sucker with Driver Cleaner Pro, after which I rebooted again and installed a fresh driver that I picked up from the Intel site. I'm keeping my fingers crossed but haven't had a single BSOD yet. One thing to keep in mind is that Dell released a new update for this driver on the 26th, while Intel driver still has a November date. Just to be on the safe side, I'm staying away from the Dell update for this driver, I'm more then fine with the outdated but problem-free Intel version

So far so good, thanks to you and your extensive knowledge of Windows environment Proficio.

Thanks to everyone who participated and helped me resolve this annoying issue, this is one nail that was worth hammering into the coffin! I can sleep now

- Alex

 

I'd like to thank everyone in this thread..

I just got an XPS M1330

And I started to get the deaddead blue screen on shutdown. in the minidump, it was too "NETw5v32.sys", I went to the Intel website and installed their driver which is "NETw4v32.sys"

I rather it work then get blue screens.

 

One thing that makes this REALLY strange is that a user-mode initated STOP that results in the DEADDEAD bugcheck is normally restricted to setups for driver debugging. There's also a registry key involved to even enable a user-mode STOP.

Those two things make me wonder if this NET driver had been released with some remnants of debug code included, and didn't get pulled out for the release build....

-Dave

 

Dell XPS M1330 gave me the same BSOD at shutdown and the startup would report that an unexpected shutdown occured bla,bla.
After finding your post I opened MSCONFIG and "enabled all" now everything is ok, no malware, no incompatable hardware, no bad memory.
I'll probably let it alone for a couple of weeks then disable items one at a time and if I locate the actual startup item that causes this I'll post it.
Take it easy...

 

I had the same issue with my XPS M1530 after installing Windows Update KB943899. I uninstalled it and on reboot Vista repaired the system. No more issues!

Found the solution in this thread...

http://forum.notebookreview.com/showthread.php?t=207087&page=2

 

Thank god I saw this thread!

I have 4GB, m1330 and have the same BSOD, deadead BC code and NETw5v32.sys driver error when restarting or shutting down the notebook. I previously called tech support about this and the tech can't figure out what the problem is except for the fact that I've tweaked the startup, shutdown process which he said might be causing the BSOD. What suprised me was he can't find the hardware that is related to that driver, which in turn is the wifi. I almost gave up and returned this new laptop as this was a replacement for a previous one that had dead pixels. He suggested to install from the backup partition which I did, and avoid the windows vista tweak thread from notebookreview. Same problem after.

I wonder if this might be a bad hardware either? Anyways, that 11/8/07 driver from Intel fixed the problem. Thanks heaps!

 

weird i just got my XPS M1330 last week monday and all was going well and i have experienced 5-10 crashes already for the last 5 days. i got the crash twice when shutting down. then i got it a few times when using the Intel Wifi N Adapter when switching connections. very annoying.

i need some help too... trying to debug right now. will post more info in a few mins.

thx-jeff

ok i definitely have this NETw5v32.sys in the debug info as problem... i will uninstall or rollback driver. by the way the driver for the wireless Intel network adapter is dated 1/17/08.

 

I have exactly the same problem and i didn't change the RAM !

 

Are you folks using the sleep or hibernate when this happens? Or are you doing actual shutdowns? The sleep and hibernate parts of vista seem be quite buggy at the moment. Lots of weird bugs like the bsod and also wireless problems. Try using regular old shutdown and set the power management settings to not sleep and see if that makes any difference. I haven't encountered this bug yet but then I don't trust the sleep/hibernate due to the number of serious errors I'm observing.

 

Hi Alex, All,

I'm quite curious to how you got NETw5v32.sys. This driver is aligned to be released later this year to support the new Intel Wifi Link adapters. This driver has not yet been released yet, and is not ready for production systems. This driver is part of the PROSet 12.0.0 beta release.

If possible, could you give an insight on how you got this driver? Did someone at Intel give you this driver? Was it pushed down by Windows Update? Was it mistakenly loaded by the Dell factory?

If you want to fix this issue, I recommend that you download the latest driver which is part of the PROSet/Wireless 11.5.1 release for the 4965AGN card from either the Intel website or from your OEM website. The proper driver to use with this adapter at this time is NETw4v32.sys.

The NETw5v32.sys will support the 3945ABG and 4965AGN adapter, but it's just not out of development yet.

Thanks,
Sean Dunn

 

Hello,

I am new here and this seems to be the only place on the net that has information on this problem. I recently purchased a Dell XPS M1330 and received it last week. I updated the BIOS to A09 a short while ago and when the computer was trying to shut down for a restart, it threw up a BSOD.

Running the debugger as proposed in the previous replies, it gave this report:



Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini022008-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Wed Feb 20 02:37:50.376 2008 (GMT-5)
System Uptime: 0 days 0:08:44.260
Loading Kernel Symbols
.....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\system32\DRIVERS\NETw5v32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5v32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5v32.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DEADDEAD, {0, 0, 0, 0}



Probably caused by : NETw5v32.sys ( NETw5v32+efe87 )

Followup: MachineOwner


I am not sure of what to do with this; my laptop is barely a week old. Would really appreciate any help on this issue asap.

Thank you so much.

 

Hi Sean,

The Dell XPS M1330 actually came installed with version 12.0.0.52 for Intel(R) Wireless WiFi Link 4965AGN. I guess I shall try to change to to NETw4v32.sys and pray that it works.

 

I, too, had the shut down/blue screen problems with a 3 day old XPS1530. After debugging and researching NETw5v32.sys, the Dell tech uninstalled the Intel Wireless driver, reinstalled, and so far, no more blue screens.

 

Thanks for your reply. I did a little more digging around and finally decided to rollback the driver to it's original state, before I downloaded the driver from Intel and installed NETw4v32.sys. It you search the directory which the file resides in, you will see that there is actually NETw4v32.sys in the driver directory on your XPS. Also, it seems like Dell is the only one that has issued this driver thus far. I hope they did not jump the gun and install the driver before it was completely tested / launched by Intel. Will contact tech support to ensure all is fine.

 

Hi sean,

I've checked the windows update log and a update of the intel wifi driver was pushed on my computer on the 2/2/2008.

 

Thanks Acetik. We've removed this driver from Windows Update, and we are putting together a fix to address users impacted by the accidental release of this driver.

-Sean