ProScan: Proscan dual instance shutdown - error logging?

[AA4TX]

Does ProScan have a general error logging file?

I am running ProScan Ver. 24.8 on Windows 11 Pro 25H2. I have had two instances (two different Uniden Scanners) running 24/7 for several years. Each instance has its own directory of course, and both instances are using the same disk for recording/logging (also different directories).

Lately (past month) I have had one of the instances shut down while the PC is unattended. It does not happen often enough for me to catch, but perhaps once a week on average. I can start it up again and it will run just fine. I can see that the recording and transmission logging just stops for the instance that shuts down, presumably at the time of shutdown (could be earlier; I have no way of telling). I see no error messages from the shutdowns. The second instance continues to run without issues when this happens.

Does anyone have any suggestions to begin narrowing down this issue?

Thanks!

 

[AA4TX]

BTW, there is an "APPCRASH event" in the event viewer that is associated with the shutdown, if this would help identifiy the issue. I dont see any useful info in the event listed, but that could just be due to my limited Windows experience (I am an Embedded Engineer, Ret.).

 

[ndebaggis]

Does the APPCRASH event have an exception code? that should be listed for Event ID 1000. If you have the exception code you may be able to get a better idea at what's crashing the program. Ask your favorite search engine: "windows exception code 0xc0000005" using the exception code from your crash event.

 

[ProScan]

Does the APPCRASH event have an exception code? that should be listed for Event ID 1000. If you have the exception code you may be able to get a better idea at what's crashing the program. Ask your favorite search engine: "windows exception code 0xc0000005" using the exception code from your crash event.

He sent me an email. The crash report is at the bottom.

This is my response

I googled --> Exception code: 0xc0000005 and I see tips like this

The 0xc0000005 error, (also known as the "Access Violation" error) can be the result of different problems.
Try the following:

Check your RAM: Faulty memory can cause the 0xc0000005 error. Run a memory test using Windows Memory Diagnostic or a third-party tool like MemTest86. If any errors are detected, you may need to replace your RAM.

Update your drivers: Outdated or corrupt drivers can lead to the 0xc0000005 error. Update your graphics card, motherboard, and other drivers to the latest versions available from the manufacturers' websites.

Check for malware: Malware infections can cause the error. Run a full system scan with a reliable antivirus software to detect and remove any potential threats.

Run System File Checker (SFC): The error could be caused by corrupt system files. Open Command Prompt as administrator and run the command sfc
/scannow. This command will scan and repair any corrupted system files.

Disable Data Execution Prevention (DEP): In some cases, DEP can cause the 0xc0000005 error. To disable DEP, open an elevated Command Prompt and type bcdedit.exe /set {current} nx AlwaysOff. Restart your PC for the changes to take effect. To enable DEP again, use the command bcdedit.exe /set {current} nx AlwaysOn.

Reinstall the affected applications: If the error occurs with specific applications, try uninstalling and reinstalling them to see if that resolves the issue.

Check your hard drive: A failing hard drive can cause the error. Run a disk check by opening Command Prompt as administrator and running the command chkdsk /f. This command will check for and fix any errors on your hard drive.

Also you may want to swap the comm. ports and sound devices. One at a time to see if the problem follows.

Fault bucket 2002969795595987013, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: ProScan.exe
P2: 24.6.0.0
P3: 69cc161e
P4: clr.dll
P5: 4.8.9325.0
P6: 693b62aa
P7: c0000005
P8: 00172b30
P9:
P10:
Analysis symbol:
Rechecking for solution: 0
Report Id: a9e793ea-d6e7-40a1-bb95-5f68f0c4e938
Report Status: 268435456
Hashed bucket: 219e31a4a0aa74536bcbfa6aba55e845
Cab Guid: 0
Faulting application name: ProScan.exe, version: 24.6.0.0, time stamp: 0x69cc161e
Faulting module name: clr.dll, version: 4.8.9325.0, time stamp: 0x693b62aa
Exception code: 0xc0000005
Fault offset: 0x00172b30
Faulting process id: 0x120
Faulting application start time: 0x1DCE9EEACA19C4B
Faulting application path: C:\ProScanBCT15X\ProScan.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: a9e793ea-d6e7-40a1-bb95-5f68f0c4e938
Faulting package full name:
Faulting package-relative application ID:
Application: ProScan.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 6EDC2B30 (6EC50000) with exit code 80131506.

 

