FTB Monster Crash

[FrostApocalyptic]

Title:

FTB Monster Crash​

Launcher Version:

1.4.7​

Modpack:

Monster​

Modpack Version:

latest​

Log Link:

​

Details of the issue:

MInecraft through FTB crashes every time it's launched at varying periods from the Mojang screen to 20 mins of gameplay. Gameplay sessions last no longer than 15-20 mins before the game crashes.
I've tried everything from re installing Monster to Java but nothing seems to work.
I'm using MInecraft 1.6.4 to run FTB Monster.
I've successfully run this exact setup for around a year, left for 3 months and came back to find this issue having just appeared.

Forge Mod Loader seems to be the thing that's displaying the most errors.​

 

[lenscas]

In your modpacks's instance is a folder called crash-reports can you provide us with a corresponding crash?
Upload the crash-report to pastebin and give us the link.

 

[FrostApocalyptic]

This is the latest crash report file.

 

[lenscas]

java.lang.RuntimeException: java.io.FileNotFoundException: D:\Frost\Monster\minecraft\config\WirelessRedstone.cfg (The requested operation cannot be performed on a file with a user-mapped section open)

Some other program has D:\Frost\Monster\minecraft\config\WirelessRedstone.cfg opened, virus scanner springs to mind as a program that might do it.

 

[FrostApocalyptic]

My anti V is Comodo but I haven't had any notifications to suggest anything's been quarantined/running behind the scenes.

 

[lenscas]

My anti V is Comodo but I haven't had any notifications to suggest anything's been quarantined/running behind the scenes.

A virus scan still opens files to check in them as most will run in the background

 

[FrostApocalyptic]

Is there any way I can stop it from approaching that file/Monster in general? You'll have to forgive me, I'm not much good with the tech side of things outside of vanilla minecraft stuff.

 

[lenscas]

Never used your virus scan but most of the times you can specify which files to not scan, you would have to use google to find out as I have no experience with your virus scan.

 

[FrostApocalyptic]

awesome thankyou. Incidentally it turns out McAfee was running behind Comodo and since removing it the issue has ceased. McAfee was obviously the offending program.