Skulltrail192 / One-Core-API-Binaries

http://shorthornproject.com
659 stars 47 forks source link

BSOD (Blue Screen of the Death) Main Thread #233

Open Skulltrail192 opened 11 months ago

Skulltrail192 commented 11 months ago

This is the main thread to report all cases what you get a BSOD with OCA installed. To report, you need to provide the following information:

KarolJ90 commented 11 months ago

I have bluescreen dead after installation drivers I have Oca 3.04 and Windows XP English Edition I can't take a photo

Skulltrail192 commented 11 months ago

how i said in the topic description, specify the information.

sal-ammoniac commented 11 months ago

0x7E BSOD after installing https://github.com/shorthorn-project/One-Core-API-Binaries-Canary/releases/tag/3.0.5-20231227-experimental

PC: On VirtualBox Ryzen 6800H 2GB RAM IDE

System:Windows XP Professional SP3 Chinese

Package:Installed all packages except modern setup

Method:Bare system installed vbox guest addition and then install all package

下载

Skulltrail192 commented 11 months ago

What version of virtual box?

sal-ammoniac commented 11 months ago

What version of virtual box?

7.0.12

idontyboi commented 11 months ago

7.0.12

Happens after installing just the Base package or all others?

Skulltrail192 commented 11 months ago

0x7E BSOD after installing https://github.com/shorthorn-project/One-Core-API-Binaries-Canary/releases/tag/3.0.5-20231227-experimental

PC: On VirtualBox Ryzen 6800H 2GB RAM IDE

System:Windows XP Professional SP3 Chinese

Package:Installed all packages except modern setup

Method:Bare system installed vbox guest addition and then install all package

下载

Describe the steps to reach at that point

sal-ammoniac commented 11 months ago

7.0.12

Happens after installing just the Base package or all others?

all others

sal-ammoniac commented 11 months ago

0x7E BSOD after installing https://github.com/shorthorn-project/One-Core-API-Binaries-Canary/releases/tag/3.0.5-20231227-experimental PC: On VirtualBox Ryzen 6800H 2GB RAM IDE System:Windows XP Professional SP3 Chinese Package:Installed all packages except modern setup Method:Bare system installed vbox guest addition and then install all package 下载

Describe the steps to reach at that point

Install XP SP3 normally (chipset was set to ICH9), then install VBox Addition and install oca,

sal-ammoniac commented 11 months ago

Problem found:

If chipset was set to PIIX3 no BSOD (VMWare will not BSOD either as it use 440BX as default chipset), but if chipset was ICH9 then BSOD occur

idontyboi commented 11 months ago

all others

My guess is that the Driver Update is to blame. You can send a memory dump file if possible to look at the driver that crashed.

sal-ammoniac commented 11 months ago

all others

My guess is that the Driver Update is to blame. You can send a memory dump file if possible to look at the driver that crashed.

i tried install driver package only and no bsod

sal-ammoniac commented 11 months ago

weird,the problem disappeared

i tried later and did not appear again (i did not find dmp for bsod either)

qwertyopus commented 10 months ago

Installing OCA (base) 3.0.4 and older always cause BSOD after reboot on XP x64 SP2 if Realtek HDA driver is installed. Installed latest Realtek R2.74 or old R1.49 - doesn't matter. Without Realtek Driver, OCA installing normaly. IMG_20240117_110424

I don't known why, but Dump not created. However it's chosen in system properties.

AMD FX-8300, 16 GB DDR3, ASRock 960GC-GS FX with Realtek ALC662 Windwos XP x64 SP2 original with all updates, include Extended Custom Support for Server 2003 up to 08.2019. On real hardware, not VM.

Edit: Hm, BSOD does not occur if the Realtek driver is from WU, not from Realtek site.

qwertyopus commented 10 months ago

Also BSOD on startup rarely (may be once at 5 times) happening without Realtek driver in this scenarios: 1) 3.0.4 base + 3.0.4 additional 2) 3.0.3 base + 3.0.3 additional 3) 3.0.2 base + 3.0.2 additional + 3.0.2 api-set And not happening ever with: 1) 3.0.1 base + 3.0.1 additional + 3.0.1 api-set 2) 3.0.2 base + 3.0.2 additional + 3.0.1 api-set 3) without OCA Something in api-set 3.0.2 and newer?