[ndebaggis]

0xc0000005 access violation, could be something writing to a null reference or read-only file? That exit code 80131506 seems to indicate something faulting in the application or .NET runtime itself, (so says duck.ai)... maybe try running SFC.EXE /SCANNOW in an elevated shell prompt then a reboot. Weird that only one instance is crashing out though. edit: I guess I should have clicked to expand your response! that covered running SFC.

 

[buddrousa]

I have had 16 version 24.8 running on 11 pro with no shut downs I have windows wait for to do updates
My PROSCAN pcs are only running PROSCAN nothing els.

 

[AA4TX]

Here are some notes from my testing.

I will be trying the solutions listed here in due time. I do not have any faults from any other usage, which is quite heavy. I use this computer for SDR applications, running several tranceivers, and using digital HF applications (none of the faults occur during the use of other radio applications). ProScan does, however, use hardware specific to my scanners, so I thought I would start there.

“ProScan” fault observations:

(I have no evidence at this point to say whether the fault is with the computer system or ProScan application)

1. Both scanner instances fault, but never simultaneously.

2. BCT15X instance faults much more often.

3. Just before the application crash fault, the audio recording has issues:

3.1. Sometimes an invalid .mp3 file is written, but the directory structure and the file name and date stamp are correct but my .mp3 player, (VLC Media Player), will not open file.

3.2. At other times, a strange phenomenon occurs:

3.2.1. Directories, file name, and time stamp are written correctly.

3.2.2. Valid .mp3 file is written.

3.2.3. The .mp3 file does NOT contain the audio received from the call – with each transmission, even on separate database channels, the identical audio snippet is recorded to the .mp3 file. If the received call is longer than the audio snippet, (a fire tone out, for example) the audio snippet is repeated over and over until the actual call ends.

3.2.3.1. This was verified by comparing the recordings of the two separate scanners. The same channels were recorded for each scanner. Identical timestamped recordings were made by each instance; one instance had the correct audio recorded; the faulting instance repeated the identical snippet as described above for each channel received. The “snippet” comes from the last correctly recorded call of the faulting scanner. It is as though the audio buffer somewhere in the chain (USB audio device, driver, etc.) was not cleared or overwritten, but continually used as valid.

I am trying to turn off ProScan features one at a time, to see if I can locate the subsystem that is causing the fault. This is an attempt to reduce the diagnostic path a bit by eliminating (or dividing) some of the possibilities (i.e., if an instance faults when NOT set up to write/read from a specific disk, then it is not a fault associated with that disk’s access or data corruption).

4.1. First feature that was turned off was the audio “Recorder” for the BCT15X instance on 2026/06/03. The location of the storage for audio recording for both instances is an external USB hard drive.

4.1.1. The BCT15X instance still failed morning of 2026/06/04.

4.1.2. This possibly indicates that this is not an access problem with the external USB hard disk.

4.1.3. Next subsystem to tested will be the audio, by using an input onboard the motherboard, rather than a USB device for the BCT15X instance.

Thanks for the suggestions!

 

[buddrousa]

I am running 16 copies on the same pc. This pc's sole purpose in life is proscan only. I do not have any of these issues. The only time it is not running Proscan is when I do manual windows updates or update proscan.

 

[AA4TX]

I am running 16 copies on the same pc. This pc's sole purpose in life is proscan only. I do not have any of these issues. The only time it is not running Proscan is when I do manual windows updates or update proscan.

I have also been running ProScan, multiple instances, for years (but not 16). I too, have had no issues. But now I do (with one thing or another)!

 

[buddrousa]

