Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on Startup 0x0000001E

26 Oct 2013   #1
AdamW

Windows 7 64 bit
 
 
BSOD on Startup 0x0000001E

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!


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: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800030C7956)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
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.



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: tcpip.sys (tcpip+0x429E5)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800030C7956)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
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.



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: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA8005169610, 0x0, 0x7FFFFFA8000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
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.





My System SpecsSystem Spec
.
27 Oct 2013   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

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
Note   Note
Do not start the trial version of MalwareBytes
  • 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. RAM - Test with Memtest86+
Let us know the results.


Code:
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 ) 
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
My System SpecsSystem Spec
Reply

 BSOD on Startup 0x0000001E




Thread Tools




Similar help and support threads
Thread Forum
BSOD soon after startup, while updating MSE definitions 0x0000001E
So I started my computer and went through my normal routine, and after a few minutes while updating MSE definitions the BSOD popped up. After restarting it popped a second time, and the third time it did a startup fix from the "improper shutdown, start windows normally" screen. After that it has...
BSOD Help and Support
BSOD 0x0000001e on startup
BSOD 0x0000001e (0xffffffffc0000005, 0x0fffff89992fd66ea, 0x0000000000000002, 0x0000000000000018) memory test using memtest 86 and also using HP memory scan both come back good Hard drive test using seatools comes back good on both short and long test ( ran for 15 passes) have had this...
BSOD Help and Support
Random BSOD on startup, error 0x0000001e
Just started getting the BSOD on a 1 year old Dell laptop. It is completely random only happening occasionally. If the startup is successful I can use the pc for as long as I want with no problems. I ran a hard disk check that came back with no issues so I'm wondering if it is a driver or software...
BSOD Help and Support
BSOD 2 minutes after startup STOP: 0x0000001E
I've been getting the BSOD about 2 minutes after startup. During those 2 minutes, I won't be able to open anything and many of my background apps crash. I managed to reach Safe Mode and looking for help now.
BSOD Help and Support
[BSOD] 0x0000001E on startup
I went to sleep and turned my computer off and when I went to start it up this morning I get a BSOD(0x0000001E). I can only boot into safe mode, any attempts to use normal mode end up with the BSOD about 1min after the desktop is loading. I'm not an expert but I dusted everything and tried...
BSOD Help and Support
0x0000001e BSOD on Startup
Hi! Recently I've been getting this BSOD over and over. It happens about 20 seconds after my computer reaches my desktop when I start up. I happens about 95% of the time I start up my computer. The other 5% it starts up normally w/o any problems. ( Which I think is weird) I had recently...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

ฉ Designer Media Ltd

All times are GMT -5. The time now is 16:15.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App