Skulltrail192 commented 10 months ago

Installing OCA (base) 3.0.4 and older always cause BSOD after reboot on XP x64 SP2 if Realtek HDA driver is installed. Installed latest Realtek R2.74 or old R1.49 - doesn't matter. Without Realtek Driver, OCA installing normaly. IMG_20240117_110424

I don't known why, but Dump not created. However it's chosen in system properties.

AMD FX-8300, 16 GB DDR3, ASRock 960GC-GS FX with Realtek ALC662 Windwos XP x64 SP2 original with all updates, include Extended Custom Support for Server 2003 up to 08.2019. On real hardware, not VM.

Edit: Hm, BSOD does not occur if the Realtek driver is from WU, not from Realtek site.

Well, in my tests, I observed that this specific BSOD happens when I leave a pen-drive connected during boot.

BillionXP commented 9 months ago

I have installed Windows XP 64 bit on vm 4 cores 2240mb ram 128 vram controler type: IDE. Normal Windows XP 64 bit iso installed. Issue: bsod after installing base package and error during the installation:

Screenshot 2024-02-06 164848

Screenshot 2024-02-06 164954

Screenshot 2024-02-06 165201

BillionXP commented 9 months ago

also: it has been fully updated by legacy update. nothing else done.

BillionXP commented 9 months ago

i found the issue out. its a bug with apic launch set. basically cant have more then 1 core.

jonm58 commented 9 months ago

i found the issue out. its a bug with apic launch set. basically cant have more then 1 core.

?

JackMauro commented 9 months ago

Hello, I have a BSOD when I try to connect to the machine using Remote Desktop connection; i suppose while negotiating TLS secure channel.

PC configuration: VMWare Workstation 12.1; Real processor i I7-6700. Windows Configuration: Windows XP SP3 Professional fully patched without PosReady trick. OCA packages installed; all OCA 3.0.5; the BSOD started after Base package installation. Steps to reproduce the BSOD. I installed OCA base on the VM installed years ago, then i tried to connect the machine from another system using MSTSC.EXE version 6.3 with Network Layer Authentication support enabled and the machine crashes during secure channel negotiation. The BSOD fault seems to be in win32k.sys.

Thank you

bsod Mini021424-01.dmp

Bozfy commented 9 months ago

i found the issue out. its a bug with apic launch set. basically cant have more then 1 core.

?

Its an issue if you give it more than 1 core on vm. I dont know why. but it works now

Vigortheindestructible commented 7 months ago

I have the same C000021Aissue where a BSOD occurs after installing the base 3.0.5 package. What you guys mention about USB pendrives may be indeed related. For me however is I have to completely physically disconnect all my USB devices such as keyboard and mouse in order to get the system to boot.

Vigortheindestructible commented 7 months ago

Copied XP installation over to another device with different hardware using only IDE and standard dual channel drivers .and I get the excact same stop on the same moment. System works ok withouth OCA installed

Vigortheindestructible commented 7 months ago

I thought of sharing a bit of the hassle so far with OCA.

I am using an older Atlhon XP 64 Narra 6 with nVIDIA MCP61P and a Geforce 6150SE and 8gb RAM. Windows XP 64-Bit with SP2 Vanilla works perfectly

Symptom: Installing OCA base gives me a stop error C000021a when booting up. When I do not attach any USB drivers, including mouse and keyboard, the system boots up. However, The chance of booting up successfully seems to decrease with every use and boot of the system or the space the disk uses I´m not sure. After some reboots and changes in the system (for example installing a non related system thing such as a game) Eventually the chance of booting up becomes practically 0%, even with disconnected usb devices