What else is the pc doing?
What does the Windows Log File about the crash.

 

[AA4TX]

What else is the pc doing?
What does the Windows Log File about the crash.

So far, the "ProScan fault" (not sure it is actually a ProScan fault) occurs about once a week on average, usually when no other user applications are running (often at night). An example from the Windows event log is provided in post #4 above. From what I can see so far, the same data for each event.

 

[buddrousa]

Like I said my Proscan PC's are only running Proscan and a remote client AnyDesk nothing else they are on their own VLAN.
With all 16 receiving and logging and recording I am running about 50% or less resources. All 16 Scanners were locked on National Weather Service so it was 16 programs all logging files and recordings so I could see the max load on the PC.
PC is a Dell with gen 9 I7 with 64GB Ram Mirrored Solid State Drive Hard drives.

 

[ProScan]

So far, the "ProScan fault" (not sure it is actually a ProScan fault) occurs about once a week on average, usually when no other user applications are running (often at night). An example from the Windows event log is provided in post #4 above. From what I can see so far, the same data for each event.

Can you check your crash report and make sure it shows Exception code: 0xc0000005 and not some other code..
Google--> Exception code 0xc0000005
I see suggestions like this so perhaps try them.

• Scan and Repair System Files: Corrupted system files can misdirect memory requests. Open the Command Prompt as an Administrator and type sfc /scannow to scan and automatically repair damaged Windows files. [1, 2]
• Run a Memory Test: Faulty RAM is a primary hardware cause for this error. Utilize the built-in Windows Memory Diagnostic or the third-party MemTest86 software to verify your RAM sticks are fully functional. [1, 2, 3]
• Scan for Malware: Rogue programs and viruses can hijack processes and memory spaces. Run a comprehensive scan using Windows Security or an established antivirus client to eliminate threats. [1, 2, 3]

Perhaps try this too. Microsoft .NET Framework Repair Tool

​

 

[AA4TX]

Can you check your crash report and make sure it shows Exception code: 0xc0000005 and not some other code..
Google--> Exception code 0xc0000005
I see suggestions like this so perhaps try them.

• Scan and Repair System Files: Corrupted system files can misdirect memory requests. Open the Command Prompt as an Administrator and type sfc /scannow to scan and automatically repair damaged Windows files. [1, 2]
• Run a Memory Test: Faulty RAM is a primary hardware cause for this error. Utilize the built-in Windows Memory Diagnostic or the third-party MemTest86 software to verify your RAM sticks are fully functional. [1, 2, 3]
• Scan for Malware: Rogue programs and viruses can hijack processes and memory spaces. Run a comprehensive scan using Windows Security or an established antivirus client to eliminate threats. [1, 2, 3]

Perhaps try this too. Microsoft .NET Framework Repair Tool

​

I am planning to do those later today. Thanks!
My system runs malware/virus detection at least once a day.

 

[AA4TX]

Ok,

I checked system files, ran the memory (RAM) test, and even performed another scan for malware and viruses. All results were clean; seems some junk files were cleaned up in the process looking at the log files.

I also ran the “NetFxRepair” tool.

I reinstalled the DotNet framework just to make sure.

Both instances have now been restarted in their original configuration.

Is there a way to see when specific versions of ProScan were installed? From the event log, I see two version, and I think must correspond to when I updated ProScan.

Someone asked about some more details from the Event viewer. I have listed them here:

Event Log Observations:

No faults before 04/30/26.

(ProScan recordings go back to 10/15/21 with no errors until 4/30/2026.)

Date, Time, Instance, and Details of Faults:

04/30/2026 10:35:50 BCT15X
AppName ProScan.exe
AppVersion 24.6.0.0
AppTimeStamp 69cc161e
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0x6a2c
ProcessCreationTime 0x1dcd534d77d2b01
AppPath C:\ProScanBCT15X\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId b98fac0a-d9f0-4222-bc3f-db7be24ee910

