Dave-H

Thanks @jaclaz. I have no normal uninstallation option for the driver, so do you think I can uninstall it using the INF file with the necessary command? The file has [Uninstall.CopyFiles] and [Uninstall.AddReg] sections, but no [DefaultUninstall] section. BTW I am horrified at the awful news coming from your country. I do hope you and yours are still OK.

Yes, I wonder if some pruning of the INF file might do the trick. I'm not interested in any of the "bells and whistles". As long as the driver will go into the mode I need, and is stable, that's all I'm hoping for. I've attached the INF file here in case anyone with more experience of customising these types of drivers has any suggestions. Thanks for any input. oem39.inf

Another update. I think I can now definitely say that the driver can work, if only at a basic level. If I boot into Safe Mode and disable the display adapter, when I then boot into normal mode and re-enable it, the driver loads and I can set higher resolutions (including 1366x786) without any problem. The display is good, although there is no acceleration. The display control panel still crashes if I try and use any of the tabs added by the AMD driver. However, that's usable as far as I'm concerned, at least it isn't stuck in VGA mode! It still won't survive a reboot though, it just blue screens again, and I have to then go into Safe Mode again and repeat the whole procedure. So, why will the driver apparently load OK when the machine is already up and running, but won't load when booting?

Apparently UBO 1.74 isn't being supported any more, whereas UBO 1.16 is, specifically for legacy browsers. See here and the subsequent posts. I use 1.16 now and it seems to work fine and auto-updates.

OK, I tried again this morning, with the same result, and then thought I would try another version of ati2dvag.dll, as that is the file apparently causing the problem. I found another version to download and substituted it. The original version is 6.14.10.7280, the substitute I found is 6.14.10.7279. Then it started OK, but with very bad resolution and colour depth, which could not be fixed. I then reverted to the original version, and to my great surprise it still started OK, and I could change the settings. I actually got it into 1024x768 with 32 bit colour! (My panel is actually 1366x768, but who cares!) Great, I thought, until I rebooted, at which point I just got the BSOD again. I've also noticed that the Advanced driver settings crash when I try to use them "Error Detected! Aborting. Please verify if EMGD is active." Still, I am heartened by this as I have seen that the driver can work! All I've got to do now is find out why it won't keep working!

OK, I gave it a try! I extracted the driver files, and added my device ID to the INF file. Running setup didn't offer the graphics driver, so I installed from the INF file. It installed the driver as "AMD Radeon HD 8240". I then rebooted and just got the following BSOD. I had to boot in Safe Mode to get back in, and the driver is still being offered, but presumably won't work again. It seemed to be so close too!

Thank you yet again @cdob! I will try that out and report back. Cheers, Dave.

It's been a while, but another glitch seems to have now appeared. I noticed a while ago that multiple images on IG posts were showing spurious ugly scroll bars on Firefox 52 ESR, but now most of them are just showing empty white boxes as well, with no content. Normal single image and video posts seem to be still fine.

Just one thing I'd like to ask about before I seriously start to see if a proper driver is possible here. I thought that if a graphics card had no drivers available, it would appear in Device Manager as "Microsoft Basic Display Adapter". My card is appearing under "Other devices" as "Video Controller (VGA Compatible)". This is fine as far as it goes, but it's prompting me to install a driver on every boot, which is really annoying! I've checked "Don't prompt me again to install this software" umpteen times, but it makes absolutely no difference. I've tried searching for "Microsoft Basic Display Adapter" as a driver option, but it doesn't seem to exist. How can I make it default to that? I can't see any left-over third-party graphics driver files in the INF folder, but if I select to search the machine for drivers I just get a list of ancient incompatible ATI drivers, which are presumably the ones that come with Windows XP. Thanks for any suggestions, I just want to get rid of the constant driver installation nag! Cheers, Dave.

Oops, another "senior moment"! I completely forgot about that other thread, that's where I was pointed to VBEMP of course. Please do merge them @dencorso. I'm definitely losing it........... To answer your question, I didn't try modding the INF file in any of the other drivers, if that's what you mean. I've actually deleted them all now as I was just getting confused as to which was which. Do you have any recommendations as to a likely one to try? All the XP Catalyst packages I've seen seem to be much too old to work with an HD series graphics chip.

Sorry I should have said this in the first post! The hardware ID is PCI\VEN_1002&DEV_9839. I had tried searching for that but didn't come up with anything. I had a look at that drp.su link, I doubt if there's anything there that will work on XP, and I'm very loathe anyway to use a site that makes you download their "driver installer" to get any drivers, which is almost certainly loaded with spyware at very least, and malware at worst!

The differences between 52.9.0 ESR and 52.9.1 ESR seem to have been very minor. 52.9.1 is also only available in US English, it needs language packs added for anything else. I'm sure you're not missing out on anything by still using 52.9.0! As for the original YouTube problem, it seems to have now gone away! Probably just a temporary glitch.

I'm not holding out much hope here, but does anyone know of an XP driver which might work on this hardware on my Asus X102B netbook? There are obviously no official XP drivers available. I have tried using @bearwindows VBEMP driver, but it doesn't seem to work, just shows "Device cannot start - code 10". All I want is something to get it out of VGA mode and to ideally 1366x768 resolution, which is the native resolution of the display panel. I'm not at all concerned about acceleration or anything like that, which is almost certainly impossible. Any suggestions gratefully received! Cheers, Dave.

