6.1.4 crashes with Windows 10 build 14295

Started by anthonyb

6.1.4 crashes with Windows 10 build 14295   02 April 2016, 15:55

Recently updated my build of Windows 10 x64 to 14295 and Network Scanner 6.1.4 has become quite unstable and crashes frequently. Sometime after startup (but before any interaction), sometimes during a scan, sometimes after 2-3 scans.

Error logged in the Windows Application event Log is

Event ID 1000
Faulting application name: netscan.exe, version: 6.1.4.0, time stamp: 0x56ef692d
Faulting module name: ntdll.dll, version: 10.0.14295.1000, time stamp: 0x56ecd09b
Exception code: 0xc0000374
Fault offset: 0x00000000000f3be8
Faulting process ID: 0x261c
Faulting application start time: 0x01d18c9a253c76b3
Faulting application path: D:\Storage\netscan.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: fbaced9b-5522-4ac5-b070-78141250f9a1
Faulting package full name: 
Faulting package-relative application ID:

Event ID 1001
Fault bucket 120441662452, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: netscan.exe
P2: 6.1.4.0
P3: 56ef692d
P4: StackHash_5d16
P5: 10.0.14295.1000
P6: 56ecd09b
P7: c0000374
P8: PCH_6A_FROM_ntdll+0x00000000000A1F54
P9: 
P10: 
SoftPerfect Support forum - Andrew avatar image

Re: 6.1.4 crashes with Windows 10 build 14295   02 April 2016, 18:17

It may be a Windows issue as the crash occurs in NTDLL.DLL, but nonetheless try this debug build. If the crash occurs again, it should produce a bug report in the same folder.

Re: 6.1.4 crashes with Windows 10 build 14295   03 April 2016, 13:21

Does it matter that I'm using the 64-bit version of Network Scanner and the debug build is 32-bit?

Initial two runs haven't produced any crashes so far...
SoftPerfect Support forum - Andrew avatar image

Re: 6.1.4 crashes with Windows 10 build 14295   03 April 2016, 13:30

May be, here is the 64-bit build.

Re: 6.1.4 crashes with Windows 10 build 14295   03 April 2016, 13:34

Thanks, will give it a crack!

Re: 6.1.4 crashes with Windows 10 build 14295   05 April 2016, 08:43

Quote

Andrew

It may be a Windows issue as the crash occurs in NTDLL.DLL, but nonetheless try this debug build. If the crash occurs again, it should produce a bug report in the same folder.


So I'm getting crashes, but not finding a bug report in the folder I'm running the netscan.exe from. What would the file name be?
SoftPerfect Support forum - Andrew avatar image

Re: 6.1.4 crashes with Windows 10 build 14295   05 April 2016, 09:53

It should be bugreport.txt, also there should be a window shown similar to this:

SoftPerfect support forum

Re: 6.1.4 crashes with Windows 10 build 14295   05 April 2016, 17:07

OK, not getting that. When it crashes I just get this:

SoftPerfect support forum

The Debug option then fires up Visual Studio on my PC.
Closes just, well, closes it.
SoftPerfect Support forum - Andrew avatar image

Re: 6.1.4 crashes with Windows 10 build 14295   05 April 2016, 18:54

It turns out error 0xc0000374 is heap corruption and it occurs deep down in NTDLL.DLL. That's why it wasn't intercepted by our bug-reporting code.

I have googled and found another guy who received exactly the same error with Skype.

At this stage I am not sure what it is and what causes it, perhaps you should try Network Scanner on another computer. So far it looks to me like a Windows issue.

Re: 6.1.4 crashes with Windows 10 build 14295   05 April 2016, 21:12

Yeah... that's what I was seeing (heap corruption) when I did open and perform a rudimentary debug in Visual Studio.
Will feed it back through the Feedback tool and hope that newer Windows builds resolve the issue!
SoftPerfect Support forum - Andrew avatar image

Re: 6.1.4 crashes with Windows 10 build 14295   06 April 2016, 10:34

It just occurred to me that Windows 10.0.14295 is a preview of Redstone 1 release of Windows 10, which simply put is a beta version.

Not surprisingly things don't work as expected.

Re: 6.1.4 crashes with Windows 10 build 14295   07 April 2016, 21:01

..on the upside, just updated to Build 14316 today and so far (touch wood) no crashes!

Sometimes you can get the answer faster if you try the forum search and/or have a look at the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

 **    **  **    **   ******    *******   ********  
 **   **    **  **   **    **  **     **  **     ** 
 **  **      ****    **        **     **  **     ** 
 *****        **     **         ********  ********  
 **  **       **     **               **  **     ** 
 **   **      **     **    **  **     **  **     ** 
 **    **     **      ******    *******   ********  

Message: