Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



Sign in to follow this  
greenhillmaniac

Artificial AMD driver block on Windows 8.0

Recommended Posts

Did you find the solution to the problem? Did messing with DALNonStandardModesBCD entries help? I guess you could compare the full list in registry after each driver is installed and maybe use the list from the older driver if it's really connected to that for some reason. But it seems strange that the default resolution list would make the whole thing crash on one OS but not the other. Would be good to know if monitor's native resolution ends up on it.

DALNonStandardModesBCD# entries can be edited with Registry Editor after the driver is installed, one could boot the OS with just the basic driver, then search for DALNonStandardModes, they should be in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000. The 0000 might differ on systems with multiple graphics cards installed or if just the driver is installed but the card is not present. The format is quite simple, it's a sequence of resolutions and refresh rates, spread through multiple entries, I have 4. I've also noticed with various drivers for older cards that the default entries can differ. They can be used to add custom resolutions, I use it to add 1440x1080 resolution to the list by adding:

14 40 10 80 00 00 00 60

It's not encoded and can be read like you read any plain number on the paper. In Registry Editor, each mode ends up in its own line, so it's easier to read from there. So the first four bytes are width x height, followed by 3 zero bytes and finally the refresh rate. Not sure about the higher numbers, I guess you use last two bytes for higher refresh rates. My hardware is not that fancy so I can't try to see. Interestingly, some resolutions in my list have refresh rate set to zero. Under normal circumstances, changes can be tested just by disabling and re-enabling graphics card in Device Manager.

Share this post


Link to post
Share on other sites

Just tested @Tripredacus's suggestions, but they didn't work...

I'm still convinced there's something going on at a sys file level that's keepign these drivers from installing, be it explicit Windows 8 blocking or just implicit code that prevents the installation by messing with the dxgkrnl.sys. Just tested with the recently released Crimson 17.12.1, but still got the same error.

If anybody has the knowledge to debug drivers and check what's causing the BSOD please post here or PM me.

Share this post


Link to post
Share on other sites
53 minutes ago, Tripredacus said:

Which suggestions would those be exactly?

The ones of changing the INF file with those older entries and replacing the coinst17_30 dll?

Share this post


Link to post
Share on other sites

Ok just making sure. In a situation like this when trying to do something that doesn't work, using as much detail as possible is best.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×