Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/696fd677-90ec-800b-a423-9848e9b171f0
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: Good result — and it tells us something useful. === Good result — and it tells us something useful. What that SFC result means * “Windows Resource Protection did not find any integrity violations” means: - Core Windows system files are clean - ntoskrnl.exe, hal.dll, core drivers, etc. are not corrupted - This effectively rules out OS corruption as the cause of your BSODs Given the crashes you’re seeing, this strongly reinforces that the issue is driver / firmware related, not Windows itself. Important detail You ran SFC offline (/offbootdir / /offwindir), which is actually better for reliability in crash scenarios. So this is a solid check, not a weak one. What this narrows it down to Since: * SFC is clean * Reinstalling the ACPI/VPC driver improved stability * You’re still getting IRQL_NOT_LESS_OR_EQUAL and UNEXPECTED_KERNEL_MODE_TRAP The remaining suspects are: # Another bad kernel driver (very likely) # BIOS / firmware mismatch (still highly likely) # Chipset driver mismatch # RAM (possible, but lower priority right now) Next steps (in order, no guessing) # Confirm Driver Verifier is OFF ``<code> verifier /query </code>`<code> If anything is active: </code>`<code> verifier /reset <syntaxhighlight>2. Update BIOS/UEFI This is the single most important remaining step for ACPI-related crashes. # Reinstall chipset drivers - From the laptop manufacturer first - Then only update via Intel/AMD if recommended # Check minidumps (if they exist) If you have files in: </syntaxhighlight> C:\Windows\Minidump </code>`` the crash culprit can usually be identified conclusively. # Only if crashes persist after all of the above - Run MemTest86 (2 passes minimum) What you should NOT do now * Don’t reinstall Windows * Don’t disable random drivers * Don’t assume hardware failure yet If you want, tell me: * Exact laptop model * CPU (Intel or AMD) * Windows 10 or 11 (and build if you know it) At this point, we’re very close to pinning the exact remaining offender.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)