Unfortunately, it's not quite as simple as that.
First off, the actual cause is rarely a Windows driver. In fact, well in excess of 90% of BSOD's are due to 3rd party drivers (ref: Windows Internals v5 and v6). After that the most common cause is hardware problems, and lastly are Windows drivers.
What often happens is that the offending driver writes to a section of memory that another driver owns. Then the offending driver exits - so there's no trace of it on the memory stack. Then the other driver goes to look at this memory location and panics because the info there is wrong - and it crashes. Yet there's no evidence left as to the original driver.
But, we can draw some conclusions from this. That is that this is a networking error, and may also be a wireless error.
This means that it's something that's using the networking - and maybe even the wireless connection drivers memory space.
If you have a wireless, USB network device - this may be a cause. Here's my canned speech on them:
I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
We use a program that will sort through the drivers, remove the Windows drivers, and will highlight known problem drivers. So that's why I ask you to:
Please provide this information so we can provide a complete analysis:
http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html
I manually looked through the driver listing and found these potential problems:
sptd.sys
a04pwd2m.SYS
These drivers belong to Daemon Tools/Alcohol % software
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program,
then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):
[DEL] DuplexSecure - FAQ [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012):
DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:
Disc-Tools.com
Manual procedure here:
Registry and SPTD problems | DAEMON Pro Help
A number of Creative Audio drivers dating from 2011 (there may be BSOD issues with these drivers in Win8)
AFAIK there aren't any updates for this - so the software should be uninstalled and the device removed from the system in order to test it.
athurx.sys wireless driver that dates from 2010 - should be updated to the latest, Win8 compatible version