Highlighted
Absent Member.
Absent Member.
8780 views

Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

Hi,

One user in our company is using Windows 7 x64 and is having a trouble with latest Novell Client. It seems that specific program we use here that accesses databases from network drive is capable of repeatedly producing BSOD's in ncfsd.sys. Normally everything works but as this user had to put the program through some more rigorous usage tests today, he got four identical BSOD's in duration of few hours.

What happened was that immediately after starting the program it sometimes hung on it's first database access attempt. It was seemingly random that the program would hung on any particular time and not on some other - usually it started up normally as it has done already for months on that same system. If it hung, OS and other programs continued to be responsive for a minute or two (Netware server was also accessible), and only then - always - the BSOD came.

The databases our program uses are of Clipper / Foxpro type (DBF).

I uploaded file Heigo_20110208.7z containing one of the minidumps to ftp.novell.com incoming folder, perhaps You can read something useful out of it. Other minidumps contain the same (bugcheck 0xd1, error in ncfsd.sys, checked with WinDbg).

Thanks!
Labels (1)
0 Likes
19 Replies
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

heigo <heigo@no-mx.forums.novell.com> wrote:

> I uploaded file Heigo_20110208.7z containing one of the minidumps to
> ftp.novell.com incoming folder, perhaps You can read something useful
> out of it. Other minidumps contain the same (bugcheck 0xd1, error in
> ncfsd.sys, checked with WinDbg).


The issue implied by the state shown in that mini-dump is an issue
currently reported and under investigation as Bug 652220. It happens
to be the same blue screen issue being reported by users of the
Autodesk Revit application.

There isn't any identified workaround or ETA for the fix yet, but
wanted to at least confirm that issue is reported and being
investigated. If you end up needing to contact Novell Support on the
issue, or simply intend to look for when a future Novell Client
release contains the fix, Bug 652220 is the reference to use.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
www.novell.com

Upgrade to OES Community
http://www.novell.com/communities/coolsolutions/upgradetooes/
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

Alan Adams;2073788 wrote:
heigo <heigo@no-mx.forums.novell.com> wrote:

> I uploaded file Heigo_20110208.7z containing one of the minidumps to
> ftp.novell.com incoming folder, perhaps You can read something useful
> out of it. Other minidumps contain the same (bugcheck 0xd1, error in
> ncfsd.sys, checked with WinDbg).


The issue implied by the state shown in that mini-dump is an issue
currently reported and under investigation as Bug 652220. It happens
to be the same blue screen issue being reported by users of the
Autodesk Revit application.

There isn't any identified workaround or ETA for the fix yet, but
wanted to at least confirm that issue is reported and being
investigated. If you end up needing to contact Novell Support on the
issue, or simply intend to look for when a future Novell Client
release contains the fix, Bug 652220 is the reference to use.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
NOVELL: Worldwide

Upgrade to OES Community
Upgrade to Open Enterprise Server | Novell User Communities


We have the same issue with Windows 7 32bit pro using the same Novell client accessing a Cobol application that run in a maped drive with Cobol DB. The Novell server is version 6.5
Please, we need an answer to this. Cant wait until future client releases to see if the bug has been solve..

Thanks.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

Alan, the bug you mentioned is allready included in the IR5
3. SYSTEM_SERVICE_EXCEPTION (0x3B) bugcheck using Autodesk Revit. (Bug 652220)

But my problem was not solved. Iam using the IR5 version.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

ryghar <ryghar@no-mx.forums.novell.com> wrote:

> Alan, the bug you mentioned is allready included in the IR5
> 3. SYSTEM_SERVICE_EXCEPTION (0x3B) bugcheck using Autodesk Revit. (Bug
> 652220)
>
> But my problem was not solved. Iam using the IR5 version.


Agreed; there were in fact changes checked in under Bug 652220 which
made it into IR5 to address a blue screen being seen in the Revit
usage scenario.

That change is reported to solve the issue according to some customer
reports, but it known to not be solving the issues for others.
Accordingly the Bug 652220 changes were left into the IR5 release (to
help those customers that it could), but the Bug 652220 issue itself
is still open and under investigation.

So the current status is still that we're looking for a future IR to
include another / further fix for Bug 652220.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
www.novell.com

Upgrade to OES Community
http://www.novell.com/communities/coolsolutions/upgradetooes/
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

