Details are;
I open up my desktop shortcut (Or through the autoplay) and it shows most symptoms to most other peoples startup crashes:
+Game initializes.
+Screen goes black.
+Returns to Desktop.
+...
So, I've looked through other topics on this, and searched the internet for as long as I can bear; and now I turn to you all, to see if I've perhaps missed something.
Things I've tried:
+Installed the 1.2 patch from the official site. [Still persists.]
+Installed the fan-patch from whatever the site is. [Still persists.]
+Copied my BIN folder contents and duplicated them in my Vampire folder. [Still Persists.]
+Checked my LCD Screen Refresh Rate, it's at 60Hz. [Still persists.]
+Pimped out my graphics options (Optimized everything.) [Still persists.]
+Tried UnInstalling, and ReInstalling. [Still persists.]
+Tried deciphering the jargon/Programming language in my Crash Files. [Couldn't tell you left-from-right.]
+Double-Checked I was the Administrator of my PC (Which is relevant to a topic I'd read here in regards to one of my Crash Logs) and I'm the only user on this computer. [Admin Status Confirmed; Still persists.]
+Checked my HKEY_LOCAL_MACHINE/Software for "Python..." and couldn't find it. It was instructed to delete this tree, and the game would work. Since the tree doesn't exists, I've already deleted it? [Still Persists.]
+Double-Checked for DirectX 9.0 to be installed: It is. [Still persists.]
+========================================+
So, that's the low-down. I'll preview to you, my Crash-Logs, as I have two different ones, to see if you can figure anything out.
--------------------------
[Because I can't paste in this box, probably due to browser confliction, I'll just jot it down in point-form.]
+Access Violation in ntdll.dll at 001b:7c91142e.
&&
+Access Violation inshaderapidx9.dll at 001b:2a01d164.
--------------------------
A little bit of information about my computer;
---Intel(R) Graphics Media Accelerator Driver Report---
+Driver Version: 6.14.10.4250.
+Operating System: Windows NT* 5.1 2600 Service Pack 2.
+Default Language: Japanese.
+DirectX* Version: 9.0.
+Physical Memory: 2047 MB.
+Min. Graphics Memory: 8 MB.
+Max Graphics Memory: 224 MB.
+Graphics Memory in use: 145 MB.
+Processor: x86.
+Processor Speed: 3000 MHZ.
+Vendor ID: 0x8086.
+Device ID: 0x2582.
+Device Revision: 4.
* Output Devices Connected to Graphics Accelerator. *
+Active Monitors: 1.
-------------------------------------
Random Information through my "System Properties." homescreen.
---System:
+Microsoft Windows XP.
+Media Center Edition.
+Version 2002.
+Service Pack 2.
---Manufactured and supported by:
+Sony Electronics Inc.
+VIAO Computer.
++++++Intel(R).
+Pentium(R) 4 CPU 3.00GHz.
+3.00 GHz, 2.99 GB of RAM.
-------------------------------
So, I have not a clue. Sorry for writing a novel, it's just to not repeat silly incidents. Well; let me know if you can help; I'm pretty eager to play the game, and rather frusterated that I can't.
Startup Crash, w00. [Details Inside.]
Startup Crash, w00. [Details Inside.]
I am drunk with this vision... God; The title suits me well.
ntdll.dll is a layer for Windows NT, it might be corrupted, which means you might need to repair it.
shaderapidx9.dll is a layer for WMI, you might try to solve the problem by reinstalling your graphic drivers ( before you do this, you need to uninstall the original drivers ) and/or DirectX 9c.
If you google those DLL's you might find other ways to cope with it, but I am pretty sure your problem is system based, not game based.
If you have to repair your system, use the repair function of your Windows XP CD.
shaderapidx9.dll is a layer for WMI, you might try to solve the problem by reinstalling your graphic drivers ( before you do this, you need to uninstall the original drivers ) and/or DirectX 9c.
If you google those DLL's you might find other ways to cope with it, but I am pretty sure your problem is system based, not game based.
If you have to repair your system, use the repair function of your Windows XP CD.
Lucita y Aragon, Childe of Ambrosio Luis Moncada, Childe of Silvester de Ruiz, Childe of Boukephos, Childe of Lasombra
when I had similar problems they were graphics-card based - I think that I found a way to set the resolution to a safer one and it worked. in your case, I would suggest using a registry-edit tool to look for errors though. I think the programmes I use are RegEdit and WinShampoo - the problems that they pick up and help fix do sometimes clear the way to solutions, as they can de-junk the registry.
that may not be very helpful, but I would recommend using a registry-cleaning utility before other repairs.
that may not be very helpful, but I would recommend using a registry-cleaning utility before other repairs.
"All the world's a stage and all the men and women merely players"