BSOD shortly after start up, Bugcheck code: 0x1E (0xFFFFFFFFC0000005,

webcrawlur · 01 Jul 2013

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

Dsprague · 01 Jul 2013

Please follow the Blue Screen of Death (BSOD) Posting Instructions

webcrawlur · 01 Jul 2013

Dsprague said:

Please follow the Blue Screen of Death (BSOD) Posting Instructions

Where will I find the zip file?

I did download and run the sf software.

Dsprague · 01 Jul 2013

Did you run the program from your desktop? or did you run it from where ever you downloaded it to?

webcrawlur · 01 Jul 2013

Where I downloaded it to. I double clicked the file in the download folder to open it.

Dsprague · 01 Jul 2013

look in the folder where you downloaded the program the program generates a folder called Desktop when you run it where ever you run it.

webcrawlur · 01 Jul 2013

Ok, I think I found it, how do I zip it? Thanks so much for your help so far.

ETA: Found how to zip it, will post it in a few.

Dsprague · 01 Jul 2013

Right click the folder select send to from the context menu, then from the menu that opens after selecting send to select Compressed(Zipped) folder

webcrawlur · 01 Jul 2013

Thanks, I attached it in the post above yours.

Dsprague · 01 Jul 2013

OK a couple of things:

Update your graphics driver it is very old and is causing problems:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80067d84e0, fffff8800414e2dc, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+72dc )

Followup: MachineOwner
---------

Driver Reference Table - atikmpag.sys

Code:

kd> lmvm atikmpag
start             end                 module name
fffff880`04147000 fffff880`04194000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Feb 10 12:15:07 2011 (4D541D1B)
    CheckSum:         0004D36C
    ImageSize:        0004D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Also update your SATA driverit seems to be causing problems and is again very old:

Code:

fffff880`0954b938  fffff880`00de6670Unable to load image \SystemRoot\system32\DRIVERS\amd_sata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amd_sata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
 amd_sata+0x1670

Driver Reference Table - amd_sata.sys

Code:

kd> lmvm amd_sata
start             end                 module name
fffff880`00de5000 fffff880`00dfb000   amd_sata T (no symbols)           
    Loaded symbol image file: amd_sata.sys
    Image path: \SystemRoot\system32\DRIVERS\amd_sata.sys
    Image name: amd_sata.sys
    Timestamp:        Thu Nov 04 19:52:21 2010 (4CD34735)
    CheckSum:         00019FF4
    ImageSize:        00016000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Both drivers can be updated from here: Support & Drivers

your wireless driver seems to be failing as well:

Code:

fffff880`031d9688  fffff880`03eb0b01Unable to load image \SystemRoot\system32\DRIVERS\rtl8192Ce.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rtl8192Ce.sys
*** ERROR: Module load completed but symbols could not be loaded for rtl8192Ce.sys
 rtl8192Ce+0x72b01

Driver Reference Table - rtl8192Ce.sys

Again it is very old:

Code:

kd> lmvm rtl8192Ce
start             end                 module name
fffff880`03e3e000 fffff880`03fab000   rtl8192Ce T (no symbols)           
    Loaded symbol image file: rtl8192Ce.sys
    Image path: \SystemRoot\system32\DRIVERS\rtl8192Ce.sys
    Image name: rtl8192Ce.sys
    Timestamp:        Tue Jan 04 11:50:10 2011 (4D234FC2)
    CheckSum:         0011554E
    ImageSize:        0016D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Updates can be found here: Realtek