
Damnation
Content Type
Profiles
Forums
Events
Posts posted by Damnation
-
-
0
-
Ah, so no crashdump or live debug is possible for this storport then?
I chose windows 8.1 storport simply because it was newer than 8.0 - From my testing storport 8.0 will also have this 9F BSOD problem.
0 -
You could maybe debug with a crashdump? i.e https://www.sysnative.com/forums/threads/how-to-debug-a-driver-power-state-failure-bugcheck-0x9f-when-1st-param-0x3.27871/
Has XP given a crashdump for this BSOD?
0 -
-
332New_stornvme81 has free build of storport 8.1 not checked, but if checked is not working then use that.
Here is the PDB symbols for that storport.sys
0 -
OK,
Can you debug with just 8.1 storport & storahci please? It should give a 9F BSOD when the system tries to restart.
0 -
This 8.1 storport.sys is from checked 8.1 debug ISO, so I think checked XP ntoskrnl/hal is needed?
0 -
You're welcome!
If you have the time, can you debug the 9F BSOD I encountered trying to port windows 8 storport.sys and post in the thread I made?
0 -
First lets try just adding the Processors onto the end of your DSDT table and leave the other ACPI tables untouched.
This seems to work fine on my B550 steel legend, although it also leaves the duplicate ACPI0007 Devices in place doing nothing.
0 -
Well, unless I'm mistaken, those old drivers are your only option for Vista.
0 -
You don't need to use NTOSKRNL Emu_Extender on Vista, NTOSKRNL Emu_Extender is for XP.
There are already Vista drivers for Intel HD 4000.
0 -
-
Can you help me debug this 9F BSOD?
0 -
If you have the free time, can you set up a VM and try to trace where the 9F BSOD occurs in checked 8.1 storport.sys? If not in XP text mode setup then on an existing XP install?
I'm able to get all the way to the end of XP textmode setup with the 8.1 storahci driver, right up to the point where the system reboots and then 9F BSOD.
I've included the PDB symbols for both my checked ntoskrn8.sys and checked 8.1 storport.sys to help with this.
Edit: hold on, checked version of storport.sys has some missing imports. I'll fix it.
edit: fixed - https://ufile.io/rwbg20oa
0 -
So I've been working on trying to get storport and stornvme of windows 8.1 working on XP and for the most part it seems to be functioning, I can get XP installed. the issue I've run into is these driver power state BSODs.
Would you be willing to help solve this issue?
I'm sure @Dietmar would be interested in helping to solve this too.
here is my modified ntoskrnl extender source code - https://ufile.io/arl8wbth
0 -
Overheating maybe? Check with HWMonitor for both temps and power usage.
I noticed this on my new B550 Steel Legend that power usage (140W) and Temps (70C) were abnormally high just sitting idle and I needed a DSDT mod to fix it.
What motherboard do you have?
0 -
Can you let @Mov AX, 0xDEAD know about those 0x7E BSOD Kernel Trap BSODs you encountered?
2 -
26 minutes ago, Dietmar said:
all browser crash on their shutdown, only Mypal from Feodor not.
Curiously, Mypal crashes on me when I close it, or at least I get that prompt windows saying it has crashed. It seems to reopen again just fine though.
0 -
Besides the CPU power thing, Do we have any other ACPI problems on Z690?
0 -
True. It is by no means the best solution, but it works for now.
It's certainly better than having the CPU draw 140W at idle.
0 -
I am happy too!
I'm surprised the solution was so simple, I wish I'd thought of it sooner.
It would seem that DSDT tables on the AMD platform are much simpler to those from intel. I guess AMD is not as strict with their ACPI implementation as Intel is.
0 -
Until we have a fix for the ACPI0007 ID for XP a simple solution is to add this code into your DSDT table -
QuoteScope (\_PR)
{
Processor (C000, 0x00, 0x00000810, 0x06){}
Processor (C001, 0x01, 0x00000810, 0x06){}
Processor (C002, 0x02, 0x00000810, 0x06){}
Processor (C003, 0x03, 0x00000810, 0x06){}
Processor (C004, 0x04, 0x00000810, 0x06){}
Processor (C005, 0x05, 0x00000810, 0x06){}
Processor (C006, 0x06, 0x00000810, 0x06){}
Processor (C007, 0x07, 0x00000810, 0x06){}
Processor (C008, 0x08, 0x00000810, 0x06){}
Processor (C009, 0x09, 0x00000810, 0x06){}
Processor (C00A, 0x0A, 0x00000810, 0x06){}
Processor (C00B, 0x0B, 0x00000810, 0x06){}
Processor (C00C, 0x0C, 0x00000810, 0x06){}
Processor (C00D, 0x0D, 0x00000810, 0x06){}
Processor (C00E, 0x0E, 0x00000810, 0x06){}
Processor (C00F, 0x0F, 0x00000810, 0x06){}
Processor (C010, 0x10, 0x00000810, 0x06){}
Processor (C011, 0x11, 0x00000810, 0x06){}
Processor (C012, 0x12, 0x00000810, 0x06){}
Processor (C013, 0x13, 0x00000810, 0x06){}
Processor (C014, 0x14, 0x00000810, 0x06){}
Processor (C015, 0x15, 0x00000810, 0x06){}
Processor (C016, 0x16, 0x00000810, 0x06){}
Processor (C017, 0x17, 0x00000810, 0x06){}
Processor (C018, 0x18, 0x00000810, 0x06){}
Processor (C019, 0x19, 0x00000810, 0x06){}
Processor (C01A, 0x1A, 0x00000810, 0x06){}
Processor (C01B, 0x1B, 0x00000810, 0x06){}
Processor (C01C, 0x1C, 0x00000810, 0x06){}
Processor (C01D, 0x1D, 0x00000810, 0x06){}
Processor (C01E, 0x1E, 0x00000810, 0x06){}
Processor (C01F, 0x1F, 0x00000810, 0x06){}}
}
*This code is for a 16-core 32 Thread CPU.Compile your new DSDT
Then simply load this new DSDT with ASL 5.0
asl /loadtable -v dsdt.aml
the changes will persist after a reboot.
1 -
Yes!
I managed to get ASL 5.0 to work!
I merged my XP friendly CPUSSDT into my DSDT, compiled it, and loaded with ASL 5.0 !
So, for whatever reason, ASL is fine with loading DSDT+CPUSSDT merged together, but it fails with an A5 BSOD if you try to load them separately.
Changes persist on reboot.
I have absolutely no idea why this makes a difference, but there you go.
0 -
How do I make the .HEX files for patching? or am I misunderstanding?
0
USBXHCI 8.1 for XP?
in Windows XP
Posted
@Dietmar
Here is my 1st attempt at getting USBXHCI of 8.1 in XP.
Currently it gives a 7E BSOD in usbxhci.sys - please debug when you have time.
https://ufile.io/mzsc3dq9
patch integrator 3.1.1.6 with 8.1 usbxhci