[color:"orange"]How Can I know if the problem is hardware or software ?[/color]
Unfortunately, the only reliable method to tell for sure is to fix the problem; if you have to replace something to do so it is a hardware problem, otherwise it is software. It is most likely software, though, since it sounds like it is getting past the CD check.
When you ran dxdiag to see if it reported any problems, did you try running the tests in the Display tab?
If you start the configuration program, can you run the test and save?
I once had a problem with cut scenes crashing a game, but after trying it on a laptop and having them work, I noticed one of the differences was that VSync was enabled on the laptop. Enabling this on my desktop cleared up the problem (under Display Properties, Advanced, and with Radeon drivers in the 3D tab, Direct3D settings). I do not have VSync enabled any more, so this is not an issue with BD, but that could be the kind of thing causing your problem.
Can you boot into Safe Mode? Another person had a corrupt monitor driver, resulting in a crash whenever the screen tried to switch to 640x480 (Safe Mode or for the inro video).
In Windows Explorer, if you browse to the '
..\Beyond Divinity\Static' folder, can you view the '
intro.mpg' video?
The install program should report any problems, such as CRC errors, during install. However, if it fails to do so, or a file becomes corrupt after installation, the integrity of the files can still be verified using a program such as
FileCheck;
download (194KB). This is a small freeware program (no install required) to calculate the CRC-32 values (the cyclic redundancy check used in zip files) of a number of files. It can also compare a previously calculated CRC file with a set of files/folders.
After doing a clean install of BD and rebooting, I deleted the files in the '
..\Beyond Divinity\DirectX9' folder (since they are not needed if/once DirectX 9 is installed). Then I used FileCheck to create a crc file of the game folders, installed the 1.45 patch and did so again, both before starting the game. If you compare the appropriate CRC file to your install, it should tell you if there are any corrupt files. You do not need to worry about moving any saved games out of the
savegames folder or deleting the files in the dynamic folders, since new files will not be tested by FileCheck, just those listed in the crc file. If you have started the game and changed any options, there will be differences reported in the
config.div and
keylist.txt files. In my install the '
..\Beyond Divinity\Editor\dgen_themes.000' file was also reported to be different.
There are several files in the
Beyond Divinity folder created when the game is started or options are changed, including
init.cfg, mapids.000, persist.dat, sinfo.000, slashed-d3d6.cfg, slashed.cfg, sound.cfg and
starlog.txt. A couple other files are also added, but another crc file including these wouldn't help much, since most or all are system or option dependent, so these files would usually be reported as different regardless of being valid or corrupt.
At least the
config.div,
slashed.cfg and
slashed-d3d6.cfg files in the
Beyond Divinity folder can be deleted, and the configuration program / game will recreate them the next time it is started.
Beyond Divinity CRC files (190 KB)
[*] These crc files are based on the UK English version; the North American version should be the same, I think, and the Australian version not too different (it uses a different copy protection).
[*] FileCheck expects the files to be in the original locations to verify, so if you installed BD to a location other than the default (
C:\Program Files\Larian Studios\Beyond Divinity), open the CRC file in Wordpad (for example), and do a search-and-replace so the file/folder paths match your install.
If your CRC values match, it is not the game itself, but likely a conflict with something else in your system or a problem in the saved game folder. When examining the list of 'errors' FileCheck produces, potential problem files would be those with an error trying to read, or with a large size difference (especially zero byte files) from the known good install.