Jump to content
  • 0

Wrye Bash does not start


richardo11

Question

Been modding Skyrim for years, never have had this problem

 

Skyrim SE is installed outsdide C:/ drive

MO2 and all others tools (LOOT, XEdit ....etc) are installed in a separate folder than Skyrim launcher

MO2 and all other applications launch properly, LOOT, xEdit, Performance Monitor, SKSE Launcher, sEdit ..... , no problem at all

The game launchs and plays without issues....

 

Tryed to install Wrye Bash many times, in a separate folder where all the other tools are, in the main skyrim folder, in C:/ drive, with Python, without Pyton, with/out extra location...

Run the app with Administration permission.. etc

Running from Windows7

 

Once the WryeBash executable is set in MO2, once i click, MO2 block (like anyother executable) for a couple of seconds .. and then un-blocks, WryeBash simply does not launch, no messages or warnings of any kind..

 

I am in a state of desesperation, googling for days, posting everywhere ... Can's make a Bash patch .... Please help

 

WryeBash Carsh Dump:

 

Version=1
EventType=APPCRASH
EventTime=132049989732206010
ReportType=2
Consent=1
UploadTime=132049989732806010
ReportIdentifier=583914ba-8eb7-11e9-97f4-ac9e17b4e9b8
IntegratorReportIdentifier=583914b9-8eb7-11e9-97f4-ac9e17b4e9b8
WOW64=1
Response.BucketId=3446077172
Response.BucketTable=373684609
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Wrye Bash.exe
Sig[1].Name=Application Version
Sig[1].Value=307.2018.731.1531
Sig[2].Name=Application Timestamp
Sig[2].Value=49180193
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.24475
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5cdd8011
Sig[6].Name=Exception Code
Sig[6].Value=e06d7363
Sig[7].Name=Exception Offset
Sig[7].Value=0000c5af
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1044
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=ad0e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=ad0e4577e1fbfd6243b60ca89f681c02
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=368c
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=368cfefa7fa92b8bc4b5e7c8499d4d7a
UI[2]=D:\Mopy\Wrye Bash.exe
UI[3]=Wrye Bash 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]=D:\Mopy\Wrye Bash.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[5]=C:\Windows\syswow64\USER32.dll
LoadedModule[6]=C:\Windows\syswow64\GDI32.dll
LoadedModule[7]=C:\Windows\syswow64\LPK.dll
LoadedModule[8]=C:\Windows\syswow64\USP10.dll
LoadedModule[9]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[15]=C:\Windows\system32\IMM32.DLL
LoadedModule[16]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[17]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[18]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[19]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[20]=C:\Windows\system32\rsaenh.dll
LoadedModule[21]=C:\Windows\syswow64\ole32.dll
LoadedModule[22]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[23]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[24]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.24460_none_2b1e532a457961ba\COMCTL32.dll
LoadedModule[25]=C:\Windows\system32\msimg32.dll
LoadedModule[26]=C:\Windows\system32\VERSION.dll
LoadedModule[27]=C:\Windows\system32\secur32.dll
LoadedModule[28]=C:\Windows\system32\uxtheme.dll
LoadedModule[29]=C:\Program Files (x86)\Ruiware\WinPatrol\PATROLPRO.DLL
LoadedModule[30]=C:\Windows\syswow64\urlmon.dll
LoadedModule[31]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[32]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[33]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[34]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[35]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[38]=C:\Windows\syswow64\iertutil.dll
LoadedModule[39]=C:\Windows\syswow64\WININET.dll
LoadedModule[40]=C:\Windows\syswow64\USERENV.dll
LoadedModule[41]=C:\Windows\syswow64\profapi.dll
LoadedModule[42]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll
LoadedModule[43]=C:\Windows\system32\WSOCK32.dll
LoadedModule[44]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[45]=C:\Windows\syswow64\NSI.dll
LoadedModule[46]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.24467_none_5c08a697a00c8eef\gdiplus.dll
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\system32\WINMM.dll
LoadedModule[49]=C:\Windows\system32\atl.DLL
LoadedModule[50]=D:\Mopy\loot_api.dll
LoadedModule[51]=C:\Windows\system32\WINHTTP.dll
LoadedModule[52]=C:\Windows\system32\webio.dll
LoadedModule[53]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[54]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[55]=C:\Windows\system32\MSVCP140.dll
LoadedModule[56]=C:\Windows\system32\VCRUNTIME140.dll
LoadedModule[57]=C:\Windows\system32\api-ms-win-crt-runtime-l1-1-0.dll
LoadedModule[58]=C:\Windows\system32\ucrtbase.DLL
LoadedModule[59]=C:\Windows\system32\api-ms-win-core-timezone-l1-1-0.dll
LoadedModule[60]=C:\Windows\system32\api-ms-win-core-file-l2-1-0.dll
LoadedModule[61]=C:\Windows\system32\api-ms-win-core-localization-l1-2-0.dll
LoadedModule[62]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.dll
LoadedModule[63]=C:\Windows\system32\api-ms-win-core-processthreads-l1-1-1.dll
LoadedModule[64]=C:\Windows\system32\api-ms-win-core-file-l1-2-0.dll
LoadedModule[65]=C:\Windows\system32\api-ms-win-crt-heap-l1-1-0.dll
LoadedModule[66]=C:\Windows\system32\api-ms-win-crt-string-l1-1-0.dll
LoadedModule[67]=C:\Windows\system32\api-ms-win-crt-stdio-l1-1-0.dll
LoadedModule[68]=C:\Windows\system32\api-ms-win-crt-convert-l1-1-0.dll
LoadedModule[69]=C:\Windows\system32\api-ms-win-crt-locale-l1-1-0.dll
LoadedModule[70]=C:\Windows\system32\api-ms-win-crt-math-l1-1-0.dll
LoadedModule[71]=C:\Windows\system32\api-ms-win-crt-filesystem-l1-1-0.dll
LoadedModule[72]=C:\Windows\system32\api-ms-win-crt-time-l1-1-0.dll
LoadedModule[73]=C:\Windows\system32\api-ms-win-crt-environment-l1-1-0.dll
LoadedModule[74]=C:\Windows\system32\api-ms-win-crt-utility-l1-1-0.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-848890124/nBucketTable=373684609/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Wrye Bash
AppPath=D:\Mopy\Wrye Bash.exe
 

Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0

Did you get 307.2018.731.1531 from Nexus or github? The 307 Beta 3 version I downloaded from Nexus (307.2018.704.57) seems to be working fine, but one of the builds I downloaded from github had much the same issue.

Link to comment
Share on other sites

  • 0

In order to be absolute sure (I know i did download from github and nexus) I went over nexus and downloaded the installer, it is not exactly the same version as you comment - Wrye Bash 307.2018.070.40057

Reinstalled (Deleted first ALL mopy/WryeBash)  --- The same problem, MO2 blocks, cmd console flash for a second,, and MO2 un-blocks, WryeBash does not even lunch

 

One thing i did see, in task manager, wrye Bash.exe*32, fires up, remains there for 1 second or less, then WerFault.exe*32 fires, and half a second after, wryebash*32 shuts down from task manager

 

How damn that could be, this computer has had Wrye Bash installed many times...

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.