Tripredacus Posted July 30, 2020 Share Posted July 30, 2020 A crash caused by a breakpoint can typically only be handled by the developer of the code that included the breakpoint. In general, it is a bad idea to release public code with a breakpoint in it without offering support for it. Now, the file that windbg complains about is the amdgpio2.sys. If this is an unmodified file from AMD, then I would say that this particular version should not be present. Or you can just not install the driver that put that in the system. In other words, you can't do anything if a breakpoint is what crashed the system, especially from binaries with no public symbols. Link to comment Share on other sites More sharing options...
asdf2345 Posted July 30, 2020 Author Share Posted July 30, 2020 8 hours ago, Tripredacus said: A crash caused by a breakpoint can typically only be handled by the developer of the code that included the breakpoint. In general, it is a bad idea to release public code with a breakpoint in it without offering support for it. Now, the file that windbg complains about is the amdgpio2.sys. If this is an unmodified file from AMD, then I would say that this particular version should not be present. Or you can just not install the driver that put that in the system. In other words, you can't do anything if a breakpoint is what crashed the system, especially from binaries with no public symbols. The GPIO was an unrelated issue, I'm talking about everything else Link to comment Share on other sites More sharing options...
Tripredacus Posted July 31, 2020 Share Posted July 31, 2020 Yet the GPIO driver caused the most recent crash in the dumps you provided. Link to comment Share on other sites More sharing options...
asdf2345 Posted July 31, 2020 Author Share Posted July 31, 2020 8 hours ago, Tripredacus said: Yet the GPIO driver caused the most recent crash in the dumps you provided. That was a faulty AMD driver I tried installing, it's not a issue I'm worried about Link to comment Share on other sites More sharing options...
asdf2345 Posted August 1, 2020 Author Share Posted August 1, 2020 I think it's a BIOS issue. I stumbled upon some old messages of me trying this in the past, but with a Ryzen 7 1700, HDD, and the same exact board, like right after I got it, and I had the exact same issues. I had assumed the 1700 was bad in some way, because of issues I had in the past with it, so I thought the Vista issues were from the CPU. (The board I used with the 1700 was what was bad) This leads me to believe it's a BIOS issue because @greenhillmaniac was able to get Vista working fine on a first gen Ryzen CPU. I posted about a custom BIOS request on Win-Raid, but didn't think about posting about me posting that here, as this doesn't have a BIOS area, but after a chat with someone, I decided to post it here, since it's related to getting Vista on my computer. https://www.win-raid.com/t7009f54-Request-BIOS-to-fix-issues-with-my-X-Gaming-Pro-Carbon-and-Windows-Vista.html Link to comment Share on other sites More sharing options...
burd Posted August 3, 2020 Share Posted August 3, 2020 Have you perhaps tried Vista x86? Maybe things are different there Link to comment Share on other sites More sharing options...
asdf2345 Posted August 3, 2020 Author Share Posted August 3, 2020 Just now, burd said: Have you perhaps tried Vista x86? Maybe things are different there Rather die than main a x86 OS Link to comment Share on other sites More sharing options...
burd Posted August 3, 2020 Share Posted August 3, 2020 Just now, asdf2345 said: Rather die than main a x86 OS You dont need to main it , just to see if the results are the same since the x86 users have 0 issues with vista (even on Haswell+ apparently) Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now