![]() |
|
Older Builds like 4.0-6492-x64, Refuse to load anymore - Printable Version +- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org) +-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support) +--- Forum: Support (https://forums.dolphin-emu.org/Forum-support) +--- Thread: Older Builds like 4.0-6492-x64, Refuse to load anymore (/Thread-older-builds-like-4-0-6492-x64-refuse-to-load-anymore) Pages:
1
2
|
Older Builds like 4.0-6492-x64, Refuse to load anymore - Temperhoof - 01-26-2016 For some unknown reason, older builds like 4.0-6492-x64 and all builds between 3000 - 7000 no longer load for me. Newer builds run just fine, however I need to run the older build like 4.0-6492-x64 to continue playing in Netplay with Game Data Loading. What I've Tried to Resolve to Problem: Reformatted C Drive & Reinstalled Windows 10 64bit twice. Reflashed Bios. Reinstalled all Drivers. Nothing works. RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - JosJuice - 01-26-2016 What goes wrong when you try to run one of the older builds? Does absolutely nothing happen? Is there an error message? Does the main Dolphin window ever appear? RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - Temperhoof - 01-26-2016 (01-26-2016, 07:24 AM)JosJuice Wrote: What goes wrong when you try to run one of the older builds? Does absolutely nothing happen? Is there an error message? Does the main Dolphin window ever appear? Does absolutely nothing happen? Most of the time yes, absolutely nothing happens. Is there an error message? No, only once I was able to get one but it only said simply: Dolphin.exe has stopped working. Does the main Dolphin window ever appear? Only does once in a blue moon, then it shut down. But mostly nothing happens. RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - Temperhoof - 01-26-2016 Additionally, I managed to nab a .dmp (Dump) of the Dolphin.exe before it crashed on me, if you want to review it here it is: https://drive.google.com/file/d/0ByP4-lar38yuUnA5dzdKZXlCTzA/view?usp=sharing RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - Temperhoof - 01-26-2016 I'm certain it's a hardware issue. Just the problem doesn't seem to have resolved itself. Must be getting hung up in my CPU threads, because after I power down the computer for a long period -- I can at least turn on the program and see it give me an error message. RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - Temperhoof - 01-26-2016 Error Report: Faulting application name: Dolphin.exe, version: 0.0.0.0, time stamp: 0x556d1faf Faulting module name: Dolphin.exe, version: 0.0.0.0, time stamp: 0x556d1faf Exception code: 0xc0000005 Fault offset: 0x00000000006e41ea Faulting process id: 0x5d0 Faulting application start time: 0x01d15813e3583d17 Faulting application path: G:\Users\NJRockingham\Desktop\Dolphin-x64\Dolphin.exe Faulting module path: G:\Users\NJRockingham\Desktop\Dolphin-x64\Dolphin.exe Report Id: 33cc7c3c-0fa7-419d-8196-20ca6be18d08 Faulting package full name: Faulting package-relative application ID: ----- Information: Fault bucket 86092044096, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Dolphin.exe P2: 0.0.0.0 P3: 556d1faf P4: Dolphin.exe P5: 0.0.0.0 P6: 556d1faf P7: c0000005 P8: 00000000006e41ea P9: P10: Attached files: C:\Users\NJRockingham\AppData\Local\Temp\WERD6A0.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Dolphin.exe_b1b739bf80b6f3e8b948b575d37bee355d5be5f_1c491fe0_168fd8a4 Analysis symbol: Rechecking for solution: 0 Report Id: 33cc7c3c-0fa7-419d-8196-20ca6be18d08 Report Status: 0 Hashed bucket: d813b24d1061872d17d1966cd3484523 ---- WER Report Version=1 EventType=APPCRASH EventTime=130982706613293438 ReportType=2 Consent=1 UploadTime=130982706613632783 ReportIdentifier=210ce941-c407-11e5-9bd1-408d5c1e1f15 IntegratorReportIdentifier=33cc7c3c-0fa7-419d-8196-20ca6be18d08 NsAppName=Dolphin.exe Response.BucketId=d813b24d1061872d17d1966cd3484523 Response.BucketTable=4 Response.LegacyBucketId=86092044096 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Dolphin.exe Sig[1].Name=Application Version Sig[1].Value=0.0.0.0 Sig[2].Name=Application Timestamp Sig[2].Value=556d1faf Sig[3].Name=Fault Module Name Sig[3].Value=Dolphin.exe Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=556d1faf Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=00000000006e41ea DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.10240.2.0.0.768.101 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=e745 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=e7457688836d1b5346c60203da485429 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=e657 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=e657c0fd44702a45d426fd2e0c629a4a UI[2]=G:\Users\NJRockingham\Desktop\Dolphin-x64\Dolphin.exe UI[3]=Dolphin.exe has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=G:\Users\NJRockingham\Desktop\Dolphin-x64\Dolphin.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll LoadedModule[4]=C:\Windows\system32\apphelp.dll LoadedModule[5]=C:\Windows\system32\USER32.dll LoadedModule[6]=C:\Windows\system32\GDI32.dll LoadedModule[7]=C:\Windows\system32\SETUPAPI.dll LoadedModule[8]=C:\Windows\system32\CFGMGR32.dll LoadedModule[9]=C:\Windows\system32\msvcrt.dll LoadedModule[10]=G:\Users\NJRockingham\Desktop\Dolphin-x64\MSVCP120.dll LoadedModule[11]=G:\Users\NJRockingham\Desktop\Dolphin-x64\MSVCR120.dll LoadedModule[12]=G:\Users\NJRockingham\Desktop\Dolphin-x64\OpenAL32.dll LoadedModule[13]=C:\Windows\system32\RPCRT4.dll LoadedModule[14]=C:\Windows\system32\ole32.dll LoadedModule[15]=C:\Windows\system32\combase.dll LoadedModule[16]=C:\Windows\system32\COMDLG32.dll LoadedModule[17]=C:\Windows\SYSTEM32\DINPUT8.dll LoadedModule[18]=C:\Windows\SYSTEM32\IPHLPAPI.DLL LoadedModule[19]=C:\Windows\system32\sechost.dll LoadedModule[20]=C:\Windows\system32\shcore.dll LoadedModule[21]=C:\Windows\system32\NSI.dll LoadedModule[22]=C:\Windows\system32\ADVAPI32.dll LoadedModule[23]=C:\Windows\system32\SHELL32.dll LoadedModule[24]=C:\Windows\system32\SHLWAPI.dll LoadedModule[25]=C:\Windows\SYSTEM32\WINMM.dll LoadedModule[26]=C:\Windows\system32\windows.storage.dll LoadedModule[27]=C:\Windows\system32\OLEAUT32.dll LoadedModule[28]=C:\Windows\system32\kernel.appcore.dll LoadedModule[29]=C:\Windows\system32\WS2_32.dll LoadedModule[30]=C:\Windows\system32\powrprof.dll LoadedModule[31]=C:\Windows\system32\PSAPI.DLL LoadedModule[32]=C:\Windows\SYSTEM32\AVIFIL32.dll LoadedModule[33]=C:\Windows\system32\profapi.dll LoadedModule[34]=C:\Windows\SYSTEM32\OPENGL32.dll LoadedModule[35]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10240.16384_none_f41f7b285750ef43\COMCTL32.dll LoadedModule[36]=C:\Windows\SYSTEM32\WINSPOOL.DRV LoadedModule[37]=C:\Windows\SYSTEM32\WINNSI.DLL LoadedModule[38]=C:\Windows\SYSTEM32\WINMMBASE.dll LoadedModule[39]=C:\Windows\SYSTEM32\MSVFW32.dll LoadedModule[40]=C:\Windows\SYSTEM32\MSACM32.dll LoadedModule[41]=C:\Windows\SYSTEM32\GLU32.dll LoadedModule[42]=C:\Windows\SYSTEM32\DDRAW.dll LoadedModule[43]=C:\Windows\SYSTEM32\bcrypt.dll LoadedModule[44]=C:\Windows\SYSTEM32\DEVOBJ.dll LoadedModule[45]=C:\Windows\SYSTEM32\DCIMAN32.dll LoadedModule[46]=C:\Windows\system32\IMM32.DLL LoadedModule[47]=C:\Windows\system32\MSCTF.dll LoadedModule[48]=C:\Windows\SYSTEM32\hid.dll LoadedModule[49]=C:\Windows\SYSTEM32\bthprops.cpl LoadedModule[50]=C:\Windows\SYSTEM32\BluetoothApis.dll LoadedModule[51]=C:\Windows\SYSTEM32\bcryptPrimitives.dll LoadedModule[52]=C:\Windows\system32\uxtheme.dll LoadedModule[53]=C:\Windows\SYSTEM32\WinUSB.DLL LoadedModule[54]=C:\Windows\system32\WINTRUST.dll LoadedModule[55]=C:\Windows\system32\MSASN1.dll LoadedModule[56]=C:\Windows\system32\CRYPT32.dll LoadedModule[57]=C:\Windows\system32\dwmapi.dll LoadedModule[58]=C:\Windows\SYSTEM32\msimg32.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Dolphin.exe AppPath=G:\Users\NJRockingham\Desktop\Dolphin-x64\Dolphin.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=8D0FAEE8729A7210280196EE378B030A RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - Temperhoof - 01-26-2016 Please help me. I'm seriously at my wits end here guys. All I can say is I really wish you'd just add Game Data Loading in NetPlay option to the newer versions of Dolphin. It really would resolve this problem and make a lot of people happy. I know you guys say it'll Dsync everything, but not for every game. Just a small toggle option would be great. RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - JosJuice - 01-26-2016 I also wish an option like that would be added. It's hard to know when it will happen, though. RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - Temperhoof - 01-29-2016 (01-26-2016, 09:34 PM)JosJuice Wrote: I also wish an option like that would be added. It's hard to know when it will happen, though. RESOLVED I finally figured out what happened. The old version of Dolphin 4.0-6492-x64 corrupted a few files from the following two download packs, just reinstall them to fix the problem: Virtual C++ 2013 Redist x64 - Download DirectX 9.0 End-User Components - Download RE: Older Builds like 4.0-6492-x64, Refuse to load anymore - mbc07 - 01-30-2016 Err... No, Dolphin does not corrupt anything. If it weren't working before you probably didn't install those redistributables after reinstalling your OS (and no, they aren't part of windows and thus should be installed separately) |