Ever since this morning, I've gotten multiple blue-screens causing my computer to seriously malfunction. This coincides with the time frame during which I played the most 4D1. I am unsure if any malware or malignant scripting was transferred via host-to-client download protocols while in-game, but I find it disturbing that as soon as I deleted my MW2 folder and 4D1 with it, the blue screens stopped...

 

I can no longer trust the stability of this game, so for the sake of the integrity and safety of my one and only computer, I must say farewell to the 4D1 in-game community until the full release is available with full anti-cheat and anti-hack implementations. I am not sure what gap in the game's security allowed this to happen, but until that is determined, I cannot run the risk of losing the functionality of a computer that I use for literally EVERYTHING from class notes to programming to my job.

 

I can't wait for 4D1 to blossom, and it pains me to have to deny myself the beta experience, but sadly, I see no other alternative. I'll always be loyal to the community, so don't worry about me completely running off. More fun mods are on the way

 

Here's to the future full version of 4D1!

Hmmm, odd. If you go into C:\WINDOWS\Minidump, and gain access into that folder, is it possible for you to put the minidumps onto MediaFire. Then we could anaylze the problem with something like WinDBG.

As lmaobox wisely said, this type of application cannot cause BSODs.

I'm also waiting for a final release. But I come here from time to time, and try the client aswell, to see how the progress goes. The only thing I can complain for now is about random crashes (mostly while loading the game or maps). Surely, these will be patched in the future, and I'll be here to check it

UPDATE: Upon further analysis as per Comodo, I've determined the error was from corrupt cache files from a different application that I, oddly, haven't used in a million years... wierd..

 

In any event, I apologize for blaming the stability of 4D1 =P

UPDATE: Upon further analysis as per Comodo, I've determined the error was from corrupt cache files from a different application that I, oddly, haven't used in a million years... wierd..

 

In any event, I apologize for blaming the stability of 4D1 =P

that is. not. cool.

at least you got your problem fixed though till next time!