BSOD on reboot

[joshmcc]

Hi, I keep getting a blue screen on reboot, but not until after the cache is significantly filled with several GB. Initial reboots are fine....

Primocache v1.01

Primary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff802`46a71000 PsLoadedModuleList = 0xfffff802`46d4a850
Debug session time: Fri Apr 17 01:56:21.055 2015 (UTC - 4:00)
System Uptime: 0 days 5:24:06.873
*******************************************************************************
* *
* 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: fffff8002ee12f92, The address that the exception occurred at
Arg3: ffffd000593cd7a8, Exception Record Address
Arg4: ffffd000593ccfb0, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

FAULTING_IP:
rxfcv+8f92
fffff800`2ee12f92 418a4818 mov cl,byte ptr [r8+18h]

EXCEPTION_RECORD: ffffd000593cd7a8 -- (.exr 0xffffd000593cd7a8)
ExceptionAddress: fffff8002ee12f92 (rxfcv+0x0000000000008f92)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000018
Attempt to read from address 0000000000000018

CONTEXT: ffffd000593ccfb0 -- (.cxr 0xffffd000593ccfb0)
rax=0000000000000000 rbx=ffffdff052e00000 rcx=0000000000000000
rdx=0000000001000034 rsi=ffffdff0538a4af0 rdi=ffffe00179bf60c0
rip=fffff8002ee12f92 rsp=ffffd000593cd9e0 rbp=ffffe001785fb820
r8=0000000000000000 r9=00000000017ab510 r10=ffffdff0450ad440
r11=0000000001000034 r12=ffffe00176600000 r13=ffffdff052e00200
r14=ffffdff052e00030 r15=ffffe001765fdc60
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
rxfcv+0x8f92:
fffff800`2ee12f92 418a4818 mov cl,byte ptr [r8+18h] ds:002b:00000000`00000018=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 1

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: 0000000000000018

READ_ADDRESS: fffff80246d38240: Unable to get special pool info
fffff80246d38240: Unable to get special pool info
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000018

FOLLOWUP_IP:
rxfcv+8f92
fffff800`2ee12f92 418a4818 mov cl,byte ptr [r8+18h]

BUGCHECK_STR: AV

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from ffffdff052e00000 to fffff8002ee12f92

STACK_TEXT:
ffffd000`593cd9e0 ffffdff0`52e00000 : ffffe001`785fb820 ffffdff0`52e00200 ffffe001`79bf60c0 ffffe001`78137040 : rxfcv+0x8f92
ffffd000`593cd9e8 ffffe001`785fb820 : ffffdff0`52e00200 ffffe001`79bf60c0 ffffe001`78137040 fffff802`46df832d : 0xffffdff0`52e00000
ffffd000`593cd9f0 ffffdff0`52e00200 : ffffe001`79bf60c0 ffffe001`78137040 fffff802`46df832d 00000000`00000000 : 0xffffe001`785fb820
ffffd000`593cd9f8 ffffe001`79bf60c0 : ffffe001`78137040 fffff802`46df832d 00000000`00000000 ffffd000`593cdad0 : 0xffffdff0`52e00200
ffffd000`593cda00 ffffe001`78137040 : fffff802`46df832d 00000000`00000000 ffffd000`593cdad0 ffffe001`78137180 : 0xffffe001`79bf60c0
ffffd000`593cda08 fffff802`46df832d : 00000000`00000000 ffffd000`593cdad0 ffffe001`78137180 00000000`00000000 : 0xffffe001`78137040
ffffd000`593cda10 fffff802`46df8184 : ffffe001`783a0830 00000000`00000001 ffffe001`78137040 ffffe001`78137040 : nt!IopShutdownBaseFileSystems+0x21
ffffd000`593cda90 fffff802`46dfc93a : fffff802`46dfc6c8 ffffe001`78137040 fffff802`46d23340 fffff802`46d23340 : nt!IoShutdownSystem+0x18c
ffffd000`593cdb10 fffff802`46b1e6bc : fffff802`46dfc6c8 fffff802`46d30c00 ffffe001`78137040 fffff802`46d23340 : nt!PopGracefulShutdown+0x272
ffffd000`593cdb50 fffff802`46b7136c : ffffc001`1c152c30 ffffe001`78137040 00000000`00000080 ffffe001`78137040 : nt!ExpWorkerThread+0x28c
ffffd000`593cdc00 fffff802`46bc82c6 : ffffd001`3a5dc180 ffffe001`78137040 ffffe001`7ce79880 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`593cdc60 00000000`00000000 : ffffd000`593ce000 ffffd000`593c8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: rxfcv+8f92

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: rxfcv

IMAGE_NAME: rxfcv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 534e987a

STACK_COMMAND: .cxr 0xffffd000593ccfb0 ; kb

FAILURE_BUCKET_ID: X64_AV_rxfcv+8f92

BUCKET_ID: X64_AV_rxfcv+8f92

Followup: MachineOwner

[InquiringMind]

Welcome to the forums Joshmcc,

Please include details on how you have configured PrimoCache (how much L1, L2, etc). Presumably you are referring to L2 cache in which case it may be worth checking that the SSD used is free of errors (remove the cache volume and run a chkdsk on it). Also check Event Viewer to see if it reports anything unusual at the time of the problem.

[Support]

@joshmcc,

Can you email the dump file to [email protected]? In additional, as InquiringMind said, we need your PrimoCache settings.
Thank you.

[joshmcc]

HI,
On the 22 may i sent the dump file and the requested information regarding primocache setup. Sorry for the delay - I had uninstalled the software and deleted the crash information. Later, I reinstalled primocache but was still getting the same BSOD error on reboot. I've tried removing some applications etc but cannot identify any conflicts. Just wondering if the dump file was analysed and if you were able to identify the issue.
I'm only using a 16 GB ssd card as L2 read cache for the system drive. The card has been scanned with no errors.

Thanks
Joshua McCosker

[Support]

@joshmcc,

We sent you an email to j***_m**[email protected]. Not sure if you have received it or not.

Thank you!

[joshmcc]

Hi,
Thanks for the email -

The SSD card I use is a Scandisk Extreme 16 GB

Laptop: HP Envy M6, i7, 8GB memory

L2 cache only: Max, 4KB

SSD card has been reformated scanned with no errors

Still get the BSOD on reboot - though not on every reboot. I have no HDD errors. I have run sfc/scannow and component store scans with no errors. When I remove the cache, I no longer get the blue screen errors on reboot.

Let me know if you need any further information

thanks - Joshua

[Support]

If you have time, could you try v2.0.0 to see if this issue still happen or not?
Many thanks!