Romex Software Forum

Posted: **Fri Aug 16, 2013 10:11 pm**

Looks like between PerfectDisk (PDEngine.exe) and PrimoCache (rxfcv.sys), there might be a little trouble trying to get along. I see a mention of Acronis (snapman.sys) but it just looks like it couldn't load the debugging symbols for it. Unfortunately, whatever caused this BSOD seems to have prevented the complete memory dump from being written, so I only have the MiniDump... Also, as a side note, the extension "dmp" is not allowed when uploading attachments...

Code: Select all

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081113-38157-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*O:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22280.amd64fre.win7sp1_ldr.130318-1534
Machine Name:
Kernel base = 0xfffff800`03860000 PsLoadedModuleList = 0xfffff800`03aa4670
Debug session time: Sat Aug 10 21:35:21.027 2013 (UTC - 7:00)
System Uptime: 7 days 23:27:36.685
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image rxfcv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rxfcv.sys
*** ERROR: Module load completed but symbols could not be loaded for rxfcv.sys
Unable to load image snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : rxfcv.sys ( rxfcv+9423 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6239643839303063
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  PDEngine.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff8813495db38 -- (.exr 0xfffff8813495db38)
ExceptionAddress: fffff88001f6f423 (rxfcv+0x0000000000009423)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038

TRAP_FRAME:  fffff8813495dbe0 -- (.trap 0xfffff8813495dbe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8019ac3cc0
rdx=fffff88076800000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001f6f423 rsp=fffff8813495dd70 rbp=0000000000000000
 r8=fffffa800f7e1b40  r9=00000000ffffffff r10=fffff80003860000
r11=fffff88076800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
rxfcv+0x9423:
fffff880`01f6f423 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800038ca07e to fffff800038d2650

STACK_TEXT:  
fffff881`3495cc18 fffff800`038ca07e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`0392a44b : nt!KeBugCheck
fffff881`3495cc20 fffff800`038fe16d : fffff800`03ae32c8 fffff800`03a260d4 fffff800`03860000 fffff881`3495db38 : nt!KiKernelCalloutExceptionHandler+0xe
fffff881`3495cc50 fffff800`038fcf45 : fffff800`03a260cc fffff881`3495ccc8 fffff881`3495db38 fffff800`03860000 : nt!RtlpExecuteHandlerForException+0xd
fffff881`3495cc80 fffff800`0390dee1 : fffff881`3495db38 fffff881`3495d390 fffff881`00000000 fffffa80`19ac3cc0 : nt!RtlDispatchException+0x415
fffff881`3495d360 fffff800`038d1d02 : fffff881`3495db38 fffff881`38c5c700 fffff881`3495dbe0 fffffa80`132959e0 : nt!KiDispatchException+0x135
fffff881`3495da00 fffff800`038d087a : 00000000`00000000 00000000`00000038 fffff800`03a51e00 fffff881`38c5c700 : nt!KiExceptionDispatch+0xc2
fffff881`3495dbe0 fffff880`01f6f423 : fffff881`38c5c700 fffffa80`132959e0 fffffa80`0f7dca90 fffff880`024742cc : nt!KiPageFault+0x23a
fffff881`3495dd70 fffff881`38c5c700 : fffffa80`132959e0 fffffa80`0f7dca90 fffff880`024742cc fffffa80`0f7e1b40 : rxfcv+0x9423
fffff881`3495dd78 fffffa80`132959e0 : fffffa80`0f7dca90 fffff880`024742cc fffffa80`0f7e1b40 fffffa80`0f7e1a50 : 0xfffff881`38c5c700
fffff881`3495dd80 fffffa80`0f7dca90 : fffff880`024742cc fffffa80`0f7e1b40 fffffa80`0f7e1a50 00000000`00000000 : 0xfffffa80`132959e0
fffff881`3495dd88 fffff880`024742cc : fffffa80`0f7e1b40 fffffa80`0f7e1a50 00000000`00000000 00000002`00000000 : 0xfffffa80`0f7dca90
fffff881`3495dd90 fffffa80`0f7e1b40 : fffffa80`0f7e1a50 00000000`00000000 00000002`00000000 00000000`00000000 : snapman+0x202cc
fffff881`3495dd98 fffffa80`0f7e1a50 : 00000000`00000000 00000002`00000000 00000000`00000000 fffff880`01f716c5 : 0xfffffa80`0f7e1b40
fffff881`3495dda0 00000000`00000000 : 00000002`00000000 00000000`00000000 fffff880`01f716c5 00000000`00000000 : 0xfffffa80`0f7e1a50


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rxfcv+9423
fffff880`01f6f423 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  rxfcv+9423

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rxfcv

IMAGE_NAME:  rxfcv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51f20d1f

FAILURE_BUCKET_ID:  X64_0x1E_0_rxfcv+9423

BUCKET_ID:  X64_0x1E_0_rxfcv+9423

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

Posted: **Sat Aug 17, 2013 12:59 am**

Thank you for the feedback! We'll anaylze the dump file soon.

PS. The reason why Windows failed to create a complete memory dump is possibly that there is no enough space on windows partition.

Posted: **Thu Sep 12, 2013 8:32 pm**

I have experienced this a few times. Because I did not enable the dump, I can offer no details.

The following is my system:

Intel 960 CPU running at 3.02 with 12G memory running at 1600 M.

SSD is OCZ 60G Vertex 2. Using the whole disk as 2-level. First level is 120M.
PrimoCache was enabled with 4K block LRU replacement for Read only.

After the filechk, there is a few snapshot file each 2M created. I am not sure if this is related but I deleted all of them.

Posted: **Fri Sep 13, 2013 12:35 am**

Motherboard is ASUS Sabertooth x58.
OS is Windows 7 64bit

Posted: **Fri Sep 13, 2013 12:37 am**

Motherboard is ASUS Sabertooth x58.
OS is Windows 7 64bit

Posted: **Tue Sep 24, 2013 4:11 pm**

I am also having this error with PrimoCache semi regularly (once a week or so) usually when the computer is left alone for 10+ mins but also a couple of times when in use, I have paused caching (lvl1 64MB and lvl2 100GB) and I have not had any problems.

Win 8 64Bit
PrimoCache 4KB Block, LFU-R, Read-Only and 64MB/100GB lvl 2 on a samsung 840 120GB SSD.

I7 920, 12GB Ram, Asus P5T, 3TB Hdd split into 2Tb and 1TB to work with old firmware, caching the 2TB C: partition, I also have 2 320GB hdd's running in raid 1 using intel RST matrix software raid but uncached.

I have a full memory dump as well but it is 1GB so not attaching.

Posted: **Wed Sep 25, 2013 6:39 am**

Disk defragment software might cause incompatible issue with level-2 cache. When source disk is defraged, the cache content stored in level-2 cache might not get notified, leading to out of sync with source disk.

Posted: **Sat Oct 26, 2013 9:58 am**

Well, this crash seems to have happened again, but this time without PerfectDisk installed. I don't have the full dump, unfortunately. I realized I had neglected to make my pagefile larger when I upgraded to 16GB of RAM, so I think that's why it couldn't be written.
Here is the minidump:

Code: Select all

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\102613-45552-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*O:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22411.amd64fre.win7sp1_ldr.130801-1934
Machine Name:
Kernel base = 0xfffff800`0385b000 PsLoadedModuleList = 0xfffff800`03a9f6d0
Debug session time: Sat Oct 26 02:09:54.213 2013 (UTC - 7:00)
System Uptime: 29 days 3:01:44.000
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image rxfcv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rxfcv.sys
*** ERROR: Module load completed but symbols could not be loaded for rxfcv.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880017de3d5, fffff880038aea78, fffff880038ae2d0}

Probably caused by : rxfcv.sys ( rxfcv+43d5 )

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880017de3d5, The address that the exception occurred at
Arg3: fffff880038aea78, Exception Record Address
Arg4: fffff880038ae2d0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
rxfcv+43d5
fffff880`017de3d5 488b8800030000  mov     rcx,qword ptr [rax+300h]

EXCEPTION_RECORD:  fffff880038aea78 -- (.exr 0xfffff880038aea78)
ExceptionAddress: fffff880017de3d5 (rxfcv+0x00000000000043d5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000440
Attempt to read from address 0000000000000440

CONTEXT:  fffff880038ae2d0 -- (.cxr 0xfffff880038ae2d0)
rax=0000000000000140 rbx=fffffa800d84ce88 rcx=fffffa800d84cd90
rdx=fffffa800d84cd90 rsi=fffffa800d84cd40 rdi=fffffa800d89cb90
rip=fffff880017de3d5 rsp=fffff880038aecb0 rbp=fffffa80181ec220
 r8=0000000080080001  r9=fffffa800da20f40 r10=0000000000000100
r11=fffff880038aec20 r12=fffffa800d84cd40 r13=fffff880017de2cc
r14=0000000000000000 r15=fffff880009d3040
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
rxfcv+0x43d5:
fffff880`017de3d5 488b8800030000  mov     rcx,qword ptr [rax+300h] ds:002b:00000000`00000440=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000440

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b09100
 0000000000000440 

FOLLOWUP_IP: 
rxfcv+43d5
fffff880`017de3d5 488b8800030000  mov     rcx,qword ptr [rax+300h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffffa800d84ce88 to fffff880017de3d5

STACK_TEXT:  
fffff880`038aecb0 fffffa80`0d84ce88 : fffffa80`181ec220 fffffa80`0d84cd40 fffffa80`0d84cd40 fffff880`038aed50 : rxfcv+0x43d5
fffff880`038aecb8 fffffa80`181ec220 : fffffa80`0d84cd40 fffffa80`0d84cd40 fffff880`038aed50 fffff800`039dbeee : 0xfffffa80`0d84ce88
fffff880`038aecc0 fffffa80`0d84cd40 : fffffa80`0d84cd40 fffff880`038aed50 fffff800`039dbeee ffffffff`fff0bdc0 : 0xfffffa80`181ec220
fffff880`038aecc8 fffffa80`0d84cd40 : fffff880`038aed50 fffff800`039dbeee ffffffff`fff0bdc0 00000000`00000000 : 0xfffffa80`0d84cd40
fffff880`038aecd0 fffff880`038aed50 : fffff800`039dbeee ffffffff`fff0bdc0 00000000`00000000 fffffa80`0d84cf08 : 0xfffffa80`0d84cd40
fffff880`038aecd8 fffff800`039dbeee : ffffffff`fff0bdc0 00000000`00000000 fffffa80`0d84cf08 fffff880`038aed00 : 0xfffff880`038aed50
fffff880`038aece0 fffff800`03b6e6ee : 00000000`fffff880 fffff880`fffff880 fffff880`00000000 00000000`00000140 : nt!EtwTraceContextSwap+0xae
fffff880`038aed40 fffff800`038bef26 : fffff880`009ce180 fffffa80`0fa8b0d0 fffff880`009d90c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`038aed80 00000000`00000000 : fffff880`038af000 fffff880`038a9000 fffff880`038aea00 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  rxfcv+43d5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rxfcv

IMAGE_NAME:  rxfcv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51f20d1f

STACK_COMMAND:  .cxr 0xfffff880038ae2d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_rxfcv+43d5

BUCKET_ID:  X64_0x7E_rxfcv+43d5

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

Posted: **Sat Oct 26, 2013 11:34 am**

Hi Zzyzx,

You might upload an old dump file...The dump file name as you wrote shall be 102613-45552-01.dmp.

PS. We have found a fatal bug in Level-2 cache which will cause some unexpected errors. And we reviewed all dump files in this topic and found that issues reported here are eaxctly caused by this bug. We'll make an quick update to fix it.
Thanks.

Posted: **Tue Oct 29, 2013 2:11 am**

We made a fix (version 0.9.2) for this issue. Please see
viewtopic.php?f=32&p=6023

Thank you all!

Romex Software Forum

rxfcv.sys BSOD - PerfectDisk Related?

rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?

Re: rxfcv.sys BSOD - PerfectDisk Related?