Windows 7 0X0000000A and 0X0000001E

[Link1227]

Having a bsod problem, and there is no error message on one, while the other says KMODE_EXCEPTION_NOT_HANDLED. I checked them in windows debugger and couldn't find anything. I've already did a hard drive scan. Can someone please help me pinpoint the problem? Thanks in advanced.

 

[usasma]

Please provide this information so we can provide a complete analysis: Link Removed

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] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (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

You also have a wireless USB X-Box controller installed that is known to cause BSOD's. Please un-install the software for this device and then physically remove the device from your system to test it. The driver (xusb21.sys) dates from 2009 and there are no known updates for it (so if it's the cause, the only "fix" is to remove it).

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

pcouffin.sys Tue Dec 5 09:39:30 2006 (457584A2)
low level access layer for CD devices (A part of many different CD/DVD burning programs)
Link Removed

PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
Sonic CD/DVD driver (used by many different CD/DVD programs)
Link Removed




Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Sat May  4 23:10:23.023 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\050413-68141-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:05:23.851[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ObpCreateHandle+29a )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff80003fcabba, 1, 18}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003fcabba, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000018, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!ObpCreateHandle+29a[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  BIOS Version                  P1.40
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May  4 20:46:03.207 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\050413-47705-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]2 days 7:09:45.409[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )[/B]
BugCheck [B]C0000005, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  ACCESS_VIOLATION
PROCESS_NAME:  0.040510416082
FAILURE_BUCKET_ID: [B]X64_ACCESS_VIOLATION_NULL_IP_nt!ExpSystemErrorHandler2+5e1[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  BIOS Version                  P1.40
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Sat May  4 23:10:23.023 2013 (UTC - 4:00)**************************
[COLOR=RED][B]pcouffin.sys                Tue Dec  5 09:39:30 2006 (457584A2)[/B][/COLOR]
[COLOR=RED][B]xusb21.sys                  Wed Apr  8 10:28:44 2009 (49DCB49C)[/B][/COLOR]
[COLOR=RED][B]PxHlpa64.sys                Tue Jun 23 19:16:35 2009 (4A416253)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
povrtdev.sys                Wed Feb 24 05:51:44 2010 (4B8504C0)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmXlCore.sys                Tue Apr 27 16:09:26 2010 (4BD74476)
WmBEnum.sys                 Tue Apr 27 16:10:19 2010 (4BD744AB)
dgmbx2.sys                  Fri Feb 11 18:02:20 2011 (4D55BFFC)
dgmbx2fu.sys                Fri Feb 11 18:02:48 2011 (4D55C018)
jakndis.sys                 Mon May 23 07:09:06 2011 (4DDA4052)
athurx.sys                  Thu Jun  2 02:57:54 2011 (4DE73472)
ay23mlwg.SYS                Tue Dec 27 17:30:45 2011 (4EFA4715)
iusb3hub.sys                Fri Jan 27 04:35:25 2012 (4F226FDD)
iusb3xhc.sys                Fri Jan 27 04:35:28 2012 (4F226FE0)
iusb3hcs.sys                Fri Jan 27 04:37:23 2012 (4F227053)
usbfilter.sys               Fri Mar 30 23:48:56 2012 (4F767EA8)
vmci.sys                    Mon Apr 30 21:14:27 2012 (4F9F38F3)
ISCTD64.sys                 Fri May  4 20:44:01 2012 (4FA477D1)
MijXfilt.sys                Sat May 12 00:27:12 2012 (4FADE6A0)
Tpkd.sys                    Wed May 16 14:09:29 2012 (4FB3ED59)
Rt64win7.sys                Tue Jun 12 10:00:29 2012 (4FD74B7D)
ikbevent.sys                Tue Jun 12 15:22:18 2012 (4FD796EA)
imsevent.sys                Wed Jun 13 21:35:28 2012 (4FD93FE0)
IntcDAud.sys                Tue Jun 19 10:40:51 2012 (4FE08F73)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
[COLOR=RED][B]sptd.sys                    Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
vsock.sys                   Tue Aug 21 17:10:15 2012 (5033F937)
dfx11_1x64.sys              Tue Aug 28 15:10:34 2012 (503D17AA)
diginet.sys                 Tue Sep 11 04:25:13 2012 (504EF569)
idmwfp.sys                  Wed Nov 21 09:42:58 2012 (50ACE872)
igdkmd64.sys                Wed Dec 12 19:42:26 2012 (50C92472)
nvhda64v.sys                Wed Dec 19 00:41:41 2012 (50D15395)
epfwwfpr.sys                Fri Dec 21 07:00:04 2012 (50D44F44)
eamonm.sys                  Fri Dec 21 07:02:24 2012 (50D44FD0)
ehdrv.sys                   Fri Dec 21 07:03:30 2012 (50D45012)
nvlddmkm.sys                Thu Mar 14 21:37:00 2013 (51427B3C)
RTKVHD64.sys                Fri Mar 29 09:40:06 2013 (515599B6)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May  4 20:46:03.207 2013 (UTC - 4:00)**************************
WmVirHid.sys                Tue Apr 27 16:08:53 2010 (4BD74455)
aeingr52.SYS                Tue Dec 27 17:30:45 2011 (4EFA4715)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
ay23mlwg.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
dfx11_1x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aeingr52.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

 

[Link1227]

Thank you!

here is the file you requested.

W7F_05-05-2013.zip - Speedy Share - upload your files here

I wasn't able to attach for some reason.

 

[usasma]

These suggestions are in addition to those that I already made in my previous post.

Please ensure that you have ALL Windows Updates. It may take several visits and reboots to get them all.

You have an Atheros AR9271 Wireless USB Network Adapter:

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.

These devices have problems in Device Manager:

ehdrv ROOT\LEGACY_EHDRV\0000 This device is not present, is not working properly, or does not have all its drivers installed.

VMware VMCI Host Device ROOT\VMWVMCIHOSTDEV\0000 This device is not working properly because Windows cannot load the drivers required for this device.

Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.

The first item belongs to your ESET NOD32. Please un-install it, then use this link to ensure that the troublesome driver is removed: How do I delete the ehdrv driver using device manager? - ESET Knowledgebase
Then download and install the latest Win7 compatible version from the ESET website.
Once installed, immediately update it and perform a full system scan.

The VMWare device isn't working either. Please un-install it, then download and install the latest, Win7 compatible version from the VMWare website

The Security Processor Loader Driver is usually a sign that an infection has damaged your system. Please be sure to perform several scans to make sure that the malware is completely gone. Here's a list of some free scanners: Link Removed