Jump to content

Damnation

Member
  • Posts

    763
  • Joined

  • Last visited

  • Days Won

    3
  • Donations

    0.00 USD 
  • Country

    Australia

Damnation last won the day on April 13 2022

Damnation had the most liked content!

4 Followers

About Damnation

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Damnation's Achievements

172

Reputation

  1. @Zorba the Geek Try Relyze disassembler, or ghidra disassembler, and see if what they output is suitable. Both are free.
  2. @Mov AX, 0xDEAD I just tried to apply your most recent .patch file for a build. Did I do it wrong somehow?
  3. @Dietmar Can you run a debug on storport 8.0 beta 8102 to find the cause of this storport 7E BSOD? (remember to restore original XP SP3 HAL and acpi.sys before running debug this) dietmar_storport_8102_7e.7z
  4. @SFMG Sorry to hear that. You could try looking around at one of those PC recycling places and see if you can pick up a GPU for free.
  5. @SFMG I'm not sure what your needs are, you may as well try out the driver and see if it works for you.
  6. @SFMG If you're stuck with the RX580 then you'll have to settle for a generic 2D driver in XP. bearwindows.zcm.com.au/vbempk.zip
  7. @SFMG I'd say your best option would be to get a cheap Nvidia GT 710 or 730 and run it along side your RX580 in a lower PCIE slot. Nvidia kept XP support up to GTX 980 whereas AMD dropped support around the R7 270.
  8. @Mov AX, 0xDEAD I know this isn't related to ACPI, but I got my hands on some windows 10 private symbols and was wondering if you could use them to make an NDIS_emu extender using them like how you did for ntoskrnl?
  9. @Dietmar Probably going to stop on trying to backport newer vista acpi.sys to XP. I just don't understand why an exception occurs at a zero address.
  10. @Dietmar I noticed that ACPI 5112, which still has XP RSDT find function in it. also gives this 7E BSOD. So I think I can narrow down the cause of the BSOD to either HalGetInterruptTargetInformation or HalGetMessageRoutingInfo in my HAL and not my ACPI table finding code.
  11. @Dietmar It seems like that's the case, I wonder why microsoft did it that way. I'm going to go through vista beta acpi.sys and see which version is first to BSOD.
  12. @Dietmar OK, thanks for testing. let me try a few things...
  13. @Dietmar There are some IoResource functions in my ntoskrn8.sys Perhaps it's getting stuck there? does loading my ntoskrn8.pdb show anything?
×
×
  • Create New...