Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Windows NT 4.0 (PowerBook G3 PDQ) occasional random BSOD with 0x00000035 #51

Open
b- opened this issue Jan 9, 2025 · 2 comments
Open

Comments

@b-
Copy link

b- commented Jan 9, 2025

Not sure if this might be my hardware or something, but I wanted to make an issue just in case, anyway.

I'm getting occasional random BSOD's with 0x00000035 NO_MORE_IRP_STACK_LOCATIONS:

*** STOP: 0x00000035 (0x00000000,0x00000000,0x00000000,0x00504D55)
NO_MORE_IRP_STACK_LOCATIONS

(The general STOP message is always the same. I'm not sure if the numbers in the parens change, I'll make a note next time it happens whether they're the same or not)

@b- b- changed the title Windows NT 4.0 random BSOD with 0x00000035 Windows NT 4.0 (PowerBook G3 PDQ) occasional random BSOD with 0x00000035 Jan 9, 2025
@Wack0
Copy link
Owner

Wack0 commented Jan 9, 2025

This is specifically the PMU driver in HAL receiving too many interrupts in quick succession, ie, running out of unused DPC slots (of which there are 16) at interrupt time.

Which ROM version do you have according to Apple System Profiler? Both my PDQs have version 0x077d41f6 - and it may be possible that the toolbox ROM puts PMU in some mode causing it to fire more interrupts than usual.

@b-
Copy link
Author

b- commented Jan 9, 2025

This is specifically the PMU driver in HAL receiving too many interrupts in quick succession, ie, running out of unused DPC slots (of which there are 16) at interrupt time.

Which ROM version do you have according to Apple System Profiler? Both my PDQs have version 0x077d41f6 - and it may be possible that the toolbox ROM puts PMU in some mode causing it to fire more interrupts than usual.

I have the same ROM revision, according to Apple System Profiler.

The issue hasn't happened again yet, so maybe something I did just stressed it out a couple of times…

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants