BSOD on Startup 0x0000001E

[AdamW]

Hello all,

I am on a custom built rig that will be 4 years this December. Yesterday, after playing a couple games of League of Legends & then taking a break to do some house chores, I came back to the computer acting very sluggish & having experienced loss of sound.
After reboot, which was very slow, I would often lock up half way after the desktop loaded, or when I tried to execute programs. As of today, I'm getting a BSOD right around the time the desktop is popping up after a reboot.
Until today, I had not updated any drivers or installed new programs in at least several weeks. Today, I updated my ATI graphics driver, as well as my USB 3.0 driver which had not been causing any issues, but was showing an error in device manager; these were no help.

I am attaching some of my dump files, as well posting my results from WhoCrashed. Thanks in advance for any help you are able to extend me from your great knowledge base!


[FONT=Segoe UI, Arial]On Sun 10/27/2013 1:47:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102613-54038-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F840)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800030C7956)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 10/27/2013 1:47:11 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]tcpip.sys[/FONT] (tcpip+0x429E5)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800030C7956)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\tcpip.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: TCP/IP Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 10/26/2013 10:39:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102613-39827-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F840)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA8005169610, 0x0, 0x7FFFFFA8000)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]

[/FONT]

 

[koolkat77]

Welcome to the forum.

Please update the drivers below:

lmimirr.sys Wed Apr 11 04:32:45 2007 (461C108D)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
Driver Reference Table - lmimirr.sys

WmXlCore.sys Fri Jan 25 05:01:22 2008 (479918C2)
Logitech WingMan Translation Driver
Driver Reference Table - WmXlCore.sys

WmBEnum.sys Fri Jan 25 05:01:30 2008 (479918CA)
Logitech WingMan Virtual Bus Enumerator Driver
Driver Reference Table - WmBEnum.sys

LMIRfsDriver.sys Mon Jul 14 22:26:56 2008 (487B7E50)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
Driver Reference Table - LMIRfsDriver.sys

cpuz132_x64.sys Fri Mar 27 05:17:23 2009 (49CC0D03)
CPU-Z
Driver Reference Table - cpuz132_x64.sys

ASACPI.sys Thu Jul 16 09:31:29 2009 (4A5E9F11)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

nusb3hub.sys Mon Oct 26 20:19:44 2009 (4AE5B000)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3hub.sys

nusb3xhc.sys Mon Oct 26 20:19:48 2009 (4AE5B004)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3xhc.sys

• Revo Uninstaller "Free"
  • Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling. This allows you to remove leftover registry entries of the software.
    • Link to download: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

• To perform a clean install of a driver, follow this tutorial:
  • How to Clean Left Over Driver Files with Driver Sweeper

• Virus Check:
  • Make scans with these tools below:
    • TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
    • Online Virus Scanner Eset
• Application conflict:
  • Reduce the start-up items. This will help avoid software conflicts:
    • Remove Startup Programs in Windows 7
    • Clean Startup in Windows 7

• Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
  • Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
  • Help protect your PC with Microsoft Security Essentials
  • Malwarebytes Free

   Note

:info: Do not start the trial version of MalwareBytes

• Also take a look at: Good & Free System Security Combination

• Use Crystal Disk Info to upload a screenshot of your Hard Drives (s).
  • Then test your Hard Drives (s) running a Hard Drive Diag.

• Check for heating issues using Speccy or HWmonitor
  • HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
  • Speccy - System Information - Free Download
    • Please upload a summary tab using Speccy. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

• Test and Diagnose RAM issues with MEMTEST86+
  • Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
    • Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Let us know the results.

BugCheck A, {0, 2, 0, fffff800030c7956} 
Probably caused by : tcpip.sys ( tcpip!UdpReceiveDatagrams+385 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {ffffffffc0000005, fffffa8005169610, 0, 7fffffa8000} 
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {ffffffffc0000005, fffff800033be8ba, 1, 18} 
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck A, {0, 2, 0, fffff800030d8956} 
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+226 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {ffffffffc0000005, fffffa800516c610, 0, 7fffffa8000} 
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck A, {0, 2, 0, fffff800030d9956} 
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+226 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {ffffffffc0000005, fffffa8005151610, 0, 7fffffa8000} 
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {ffffffffc0000005, fffff800033ca8ba, 1, 18} 
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {ffffffffc0000005, fffffa800515b610, 0, 7fffffa8000} 
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {ffffffffc0000005, fffffa800517d3ef, 0, 7fffffa003c} 
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {ffffffffc0000005, fffffa80051163ef, 0, 7efa003c} 
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``