EasyBCD 2.0 Beta 100 crashing.

#1
When I try to run BCD 2.0 Beta 100 I get the following error message.

BCDError.jpg

Crash Details
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: easybcd.exe
Problem Signature 02: 2.0.0.100
Problem Signature 03: 4c100c32
Problem Signature 04: EasyBCD
Problem Signature 05: 2.0.0.100
Problem Signature 06: 4c100c32
Problem Signature 07: 10b
Problem Signature 08: 21f
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I have the same error while using beta 99 however, when I use beta 88 I get the following

BCDError2.jpg

I have installed Windows 7 Ultimate in a VHD and the drive letter for the Bootdisk/System Disk (XP) is removed..

However both versions of EasyBCD work when I give a drive letter to system partition.
 

mqudsi

Mostly Harmless
Staff member
#2
Hi rmittal,

Thanks for your bug report.

Can you please post the output of "bcdedit.exe" from an elevated command-prompt?

2.0 is almost set for release, so I would appreciate if you could reply ASAP.
 

Terry60

Knows where his towel is.
Staff member
#4
Can you post a screenshot of your Disk Management
 

mqudsi

Mostly Harmless
Staff member
#5
OK, I'll check now and see if I can fix the crash.

Addendum:

Terry, it's a known issue for Windows and bcdedit to break down with that error message, EasyBCD still works via manual selection. It definitely shouldn't crash, though.
 
Last edited:

Terry60

Knows where his towel is.
Staff member
#6
There's no problem per se with the RC not finding the BCD, (my config tests that aspect of every new build), so I thought it might be relevant to see what about this config crashes the app.
(I removed the letter from my "active" "non-system" partition as a test. Easy is still fine)
 

mqudsi

Mostly Harmless
Staff member
#7
I have no drive letter on my hidden partition as well, but I had forgotten that you get that dialog on each system start.

/testing.....


aaaand you're right. That's not the problem. EasyBCD handles that error gracefully enough.


Addendum:


Oh wait.

rmittal, please delete this folder and see if the error goes away:
C:\Users\Your User Name\AppData\Local\NeoSmart_Technologies
 
Last edited:
#8
Sorry for the delay in posting.

@Terry60
Disk Management Screen.

DiskManagement.jpg

@Computer Guru
deleting the folder "C:\Users\my User Name\AppData\Local\NeoSmart_Technologies"
did not change anything.

I once again want to inform that if I give a drive letter to my Boot/system disk all works without any problem.
 

mqudsi

Mostly Harmless
Staff member
#9
Select "Change Boot Drive" and choose "Drive D:" as the new destination.
Once that's done, go to "Add Entries" and add a Windows XP and a Windows 7 entry.

IF that doesn't work:

Select "Change Boot Drive" and choose "Drive C:" as the new destination.
Once that's done, go to "Add Entries" and add a *Windows 7 entry only.*
Enter the BIOS and swap the order of drive 0 and drive 1 (or physically do so with the cables)
Boot back into 7, use EasyBCD to add a Windows XP entry now.
Reboot and test.
 
#10
Select "Change Boot Drive" and choose "Drive D:" as the new destination.
Once that's done, go to "Add Entries" and add a Windows XP and a Windows 7 entry.

IF that doesn't work:

Select "Change Boot Drive" and choose "Drive C:" as the new destination.
Once that's done, go to "Add Entries" and add a *Windows 7 entry only.*
Enter the BIOS and swap the order of drive 0 and drive 1 (or physically do so with the cables)
Boot back into 7, use EasyBCD to add a Windows XP entry now.
Reboot and test.
Pardon, but is it relevent to my post, I am unable to follow you.
 

mqudsi

Mostly Harmless
Staff member
#11
Oh god.. sorry, wrong thread!

Addendum:

For your problem: I'll send you build that can generate a crash dump that I can use to trace the issue.
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#15
@rmittal: Found the problem. Can you please provide the output of "bootgrabber.exe /tlist" from the command line? BootGrabber.exe is found in C:\Program Files\NeoSmart Technologies\EasyBCD\bin\

@Tricky Dicky: Well, build 100 is the latest build of "Release Candidate" quality. There are builds 101, 102, and now 103 floating around the forums that each address specific issues for certain users. When these issues are resolved for sure, I will release RC2. And when an RC is out with no issues, I will release EasyBCD 2.0 Final.
 
#16
Screenshot for command "bootgrabber /tlist"
BG.jpg

Console Output
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>bootgrabber.exe /tlist
BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>
Could not get FileFsFullSizeInformation on partition \Device\Harddisk0\Partition1. Error: 0x80000010D0,3,3,1,320072933376
P1,,7,26839056384,0,Yes,multi(0)disk(0)rdisk(0)partition(1)
P2,,23,26847313920,26750799872,Yes,multi(0)disk(0)rdisk(0)partition(2)
P0,,5,266383918080,0,Yes,
P0,,5,266383886336,0,No,
P3,D:\,7,266383885824,111173644288,No,multi(0)disk(0)rdisk(0)partition(3)
D1,1,1,0,26739736576
P1,C:\,7,26738688000,6177161216,Yes,
D2,1,1,0,2000683008
P1,X:\,11,2000616960,1603121152,Yes,
 

mqudsi

Mostly Harmless
Staff member
#17
Can you replace bootgrabber with this one and try again?

IF it still crashes, please post the output of BootGrabber.exe /tlist once more.

Thanks :smile:
 

Attachments

#18
Screenshot for command "bootgrabber /tlist" Bootgrabber.exe downloaded from the post above.

BG2.jpg

Note : Run directly from my download location. (Didn't replace the original)
 

mqudsi

Mostly Harmless
Staff member
#19
Ok, looks good. Replace bootgrabber in the easybcd folder and the easybcd crash should go away.
 
#20
@Tricky Dicky: Well, build 100 is the latest build of "Release Candidate" quality. There are builds 101, 102, and now 103 floating around the forums that each address specific issues for certain users. When these issues are resolved for sure, I will release RC2. And when an RC is out with no issues, I will release EasyBCD 2.0 Final.
OK. So if I want to use it now, the 100 is the right way to go .. right?