Rapidboot Error in Event Viewer

[EverThunder]

Folks - I am getting the following persistent error in Event Viewer on my brand new x220:

Faulting application name: HyperW7Svc64.exe, version: 1.0.0.1, time stamp: 0x4cf5de0b
Faulting module name: HyperW7Svc64.exe, version: 1.0.0.1, time stamp: 0x4cf5de0b
Exception code: 0xc0000005
Fault offset: 0x000000000000d248
Faulting process id: 0x35c
Faulting application start time: 0x01cc1678fdbedc11
Faulting application path: C:\Program Files\Lenovo\RapidBoot\HyperW7Svc64.exe
Faulting module path: C:\Program Files\Lenovo\RapidBoot\HyperW7Svc64.exe
Report Id: 41b6ea8b-826c-11e0-af33-f0def15ccf15

Would appreciate any thoughts.  Thanks.

[gan Guru]

What is the model/type of your X220 (xxxx-yyy)?

Also are you using the Lenovo pre-installed Windows or is it a clean install?

Do you use Windows 7 with SP1 or without SP1?

You could try to uninstall and reinstall the rapidboot software and see if that makes a difference.

http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-77013

-gan

[EverThunder]

Gan - Per your suggestion, I tried to proactively uninstall Rapidboot before reinstalling from the link you provided.

Result: I BSOD'ed upon trying to uninstall Rapidboot from the Programs/Features window.  Contents of the minidump file analyzer are below.  At a high level, it appears that the PHCORE64.SYS (whatever that is) driver was unloaded without cancelling pending operations.

Thoughts?

My computer has Lenovo preinstalled Windows.  Specifics of my config is as follows:

Microsoft 7 Home Premium

Version 6.1.7601 Service Pack 1 Build 7601

System Model 4286CTO

x64-based PC

Core i5-2410M

Bios 1.1

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck CE, {fffff8800f226cac, 8, fffff8800f226cac, 0}

Probably caused by : PHCORE64.SYS ( PHCORE64+1cac )

Followup: MachineOwner

---------

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)

A driver unloaded without cancelling timers, DPCs, worker threads, etc.

The broken driver's name is displayed on the screen.

Arguments:

Arg1: fffff8800f226cac, memory referenced

Arg2: 0000000000000008, value 0 = read operation, 1 = write operation

Arg3: fffff8800f226cac, If non-zero, the instruction address which referenced the bad memory

                address.

Arg4: 0000000000000000, Mm internal code.

Debugging Details:

------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003105100

 fffff8800f226cac

FAULTING_IP:

PHCORE64+1cac

fffff880`0f226cac ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xCE

PROCESS_NAME:  HyperW7Svc64.e

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ca7f760 -- (.trap 0xfffff8800ca7f760)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff8800f226cac rbx=0000000000000000 rcx=0000000000001778

rdx=00000000000015b8 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8800f226cac rsp=fffff8800ca7f8f8 rbp=0000000000000001

 r8=0000000000000000  r9=0000000000000000 r10=fffffa8007d2a900

r11=fffff8800ca7f8a0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

<Unloaded_PHCORE64.SYS>+0x1cac:

fffff880`0f226cac ??              ???

Resetting default scope

IP_MODULE_UNLOADED:

PHCORE64+1cac

fffff880`0f226cac ??              ???

LAST_CONTROL_TRANSFER:  from fffff80002e81a0c to fffff80002ed5d00

STACK_TEXT: 

fffff880`0ca7f5f8 fffff800`02e81a0c : 00000000`00000050 fffff880`0f226cac 00000000`00000008 fffff880`0ca7f760 : nt!KeBugCheckEx

fffff880`0ca7f600 fffff800`02ed3e2e : 00000000`00000008 fffff880`0f226cac fffffa80`09e35500 fffffa80`0998e630 : nt! ?? ::FNODOBFM::`string'+0x4621f

fffff880`0ca7f760 fffff880`0f226cac : fffff800`0318e3de fffffa80`0998e630 fffff8a0`000a2b70 fffffa80`0998e630 : nt!KiPageFault+0x16e

fffff880`0ca7f8f8 fffff800`0318e3de : fffffa80`0998e630 fffff8a0`000a2b70 fffffa80`0998e630 fffffa80`05d3c920 : <Unloaded_PHCORE64.SYS>+0x1cac

fffff880`0ca7f900 fffff800`031ab189 : 000007ff`fffdc000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x156

fffff880`0ca7f960 fffff800`0318e87c : 00000000`00000000 00000000`00000001 000007ff`fffdc000 00000000`00000000 : nt!PspExitThread+0x4e9

fffff880`0ca7fa60 fffff800`02ed4f93 : fffffa80`0998e630 000007fe`00000000 fffffa80`09089b60 000007fe`ff1726c8 : nt!NtTerminateProcess+0x138

fffff880`0ca7fae0 00000000`77a215da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`001ffd58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a215da

STACK_COMMAND:  kb

FOLLOWUP_IP:

PHCORE64+1cac

fffff880`0f226cac ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  PHCORE64+1cac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PHCORE64

IMAGE_NAME:  PHCORE64.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0xCE_PHCORE64+1cac

BUCKET_ID:  X64_0xCE_PHCORE64+1cac

Followup: MachineOwner

---------

[someotherguy]

EverThunder,

I'm very sorry about these issues you're having with the RapidBoot software.  It seems that the event viewer error and blue-screen error are separate issues. 

For the event viewer problem, may I please ask what software you have installed on your ThinkPad since you received it?  I suspect that maybe RapidBoot is incompatibile with some other piece of software that you have installed, and we'll need to update RapidBoot accordingly.  Did you happen to notice when this error in Event Viewer started to occur?  Could you please post a list of software installed on your system by using the following steps:

1.  run a command prompt as administrator

2.  in the command prompt, type "wmic"

3.  then type "/output:c:\installlist.txt product get name,version"   (this may take a couple minutes to execute)

4.  type "exit" to leave the wmic environment

5.  copy the contents of c:\installlist.txt to the forum or else please send it to me in a private message

For the blue screen issue during uninstall, the RapidBoot software will be updated soon to fix that.

Thanks for your help!

[EverThunder]

Someotherdude  - Thanks for chiming in.  PM sent to you.

[EverThunder · Accepted solution]

I was able to resolve this issue and the PHCORE (Rapidboot driver) error no longer appears upon boot in Event Viewer.

I noticed that when Rapidboot's executable file (HYPERW764) BSOD'ed, both Superfetch and VSS became disabled in the Services - a big no-no.   After re-enabling Superfetch and VSS, I was able to successfully uninstall and reinstall Rapidboot.

I believe the root cause may have been one of my antivirus programs (MSE or Malwarebytes), and since uninstalling them and installing ESET, I have had no issues with Rapidboot.

[gan Guru]

Glad to hear you found a solution and solved the problem.

-gan

[someotherguy]

EverThunder,

Thanks for following up.  I sent you a private message a few days ago, I wonder if you saw it?

I guess it does not matter now since you are no longer having the issue, but please let me know if you start seeing similar event viewer entries in the future so hopefully we can get to the bottom of it.  Thanks and sorry again for the trouble.

[EverThunder]

Yeah, I'm just getting used to using the forums, so I did not see your PM.

Glad this thing is resolved. I hate having a brand new computer with something awry.

[mwauki]

I have a Lenovo Thinkpad T420s, and it just started booting up very slow often times i had to forceshutdown, bootup in safe mode, shutdown normally then it goes normal. and in the event viewer logs, i see that hyperW7svc64.exe often... is this possibly what causing my issue?