Strange pid error MC 1-18-2 Forge 40.0.52 and Futurepack 33.0.7268
trogarus opened this issue · 43 comments
A strange pid error is crashing the game. I haven't played futurepack for a while and wanted to have a look at it in MC 1-18-2. I made a pack, loaded the game, and it crashes with a pid file mention about futurepack.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Attempt to load my custom made modpack and it crashes
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Version
Minecraft Version: 1-18-2
Forge Version: 40.0.52
Futurepack Version: 33.0.7268
Logs
Isn't producing a crash log.
https://pastebin.com/XKmYvQcn - pid log
Debug is too big for pastebin
https://pastebin.com/yVCuppKr - fp latest
https://pastebin.com/uH2TVaZt - latest log
On the SSD drivers, why would it only happen with Futurepack? Same thing with re-installing Java. I have 178 mods in this self built pack. Logged out of launcher, logged back in. Again, if I remove futurepack, this all goes away. Pack launches. I can create worlds. I can save and rejoin worlds, but not when Futurepack is enabled. Latest logs, still no crash log.
New Pid https://gist.github.com/trogarus/29105a696b059196c4e8939597b2d5a3 New Debug https://gist.github.com/trogarus/3f6b7e8d15e67592991db25208b6a7f5 New FP-Latest https://gist.github.com/trogarus/cbb07ae8ed9900a6e3d83f67498735e7 New Latest https://gist.github.com/trogarus/ed2de44652e0e539d50a3f9ec4c01687
it crashed in ntdll.dll ?! something in your system is unstable. and I have no idea why futrepack isc ausing that, its just a normal stacktrace trying to be printed. When the crash occurs is cour CPU at 100% ? Becuase my only guess right now is its load depedendant as its happening during worldgen.
Also you can try with a powershell run as administrator:
Repair-WindowsImage -Online -RestoreHealth
That should fix any windows related issues
On the SSD drivers, why would it only happen with Futurepack? Same thing with re-installing Java. I have 178 mods in this self built pack. Logged out of launcher, logged back in. Again, if I remove futurepack, this all goes away. Pack launches. I can create worlds. I can save and rejoin worlds, but not when Futurepack is enabled. Latest logs, still no crash log.
New Pid https://gist.github.com/trogarus/29105a696b059196c4e8939597b2d5a3
New Debug https://gist.github.com/trogarus/3f6b7e8d15e67592991db25208b6a7f5
New FP-Latest https://gist.github.com/trogarus/cbb07ae8ed9900a6e3d83f67498735e7
New Latest https://gist.github.com/trogarus/ed2de44652e0e539d50a3f9ec4c01687
More testing. Built a minimalist pack with futurepack, added like 5 - 10 most common mods. No issues. So, I'm guessing this is some kind of weird mod interaction issue. Will start testing the pack I have and remove mods to try and narrow it down. Will report back.
So, spent hours enabling and disabling mods. This is what I've found.
The mods in question require:
Supermartijn642's Config Library 1.0.9
Supermartijn642's Core Library 1.0.16b
Mods in question (all Supermartijn mods)
Entangled 1.3.10
Packed Up 1.0.25
Scarecrow's Territory 1.1.4
Wormhole Portals 1.1.9b
Enable any of the mods in question and the crash happens. The libraries don't seem to affect anything alone.
Used the following, administration level command prompt, no errors
sfc /scannow
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
The file ntdll.dll is a DLL (Dynamic Link Library) file stored in the system folder of Windows operating system. It is usually created automatically during the installation of the Windows operating system. The file ntdll.dll has a description of “NT Layer DLL”. The file ntdll.dll contains NT kernel functions, so it is essential for the normal function of the Windows operating system.
So the above scans should have found corruption if it existed. I was internet connected when I ran them so they functioned proplerly.
Honestly, not trying to be difficult here. I enjoyed your mod last time I played it and wanted to be able to play it again to see how far it's come without having to sacrifice other mods I also enjoy. I do appreciate the work you guys have done on this and I'm sure this time will be just as enjoyable as the last.
@SuperMartijn642 what are your libs doing? any idea what could cuase this weird interaction?
Used the following, administration level command prompt, no errors
sfc /scannow Dism /Online /Cleanup-Image /ScanHealth Dism /Online /Cleanup-Image /CheckHealth
The file ntdll.dll is a DLL (Dynamic Link Library) file stored in the system folder of Windows operating system. It is usually created automatically during the installation of the Windows operating system. The file ntdll.dll has a description of “NT Layer DLL”. The file ntdll.dll contains NT kernel functions, so it is essential for the normal function of the Windows operating system.
So the above scans should have found corruption if it existed. I was internet connected when I ran them so they functioned proplerly.
Did you also restart your computer after that ?
Entangled 1.3.10
Packed Up 1.0.25
Scarecrow's Territory 1.1.4
Wormhole Portals 1.1.9b
Apart from Packed Up, those mods themselves don't directly interact with the file system. The only thing I can think of is my config library, since of all those mods do use it for config files.
The config library just uses Night Config's CommentedFileConfig under the hood though, it doesn't directly write anything to file.
Apart from that, I don't think my libraries really interact much with the system. My core library is mostly just some default implementations for tile entities, guis, etc. and helper classes.
@trogarus Could you test if the same issue occurs with Future Pack and another mod Durability Tooltip. Durability Tooltip just requires my config library and not the core one. Durability Tooltip itself is also a very simple mod, so if it still crashes, it is just something todo with my config library.
Do you use the lunacher provided java or a self installed one? if its from the launcher try a self installed java 17.
No overclocking. 16GB RAM. New SSD installed a little over a year ago. I'll double check file permissions on the folder to see if maybe those are read only.
Its weird, it crashed while trying to write files to your disk. Is it always the same PID crash report? Also areoyu using and SSD, a HDD or a m2 SSD? And what about your RAM is that old are you overclocking ?
Also you should relog into the launcher as that file contains your access token
Check your SSD drivers then, I am only guess at straws here but its something very low lever thats crashing here.
OK, just did the file permissions, will log out and back into the launcher and try again.
Just double checked paths and system stuff for Java. I already re-installed Java :) About to try another launch after ensuring proper file permissions in game folder and checking system environment. Will report back.
It is always crashing nativly when writing to file ( as the PID crash stack trace confirmed). This means its either a hardware fault, in this case the either the storage controler on your mother board or the drive itself. Or its a JVM bug, this is unlikely but not impossible. Also its amazing how much you test, thank you for that and your patience!
Thinks you can try:
- try to run minecraft from another drive (so the minecraft folder and everythign is on a different drive - this way we can check if the drive is the issue or soemthing else
- try to run it from a USB3 stick (this should use different drivers & different mainboard ships so with this and the other test we should know if its hardware or software)
- try to reinstall/update drivers for your mainboard, HDD and SSD
- try to start minecraft in a VM - on my laptop I have some games which only work in a VM for some reason - this means there is a software fault somewhere.
Sure. I'll just put together a pack with Futurepack and Durability tooltip and see what happens. Got some stuff going on, so might take a day or two, but I'll do this and report back.
Also, I did the powershell stuff too that you posted above @mcenderdragon. Still didn't fix the issue. Right now, with the pack, I'm just playing it without the mentioned mods that seemed to help create the conflict.
So, I did two things. I created an instance with nothing but Futurepack and Mod Durability Tooltip. No issues.
Then I added it to the modpack that's been crashing. Here's updated files related to that add.
Current Pid error log https://gist.github.com/trogarus/bfbaed692ca06f542d2efec3525d7a26
Current Debug log https://gist.github.com/trogarus/0428d0906d246fb65e81cc310d4e6db9
FP-Latest log https://gist.github.com/trogarus/067518ce3245e8a09110d73fcf95327f
Latest log https://gist.github.com/trogarus/48517f519ad4b02ddfaed9250ea96f6c
And yes @mcenderdragon, I have restarted after attempting to uninstall java, then after re-installing java (which I've done now a couple times trying to deal with this). I also did restarts after running the various administration command prompts and the power shell you mentioned.
Additional information, don't have the time to reply to your last comment at this point @SuperMartijn642 but I will later. Simply disabling Durability Tooltip did not prevent the crash. I had to actually delete the contents of the config folder to get the game to run again. So maybe mine is some kind of edge case. I'll reply to your last comment later when I'm able. Thanks to both of you for trying to look into this.
Your first two pid crash logs seem to come from the same code path during (what looks like) the FMLCommonSetupEvent. Your latest pid crash log (and latest.log) seems to occur at a different place, something to do with saving dimension data.
From your previous comments I got the impression that it simply crashes everytime during startup of the client.
Is this correct or does it crash at some other point?
Your last crash seems to occur when saving a dimension. The only thing mods like Entangled and Wormhole would contribute to this is block entity data in the form of nbt, which should be no different from something like a regular chest.
So, I did two things. I created an instance with nothing but Futurepack and Mod Durability Tooltip. No issues.
You previously confirmed your pack does startup fine when Future Pack is disabled. Since my mods you mentioned don't have much in common, I was wondering if the issue is actually specific to a combination of my mods and Future Pack. To test this, does your pack also crash when all of my mods you mentioned (including the core and config library) are disabled, but Future Pack is enabled? (Thank you for all the testing you did so far by the way 🙂)
As a last note, I also tried to recreate the issue. I added Future Pack and all of my mods to a 1.18 CurseForge instance, all with the versions you mentioned and the same Forge version, and it starts without a problem. From this and from what I've gathered from the conversation, it seems like it is something specifically with your system. Especially since pid crashes, as far as I know, are usually something caused either by OpenGL, the JVM, or some native dll. (I may be wrong though, this is just when I've encountered pid crashes previously)
Whelp, gonna be a while until I can update this. SO, I thought maybe I'd just uninstall MC and then reinstall it. Goto my account, get the install exe, try to re-install MC. The installer doesn't want to install and sends me to MS Store. But, there's an error there. So trying to figure this out now before I can even get back into the game. Tech, it's great when it works, not so much when it doesn't. Gp figure.
Firstly, two things. Sorry for the delay in replying to this again with updated information. Secondly, thanks to both @mcenderdragon and @SuperMartijn642 for trying to help me address this issue.
My ordeal, which included things from my last reply wound up causing many issues that I just entirely got tired of dealing with and trying to fix. So, I decided to do a CLEAN install of windows 10. Problem still persists. All drivers are updated as far as possible. My Crucial SSD diagnostics are fine and drive is healthy. Graphics are as up to date as possible. Only thing I can think of is that there is a video driver conflict and the manufacturer has not yet done another graphics driver update. All else, corruption or lack of updated drivers is now removed from the equation. Things are still as before concerning disabling the following mods
Entangled 1.3.10
Packed Up 1.0.25
Scarecrow's Territory 1.1.4
Wormhole Portals 1.1.9b
Again, doing this allows things to function properly with the potential additional removal of all config files allowing them to regenerate after disabling/removing the mods in question.
Most recent PID error https://gist.github.com/trogarus/00e77e15218275c7e4ff67bf1c1ebced
Thanks to you both, again. Your time and attempts are greatly appreciated. Just wish I could get it all functioning as I do depend allot on entangled for certain things and scarecrow's territory was something I've never played with before. I could do without packed up and wormhole as I have other backpack mods and waystones to deal with teleporting.
Additional clarification. Clean install was courtesy of Microsoft Media Creation tool. All filed new and direct from MS.
Just a note, did the most recent updates for the Supermartijin mods and attempted to start the game. Game crashed with pid error before I could even select a world. Had to delete all of the config files to get it to load again after disabling the updated mods. Was able to run core without issue though.
Mods included
Entanlged 1.3.11
Scarecrow's Territory 1.1.5
Supermartijn Core 1.0.18
Just a note, did the most recent updates for the Supermartijin mods and attempted to start the game. Game crashed with pid error before I could even select a world. Had to delete all of the config files to get it to load again after disabling the updated mods. Was able to run core without issue though.
Mods included Entanlged 1.3.11 Scarecrow's Territory 1.1.5 Supermartijn Core 1.0.18
what was the PID crash here ?
Latest PID from above. So it's not just futurepack that has issues with supermarijn code :)
https://gist.github.com/trogarus/e6713957c6727744101ebd774e5dd920
Now its Lost CIties from @McJty , if you have any idea what else to try and fix this it would be nice.
@trogarus even reisntalling the system did not help right? and its an access violation which means your hardware is broken. Its either mainboard, CPU, RAM (unlikely since it always happened with file IO) or the hard drive. I would check with a differen hard drive first. so unplug all harddrives so only one is available at the time and test.
use Prime95 to check your CPU
use https://www.memtest86.com/ to check your ram
RAM and drive are not even a year old. Had the drive and RAM upgraded at the same time @mcenderdragon. It;s the only drive I have connected to the system as well. I'll still try the ram check since you posted a link,
ohh it sometimes happen that components are fualty from the start - or they arent connectetd properly (becazse ram is not fully in or the cable to the drive is broken)
Prime95 link: https://www.mersenne.org/download/
@mcenderdragon Sorry the reply has taken so long but I only seem to have found the culprit today. The reason nothing above worked is because none of it was the issue.
Not sure about the load impact of your mod but it’s looking like a page file size issue in windows 10. By default, windows 10 manages page file size. To bypass the load issue, I had to increase page file size to 3100. Once I did that, things load normally now.
Again, thanks to you a @SuperMartijn642 for looking into this. I enjoy both of you two’s mods.
Premature.
It seemed to work, but on game restart, I had to once again remove config for forge and fml for game to load again. Once again, if I let the mods in, I delete the forge and fml config files, then it runs without crashing. Sorry, thought I had it figured out. Not the case.