New
#1
BSOD shortly after start up, Bugcheck code: 0x1E (0xFFFFFFFFC0000005,
Hello, I have a Toshiba laptop that started with the BSOD right after a virus that was removed, not sure if related. Here is my who crashed copied and pasted. Not sure how to do a zip file of my minidump.
System Information (local)
</B>
computer name: OD-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\windows
CPU: AuthenticAMD AMD C-50 Processor AMD586, level: 20
2 logical processors, active mask: 3
RAM: 8160927744 total
VM: 2147352576, free: 1970311168
Crash Dump Analysis
</B>
Crash dump directory: C:\windows\Minidump
Crash dumps are enabled on your computer.
On Sun 6/30/2013 12:31:50 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\062913-54101-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003DD6BBA, 0x1, 0x18)
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.
On Sun 6/30/2013 12:31:50 AM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003DD6BBA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
On Sat 6/29/2013 4:24:00 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\062913-35973-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA800775C610, 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.
On Sat 6/29/2013 4:18:40 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\062913-54569-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003ACB315)
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 Sat 6/29/2013 3:19:27 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\062813-37268-01.dmp
This was probably caused by the following module: unknown_module_00000000_00000001.sys (Unknown_Module_00000000_00000001+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003D84BBA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000_00000001.sys .
Google query: unknown_module_00000000_00000001.sys KMODE_EXCEPTION_NOT_HANDLED