Win8x64 boot freezes

vbimport

#1

Win8x64, fully patched at Phenom x4, 8gb.
I had 2.1.0.2 installed on my rid for several months. I didn’t use it though (didn’t needed as all virtual machines fit on a single SSD).
Lately I decided to give it a run. I tried several time to accelerate simple ntfs formatted non-system volume, but without any success. Every time I got stuck at boot (at circling dots). The system didn’t bsod, but stay in this state indefinetely (just dots stop circling after half an hour or so).

Uninstall/install resulted in no improvement (just lost my activation).

NB: It looks like Elitebytes filter drive is not getting removed upon uninstalled properly. At least, driver event tab doesn’t show recent unistall/install event. I will try manual driver uninstall & reinstall app.


#2

Update:
I manually removed leftover Velossd 2012 driver, which leftover after installation, reinstalled software, but the problem persists.

NB: The system is a really minimalistic (by my standards:rolleyes:) setup with just a dozen third party software being install on top of the vanilla Windows.


#3

You are trying to cache a non boot volume ?

When rebooting your system freezes ?

What SSD do you use, is its firmware uptodate ?

Does that SSD had freeze issues in the past ? ( please specify SSD Brand )

Caching a non boot volume works normally with no problems.


#4
  1. I’m caching non-boot volume. I believe it should be simpler than boot volume.
  2. Win 8 freezes on logo (with circling dots).
  3. OCZ Agility 3 with latest firmware.
  4. The SSD is fine. I’m using it for other purposes without any issues. Everytime (3 times) I resolved the problem with system restore, so this is purely software issue.

I will gladly provide logs if it would help.


#5

So the SSD works just fine and never freezes.
We believe you, although google brings 60000 hits for OCZ Agility 3 freeze.

We will test a non boot volume on Win 8 and report our findings.
2.1.0.2 has been all tested through and no issues are known.

Is there any special configuration we need to apply like relocated folders ?


#6

[QUOTE=EliteBytes;2704162]So the SSD works just fine and never freezes.
We believe you, although google brings 60000 hits for OCZ Agility 3 freeze.

We will test a non boot volume on Win 8 and report our findings.
2.1.0.2 has been all tested through and no issues are known.

Is there any special configuration we need to apply like relocated folders ?[/QUOTE]

  1. You are correct. Sandforce based SSD can cause freezes under certain circumstances. I had this kind of problems several times. I know how these freezes looks like. The drive simply vanish from BIOS. In this case, the symptoms are not even close.

Just to close this issue. I will try to reproduce the issue with another ssd.

  1. The NTFS is dynamic, if it is of any importance to you.

#7

Actually another ssd resulted in a bit different experience:
SSD is Silicon Power V20, which is based on previous generation of SandForce controller (http://www.thessdreview.com/our-reviews/silicon-power-velox-v20-60gb-sata-2-ssd-review-using-a-different-flavor-in-nand-flash-memory/).
I’ve managed to add cache, run some test remove cache. Few seconds after flushing write-back cache, Windows threw a BSOD. I’ve attached a minidump for your convenience.
Indeed, you shall create HCL for VeloSSD. Agility 3, probably, shall not be recommended:(. Yet my Velossd setup is still broken.

101313-19921-01.zip (24.5 KB)


#8

bump
Is there any update?


#9

Its a Vista OS BSOD comes from snapman.sys ( part of OS ).
The BC Code is: PFN_LIST_CORRUPT (4e)
( see blow )
Listen please: this is not from VeloSSD ok ?

AULTING_MODULE: fffff801eda08000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 50f6aea6

BUGCHECK_STR: 0x4E_9a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff801edb96fdf to fffff801eda62440

STACK_TEXT:
fffff88002d1b118 fffff801edb96fdf : 000000000000004e 000000000000009a 0000000000232c6f 0000000000000006 : nt+0x5a440
fffff88002d1b120 000000000000004e : 000000000000009a 0000000000232c6f 0000000000000006 0000000000000002 : nt+0x18efdf
fffff88002d1b128 000000000000009a : 0000000000232c6f 0000000000000006 0000000000000002 fffff801edc7810e : 0x4e
fffff88002d1b130 0000000000232c6f : 0000000000000006 0000000000000002 fffff801edc7810e fffffa800bfaf8a0 : 0x9a
fffff88002d1b138 0000000000000006 : 0000000000000002 fffff801edc7810e fffffa800bfaf8a0 fffff801edab0f8c : 0x232c6f
fffff88002d1b140 0000000000000002 : fffff801edc7810e fffffa800bfaf8a0 fffff801edab0f8c fffffa8006e6cb20 : 0x6
fffff88002d1b148 fffff801edc7810e : fffffa800bfaf8a0 fffff801edab0f8c fffffa8006e6cb20 fffff88000bbd370 : 0x2
fffff88002d1b150 fffffa800bfaf8a0 : fffff801edab0f8c fffffa8006e6cb20 fffff88000bbd370 fffffa800b2aa640 : nt+0x27010e
fffff88002d1b158 fffff801edab0f8c : fffffa8006e6cb20 fffff88000bbd370 fffffa800b2aa640 0000000000000000 : 0xfffffa800bfaf8a0 fffff88002d1b160 fffffa8006e6cb20 : fffff88000bbd370 fffffa800b2aa640 0000000000000000 fffff88002d00000 : nt+0xa8f8c fffff88002d1b168 fffff88000bbd370 : fffffa800b2aa640 0000000000000000 fffff88002d00000 0000000000000801 : 0xfffffa8006e6cb20
fffff88002d1b170 fffffa800b2aa640 : 0000000000000000 fffff88002d00000 0000000000000801 000000020b2a9470 : snapman+0x33370
fffff88002d1b178 0000000000000000 : fffff88002d00000 0000000000000801 000000020b2a9470 fffffa800dc8d000 : 0xfffffa80`0b2aa640

STACK_COMMAND: kb

FOLLOWUP_IP:
snapman+33370
fffff880`00bbd370 ?? ???

SYMBOL_STACK_INDEX: b

SYMBOL_NAME: snapman+33370

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: snapman.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

3: kd> .reload
Loading Kernel Symbols



Loading User Symbols
Loading unloaded module list

3: kd> !analyze -v


  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a,
Arg2: 0000000000232c6f
Arg3: 0000000000000006
Arg4: 0000000000000002

Debugging Details:

BUGCHECK_STR: 0x4E_9a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff801edb96fdf to fffff801eda62440

STACK_TEXT:
fffff88002d1b118 fffff801edb96fdf : 000000000000004e 000000000000009a 0000000000232c6f 0000000000000006 : nt!KeBugCheckEx
fffff88002d1b120 fffff801edab0f8c : fffffa8006e6cb20 fffff88000bbd370 fffffa800b2aa640 0000000000000000 : nt!MiBadRefCount+0x4f
fffff88002d1b160 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!MiInsertNonPagedPoolOnSlist+0x390

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiBadRefCount+4f
fffff801`edb96fdf cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiBadRefCount+4f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 51a966cd

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x4E_9a_nt!MiBadRefCount+4f

BUCKET_ID: X64_0x4E_9a_nt!MiBadRefCount+4f

Followup: MachineOwner


#10

Ups, you are write. This is from Acronis.
It just agreed in time with cache removal…
Probably, we shall officially blame Agility 3.