The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
DirectX refuses to get the fuck in line and play ball.
psycojester
Registered User regular
Registered User regular
Last night on a whimsical flight of fancy i bought Overlord: Raising hell for the PC. Got it home tried to install it, everything seems to be going well. The game seems to install just fine, up until it decides that i'm too stupid to know if i'm using the correct version of DirectX and it has to check for it.
Thats where things get fucked up and the installation causes a BSOD. After that happened a couple of times i tried going directly to microsoft, and downloading the latest version of directx 9, same BSOD. So i went and download the latest drivers for my graphics card (Nvidia 8800 GT) and see if that helped at all. After i installed those directx would update just fine and dandy but Overlord still BSODs when it gets up to looking for the latest version of directx.
Could anybody suggest any probably causes for this behaviour and/or solutions. I'd give you the BSOD error code, but the screen only flashes up for a second or two before my system resets, is there a way to recover the information on the BSOD after it's occoured?
Thats where things get fucked up and the installation causes a BSOD. After that happened a couple of times i tried going directly to microsoft, and downloading the latest version of directx 9, same BSOD. So i went and download the latest drivers for my graphics card (Nvidia 8800 GT) and see if that helped at all. After i installed those directx would update just fine and dandy but Overlord still BSODs when it gets up to looking for the latest version of directx.
Could anybody suggest any probably causes for this behaviour and/or solutions. I'd give you the BSOD error code, but the screen only flashes up for a second or two before my system resets, is there a way to recover the information on the BSOD after it's occoured?
[SIGPIC][/SIGPIC]
psycojester on
0
Posts
PAGE-FAULT_IN_NONPAGED_AREA"
"Technical information
*** STOP: 0x00000050 (0xE61CD230, 0x00000000, 0xB80DB510, 0x00000001)
*** 3f14f3c5450ba7c07100e4e93648d77- address B80DB510 base at B80D8000, Datestamp 483bef3d "
anything helpful there?
The name of the file your BSOD is referring to sounds suspicious to say the least, so I think I would have tried looking into where it comes from. I'm pretty much certain that it does not come from any display driver, or any other "official" hardware driver. The only non-malware software I can think of that generates such random filenames for its drivers is Daemon Tools (and similar software).
If not XP you might want to try running the Overlord install in one of the XP compatability modes and see if that helps.
Tofu wrote: Here be Littleboots, destroyer of threads and master of drunkposting.