cleverest Posted August 29, 2017 Author Share Posted August 29, 2017 25 minutes ago, lordmonkus said: There shouldn't be any issues with any version of Windows 7, 8 or 10. I have used all 3 of them with Launchbox with no problems. It's too bad you are having problems with Windows 10 but I can assure you there is something else going on with it for you. Myself and several others use Windows 10 and Launchbox daily without problems. But do you have the Windows 10 Fall Creators Update? Nothing else fails with this computer, only LB....there is some conflict with this update and LB...I used it with Windows 10 fine for weeks before this got installed, and now it bombs constantly. :-( Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted August 29, 2017 Share Posted August 29, 2017 I don't use the Creators Update but some people have reported issues with it. They did fix the issues though by reinstalling video drivers or direct x and we do have some people using the CU. Quote Link to comment Share on other sites More sharing options...
cleverest Posted August 29, 2017 Author Share Posted August 29, 2017 This is my version. Quote Link to comment Share on other sites More sharing options...
cleverest Posted August 29, 2017 Author Share Posted August 29, 2017 I've done everything recommended, and nothing works, no choice but to try 8.1 again...can't live without my Launchbox! LOL...Not after spending this much time on it..... Quote Link to comment Share on other sites More sharing options...
neil9000 Posted August 29, 2017 Share Posted August 29, 2017 Well i'm on the same windows version as you, all be it the home version, and i have the same cpu, but 16gb of ram, and a gtx 1060. I have had zero issues with Launchbox. 1 Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted August 29, 2017 Share Posted August 29, 2017 I really don't want to do the Creators Update but it's sitting in my system right now just waiting for the "Update and Restart". Quote Link to comment Share on other sites More sharing options...
cleverest Posted August 29, 2017 Author Share Posted August 29, 2017 (edited) 5 hours ago, lordmonkus said: I really don't want to do the Creators Update but it's sitting in my system right now just waiting for the "Update and Restart". Yes, I highly recommend you avoid it! Even if some have had luck overcoming it, some haven't...I'm no tech-newbie either, I fix computers for a living... :-\ Edited August 30, 2017 by cleverest Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted August 29, 2017 Share Posted August 29, 2017 Did the update and zero problems other than a couple of extremely minor things like some simple settings. Launchbox worked perfectly with no need to do anything with drivers, Direct X or Visual C++. Quote Link to comment Share on other sites More sharing options...
cleverest Posted September 13, 2017 Author Share Posted September 13, 2017 UNBELIEVABLE. So finally, in desperation to have my collection working again, I changed my OS from Windows 10 creators update, to Windows 8.1 (a CLEAN install!)...was so thrilled it seems to work for a good hour or so, then it crashed again... this time not giving me a debug button option, otherwise the same crash.... a not responding window to click OKAY on, then it closes... I'm pretty rage-quit DEPRESSED at this point. Never thought I would say it, but I guess I may have to go back to Hyperspin / Rocketlauncher... short of changing entire computers, I don't know what the hell to do anymore. UGH! Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted September 13, 2017 Share Posted September 13, 2017 I don't know what to tell you other than there is something really weird going on with your system. I have had zero issues across 3 versions of Windows, 7, 8.1 and 10 (including creators update). Quote Link to comment Share on other sites More sharing options...
cleverest Posted September 13, 2017 Author Share Posted September 13, 2017 Maybe it's a hardware issue at this point...sigh. Quote Link to comment Share on other sites More sharing options...
cleverest Posted September 13, 2017 Author Share Posted September 13, 2017 Nothing else to try but allow beta updates in LB, and try that...doing it now, it's installing the latest beta now. Quote Link to comment Share on other sites More sharing options...
DarkMain Posted September 13, 2017 Share Posted September 13, 2017 Have you had a look in "Event Viewer" just after the crash happens? It will often give you an indication as to whats causing the crash. Quote Link to comment Share on other sites More sharing options...
ckp Posted September 16, 2017 Share Posted September 16, 2017 On 9/12/2017 at 8:13 PM, DarkMain said: Have you had a look in "Event Viewer" just after the crash happens? It will often give you an indication as to whats causing the crash. Yeah, you should filter on Critical and Error in your event viewer inside Application and System. Look a the bad stuff. Maybe you have a failing hard drive or two or something else. Quote Link to comment Share on other sites More sharing options...
cleverest Posted September 24, 2017 Author Share Posted September 24, 2017 So not that anyone can truly help me with this, but I've moved my Launchbox collection to a new 8 TB hard drive, and am now using Windows 8.1 pro (instead of 10) Although it is more stable then it was previously, the crash still occurs all the time if I have launchbox open for long enough....not responding, just the option to CLOSE it... I don't know what else I can do short of a different computer.... Quote Link to comment Share on other sites More sharing options...
cleverest Posted September 24, 2017 Author Share Posted September 24, 2017 BTW my eventvwr / applications shows this for the last crash: WARNING STATUS: Application: LaunchBox.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF9E655FE00 (00007FF9E63C0000) with exit code 80131506. AND this is the actual CRASH that is logged 5min later: ERROR STATUS Faulting application name: LaunchBox.exe, version: 7.11.0.0, time stamp: 0x59baa395 Faulting module name: clr.dll, version: 4.7.2114.0, time stamp: 0x59a63e48 Exception code: 0xc0000005 Fault offset: 0x000000000019a5c1 Faulting process id: 0x1058 Faulting application start time: 0x01d334e4c49d5250 Faulting application path: L:\LaunchBox\LaunchBox.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: f5202a24-a0db-11e7-8267-d050990cbf7b Faulting package full name: Faulting package-relative application ID: Quote Link to comment Share on other sites More sharing options...
cleverest Posted September 24, 2017 Author Share Posted September 24, 2017 As per the above...it crashed 25min before that when I was using it and this is what it gave me in eventvwr that time, it's slightly different for the top entry "runtime at IP" number given: WARNING: Application: LaunchBox.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF9E655A5C1 (00007FF9E63C0000) with exit code 80131506. CRASH (ERROR): Faulting application name: LaunchBox.exe, version: 7.11.0.0, time stamp: 0x59baa395 Faulting module name: clr.dll, version: 4.7.2114.0, time stamp: 0x59a63e48 Exception code: 0xc0000005 Fault offset: 0x000000000019a5c1 Faulting process id: 0x1058 Faulting application start time: 0x01d334e4c49d5250 Faulting application path: L:\LaunchBox\LaunchBox.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: f5202a24-a0db-11e7-8267-d050990cbf7b Faulting package full name: Faulting package-relative application ID: Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted September 24, 2017 Share Posted September 24, 2017 23 minutes ago, cleverest said: the crash still occurs all the time if I have launchbox open for long enough Hmm, there definitely has to be something weird going on because I leave launchbox pretty much all day all. The only time its not running it's when i'm rebooting the PC, re-starting LB for a change and when I close it accidentally. Running Win 10 w/ Creators I surely cannot say its your computer but if it's doing it on 2 OS's for you it's hard to say what it is. Quote Link to comment Share on other sites More sharing options...
cleverest Posted September 24, 2017 Author Share Posted September 24, 2017 Given my error logs above from eventvwr.msc, does anyone have a suggestion I can try? The only thing I can find online is people having the same crash having to contact Microsoft...I guess I may have to do that. Quote Link to comment Share on other sites More sharing options...
cleverest Posted September 27, 2017 Author Share Posted September 27, 2017 (edited) Would Jason be willing to take a look at a details crash dump analysis I did on the error? How can I submit this to him? I'm so beyond frustrated with this, and love Launchbox so much...it really bums me out....new OS, new 8 TB hard drive, doesn't matter...still crashes....from what I can tell based on it, seems to be an issue with "ExecutionEngineException occurs during Garbage Collection" Ref: https://stackoverflow.com/questions/4367664/application-crashes-with-internal-error-in-the-net-runtime I had a deeper analysis done through OSRONLINE, and I got this... ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\01f72c20ca7ef7505aa3e474eb475713\mscorlib.ni.dll, Win32 error 0n2 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2 Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\e6dedc2de7c2e5023675009390320ec6\System.Windows.Forms.ni.dll, Win32 error 0n2 *** WARNING: Unable to verify checksum for System.Windows.Forms.ni.dll Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_64\System\77f2b01bba095688313172d73e7406bf\System.ni.dll, Win32 error 0n2 *** WARNING: Unable to verify checksum for System.ni.dll TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 GetUrlPageData2 (WinHttp) failed: 12029. *** The OS name list needs to be updated! Unknown Windows version: 6.3 *** FAULTING_IP: clr!WKS::gc_heap::mark_object_simple1+241 00007fff`6c38a5c1 f70200000080 test dword ptr [rdx],80000000h EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 00007fff6c38a5c1 (clr!WKS::gc_heap::mark_object_simple1+0x0000000000000241) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000001 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff PROCESS_NAME: LaunchBox.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: ffffffffffffffff FOLLOWUP_IP: clr!WKS::gc_heap::mark_object_simple1+241 00007fff`6c38a5c1 f70200000080 test dword ptr [rdx],80000000h NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 MANAGED_STACK: !dumpstack -EE No export dumpstack found MANAGED_BITNESS_MISMATCH: Managed code needs matching platform of sos.dll for proper analysis. Use 'x64' debugger. FAULTING_THREAD: 0000000000002b44 BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS_INVALID_POINTER_READ_NOSOS PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS_NOSOS DEFAULT_BUCKET_ID: WRONG_SYMBOLS_NOSOS LAST_CONTROL_TRANSFER: from 00007fff6c388f8f to 00007fff6c38a5c1 STACK_TEXT: 000000fa`30e1e460 00007fff`6c388f8f : 000000fa`21680648 000000fa`2d5bc2e0 000000fa`142d9aa0 000000fa`142b5aa0 : clr!WKS::gc_heap::mark_object_simple1+0x241 000000fa`30e1e4f0 00007fff`6c38a224 : 000000fa`2d5b67b0 0000010a`c0a00000 00000000`00000000 00000000`00000000 : clr!WKS::gc_heap::mark_object_simple+0x1f6 000000fa`30e1e540 00007fff`6c3719c8 : 000000fa`2d5b67b0 000000fa`14191728 000000fa`30e1e8b0 00000000`00000000 : clr!WKS::GCHeap::Promote+0x6a 000000fa`30e1e5b0 00007fff`6c371917 : 00007fff`6c381200 000000fa`14191728 000000fa`30e1e8b0 00007fff`6c371990 : clr!PinObject+0x38 000000fa`30e1e5f0 00007fff`6c3812d4 : 000000fa`30e1e778 000000fa`14190000 00000000`00000003 00000000`00000001 : clr!ScanConsecutiveHandlesWithoutUserData+0x6b 000000fa`30e1e620 00007fff`6c36cb77 : 00000000`00000001 00000000`00000002 000000fa`14190000 00007fff`6c1f6793 : clr!BlockScanBlocksWithoutUserData+0x44 000000fa`30e1e650 00007fff`6c36cc98 : 000000fa`30e1d868 000000fa`30e1d870 00007fff`6c381290 00007fff`6c1ffe7b : clr!TableScanHandles+0x1f7 000000fa`30e1e720 00007fff`6c371152 : 00007fff`6cb2ab50 00000000`00000000 00000000`0000000a 00007fff`6c387f80 : clr!HndScanHandlesForGC+0x118 000000fa`30e1e7c0 00007fff`6c36cf19 : 000000fa`30e1e8b0 000000fa`30e1e8e8 00000007`00000003 00000000`00000001 : clr!Ref_TracePinningRoots+0xfe 000000fa`30e1e840 00007fff`6c3882f7 : 00000000`0071c90b 00000000`00000002 00007fff`0071c90b 00000000`00000002 : clr!GCScan::GcScanHandles+0x45 000000fa`30e1e880 00007fff`6c3866d0 : 00007fff`6cb379d8 00007fff`00000001 00000000`00000000 000000fa`1428d3a0 : clr!WKS::gc_heap::mark_phase+0x1ef 000000fa`30e1e930 00007fff`6c386602 : 00007fff`6cb379d8 000000fa`00000002 00000000`00000004 00007fff`6cb379d8 : clr!WKS::gc_heap::gc1+0x88 000000fa`30e1e990 00007fff`6c38633d : 000000fa`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : clr!WKS::gc_heap::garbage_collect+0x253 000000fa`30e1ea20 00007fff`6c32a58d : 00000000`00000044 00007fff`00000002 00000000`00000002 00007fff`6c1f62d1 : clr!WKS::GCHeap::GarbageCollectGeneration+0x10d 000000fa`30e1ea80 00007fff`6c2db07a : 00007fff`6c32a500 000000fa`30e1ec00 00000000`00000002 00007fff`6c3592d4 : clr!WKS::GCHeap::GarbageCollect+0x8d 000000fa`30e1ead0 00007fff`6b100d92 : 000000fa`2f17b150 00007fff`6b04e4a3 000000fa`15ddfd48 000000fa`15cff5e0 : clr!GCInterface::Collect+0x6a 000000fa`30e1eb60 00007fff`0d52cb56 : 000000fa`30e1ed40 000000fa`15cff5c8 000000fa`30e1ef80 000000fa`20e00b18 : mscorlib_ni+0x590d92 000000fa`30e1ec10 00007fff`0d39c05b : 000000fa`20d0b410 000000fa`0000091d 00000000`00000000 00007fff`6b086e99 : 0x7fff`0d52cb56 000000fa`30e1ec90 00007fff`0d3e3ff2 : 000000fa`20d38848 00000000`0000009b 00000000`00001388 00000000`00001388 : 0x7fff`0d39c05b 000000fa`30e1ece0 00007fff`0d37ee24 : 000000fa`497c9278 000000fa`497c9278 000000fa`15cfc084 00000000`00008000 : 0x7fff`0d3e3ff2 000000fa`30e1ed10 00007fff`6b04ca72 : 000000fa`497c5908 000000fa`497c5908 000000fa`30e1ed80 00000000`00000000 : 0x7fff`0d37ee24 000000fa`30e1ed50 00007fff`6b04c904 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mscorlib_ni+0x4dca72 000000fa`30e1ee20 00007fff`6b04c8c2 : 000000fa`497c59a8 00000000`00000000 00000000`00000000 00000000`00000000 : mscorlib_ni+0x4dc904 000000fa`30e1ee50 00007fff`6b086472 : 000000fa`30e1eff8 00000000`00000000 00000000`00000000 00000000`00000000 : mscorlib_ni+0x4dc8c2 000000fa`30e1eea0 00007fff`6c1f6793 : 000000fa`497c59d0 00000000`00000000 000000fa`30e1f1b8 00007fff`6b282b30 : mscorlib_ni+0x516472 000000fa`30e1eee0 00007fff`6c1f6665 : 00000000`00000000 00007fff`6c1f78a1 00000000`00000000 00007fff`6c1f5017 : clr!CallDescrWorkerInternal+0x83 000000fa`30e1ef20 00007fff`6c1f736d : 00000000`00000001 000000fa`30e1f2c0 000000fa`30e1f0f8 000000fa`30e1f1b8 : clr!CallDescrWorkerWithHandler+0x4e 000000fa`30e1ef60 00007fff`6c2dbf59 : 000000fa`30e1f570 000000fa`30e1f4b0 00007fff`6b282b30 000000fa`30e1f4b0 : clr!MethodDescCallSite::CallTargetWorker+0xf8 000000fa`30e1f060 00007fff`6c1f7ce5 : 000000fa`497c59d0 00007fff`6c2dbe50 000000fa`30e1f4b0 00000000`00000000 : clr!ThreadNative::KickOffThread_Worker+0x109 000000fa`30e1f2c0 00007fff`6c1f7c60 : 000000fa`30e1f4b0 00007fff`6c1f6071 ffffffff`fffffffe 00000000`00000002 : clr!Frame::Push+0x59 000000fa`30e1f300 00007fff`6c1f7b9e : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : clr!FillInRegTypeMap+0x198 000000fa`30e1f400 00007fff`6c1f7d1f : ffffffff`ffffffff 000000fa`2f17b150 000000fa`2f17b150 000000fa`2f101bd0 : clr!FillInRegTypeMap+0xc1 000000fa`30e1f490 00007fff`6c2dbe3b : 000000fa`2f17b150 000000fa`00000001 000000fa`2f101bd0 00000000`00000009 : clr!FillInRegTypeMap+0x47 000000fa`30e1f4f0 00007fff`6c3b159f : 000000fa`2f101bd0 000000fa`2f17b150 000000fa`30e1f548 000000fa`2f17c9a0 : clr!ThreadNative::KickOffThread+0xdb 000000fa`30e1f5c0 00007fff`785413d2 : 00007fff`6c3b1520 000000fa`2f17c9a0 00000000`00000000 00000000`00000000 : clr!Thread::intermediateThreadProc+0x86 000000fa`30e1fe00 00007fff`7a6454f4 : 00007fff`785413b0 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x22 000000fa`30e1fe30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: clr!WKS::gc_heap::mark_object_simple1+241 FOLLOWUP_NAME: MachineOwner MODULE_NAME: clr IMAGE_NAME: clr.dll DEBUG_FLR_IMAGE_TIMESTAMP: 59a63e48 STACK_COMMAND: ~13s; .ecxr ; kb FAILURE_BUCKET_ID: WRONG_SYMBOLS_NOSOS_c0000005_clr.dll!WKS::gc_heap::mark_object_simple1 BUCKET_ID: X64_APPLICATION_FAULT_WRONG_SYMBOLS_INVALID_POINTER_READ_NOSOS_clr!WKS::gc_heap::mark_object_simple1+241 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/LaunchBox_exe/7_11_0_0/59baa395/clr_dll/4_7_2114_0/59a63e48/c0000005/0019a5c1.htm?Retriage=1 Edited September 27, 2017 by cleverest fix Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.