Windows 7 "AppHangB1"
I've been struggling with the 'black screen startup' issue for a while. Today, my Logos 6 didn't even get that far...
Here's the log file: 1067.Logos Log Files_AppHangB1.zip
In addition, here's what Windows had to say:
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: Logos.exe
Application Version: 6.14.0.79
Application Timestamp: 58349feb
Hang Signature: ab13
Hang Type: 513
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105
Additional Hang Signature 1: ab1352bbb16c38d1bab9085f985d54ae
Additional Hang Signature 2: daf7
Additional Hang Signature 3: daf73c0dc9d2350cfadcd21c7fb807fd
Additional Hang Signature 4: 22a9
Additional Hang Signature 5: 22a9d85bec15d099d40ce63ff5d49c41
Additional Hang Signature 6: 85f3
Additional Hang Signature 7: 85f3375d139e0cb88d425430252a0229
It started on the second attempt, but the number of recent crashes has become worrisome... I'd appreciate any help with this!
Paul
Comments
-
That's a difficult one to diagnose, but this may help.
Check for any system file corruptions:
a. Click Start, All programs and then Accessories. Right Click Command Prompt and select Run as administrator.
b. In the Command Prompt window type “sfc /scannow” (without quotes) and then press Enter.
c. After the scan has completed, close the command prompt window, restart the computer and check for the issue.
Dave
===Windows 11 & Android 13
0 -
Paul Unger said:
I've been struggling with the 'black screen startup' issue for a while. Today, my Logos 6 didn't even get that far...
What is the graphics hardware and driver version ?
Does a Steam folder exist in C:\Program Files (x86) ?
Another idea is scanning for malware; personally have used Malwarebytes
Keep Smiling [:)]
0 -
-
sfc /scannow returned the result: "Windows Resource Protection did not find any integrity violations."Dave Hooton said:That's a difficult one to diagnose, but this may help.
Check for any system file corruptions:
a. Click Start, All programs and then Accessories. Right Click Command Prompt and select Run as administrator.
b. In the Command Prompt window type “sfc /scannow” (without quotes) and then press Enter.
c. After the scan has completed, close the command prompt window, restart the computer and check for the issue.
I guess I'll just keep submitting logs if there are issues. Thanks for your help!
0 -
Paul Unger said:
Intel has newer 15.33.43.4425 driver for Intel HD Graphics 4000 (released on 31 May 2016)
https://downloadcenter.intel.com/product/81499/Intel-HD-Graphics-4000
Keep Smiling [:)]
0 -
Roger that. I had already checked whether there was an update when you asked about my graphics driver version. Even though I found the driver version you found, I ran the Intel Driver Update Utility just for fun, which gave me the following message:Intel has newer 15.33.43.4425 driver for Intel HD Graphics 4000 (released on 31 May 2016)
https://downloadcenter.intel.com/product/81499/Intel-HD-Graphics-4000
"A customized computer manufacturer driver is installed on your computer. The Intel Driver Update Utility is not able to update the driver. Installing a generic driver instead of the customized computer manufacturer driver may cause technical issues. Contact your computer manufacturer for the latest driver for your computer."
Lenovo provides this driver for my X230, which I already have installed (release date 2016-09-01 [newer than the one you linked]). So it seems my graphics driver is up to date.
0 -
Paul Unger said:
Lenovo provides this driver for my X230, which I already have installed (release date 2016-09-01 [newer than the one you linked]). So it seems my graphics driver is up to date.
Concur plus learned Intel version numbers are a bit challenging: last four are significant:
Lenova read me mentions 10.18.10.4425 date of 2016/08/26
Paul Unger said:I've been struggling with the 'black screen startup' issue for a while. Today, my Logos 6 didn't even get that far...
From Alpha and Beta release crash experience, have my program settings open to a blank layout. Some crashes happened before blank layout appeared. Other crashes happened after blank layout opened OK followed by opening something else: e.g. Home Page. Most crashes only affected some functionality while some crashes prevented application usage. Documenting how to repeat crash allowed Faithlife development to replicate and fix.
Keep Smiling [:)]
0 -
Paul Unger said:
I guess I'll just keep submitting logs if there are issues. Thanks for your help!
You should try Technical Support as they can diagnose whilst logged on to your computer.
Dave
===Windows 11 & Android 13
0
said: