New
#1
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.
Last edited by AdamW; 26 Oct 2013 at 22:32.