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. 


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


Everything posted by greenhillmaniac

  1. The last branch of drivers to work with Windows 8 was the 16.30, which means the Radeon 16.7.3 work great (tested it just now. The drivers install through device manager just fine. No need to disable driver signature enforcement). Link: http://www.guru3d.com/files-details/amd-radeon-software-crimson-16-7-3-whql-driver-download.html
  2. Maybe it was a temp link... Here's the driver's article page (I'm using the W7 x64 version, BTW): http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-17.9.3-Release-Notes.aspx I have a R9 380 4Gb version with the following driver ID: PCI\VEN_1002&DEV_6939
  3. Yeah, I should've probably been more explicit on this... I'm trying to install the AMD Radeon Crimson 17.9.3 (the latest WHQL drivers available) and I'm trying to install them through the Device Manager, linking directly to the INF fille. The BSOD happens after the driver files have copied, when the screen is shifting resolutions (and you even hear the W8 sounds of hardware being unplugged and plugged, indicating the GPU is being installed). After that the BSOD appears on my desktop resolution of 1920x1080. I don't even get to see the desktop on its full resolution. As soon as the screen is changing resolutions the BSOD happens. Here's the link to the driver. I extracted the files from the .exe with 7-Zip and used the INF in \Packages\Drivers\Display\W76A_INF\C7318501.inf https://www2.ati.com/drivers/beta/whql-radeon-software-crimson-relive-17.9.3-win7-64bit-oct2.exe Yeah. It was part of the May 2016 Patch Tuesday, which you installed just fine back then
  4. Nope, still BSOD. This confirms my suspicion that AMD is blocking installation on NT 6.2. The only way this seems to be fixable is to actually mod the driver... Shouldn't be too hard. Only look for the DRIVER_INSTALL_NT62=0 section Here's the minidump. 110717-34890-01.dmp
  5. Welp, there's a Server 2012 version, which means there is a version for Windows 8.0 I'll try it and report back.
  6. For anyone willing, I have a MiniDump file of the BSOD. I was trying to analyze it, and it says the error was with dxgkrnl.sys? Seems weird, considering it's a system file... MiniDump contents: Microsoft (R) Windows Debugger Version 10.0.17016.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\John\Downloads\110617-37484-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 8 Kernel Version 9200 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9200.16384.amd64fre.win8_rtm.120725-1247 Machine Name: Kernel base = 0xfffff801`fe206000 PsLoadedModuleList = 0xfffff801`fe4d0a60 Debug session time: Mon Nov 6 16:31:18.127 2017 (UTC + 0:00) System Uptime: 0 days 0:04:21.807 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list .............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 139, {3, fffff88004ef9dd0, fffff88004ef9d28, 0} Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::SubmitPresentHistoryToken+1ef ) Followup: MachineOwner --------- nt!KeBugCheckEx: fffff801`fe281040 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`04ef9ab0=0000000000000139 110617-37484-01.dmp
  7. Doesn't work. Booted with Driver Signature Enforcement disabled and the same BSOD happened. Even edited the INF file to see if it did anything. I don't think this is an issue, because the driver was designed for Windows 7.
  8. Starting in 2016 AMD drivers stopped working on Windows 8.0, giving a BSOD with the following message: KERNEL_SECURITY_CHECK_FAILURE. This seems to be an artificial block imposed by AMD, because the drivers work just fine in Windows 7 and Windows 8.1 and the BSOD occurs when the driver has already adjusted to the screen resolution of my monitor (switching from the default 1024x720). It's a shame really, because previous driver versions worked great, with the Radeon Control Panel, Vulkan and video acceleration all working fine with WDDM 1.2! My question to anyone with enough knowledge on this subject: is there a way to remove this artificial block? Any tools you might recomend for me to trace this issue and possibly fix it? Also, please don't come with the useless response of "Just use the older version" because that's not the point. The point is to extend the longevity of NT 6.2, seeing new driver versions support new GPUs (for example, the recently released RX Vega is not compatible with Windows 8.0 because of this driver block).
  9. IE10 updates are cumulative and only necessary if you only install the Security Only updates, since the Monthly Rollups already include it. As for .NET updates, there are 3 files basically released each month: one for .NET 3.5 SP1, one for .NET 4.5.2 and one for .NET 4.6, 4.6.1, 4.6.2 and 4.7. Security Only .NET updates are a mess, and I recomend that you just simply install the Quality Rollups, because they don't release in tandem with the QR and are harder to track.
  10. BTW, does anyone want me to include a folder in the repository with the Windows Update speedup patches, as mentioned in @2008WindowsVista's video on the subject? I think it would help whoever is trying to fresh install Vista in 2017 and beyond (all 0 people, lol)
  11. And following my Windows 8.0 repository update, here comes the Vista update for October! Better late than never Added the following Security Updates: KB4041671 KB4041944 KB4041995 KB4042007 KB4042050 KB4042067 KB4042120 KB4042121 KB4042122 KB4042123 KB4042723 Added the following .NET Security and Quality Rollups: KB4040978 for .NET 2.0 SP2 KB4040977 for .NET 4.5.2 KB4043764 for .NET 4.6-4.6.1 Added the following non-security update in the extras folder: KB4035176 - Improvements and Fixes to Universal C Runtime in Windows Added a readme file in the extras folder with details on what each update does Changed the names of the .NET Security Only and Security and Quality Rollup folder for easier navigability Corrected a file insider the mandatory .NET updates on the x86 folder See y'all next month https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w
  12. And another (late) repository update with October's patches plus one extra for both x64 and x86. These include: Monthly Rollup: KB4041690 Flash Update (released a week after the Monthly Rollup): KB4049179 Internet Explorer 10 Cumulative Update and Security Only Update: KB4040685 and KB4041679, respectively .NET Framework Security and Quality Rollup Updates for .NET 3.5 SP1 and 4.5.2 and 4.6, 4.6.1, 4.6.2 and 4.7: KB4040979, KB4040975 and KB4043762, together with the required pre-requisite update KB4019990 .NET Framework 4.7.1: KB4033345 (extracted from the .exe installer), together with the required pre-requisite update KB4019990 and instructions for language pack installation I've also put the Update Rollups in their own folder in the Extras, for easier navigation. That is all... See you next month https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ
  13. Could you explain specifically in which scenarios this happens?
  14. I managed to get the Catalyst 15.6 somewhat working with my R9 380, but it's super unstable (not suitable for day to day work): http://www.msfn.org/board/topic/175825-about-amd-drivers-on-vista/?do=findComment&comment=1128711 Hope this suffices.
  15. OK, let me be perfectly clear, since apparently I'm not getting through... I was asking if you could take a look at later driver releases of AMD drivers made for Windows 7, and see if you could somehow make them work on Vista, since newer AMD cards need those drivers to work properly. If you need links, this is the first driver that with modifications stopped working on Vista. This is for Windows 7 x64 BTW! https://us.softpedia-secure-download.com/dl/1069864f843f79accc67b99dffd22ee4/59e24e1b/300450294/drivers/video/amd-catalyst-15.7-with-dotnet45-win7-32bit.exe Sorry for getting off topic guys!
  16. I would redirect you to this thread, where everything is explained: But basically, we were able to mod driver versions newer than the latest official one (the Catalyst 13.12 that you mention), but we got stuck on Catalyst 15.6. After that each and every INF modded driver gives Error 39 when trying to install (this happens on Catalyst 15.7 and later). This means any user with a Rx 300 series, RX 400 series, RX 500 and RX Vega card cannot get 3D acceleration on Vista (I'm included in the Rx 300 series group )
  17. .NET Security and Quality Rollup for October 2017 https://www.catalog.update.microsoft.com/Search.aspx?q=4043769 https://support.microsoft.com/en-us/help/4043769/october-2017-security-and-quality-rollup-for-net-framework-3-5-4-5-2-4
  18. I hate to derail a perfectly good thread, but consider this a side note: Could you also take a look at the AMD drivers? They don't work since the 15.200 branch of drivers (or since Catalyst 15.7), leaving anyone with a Rx 300 series or newer GPU on the cold, when it comes to Vista...
  19. I would also add this to the analogy: the motorbikes were great to use, and had in many ways superior handling and features to the competition! But the new CEO decided to make the exclusive parts of their bikes for other bike manufacturers, all the while not telling consumers if their own brand of motorbikes was still worth getting. Ultimately they decided to shrink their offer of motorbikes, stopped offering new firmware updates, replacemant parts, etc. and left users with a dead end motor vehicle
  20. To be fair... Windows Media Player was always garbage
  21. I usually disable account sync from the settings when I use a Microsoft account, along with automatic OneDrive photo upload, which means OneDrive only functions as a cloud file server and nothing else. Also, since I disable settings sync, I don't get any extra disk IO or network activity. Besides, OneDrive on 8.1 has the huge advantage of file placeholders, which means my HDD won't be filled with useless space (I have almost 3GB worth of data).
  22. I've done some digging, and it turns out the new Monthly Rollup Preview is not at fault for the inability to login with a Live account on Windows 8.x. Turns out it's just Microsoft's servers' fault (what a shock). They say they are working on a fix for this issue, but don't have an ETA. On the other hand, the corruption of the CBS is the fault of the new MRP, since i ran the command "sfc /scannow" before and after applying the patch, and it reported corruption after installing it. Just clearing up some (dis)information
  23. Do you know where I can find PEMaker? I can't find it with a simple Google search.
  • Create New...