Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - astuni

Pages: [1] 2 3
1
Today i had another BSOD on NZFSD.sys while stopping the array.

Windows version is still 1709 (Buld 16299.431), i don't know if it's related to the one occurring when updating to 1803 or not but i will attach the analysis for you just in case.

Code: [Select]
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 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
Machine Name:
Kernel base = 0xfffff803`a509e000 PsLoadedModuleList = 0xfffff803`a5404030
Debug session time: Sun Jun  3 15:44:55.017 2018 (UTC - 4:00)
System Uptime: 5 days 7:44:25.415
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffd584052ffcb8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80cde68b5a4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


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

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffd584052ffcb8

FAULTING_IP:
NZFSD+2b5a4
fffff80c`de68b5a4 3bb808030000    cmp     edi,dword ptr [rax+308h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  2

TRAP_FRAME:  fffffd8618c7d990 -- (.trap 0xfffffd8618c7d990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd584052ff9b0 rbx=0000000000000000 rcx=0000000000000001
rdx=ffffd584001571f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80cde68b5a4 rsp=fffffd8618c7db20 rbp=000000003b9aca04
 r8=fffffd8618c7db00  r9=ffffac806e760180 r10=0000000000000fff
r11=00000000000000a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
NZFSD+0x2b5a4:
fffff80c`de68b5a4 3bb808030000    cmp     edi,dword ptr [rax+308h] ds:ffffd584`052ffcb8=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff803a523faab to fffff803a5213570

STACK_TEXT: 
fffffd86`18c7d718 fffff803`a523faab : 00000000`00000050 ffffd584`052ffcb8 00000000`00000000 fffffd86`18c7d990 : nt!KeBugCheckEx
fffffd86`18c7d720 fffff803`a50ee43d : 00000000`00000000 ffffd584`052ffcb8 fffffd86`18c7d990 fffffd86`18c7d8c0 : nt!MiSystemFault+0x15302b
fffffd86`18c7d7c0 fffff803`a5221e42 : ffffc00f`8e40dd7f fffff803`a3890800 ffffd584`040ec1c0 ffffd584`040ec180 : nt!MmAccessFault+0x23d
fffffd86`18c7d990 fffff80c`de68b5a4 : ffffd584`040ec080 ffffd584`040ec3a0 00000000`00000000 ffffd583`ffc112e0 : nt!KiPageFault+0x382
fffffd86`18c7db20 ffffd584`040ec080 : ffffd584`040ec3a0 00000000`00000000 ffffd583`ffc112e0 00000000`00000000 : NZFSD+0x2b5a4
fffffd86`18c7db28 ffffd584`040ec3a0 : 00000000`00000000 ffffd583`ffc112e0 00000000`00000000 00000000`00000080 : 0xffffd584`040ec080
fffffd86`18c7db30 00000000`00000000 : ffffd583`ffc112e0 00000000`00000000 00000000`00000080 ffffd583`ff5f9c60 : 0xffffd584`040ec3a0


STACK_COMMAND:  kb

FOLLOWUP_IP:
NZFSD+2b5a4
fffff80c`de68b5a4 3bb808030000    cmp     edi,dword ptr [rax+308h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NZFSD+2b5a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NZFSD

IMAGE_NAME:  NZFSD.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5a15a5da

FAILURE_BUCKET_ID:  X64_AV_NZFSD+2b5a4

BUCKET_ID:  X64_AV_NZFSD+2b5a4

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

Wishing you an happy debugging :)
Thanks for your work on this amazing piece of software.

2
Thank you Brahim.

Do you have any ETA?

3
I can also add that by going back to the previous windows build (1709) using the recovery feature instantly fixed everything.

I really think there's something going on between flexraid transparent raid and that new windows 10 build.

Fyi my installed versions are as follows:



Transparent RAID - Home & Small Business License

OS: Microsoft Professional (build 9200), 64-bit
Broker: 1.1.0 2017.11.22
Kernel: 1.1.0 2017.11.22

Thanks again.


4
Hello there Brahim,
after updating to windows 10 build 1803 flexraid transparent raid does not start anymore the array, giving a bsod.

Here's the minidup analysis. Hope you can help.

Thanks

Code: [Select]
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 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`8f011000 PsLoadedModuleList = 0xfffff802`8f3ce1d0
Debug session time: Tue May 29 07:34:10.853 2018 (UTC - 4:00)
System Uptime: 0 days 0:03:31.549
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffcf8909a9e658, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80af66fb5a4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 000000000000000c, (reserved)

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


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

OVERLAPPED_MODULE: Address regions for 'srvnet' and 'dump_storpor' overlap

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffcf8909a9e658