05/10/2026 22:20:49 BCD996XT
AppName ProScan.exe
AppVersion 24.6.0.0
AppTimeStamp 69cc161e
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0x627c
ProcessCreationTime 0x1dce09068da09f3
AppPath C:\ProScan\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId 6a3b08af-368a-41ba-a703-57988d4da9e3

05/22/2026 02:36:20 BCT15X

AppName ProScan.exe
AppVersion 24.6.0.0
AppTimeStamp 69cc161e
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0x120
ProcessCreationTime 0x1dce9eeaca19c4b
AppPath C:\ProScanBCT15X\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId a9e793ea-d6e7-40a1-bb95-5f68f0c4e938

05/25/2026 04:22:41 BCD996XT
AppName ProScan.exe
AppVersion 24.6.0.0
AppTimeStamp 69cc161e
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0xbec
ProcessCreationTime 0x1dcec9e82c649ce
AppPath C:\ProScanBCT15X\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId e8d2db60-4e06-4dac-bff4-71bf2fec1f76

05/26/2026 15:10:48 BCT15X
AppName ProScan.exe
AppVersion 24.6.0.0
AppTimeStamp 69cc161e
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0x2238
ProcessCreationTime 0x1dcecc59ede1081
AppPath C:\ProScanBCT15X\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId 1ffa31c3-8a5c-47f1-819d-6b9b5a7774c2

05/31/2026 06:45:28 BCT15X
AppName ProScan.exe
AppVersion 24.8.0.5
AppTimeStamp 6a15ba03
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0x83b8
ProcessCreationTime 0x1dced4e84c6aac0
AppPath C:\ProScanBCT15X\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId 65b83724-54ba-449c-9fc6-76f443137457

06/03/2026 13:30:33 BCT15X
AppName ProScan.exe
AppVersion 24.8.0.5
AppTimeStamp 6a15ba03
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0x1848
ProcessCreationTime 0x1dcf394ff0a636a
AppPath C:\ProScanBCT15X\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId d9350432-9591-4042-a96e-6017e294dbd9



06/04/2026 02:52:51 BCT15X
AppName ProScan.exe
AppVersion 24.8.0.5
AppTimeStamp 6a15ba03
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0x5cc
ProcessCreationTime 0x1dcf3aaec1f05c4
AppPath C:\ProScanBCT15X\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId 37094b48-04cb-48dd-86d0-2090d3c0fff0

06/05/2026 07:31:52 BCD996XT
AppName ProScan.exe
AppVersion 24.8.0.5
AppTimeStamp 6a15ba03
ModuleName clr.dll
ModuleVersion 4.8.9325.0
ModuleTimeStamp 693b62aa
ExceptionCode c0000005
FaultingOffset 00172b30
ProcessId 0x4fb8
ProcessCreationTime 0x1dcf47a5b0e056b
AppPath C:\ProScan\ProScan.exe
ModulePath C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
IntegratorReportId a3886c81-7a18-408e-9bb2-8ca2c4ba70de

 

[ProScan]

Ok,

I checked system files, ran the memory (RAM) test, and even performed another scan for malware and viruses. All results were clean; seems some junk files were cleaned up in the process looking at the log files.

I also ran the “NetFxRepair” tool.

I reinstalled the DotNet framework just to make sure.

Both instances have now been restarted in their original configuration.

No faults before 04/30/26.

(ProScan recordings go back to 10/15/21 with no errors until 4/30/2026.)

If it crashes again, try reverting back.
I would start with ver 24.7.

https://www.proscan.org/ProScan_24_7.zip

4/17/26 release data

https://www.proscan.org/ProScan_24_6.zip

3/31/26

https://www.proscan.org/ProScan_24_5.zip

2/18/26

 

[AA4TX]

If it crashes again, try reverting back.
I would start with ver 24.7.

https://www.proscan.org/ProScan_24_7.zip

4/17/26 release data

https://www.proscan.org/ProScan_24_6.zip

3/31/26

https://www.proscan.org/ProScan_24_5.zip

2/18/26

Ok, Thanks!

And thank you very much for your effort!

John