Actually yes there was and is! See here.

I've just now noticed that on Firefox 52.9.1 ESR, I'm no longer seeing the proper sidebar when I go to https://www.youtube.com/feed/subscriptions. I'm just seeing this - If I go just to youtube.com and then select "subscriptions" on the left I get the correct display, with all my subscribed channels displayed in the sidebar. I've tried using different user agent strings, but no difference. Seems to be fine in Google Chrome 49 and Otter, but not on Opera 36, where the sidebar is showing the same as Firefox! It was fine yesterday! Any ideas anyone?

Thanks, I tried it as it was, and at last it worked! The "IDE ATA/ATAPI Controllers" section has completely disappeared from Device Manager, and there is now an "AMD AHCI Compatible RAID Controller" instead, which the system disk is connected to. I guess that's correct. I'm so sorry guys that I made such heavy weather of this. @RainyShadow, @jaclaz, and @cdob, I'm so grateful to you all. I like to think that I always learn something new from all these problems, whether I remember it is another matter of course! Now, all I need is drivers for the graphics and the Ethernet controller, and a driver that works for the touchpad so I can actually change its settings (the "tap to click" function is driving me mad!) and I will be in business! That's not for this thread though, as this was specifically about booting problems, I will start new threads for the other drivers if I don't have any luck finding them (the graphics I am very pessimistic about). Cheers, Dave.

Sorry to be thick, but you've lost me there! Are you saying I should add PCI\VEN_1022&DEV_7801&CC_0106 to that registry file before importing it, and it won't work as it is?

Thank you! What do you think @jaclaz?

Oops, hadn't seen your previous post @jaclaz! The forum page was sitting there for ages and for some reason it didn't flag that there had been another post. OK, I will do it again with the driver from the IN1VDO11WW1 package, or are you saying I should be using the IN1AHC20WW1 package? Sorry to be so confused with all these different packages which all look like different versions of the same thing to me!

OK, I force installed the Ahcix86,sys RAID driver onto XP using driver inject on 8.1. All went successfully, but still BSOD 7B on XP startup in AHCI mode. Still starts OK in IDE mode thank goodness! The controller is still showing "Standard Dual Channel PCI IDE Controller". ahcix86.sys is not present in the system32\drivers folder. amd_sata.sys is in the folder, but doesn't seem to be being used. It identifies as "AHCI 1.2 Device Driver".

OK, I've now removed all the AMD software, and the controller is now back to being the Microsoft "Standard Dual Channel PCI IDE Controller". I've also lost the driver for the HD audio bus and the USB 3 controller, but I know I can now put them back from the AMD package, and they work! I'm intending to now use the "AMD_WinXP_KV_KB_BON_Jan13_2014.exe" package as it is I suspect the last XP version if it's from 2014, newer than the Lenovo package.

Sorry for muddying the waters with the graphics problem, you are absolutely right that I should be concentrating on just one issue at a time! I've been working on drivers for the graphics and touchpad at the same time and getting in a confused mess. The ACHI issue really does have the highest priority at the moment as at present I am having to switch the controller mode between operating systems, with is annoying. I have been confusing myself by installing different drivers in the hope of hitting on one which works, which is obviously not a very scientific way of going about it! I did install from IN1VDO11WW1, but then tried other AMD Catalyst packages too, mainly to try and find a graphics driver which worked, but they installed other drivers too. This included most recently the "AMD_WinXP_KV_KB_BON_Jan13_2014.exe" software suite package that @RainyShadowlinked to in a previous post (as an aside it is really beyond annoying that this forum doesn't number its posts!) This being apparently from 2013 seemed to be newer than the IN1VDO11WW1 (signed 2011) package. I will now uninstall everything and start again! I should be able to roll back to the generic Microsoft IDE driver (I hope!) Sorry for the mess, I should know better after all the times I've solved problems with people here in the past, including you @jaclaz Cheers, Dave.

Well I thought I had! The driver in Device Manager changed from the generic one to an AMD one, even though it;s running in IDE mode at the moment. I was assuming that the AMD driver is AHCI capable as well, it's just not using that mode at the moment, but would if it was seeing the right device ID.

Thanks again! I uninstalled the VBEMP driver, sorry I really should have found that page myself with the details of how to do it! Annoyingly it's trying to find a graphics driver every time I boot up now, even though I've ticked the "do not ask again" box umpteen times! So, if the device SATA controller ID does change according to the BIOS setting, why when I put the BIOS to AHCI just it just BSOD when I run XP? Shouldn't it detect the change and load the correct driver, assuming it's on the system of course?

Unfortunately all the INF files in these drivers don't include my hardware ID, which is PCI\VEN_1022&DEV_7800. They contain 7801, 7802, 7803, 7804, but none of them contain 7800! I've done some more research, and that 7800 ID seems to be always listed as "AMD SATA Controller (IDE Mode)". The other IDs are listed as "AMD SATA Controller (AHCI Mode)". Now I know the hardware supports AHCI because it does on Windows 8.1. However, on XP it seems to be identifying as an IDE only device. Is it possible for its device ID to change depending on BIOS settings or something like that?!