Solved BSoD when PC sleeps or hibernates, ntoskrnl.exe & ikeyenum.sys

[CurtisL]

Hi,

I am currently having an issue with a users PC that every time the lock the computer and 15 minutes later when it goes to sleep it will either BSoD at that point in time or as soon as they try to wake it (I think it's when they try to wake it). The monitors will flash quickly, you don't see an actual BSOD screen but it restarts and then the BSod message shows after logging into windows.

I have attached all necessary information in the zip file. If you need more information please let me know.

 

[YoYo155]

Welcome.

In the last dump you had Driver Verifier running and querying on your system,
so I can assume its still is.

As a matter of fact it was quite helpful in pinpointing a problematic driver;

2: kd> lmvm ikeyenum
start             end                 module name
fffff880`048a7000 fffff880`048af000   ikeyenum T (no symbols)           
    Loaded symbol image file: ikeyenum.sys
    Image path: \SystemRoot\system32\DRIVERS\ikeyenum.sys
    Image name: ikeyenum.sys
    Timestamp:        [COLOR=Red][U][B]Mon Nov 09 08:14:39 2009[/B][/U][/COLOR] (4AF7B34F)
    CheckSum:         0001063A
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

EDIT:

The driver is a part of Rainbow ikey enumerator.

Sorry for the confusion.

I suggest you uninstall the software, then to remove any remains run Driver Fusion/Sweeper.

 

[CurtisL]

I have since turned off the verifier, I will turn it back on though.

Would the iKey problem really be the one that is causing the bluscreen on waking of the PC? I thought for sure it would be an issue with the graphics driver or something.

I thought I had the right driver as well but I will research some more.

Curtis

 

[YoYo155]

I have since turned off the verifier, I will turn it back on though.

Would the iKey problem really be the one that is causing the bluscreen on waking of the PC? I thought for sure it would be an issue with the graphics driver or something.

I thought I had the right driver as well but I will research some more.

Curtis

I advise checking the HDD;

Hard Drive Diagnostic Procedure - Yours will need Seagate SeaTools

SeaTools for Windows | Seagate

​

 

[YoYo155]

I edited my initial post sorry for the confusion!

[U][B]EDIT:
 [/B][/U]
The driver is a part of [B]Rainbow ikey enumerator[/B].
 
 [U][B]Sorry for the confusion.[/B][/U]
 
I suggest you uninstall the software, then to remove any remains run [FONT=Calibri][URL="http://majorgeeks.com/Driver_Sweeper_d6171.html"][B][COLOR=#3485bd][FONT=Verdana]Driver Fusion/Sweeper[/FONT][/COLOR][/B][/URL].[/FONT]

 

[CurtisL]

It looks like that was the issue, now I just need to find out an updated driver for it.

This software was working before, but then after setting up a new profile for the user and windows updates it BSoD's. Not sure if it is tied directly to a Win update but it's the only thing that comes to mind.

Thanks for the help.

 

[YoYo155]

It looks like that was the issue, now I just need to find out an updated driver for it.

This software was working before, but then after setting up a new profile for the user and windows updates it BSoD's. Not sure if it is tied directly to a Win update but it's the only thing that comes to mind.

Thanks for the help.

My pleasure!
Happy to hear it worked out for you .

 

[CurtisL]

Sorry, looks like even uninstalling the software didn't work. It's still BSoD's. I have attached the latest to the thread here, I know I said it's resolved so if need be I can start a new thread. I didn't have verifier running this time, I will have to turn it on and try again.

 

[YoYo155]

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an [COLOR=Red][U][B]I/O error[/B][/U][/COLOR] status of 0x%x.

BUGCHECK_STR:  0xF4_[U][B]IOERR[/B][/U]

FAILURE_BUCKET_ID:  X64_0xF4_[U][B][COLOR=Red]IOERR[/COLOR][/B][/U]_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_[COLOR=Red][U][B]IOERR[/B][/U][/COLOR]_IMAGE_csrss.exe

KERNEL_DATA_[COLOR=Red][U][B]INPAGE_ERROR[/B][/U][/COLOR] (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, [COLOR=RoyalBlue][U][B]0xC000009D [/B][/U][/COLOR]or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: [COLOR=RoyalBlue][U][B]ffffffffc000009d[/B][/U][/COLOR], error status (normally i/o status code)
Arg3: fffffa800363b078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

I advise checking the HDD;

Hard Drive Diagnostic Procedure - Yours will need Seagate SeaTools
​

SeaTools for Windows | Seagate​