FAULTING_IP:
NZFSD+2b5a4
fffff80a`f66fb5a4 3bb808030000    cmp     edi,dword ptr [rax+308h]

MM_INTERNAL_CODE:  c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  1

TRAP_FRAME:  fffffe87f91a3990 -- (.trap 0xfffffe87f91a3990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcf8909a9e350 rbx=0000000000000000 rcx=0000000000000001
rdx=ffffcf8910f7e1f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80af66fb5a4 rsp=fffffe87f91a3b20 rbp=000000003b9aca04
 r8=fffffe87f91a3b00  r9=0000000000000000 r10=ffffbe01844b79e0
r11=ffffcf890fa5b050 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
NZFSD+0x2b5a4:
fffff80a`f66fb5a4 3bb808030000    cmp     edi,dword ptr [rax+308h] ds:ffffcf89`09a9e658=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8028f1ecd39 to fffff8028f1a8670

STACK_TEXT: 
fffffe87`f91a36d8 fffff802`8f1ecd39 : 00000000`00000050 ffffcf89`09a9e658 00000000`00000000 fffffe87`f91a3990 : nt!KeBugCheckEx
fffffe87`f91a36e0 fffff802`8f0826d8 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb8dc`6e371b88 : nt!MiSystemFault+0x16eb89
fffffe87`f91a3820 fffff802`8f1b79c7 : 00000000`00000000 00000000`000001d4 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x1f8
fffffe87`f91a3990 fffff80a`f66fb5a4 : ffffcf89`14937700 ffffcf89`14937a20 ffffcf89`0fa5b0e0 ffffcf89`1064a2c0 : nt!KiPageFault+0x3c7
fffffe87`f91a3b20 ffffcf89`14937700 : ffffcf89`14937a20 ffffcf89`0fa5b0e0 ffffcf89`1064a2c0 00000000`00000000 : NZFSD+0x2b5a4
fffffe87`f91a3b28 ffffcf89`14937a20 : ffffcf89`0fa5b0e0 ffffcf89`1064a2c0 00000000`00000000 00000000`00000080 : 0xffffcf89`14937700
fffffe87`f91a3b30 ffffcf89`0fa5b0e0 : ffffcf89`1064a2c0 00000000`00000000 00000000`00000080 ffffcf89`0fbbcc60 : 0xffffcf89`14937a20
fffffe87`f91a3b38 ffffcf89`1064a2c0 : 00000000`00000000 00000000`00000080 ffffcf89`0fbbcc60 fffff80a`f66f942f : 0xffffcf89`0fa5b0e0
fffffe87`f91a3b40 00000000`00000000 : 00000000`00000080 ffffcf89`0fbbcc60 fffff80a`f66f942f ffffcf89`0fa5b050 : 0xffffcf89`1064a2c0


STACK_COMMAND:  kb

FOLLOWUP_IP:
NZFSD+2b5a4
fffff80a`f66fb5a4 3bb808030000    cmp     edi,dword ptr [rax+308h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NZFSD+2b5a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NZFSD

IMAGE_NAME:  NZFSD.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5a15a5da

FAILURE_BUCKET_ID:  X64_AV_NZFSD+2b5a4

BUCKET_ID:  X64_AV_NZFSD+2b5a4

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

5
tRAID on Windows / Anyone upgraded to Windows 10 build 1803?
« on: May 29, 2018, 12:44:33 am »
Unfortunately the system forced the update past night and today I get a bsod while trying to start the array.

I’ve already tried to uninstall and reinstall transparent raid without success.
May I send you something like the mini dump to try to find a reason?


Inviato dal mio iPhone utilizzando Tapatalk

6
tRAID on Windows / Re: Anyone upgraded to Windows 10 build 1803?
« on: May 22, 2018, 11:51:09 pm »
Thanks, I will pull the trigger during the weekend!

7
tRAID on Windows / Anyone upgraded to Windows 10 build 1803?
« on: May 09, 2018, 01:00:51 am »
Hello there, anyone upgraded yet? Any problem bless with flexraid traid?

Just wanted to be sure before pulling the trigger...

Thanks

8
Thanks, i just managed to activate again.

Thanks for the prompt support!

9
Hello there Brahim,
i have just reinstalled my system on a fresh windows installation on a brand new ssd, i then installed FlexRaid Traid to bring back up my array but i can't seem to be able to connect to https://secure.flexraid.com for activation.

I have also emailed you at sales address to let you check out my purchase code.

Hope i can get this back up soon.

Thank You.
Giorgio

10
Thanks Brahim, and regarding backup products, is acronis safe to use on a tRAID server too (i've read the issues with paragon wondering if acronis is ok)?

11
Hello there,
i'm using default windows 10 defender right now but i'm aiming on a more robust protection, there's any recommendation about using anti viruses on machines with tRAID configurations running?

Thanks

12
Cool, i will hold on this then, thanks.

13
tRAID on Windows / Is it safe to upgrade to newest Windows 10 build (1511)?
« on: December 29, 2015, 02:32:45 am »
I am currently running latest tRAID off a Windows 10 build 10240 installation.

Is it safe to upgrade it to the latest build in subject?

Should i take some actions before doing it?

Thanks!

14
Ok more news:

The array built the parity without errors, however as soon as i started it after parity creation the webui log throwed the RPC error again for the first time and now it's permanent on every boot.
The storage pool starts without problems and gets mounted at the right letter (V) BUT if i stop it windows complains in the event viewer about all the transparent disks being surprise removed.

I believe these are a couple of issues you should look at.

I am attaching the logs, there were a couple of trace lines too because once installed i've switched it to trace level, then i switched back to warn.
I think overall it's working ok now, tell me if you feel i could do something else to test those issues out.

Thanks

15
Done, worked like a charm. I'll leave it building, good night.

I will investigate on the media card reader issue, later tomorrow.

Pages: [1] 2 3