What I tried: -Rebooting in Safe mode -Tried to install from safe mode -Tried to install OCA withouth any installed drivers on the system (No vga, ethernet, nothing, just bare Windows and standard Microsoft drivers -Tried to see if this gdiplus.man file (one that shows up during the OCA base setup as file protection) helps and placed in Windows/system32

Nothing helped so far. The only point of change I see is somewhere in the USB field. If I leave out all USB devices or disable openhcd and ehci drivers, the system seems to boot up fine. I could see to consider getting a PS/2 card for a mouse and keyboard as workaround.

So there I have some of my experience in installing. Perhaps someone has some idea of where to find a solution and maybe this helps in our search because I am probably not the only person with the same STOP error

jonm58 commented 7 months ago

https://github.com/Skulltrail192/One-Core-API-Binaries/issues/269

Skulltrail192 commented 7 months ago

Hello guys, i'm investigating that BSOD. I hope fix on the next days and on 4.0.0 RTM it will be fixed.

XboxAndVRAlex commented 3 months ago

Hello, I'm having this BSOD trying to install the base core. The system would ask me if I wanted to fix the files that were replaced by the base, and after a second or two, it BSODs. The hardware I'm using is a N68-GS4 FX R2.0 Mobo, with an AMD FX 4300 CPU. The RAM installed is 16 GBs of DDR3 DIMMs, running in Dual-Channel. The storage configuration is Sata, running as IDE. I'm running the x64 SP2 version. The only things that I have installed are the drivers for the integrated stuff for the motherboard (Network, SM Bus.), Palemoon, and VLC Media Player. I cannot replicate the BSOD, as the install cannot boot anymore, sadly.

BillionXP commented 3 months ago

Hello, I'm having this BSOD trying to install the base core. The system would ask me if I wanted to fix the files that were replaced by the base, and after a second or two, it BSODs. The hardware I'm using is a N68-GS4 FX R2.0 Mobo, with an AMD FX 4300 CPU. The RAM installed is 16 GBs of DDR3 DIMMs, running in Dual-Channel. The storage configuration is Sata, running as IDE. I'm running the x64 SP2 version. The only things that I have installed are the drivers for the integrated stuff for the motherboard (Network, SM Bus.), Palemoon, and VLC Media Player. I cannot replicate the BSOD, as the install cannot boot anymore, sadly.

I had a bsod problem once to. The only thing that fixed it was to set the CPU core amount to 1 for 64x bit windows XP. After installing one core and other components, setting back to four cores didn't show the bsod anymore. Anyways try that if possible. Because like I have mentioned it worked for me.

IzKuipers commented 1 month ago

Got 0x000000A5 after installing OCA (base order followed as per the readme). I restarted when it asked me, and then restarted one final time after everything was installed. Now it just bluescreens on boot:

IMG_0549

Skulltrail192 commented 1 month ago

Got 0x000000A5 after installing OCA (base order followed as per the readme). I restarted when it asked me, and then restarted one final time after everything was installed. Now it just bluescreens on boot:

IMG_0549

* HP Pavilion HDX9000

* Intel Core 2 Duo T7500

* Windows XP Professional SP3, English, no other modifications besides OCA

* Running on Intel AHCI

* 4GB DDR2

Do you installed OCA Driver Package?

IzKuipers commented 1 month ago

yes I did, I followed the readme exactly

jonm58 commented 1 month ago

yes I did, I followed the readme exactly

OCA Driver Package's ACPI.sys causes 0x5A BSOD

If you have Windows PE, you can solve it yourself:

  1. Obtain ACPI.sys for Windows XP yourself from the ISO in your hand(or 3rd-party ACPI,sys)
  2. Boot your Windows PE from USB/CD/DVD
  3. Delete "ACPI.sys" in "C:\WINDOWS\system32\drivers\"
  4. Get the "ACPI.sys" of Windows XP from the ISO in your hand and put it into "C:\WINDOWS\system32\drivers\"
  5. Close Windows PE and start your Windows XP

Good Luck

jonm58 commented 1 month ago

btw now One-Core-API's ACPI.sys is Longhorn 5048 or (?)?

IzKuipers commented 1 month ago

yes I did, I followed the readme exactly

OCA Driver Package's ACPI.sys causes 0x5A BSOD

If you have Windows PE, you can solve it yourself:

  1. Obtain ACPI.sys for Windows XP yourself from the ISO in your hand(or 3rd-party ACPI,sys)
  2. Boot your Windows PE from USB/CD/DVD
  3. Delete "ACPI.sys" in "C:\WINDOWS\system32\drivers"
  4. Get the "ACPI.sys" of Windows XP from the ISO in your hand and put it into "C:\WINDOWS\system32\drivers"
  5. Close Windows PE and start your Windows XP

Good Luck

Replaced the file, looks to be booting successfully. Any idea why this updated file would claim that my BIOS isn't ACPI compliant? Could be some obscure HP thing but seems strange to me nonetheless