burd
Content Type
Profiles
Forums
Events
Posts posted by burd
-
-
23 hours ago, win32 said:
At that offset, there is call to an internal function called _errno. Unfortunately it is difficult to determine what exactly caused the crash, but I have some ideas.
I noticed that the d3d12 runtime is digitally signed, and as such is not supposed to be modified. So I'll remove it and you can see how that works (no d3d12 games here). You may need to boot with driver signing disabled.
will the game authenticate without that? im pretty sure its needed for anticheat purposes
0 -
4 minutes ago, asdf2345 said:
Rust works, but it requires you to mod the absolute newest version of Steam to work.
Also, I believe that Vista maxes out at 5.9
Sounds good , but is the fps like it should be?
0 -
27 minutes ago, asdf2345 said:
I decided to see how well 372.70 worked on my GTX 970, and when I tried playing some games, this happened.
Edit: I don't know why MSFN spoilers are broken. The part at the bottom of the spoiler is supposed to be outside the spoiler, and I can't edit or even select the text to fix it.
Problem signature:
Problem Event Name: APPCRASH
Application Name: Watch_Dogs.exe
Application Version: 0.1.0.1
Application Timestamp: 543589ed
Fault Module Name: StackHash_493a
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 000000017fff0004
OS Version: 6.0.6003.2.2.0.256.1
Locale ID: 1033
Additional Information 1: 493a
Additional Information 2: db691d52f1d1bc8218a5cad3c00cd028
Additional Information 3: f392
Additional Information 4: 4f4ce8141131ece1da3d928f04aee506Problem signature:
Problem Event Name: APPCRASH
Application Name: 7DaysToDie.exe
Application Version: 2019.1.0.11155
Application Timestamp: 5cae8f21
Fault Module Name: StackHash_4a28
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 000000017fff0004
OS Version: 6.0.6003.2.2.0.256.1
Locale ID: 1033
Additional Information 1: 4a28
Additional Information 2: ead5b3bdbb7aa35a106bb8b81109b2ba
Additional Information 3: 536b
Additional Information 4: bee453f194032ed77cde1c9b5beb3f04Problem signature:
Problem Event Name: APPCRASH
Application Name: DXMD.exe
Application Version: 1.19.801.0
Application Timestamp: 591411c6
Fault Module Name: StackHash_4957
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 0000000077490944
OS Version: 6.0.6003.2.2.0.256.1
Locale ID: 1033
Additional Information 1: 4957
Additional Information 2: ab25935ae6ae30f242345b0730db8e9c
Additional Information 3: b24f
Additional Information 4: 6cce6912c4101dc8c9d3ae89d42ddd3cProblem signature:
Problem Event Name: APPCRASH
Application Name: NeptuniaReBirth1.exe
Application Version: 0.0.0.0
Application Timestamp: 5e02ca9c
Fault Module Name: kernel32.dll
Fault Module Version: 6.0.6002.19623
Fault Module Timestamp: 5f11ff53
Exception Code: c0000005
Exception Offset: 00017914
OS Version: 6.0.6003.2.2.0.256.1
Locale ID: 1033
Additional Information 1: bdf7
Additional Information 2: 1d97f60290d369b2d98b4cb9f7abcd9a
Additional Information 3: 19da
Additional Information 4: 7b3170d5807c432865c8366ace394cf1Problem signature:
Problem Event Name: APPCRASH
Application Name: SRTTR.exe
Application Version: 1.0.0.1
Application Timestamp: 5ec50f06
Fault Module Name: SRTTR.exe
Fault Module Version: 1.0.0.1
Fault Module Timestamp: 5ec50f06
Exception Code: c000001d
Exception Offset: 00000000007e66cd
OS Version: 6.0.6003.2.2.0.256.1
Locale ID: 1033
Additional Information 1: 919e
Additional Information 2: 8922e810363c0ea80f2c733c5549e161
Additional Information 3: c5ac
Additional Information 4: e1fa0aab24955821ee042acce64d70cc3DMark 11 worked great though, as long as I used windowed mode.
The errors also happened on 365.19, so I'm guessing it's a issue with the extended kernel. One of the games even officially support Vista, so I don't know why they're crashing.
does any game work to be testable? perhaps windows score assessment?
i get 5.9 even on a 1060gtx , but on w7 its 7.9
0 -
9 hours ago, win32 said:
I found a version block for Windows 8/8.1 in the file, but nothing for Vista.
So I think the D3D parts of 368.xx/372.70 are like this:
900 series and below: works on Vista as with old drivers
Pascal support added in these new drivers that have no official Vista support, so no workie on Vista
Drivers have specific Windows 7 directives, so Pascal probably works when Windows 7 directives are in force.
So I think that once I can get the drivers to use the Windows 7 directives, that may be enough to get D3D working as good as Windows 7. Possibly including 12 unless DXGI does not cooperate.
would i still need to use winload.efi and ntoskrnl for these updates or theyre not necessary?
0 -
32 minutes ago, win32 said:
Apparently they have specific blocks for 8.x too. I just need a copy and I'll look at it.
You want the d3d12 file? Done.
0 -
@win32 do you think d3d12 binaries can be backported or tricked to run on Vista from Windows 7 , ofcourse currently Direct3D is barely functioning on Vista but i feel like it could be possible.
One of my game folders also possess this dll , https://imgur.com/a/euTUEPn
0 -
1 minute ago, windows2 said:
I mean, Windows Vista is no longer specifically supported by Microsoft. Even if it still gets monthly updates from Server 2008. This is not enough for complete protection
But better than W2K , last patch 10 years back , even Vista users are finding it hard to keep up to date with everything dropping support , their former glory days will never return sadly , i dont mean disrespect to w2k but its just overly outdated imo just like XP and support for w7 dropping will only make it harder for all of us in the future.
0 -
5 minutes ago, windows2 said:
As for Windows Vista, it is no less dangerous than Windows 2000 in terms of protection.
It gets monthly updates from Server 2008 , Windows 2000's last update was in 2010 and even with kernelEx its not much , not sure how its the same according to you in terms of protection , not to forget lack of newer directx aswell
0 -
37 minutes ago, windows2 said:
What are the problems exactly. Because by using the extended kernel, the programs are mostly compatible with Win2K
lack of security , lack of dlls and functions , basically one would need Vista SP2 as a bare minimum for todays real standards
0 -
4/10 , too outdated its broken beyond repair almost
0 -
2 hours ago, win32 said:
I will work on modding 372.70 usermode components. I just looked at nvd3dumx.dll (D3D usermode driver for x64 components) and I found this suspect code:
.text:00000001806B94AF mov cs:VersionInformation.dwOSVersionInfoSize, 11Ch .text:00000001806B94B9 mov cs:VersionInformation.dwMajorVersion, 6 .text:00000001806B94C3 mov cs:VersionInformation.dwMinorVersion, 1 .text:00000001806B94CD mov cs:VersionInformation.wServicePackMajor, r15w .text:00000001806B94D5 call cs:VerifyVersionInfoW
Maybe u can see from the 32bit version and compare? since it seems like the 32bit apps have no issue with it.
1 -
3 hours ago, win32 said:
did this start with my modified files? If there's an error, please tell me more (is it the same one that occurs with winSAT? if so, maybe an update to ntext could help).
It didnt start with your files the drivers are just broken on vista , your files dont fix those errors , there are many instances where i get this error , IE9 64bit , Steam games , sometimes in windows score assessment (winsat i think) , All of them 64bit , 32bit dxdiag works fine , while 64bit crashes
one thing to note is that , the steam games would just crash without your modified files , but with it , it would probably run with proper drivers since it crashes on the nvidia D3D10 dll now.
1 -
9 hours ago, win32 said:
Drivers will take awhile (need to really extend ntoskrnl/ntrknlmp), especially newer NVIDIA drivers that are needed for RTX and GTX 16xx. I'll have to add like 40 functions for the 41x drivers. Some are very complex and there is no guarantee of stability.
could the old drivers 368.XX - 372.70 be fixed easily? compared to the 400.XX drivers? Even an old fully functional driver could help , currently applications and many games crash with nvwgf2umx.dll error specifically and with DirectX and Vulkan both broken and Opengl not supporting many low tier apps its hard to do much especially on Pascal.
0 -
@win32 i see ntext in the folder , is it usable currently or just there incomplete and how would one get it to work?
0 -
7 hours ago, Vistapocalypse said:
You must be referring to https://forums.mydigitallife.net/threads/windows-vista-bypass-eol-with-windows-update.81026/page-2#post-1617010. It sounds like a Server 2008 license would be required. For mere mortals, it might be a lot easier to just switch to Server 2008.
actually theres a separate topic with the how-to's and requirements , server 2008 license isnt required(for the tool atleast) to do this and one can choose between only having Vista or 2008 Updates or even both in my case.
1 -
abbodi on mdl has managed to restore WU functionality with working SHA-2 apparently and can get both Vista and Sever 2008 Updates (even ESU) and possibly even Windows defender updates?
2 -
2 hours ago, win32 said:
I have resigned myself to declaring that ntdll on Vista and up is indeed off limits. I again went to XP x64 for some inspiration and installed (Vista-compatible) Blender 2.90 on it. Several functions were missing like InitializeCriticalSectionEx. That function imports RtlInitializeCriticalSectionEx from ntdll, which also was introduced in Vista. So that requires doing the near-impossible, import table expansion.
Then I looked at One-Core-API. As @Ximonite pointed out, ntext helps extend ntdll. ntext is a layer between kernel32 and ntdll, and most of ntext is imports and forwards respectively from/to ntdll. No new imports unless we make our own binaries, but forwards are indeed exports from the file. The people designing the PE format certainly had some nice tricks up their sleeves!
Though I was forwarding functions to ntdll from kernel32 in Windows 2000 back in June, so my memory is going I guess.
So this ntext would be a copy of ntdll with new and upgraded functions. But what about programs that call ntdll directly (which is frowned upon for win32 applications as kernel32 is what they're supposed to call as an intermediary)? A patcher that changes import table references from ntdll to ntext in a particular program is needed.
Preferably, I'd like to make the file that ntoskrnl loads and is integrity-checked a decoy named ntext (which would be the original ntdll), while everything else calls a modified ntdll (so no changes to import tables are necessary). But changing the reference to ntdll I found in ntoskrnl did nothing.
so making the winload.efi is still a thing or it wont be needed anymore?
0 -
9 hours ago, win32 said:
Technically Vista can take advantage of WDDM 1.1 features. I use driver version 320.92 x64 and DWM RAM usage remains stable even with over 25 windows open, as opposed to increasing linearly as what happens with WDDM 1.0.
I found this, 38x drivers running on Vista:
But how exactly? The kernel mode part has exported missing functions since 372.90.
Later on i found out , it doesn't work at all , 372.70 is indeed the last working so you are correct.
0 -
51 minutes ago, win32 said:
Well, it appears that MS got around to improving Haswell, though there are still some issues.
I haven't been able to test it due to issues with Windows Update on my Kaby Lake though.
Now I'm thinking; do I rebase the extended kernel on the September 2020 versions of files, thus abandoning the April 2017 versions? Or do I still work on LoadLibraryExW from build 6519 since that is flawless, while this one is not (mind you, the UAC permission issues may lie elsewhere).
The issues still exist , the stability is just a bit better , it would have a 65% successful boot compared to 50% of before august
0 -
6 minutes ago, win32 said:
So there seems to be something wrong with my custom osloader.efi. Unfortunately there is no EFI hardware here for me to test it with, so any corrections will take awhile.
Does my ntkrnlmp.exe work with the regular winload.efi and nointegritychecks = 1 (yes) in the boot entry?
Though this could also be used in theory, but I need to test it:
it doesn't work even with winload.efi same error
0 -
0
-
1 minute ago, win32 said:
I don't see a picture.
hold up
0 -
Just now, win32 said:
Delete osloader.exe and just download my osloader.efi that I just added to the extended kernel folder. Then replicate my bcdedit instructions (including the new one above).
i get an error see above link :S
0 -
ok I did it and I get this error
0
[WIP] Windows Vista Extended Kernel
in Windows Vista
Posted · Edited by burd
ill try them and let you know , hopefully it works out. is the nvwgf2um wrongly named?