JaariAtmc

Please upload the said logs to either www.pastebin.com (or paste.ubuntu.com if pastebin throws an file limit error) You can find the logs in %AppData%\Roaming\.technic\logs. I need the latest logs with said error.

Update your graphics driver or downgrade to Java8u25.

Launcher logs please.

For the love of god pastebin it >.> Also, update your graphics drivers, they are incompatible with Windows 10 atm.

@Munaus It is time for your most favorite action on these forums

Ah, but would be important if he wants to share his pack. Because that's what the majority of the people come here for in the end.

Also, always read the disclaimer: Disclaimer This mod is the fruit of countless hours of work and effort. You download it for free as it is and we are not responsible for any damage done to your saved games. This mod can not be distributed in any other way than through this website. You don't have the permission to distribute this mod through 'mod packages', installers or plugins. A multiplayer plugin is allowed as long as it requires you to download the unmodified single player mod to work. An installer can not host this mod, it must redirect the user to this page. You can't modify or redistribute this mod without written permission. The only package that can currently distribute this mod is the YogBox. Please do not contact us asking for permission to add the mod to your modpack, the answer is 'No'.

Nope, welcome to Bteam, all the good stuff has not been included. There's an "issue" with magmatics and lava fabricators though (look it up on youtube) and this same principle works for BioFuel.

Magmatic dynamos or biofuel generators. Because someone, aka a certain modpack maker, didn't include any real sources of power... For the matter, you need 250 magmatic dynamos or 125 biofuel generators to fully power one laser drill.

Strange, I don't have said issue. Maybe increment your version number?

Nope, that's a vanilla bug that's like finally (hopefully) fixed in Minecraft 1.9. You could try placing conveyor blocks around the farm, which push the chickens back to the middle.

The pipe itself does exactly zero crafting. It will only empty into whatever machine or block you could use to autocraft something. Also, from my own research: 1. Do not use multi-step crafting recipes. It will boot you off when you try. An example of this: Oak wood to Chest. Wood to planks, Planks to chest. You try crafting chests without enough planks in the system, and it will now boot you as it can't perform the other crafting step automatically. 2. Make sure you have enough space in whatever machine/block you are using. If the crafting pipe has to place one more item in the block's inventory than it can fit, it will bounce back into the system, and the moment it leaves the crafting pipe, the pipe corrupts. Aka causing you to keep on crashing when you relog ( player at area only, does not crash server). Final statement: ProjectRed autocrafting is so, awfully, insanely broken in past Bteam 1.0.9a or 1.0.10b. I'm really unsure why they didn't just add Applied Energistics...

Hey look, Windows 10 and Intel HD Graphics. Now if Windows actually updated your graphics card instead of leaving it broken... Anyways, check if you can update your Intel HD Graphics driver here: https://downloadcenter.intel.com/ Otherwise, try if downgrading to Java8u25 helps (you are currently on 8u73).

I would suggest using WinDirStat (google it) to find out where all your storage space went.

Downloading your modpack, it seems that your bin/config/mods folders are placed in a subfolder. They need to be in the top folder to work correctly.

1. Backup your save. 2. Go to config, Forge, set this to "true": "B:removeErroringTileEntities=false", try joining your world again and see if it works. 3. If not, use MCedit to remove the smeltery.

For the love of god, don't use 7 GB of RAM, you are just starving your system of RAM and then this happens. Don't use more than 3-4 GB. Anything more is, in most cases, actually hurting you.

Why? Why did you add in DragonAPI if you don't have any of the other mods Reika made? Its quite literally written in the crashreport: ... 10 more Caused by: Reika.DragonAPI.Exception.InstallationException: DragonAPI was not installed correctly: The version file was either damaged, overwritten, or is missing! Try consulting http://www.minecraftforum.net/topic/1969694-for information. This is not a DragonAPI bug. Do not post it to http://www.minecraftforum.net/topic/1969694- unless you are really stuck. at Reika.DragonAPI.Extras.ModVersion.readFromFile(ModVersion.java:127) at Reika.DragonAPI.Base.DragonAPIMod.<init>(DragonAPIMod.java:79) at Reika.DragonAPI.DragonAPIInit.<init>(DragonAPIInit.java:203) at Reika.DragonAPI.DragonAPIInit.<clinit>(DragonAPIInit.java:196) ... 34 more Besides that, you included a version that isn't officially obtainable anymore? As of recently, you can only download V12e, you added V10a. How did you even manage to do that?

You may have upped your RAM to 8 GB (which you shouldn't do btw, lower it to 4 GB), but you have an issue with an interfering java environment variable, which is limiting your max usage to " Xmx512M" (aka 512 MB). https://cdn.discordapp.com/attachments/96563656271093760/166334782450565121/clearJavaEnvVars.bat Use that .bat, then restart your launcher and try again.

So uh yeah, it took the modpack 2 minutes, before it crashed. And it crashed with: [B#347] 2016/04/24 12:26:32 [INFO] 2016-04-24 12:26:32 [INFO] [STDOUT] java.lang.OutOfMemoryError Meaning, you have not allocated enough RAM to the modpack. As I saw in your java arguments, you only have allocated 1 GB of RAM, which isn't enough for most modpacks nowadays (2 GB or 3 GB preferred). If you can, try updating to Java 64-bit, if you have the system to support it (in your case, Win7-64bit). This way, you can allocate more memory in the Launcher Options.

[B#347] Picked up _JAVA_OPTIONS: -Xmx512M https://cdn.discordapp.com/attachments/96563656271093760/166334782450565121/clearJavaEnvVars.bat Open that .bat, restart your launcher, retry loading modpack.

No, google around, giving out such links is legally not possible anymore.

Well, maybe we blame Windows 10 because just about every single user that comes to us with such a problem is running Windows 10? Also, its quite easy to blame Win10 when people don't include logs. I wonder what's more annoying and stupid, the amount of crashes on Windows 10 or the amount of people that say "OMG IT CRASHED FIX PLOX" in different ways without providing ANY kind of logs.

Just maybe, an option called "modpack options" when you have a modpack selected? Just look at the launcher with a magnifying glass, maybe you'll find it!

Yes. that happens...