I'm using Novell Client 2 SP1 for Windows 7 (IR8), and still having the BSOD pointing back to ncfsd.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED. Not sure if this is the exact same thing that's being addressed in the bug, but I can reproduce it. This is happening while using TreeSize Pro, and scanning against a SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10
PATCHLEVEL = 3 server in a single directory structure. (To clarify, it's not the directory structure that's causing the BSOD - it happens in different directory structures - My point is that I'm not starting at the root of the volume, rather, going down a couple of levels and starting there. There are in fact other subdirectories under where I'm starting.)

I have disabled file caching on my client. That didn't help.

Thanks,
Sam

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

I'm unable to edit my original message, but I wanted to add that I have several crash dumps of this happening, and can upload them if needed (the ones Windows generates upon a BSOD) if they would help. Since I can't add an attachment I'm unsure of where I can put them though.

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

On 9/7/2011 2:46 PM, samthendsgod wrote:
>
> I'm using Novell Client 2 SP1 for Windows 7 (IR8), and still having the
> BSOD pointing back to ncfsd.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED. Not
> sure if this is the exact same thing that's being addressed in the bug,
> but I can reproduce it. This is happening while using TreeSize Pro, and
> scanning against a SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10
> PATCHLEVEL = 3 server in a single directory structure. (To clarify,
> it's not the directory structure that's causing the BSOD - it happens in
> different directory structures - My point is that I'm not starting at
> the root of the volume, rather, going down a couple of levels and
> starting there. There are in fact other subdirectories under where I'm
> starting.)
>
> I have disabled file caching on my client. That didn't help.
>
> Thanks,
> Sam
>
>


What version of treesize pro. I've seen quite a few buggy ones that
crash in various ways scanning large volumes. The 5.5.2 however works
nicely. I've even run a duplicate search against 4TB volumes with no
issues with Win 7 sp1, client 2 sp1 ir8.



0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

hanks for the reply Grimlock. I was using an older version of Treesize (4.x). I just upgraded to 5.2.2. I've started a scan, and will let you know tomorrow if it makes it through this one directory structure.

Thanks
Sam

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

On 9/7/2011 4:26 PM, samthendsgod wrote:
>
> hanks for the reply Grimlock. I was using an older version of Treesize
> (4.x). I just upgraded to 5.2.2. I've started a scan, and will let you
> know tomorrow if it makes it through this one directory structure.
>
> Thanks
> Sam
>
>


5.2.2 or 5.5.2?


0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

grimlock;2135391 wrote:
On 9/7/2011 4:26 PM, samthendsgod wrote:
>
> hanks for the reply Grimlock. I was using an older version of Treesize
> (4.x). I just upgraded to 5.2.2. I've started a scan, and will let you
> know tomorrow if it makes it through this one directory structure.
>
> Thanks
> Sam
>
>


5.2.2 or 5.5.2?


My apologies...5.5.2. I kicked it off on its scan about two hours ago. So far so good. But yesterday it took about seven hours to crash. So we should know by morning. 🙂

Thank you again for your help Grimlock!
Sam

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Win7 x64 Novell Client 2 SP1 IR5 BSOD in ncfsd.sys

samthendsgod;2135398 wrote:
My apologies...5.5.2. I kicked it off on its scan about two hours ago. So far so good. But yesterday it took about seven hours to crash. So we should know by morning. 🙂

Thank you again for your help Grimlock!
Sam


Bad news - crashed again, same error code. I'm going to try disabling the AV on the PC and see if that helps, but I don't see how it would. It's worth a shot though.

(I'm not sure if any of this is of much help, but just in case):


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 9BF0E4E9
BCP3: 8DADE588
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

And from the coredump analysis tool I have ("whocrashed"):

On Thu 9/8/2011 1:56:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090711-15724-01.dmp
This was probably caused by the following module: ncfsd.sys (ncfsd+0x54E9)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9BF0E4E9, 0xFFFFFFFF8DADE588, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Program Files\Novell\Client\XTier\Drivers\ncfsd.sys
product: Novell® Client(TM) for Windows®
company: Novell, Inc.
description: Novell Client File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ncfsd.sys (Novell Client File System Driver, Novell, Inc.).
Google query: ncfsd.sys Novell, Inc. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Thu 9/8/2011 1:56:52 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ncfsd.sys (ncfsd+0x5B27)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF9BF0E4E9, 0xFFFFFFFF8DADE588, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Program Files\Novell\Client\XTier\Drivers\ncfsd.sys
product: Novell® Client(TM) for Windows®
company: Novell, Inc.
description: Novell Client File System Driver
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ncfsd.sys (Novell Client File System Driver, Novell, Inc.).
Google query: ncfsd.sys Novell, Inc. KERNEL_MODE_EXCEPTION_NOT_HANDLED


It always crashes twice, in case that's relevant.

Thanks
Sam

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.