And if you think there is no stop to those BSODs you see on Windows XP and Windows Vista, here’s one weird BSOD error message. 0xDEADDEAD. How strange isn’t it? Is Microsoft trying to be funny here or what? What’s the deal with this stop error code? So I wore my Sherlock Holmes hat and whipped out my magnifying glass and tried to find the cause of this issue. Most the the systems affected by this BSOD error are DELL Systems the XPS 1330 and XPS 1530 line. Using the microsoft debugger program it spewed out this driver file, NETw5v32.sys. This driver file is part of the beta drivers that Intel is going to release later this year. It is part of the Proset 12.0.0 driver set. The solution to this problem is to rollback the driver or try the drivers that are currently posted right now at support.dell.com. The NETw5v32.sys was purported to support the 3945ABG and 4965AGN adapter, but these adapters are still not in production.
Bug Check 0xDEADDEAD: MANUALLY_INITIATED_CRASH1 <— that is the complete error message. This is usually part of a debugging a driver to be used in windows. It is a manually initiated crash and according to the websites that I read there would usually be a registry that is manually added to cause this crash. Now if your system installed a driver that is still in beta and is still being “DEBUGGED” I guess that would result into this 0xDEADDEAD BSOD.
Any other ideas?
