I bought a Dell XPS M1710 with Vista Home Premium 32 bit (wanted XP, but Dell gave me no choice) about 6 months ago and now it is falling apart.
It started with the mic port not working about 2 months after I got it, but that's not a big deal so I ignored it. I figured I'd call a local Dell support guy to fix that when I had time.
Then about 3-4 months in, I got chronic overheating to the point where i could not run a GPU heavy program (like newer games) without the computer shutting down in 2 minutes but I could still run CPU heavy program (i.e. Half-Life 2, an older game) without the slightest problem. I raised the computer off of my desk with books under its corners and this problem is less common, but still existant. I can't even touch the bottom of my computer without burning my fingers most times.
Recently (the past 2-3 weeks) I get the BSoD at completely random times. I could be listening to music, playing a game, surfing the internet, or nothing at all and my computer will shut down. It happens at random intervals as well. I can go days with no BSoD and then get 6 in a single day. The only thing that the BSoD says about Technical Information is "STOP:0xDEADDEAD (0x00000000, 0x00000000, 0x00000000, 0x00000000)". I've uninstalled my drivers and reinstalled them with the patches offered on the official Dell website, but to no avail. I have no system restore points that go back far enough to where there were no BSoDs. I've considered doing a factory reset, but everytime I try to back up my files to DVD, the computer crashes before its finished. For some reason it is taking obscene amounts of time to back up the files (2 hours for 100 songs). My friend has suggested trying to back them up in safe mode, and I will try that tonight, but if anyone knows of a way to fix this, please help me.
Message Edited by rookiegreene on 02-19-2008 01:38 PM
Message Edited by rookiegreene on 02-19-2008 01:39 PM
I had a similar problem with the 0xdeaddead (a hex error that happens to spell deaddead, also one that spells deadbeef) anyways I tracked it down to a vista update, can't remember the KB number though, after I unistalled it the system has been stable ever since. Just to be sure I didn't do it again I hid the update so I don't reload it again by mistake.
I had run a windows debug and the offending file was netw5v32.sys, nic driver. The update had to do with a wireless update. After I removed it I reloaded the manfacturers driver and it's all good. I found the info to the fix, a few different possibilities one there about reloading the Intel Storage matrix app, on this site: http://forum.notebookreview.com/showthread.php?t=207087&page=2
Check out this thread: http://forum.notebookreview.com/showthread.php?p=3013509 I had the same problem with my brand new XPS M1530 and found out that my Intel Wireless WiFi Link 4965AGN had been updated to a beta version of a driver that has yet to be released. I rolled back the driver and the blue screens have stopped.
I got my M1530 in Feb 2008 and my WiFi would BSOD when I tried to Disconnect.
By finding this thread, I found out the problem. I found out the correct version of the driver for the Intel Wireless WiFi 4965AGN. The version Dell installed on my machine is V12.0.0.52 which was the Beta version you mentioned that should not have been installed. I downloaded V11.1.1.22 (listed as V11.1.1.3) from the Dell XPS website and no more BSODs.
Felkis
1 Rookie
•
66 Posts
347
0
Posted February 19th, 2008 19:00
Hi,
I had a similar problem with the 0xdeaddead (a hex error that happens to spell deaddead, also one that spells deadbeef) anyways I tracked it down to a vista update, can't remember the KB number though, after I unistalled it the system has been stable ever since. Just to be sure I didn't do it again I hid the update so I don't reload it again by mistake.
I had run a windows debug and the offending file was netw5v32.sys, nic driver. The update had to do with a wireless update. After I removed it I reloaded the manfacturers driver and it's all good. I found the info to the fix, a few different possibilities one there about reloading the Intel Storage matrix app, on this site: http://forum.notebookreview.com/showthread.php?t=207087&page=2