You're using an Sony Ericsson Device 1039 USB Ethernet Emulation (NDIS 5)
I'm not familiar with these devices - but I do know that wireless USB devices will cause BSOD's in Win7 systems.
Is there another way that you can connect to the internet (so you can remove this device and it's drivers to test?)?
Please provide a link to the actual device at the manufacturer's website so we can see more details about it.
This device is disabled:
Not Available ACPI\ATK0110\1010110 This device is disabled.
It must be enabled and you must have the 2009 or later driver for it (the 2004/5/6 and 2007 versions will cause BSOD's)
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall 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 Alternate link:
Disc-Tools.com Manual procedure here:
Link Removed - Invalid URL AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from
Link Removed - Invalid URL (in the upper right corner of the page)
Use this procedure to install the
DRIVER ONLY:
ATI video cards - DRIVER ONLY installation procedure If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.
If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
There are 3 unknown drivers:
s1039cm.sys Tue Nov 17 17:16:09 2009 (4B0320A9)
s1039cr.sys Tue Nov 17 17:19:39 2009 (4B03217B)
s1039wh.sys Tue Nov 17 17:07:04 2009 (4B031E88)
I believe that the belong to the Sony Ericson device. Please update them.
Creative Audio drivers date from 2008 - please update to a Win7 compatible version or un-install it and remove the device from your system.
Analysis:The following is for information purposes only. Code:
[font=lucida console]**************************Thu Aug 16 03:00:14.850 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081612-15288-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
System Uptime:[B]0 days 0:00:06.474[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 124, {0, fffffa8007cd64b8, 0, 0}[/B]
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
Probably caused by :[B]AuthenticAMD[/B]
BugCheck Info: [B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
BUGCHECK_STR: 0x124_AuthenticAMD
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 12 19:45:28.472 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081312-25755-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:15:18.705[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 101, {31, 0, fffff88002fd5180, 3}[/B]
Probably caused by :[B]ntoskrnl.exe[/B]
BugCheck Info: [B]CLOCK_WATCHDOG_TIMEOUT (101)[/B]
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BIOS Version 1103
BIOS Release Date 03/26/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 12 18:33:24.962 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081312-15974-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]1 days 13:13:35.498[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 101, {31, 0, fffff88002f64180, 2}[/B]
Probably caused by :[B]ntoskrnl.exe[/B]
BugCheck Info: [B]CLOCK_WATCHDOG_TIMEOUT (101)[/B]
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BIOS Version 1103
BIOS Release Date 03/26/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug 1 12:58:06.448 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080112-21153-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]1 days 10:56:06.040[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: [B]BugCheck 101, {31, 0, fffff88002f64180, 2}[/B]
Probably caused by :[B]ntoskrnl.exe[/B]
BugCheck Info: [B]CLOCK_WATCHDOG_TIMEOUT (101)[/B]
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BIOS Version 1103
BIOS Release Date 03/26/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
