Occulus
(1000+ posts)
Send PM |
Profile |
Ignore
|
Tue Aug-02-11 11:46 AM
Original message |
"d3dcompiler_42.dll is either not designed to run on Windows..." |
|
Can someone help me with a DirectX problem?
It seems d3dcompiler_42.dll is somehow broken. When I try to play one specific game, I get the message in my subject line. The game itself does not install that file.
I have tried copying the actual .dll from the .CAB files in the DirectX SDK download, I've tried reinstalling DirectX (no luck there, it's not even possible in Windows 7).... I still get that error, that the file is "not designed to run on Windows".
I just deleted the file entirely and reran the dxwebsetup program from Microsoft, and I still get that same error.
HELP!
|
ChromeFoundry
(1000+ posts)
Send PM |
Profile |
Ignore
|
Wed Aug-03-11 07:42 AM
Response to Original message |
1. DirectX End-User Runtime Web Installer |
|
You are running DirectX 11 and the application is probably looking for the 9.0c API extensions. Backup, then, try installing this: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=35
|
Syrinx
(1000+ posts)
Send PM |
Profile |
Ignore
|
Thu Aug-04-11 04:26 AM
Response to Reply #1 |
2. what is that number in your sig? |
ChromeFoundry
(1000+ posts)
Send PM |
Profile |
Ignore
|
Thu Aug-04-11 11:53 AM
Response to Reply #2 |
4. It is a random number that changes evey time you refresh. n/t |
Occulus
(1000+ posts)
Send PM |
Profile |
Ignore
|
Thu Aug-04-11 10:23 AM
Response to Reply #1 |
|
I even copied the .dll directly from the /cab when that didn't work. Believe it or not, I get the same error- even when the file is downloaded as part of a package from the Microsoft website.
Maybe I just need to reinstall Windows.
|
ChromeFoundry
(1000+ posts)
Send PM |
Profile |
Ignore
|
Thu Aug-04-11 12:05 PM
Response to Reply #3 |
5. Before you reinstall Windows... |
|
Open command prompt, with "Run as administrator" via right-click.
Then execute: sfc /scannow
That will repair Windows 7, you will need the installation CD for this command.
|
Occulus
(1000+ posts)
Send PM |
Profile |
Ignore
|
Tue Aug-09-11 01:17 PM
Response to Reply #5 |
6. Well, it appears Windows wasn't the culprit |
|
Yesterday was the day my hardware decided to give up the ghost entirely. Thankfully, I have backed up everything I wish to back up, but it suddenly started losing CMOS settings (replacing the battery was the first thing I did) and three times got stuck in a "try to boot- power down completely and try again" loop. For some reason, the only way the PC will now boot properly is to power down, manually clear the CMOS using the tiny button on the mobo, power up, and ignore the warnings and use the factory defaults. This will get me into Windows, but unfortunately, there are several BIOS settings I need to have enabled for things like SLI and such.
Additionally, as of last night the POST screen didn't show on the screen at all; neither did the Grub menu, nor the Windows splash screen. I don't know what I did or how I did it and I couldn't replicate the keystrokes I used if you paid me because I was literally flying blind, but after several tries, I'm now- somehow- in Windows with all my desired CMOS settings in place. I really don't want even to reboot, though.
Obviously, there is more going on here than a simple collapse of the OS. That I can live with, but it's looking more and more like I need a new mobo (which of course also means a new CPU and RAM), and which oh yes, must also have an nForce chipset and support an SLI configuration so I don't also have to shell out for a new GPU (when I already have two that work).
Mommy...
|
DU
AdBot (1000+ posts) |
Mon Sep 22nd 2025, 03:07 AM
Response to Original message |