Page 1 of 2
Posted: Thu Oct 09, 2014 10:20 pm
by finisher2
Just to append to the original story, which is a closed thread, I finally got Windows 7 installed and did a fresh alleg install (two of them actually, one with and one without .wav) and still crash on Pcore....
Posted: Thu Oct 09, 2014 10:26 pm
by MagisterXF94
fin wrote:QUOTE (fin @ Oct 10 2014, 12:20 AM) Just to append to the original story, which is a closed thread, I finally got Windows 7 installed and did a fresh alleg install (two of them actually, one with and one without .wav) and still crash on Pcore....
It must be something draconium related...
Posted: Sat Oct 11, 2014 2:37 am
by finisher2
The fault occurs in the module ntdll.dll if that means anything to anyone. I've tried some online instructions regarding this error and can't register the dll...it checks ok for integrity with sfc but regsvr32 won't work.
Posted: Sat Oct 11, 2014 8:01 am
by Djole88
ntdll is part of the win kernel, you wouldn't be posting this if it was its fault.
You get the report that the error occurred in ntdll but I can assure you that the error happened before it got there but as a result stuff got passed to ntdll until it eventually killed the app
Posted: Sat Oct 11, 2014 10:58 pm
by finisher2
Thanks for the tip. Just updated .NET, going to keep trying things in a random, don't know what I'm doing kinda way. It's not harddrive, virus or malware. Don't think it's memory, though the memory test didn't provide the promised report after windows started.
Fixing my John Deere is a lot simpler, just follow the leak
Djole88 wrote:QUOTE (Djole88 @ Oct 11 2014, 04:01 AM) ntdll is part of the win kernel, you wouldn't be posting this if it was its fault.
You get the report that the error occurred in ntdll but I can assure you that the error happened before it got there but as a result stuff got passed to ntdll until it eventually killed the app
P.S. After some fiddling the module changed to a different dll, mscvd100 or somewhat, and now it's just a stackhash...I'm not sure if that is swimming upstream or downstream, but I'm out of ideas. Drivers all up to date, minimum startup services. Wtf
Posted: Sun Oct 12, 2014 10:23 pm
by finisher2
Just checked the video log, does the "GetAdapterMonitor failed!" mean anything?
Log file VideoSettings.log created - Oct 12, 18:15
DX registered the SW Rasterizer.
Created D3D9 interface.
Found 1 adapters.
Extracting adapter 0: \\.\DISPLAY1 - Mobile Intel® 945 Express Chipset Family
DX GetAdapterMonitor failed!
800 x 600 @ 60Hz [32 bit] [HW 0 WND 1 DS 77 AA 0x01]
1024 x 768 @ 60Hz [32 bit] [HW 0 WND 1 DS 77 AA 0x01]
1280 x 600 @ 60Hz [32 bit] [HW 0 WND 1 DS 77 AA 0x01]
1280 x 720 @ 60Hz [32 bit] [HW 0 WND 1 DS 77 AA 0x01]
1280 x 768 @ 60Hz [32 bit] [HW 0 WND 1 DS 77 AA 0x01]
1280 x 800 @ 60Hz [32 bit] [HW 0 WND 1 DS 77 AA 0x01]
800 x 600 @ 60Hz [16 bit] [HW 0 WND 1 DS 77 AA 0x01]
1024 x 768 @ 60Hz [16 bit] [HW 0 WND 1 DS 77 AA 0x01]
1280 x 600 @ 60Hz [16 bit] [HW 0 WND 1 DS 77 AA 0x01]
1280 x 720 @ 60Hz [16 bit] [HW 0 WND 1 DS 77 AA 0x01]
1280 x 768 @ 60Hz [16 bit] [HW 0 WND 1 DS 77 AA 0x01]
1280 x 800 @ 60Hz [16 bit] [HW 0 WND 1 DS 77 AA 0x01]
FOUND RESOLUTIONS (MODE 0) (MAXRATE: 60):
0) 800x600 @ 60
1) 1024x768 @ 60
2) 1280x600 @ 60
3) 1280x720 @ 60
4) 1280x768 @ 60
5) 1280x800 @ 60
CURRENT IN-GAME RESOLUTION: 800x600 @ 60
User selected values:
AD 0 MON 0x00010001 WIN 0 VSYNC 0
Fullscreen settings:
FMT 22 W 800 H 600 RR 60 DEP 77
Windowed settings:
FMT 22 W 800 H 600 RR 60 DEP 77
FSMS 0 WINMS 0
MIN 7 MAG 7 MIP 2
Window offset: 0 0
Log closed.
Posted: Sun Oct 12, 2014 10:39 pm
by pkk
Posted: Sun Oct 12, 2014 10:42 pm
by Djole88
tried to reinstall directx?
Posted: Mon Oct 13, 2014 10:49 pm
by finisher2
I assume you are referring to the modified ta_figbmp.mdl? I tried that once before and autoupdate replaced it as soon as I logged in, but I'll try it again now. Yeah, autoupdate instantly replaces it. I'll try reinstalling directx...yeah it's utd. I did a large windows update the last couple of nights and the only thing that changed was now I can't request details of the crash when it occurs...the option is not longer given. Thanks Microsoft
I just downloaded processmon and I'll see if I can get a clue...
Did Yiggz ever get up and running?
So, scrolling through the process monitor, in a nutshell, alleg reads all the artwork files, itself and then msvcr100.dll, the launcher starts querying the graphics hardware, alleg does a udp send and receive and then starts closing about 20 threads, then it queries almost 100 .dlls successfully, the last one being apisetschema.dll, and then we see process exit and it starts closing registry keys and various files. The only other anomalous thingto me is the launcher steps in with an entry: notify change directory entry on the alleg directory, whatever that means....but then alleg closes all the artwork files and thats all she wrote for alleg, the launcher does a couple more change directory entries and otherwise does whatever the launcher likes to do. Does any of that help?
Oh, and the output log ofc:
Code: Select all
13/10/2014 11:28:41 PM UTC: AssemblyLoader::ValidateEntryAssembly() calling checkin.
13/10/2014 11:28:41 PM UTC: AssemblyLoader::ValidateEntryAssembly() calling checkin.
13/10/2014 11:29:41 PM UTC: AssemblyLoader::ValidateEntryAssembly() - data length: -1
13/10/2014 11:29:41 PM UTC: AssemblyLoader::ValidateEntryAssembly() loaded assembly: System.Reflection.Assembly
13/10/2014 11:29:41 PM UTC: AssemblyLoader::ValidateEntryAssembly() machine info created.
13/10/2014 11:29:41 PM UTC: AssemblyLoader::ValidateEntryAssembly() calling checkin.
13/10/2014 11:29:41 PM UTC: AssemblyLoader::ValidateEntryAssembly() calling checkin.
13/10/2014 11:29:58 PM UTC: ProcessHandler()::Debugger - Sending on exit task().
13/10/2014 11:29:58 PM UTC: ProcessHandler()::Debugger - Calling OnExiting().
13/10/2014 11:29:58 PM UTC: AllegianceLoader::process_OnExiting - Called!
13/10/2014 11:29:58 PM UTC: AllegianceLoader::process_OnExiting - System Watcher Closed.
13/10/2014 11:29:58 PM UTC: AllegianceLoader::process_OnExiting - Calling Allegiance Exit.
13/10/2014 11:29:58 PM UTC: PlayControl::AllegianceProcess_OnExiting - Logout.
Posted: Tue Oct 14, 2014 3:58 am
by ThePhantom032
Yiggz issue has not yet been resolved - HOWEVER I just released PCore007 with different versions to see if one of them works (from what I know at least one *should* work for yiggz, and you too if you have the same issue)
It should be on autoupdate/the servers soon, usually within 24 hours (mostly faster).
Hope it works out, having a working version will help narrow down what exactly the issue is.