7.0 Kernelbase.dll error

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

Chris450

6 discussion posts

When the user starts DF the start button flickers on the 2nd screen, then he gets an error message:
Fault Module name: Kernelbase.dll
DF Pro 7.0
Windows 7 enterprise 32 bit.

Any ideas how to fix this?

Thanks

• Attachment [protected]: DF.png [9,331 bytes]

Dec 23, 2014 • #1

Haven't run into that one before! Would you be able to send over a debug log? Here are the steps:

On the Troubleshooting tab, change the Logging drop-down to "L2: Log Detailed"
Restart DisplayFusion
Reproduce the issue and note the time so we'll know where to check in the log file
Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
Disable debug logging after sending the log

After sending the log, if you'd like to temporarily roll back to 6.1.2, here's the link: http://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-6.1.2.exe

Thanks!

Dec 24, 2014 • #2

Chris450

6 discussion posts

Attached is the .log file, the only other file in the directory is a .db file, I do not see a debuginfo.html file. The error happened at 8:08am and 8:09am.

• Attachment [protected]: DisplayFusion log.log [6,205,577 bytes]

Dec 29, 2014 (modified Dec 29, 2014) • #3

RyanW

11 discussion posts

Getting the same second screen flicker and then a crash by DF7. I never get a readable error message but I assume it's a similar issue.

Win7 Pro 64 bit

Look around the 11:32-11:33 AM mark for 12/29/14

• Attachment [protected]: DisplayFusion.zip [435,782 bytes]

Dec 29, 2014 (modified Dec 29, 2014) • #4

RyanW

11 discussion posts

I'm dyin here! I reverted back to 6.1.2 and none of my window management features enabled by group policy are working.

Such as: "prevent mouse from snagging on uneven monitors" or "use mouse to scroll window under mouse that are not in focus" they are checked and greyed out because they are set via GPO but they aren't working.

I'd rather just upgrade to 7.. but as posted above it just grenades out on me.

Dec 29, 2014 • #5

Hey guys, we're looking into this to see what's up.

@Chris450: Can you roll back to 6.1.2 (http://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-6.1.2.exe) and then see if there's a DebugInfo.html file in %localappdata%\DisplayFusion? If there isn't, can you just copy the info from the Settings > Troubleshooting tab to a text file and attach it?

Thanks!

Dec 29, 2014 • #6

Chris450

6 discussion posts

Quote:

Will do.

Dec 29, 2014 • #7

RyanW

11 discussion posts

here's my HTML

• Attachment [protected]: DebugInfo.html [105,617 bytes]

Dec 29, 2014 (modified Dec 29, 2014) • #8

Also, we've just put up a test build with some more logging added to try and track down the issues with the 7.0 taskbar. Could you give it a try, and send over new logs if it still crashes?

http://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-7.0.0.1.exe

Thanks!

Dec 29, 2014 • #9

Chris450

6 discussion posts

OK, so here is what I have done:
Version 6.1.2- works fine for all users
V 7.0- works fine for local administrator account, and my AD user account, but not for user(AD) of that PC
V 7.0.1- works fine for local administrator account, and my AD user account, but not for user(AD) of that PC
I installed 7.0.1 per request, I logged on as user with the issue and DF error-ed out at 8:08 and again when I tried at 8:10, log files attached

• Attachment [protected]: Debug DF.zip [212,880 bytes]

Jan 2, 2015 • #10

Ok, interesting! We're adding some more logging for 7.1 Beta 2, but in the meantime, would you be able to try each of the 7.0 Betas (starting with Beta 1), to determine which beta this started happening in? That will help us narrow down which changes might have broken it.

Here's the link to a ZIP file containing all of the 7.0 Betas: http://www.binaryfortress.com/Files/DisplayFusion/DF-7.0-Betas.zip

Jan 2, 2015 • #11

Please disregard my previous post. This issue should be all fixed up for 7.1 Beta 3