Need help with laptop BSODs

Hi, "Both approaches failed to run sysnative collection app unfortunately." Why is it not running ?? Have you Right Clicked it and used Run as Administrator ??

Have you stopped Defender and tried ??

You have now found out why you should always buy Windows Pro Version and not home.  Or can Update to it but costs a $100 bucks.

Need to know about that Driver Update in Optional.  if there the Name ... see below.

After uninstalling the Intel® Wi-Fi 6 AX200 160MHz software. Is Optional Drivers offering you the Driver ?

Is it in the Updates and or downloading and installed see Settings-->Windows Updates-->Update History--> and will say for Wi-Fi 6 AX200 160MHz  OR in---> Drivers

It will say Intel Software Component or Intel System and they will have version numbers.

You can highlight the above and version number and copy / paste into Google Search and find out what that is.

Please tell us what is in there.

Please recheck : https://www.windowscentral.com/software-apps/windows-11/how-to-enable-or-disable-fast-startup-on-windows-11 Want Disable.

&

Re- Check in BIOS make sure ASUS Fast Boot is Disabled.  Do not Exit with use Optimized Defaults.

Ok, the Intel® Wi-Fi 6 AX200 160MHz  going to Device Manager, expand Network adapters then double-click the Intel® Wi-Fi 6 AX201 160MHz.

Go to its Driver tab and look for the Driver version.

netwtw10.sys Mar 15th  If it shows as this old one still. See if the Rollback driver option is available. Try rolling back the driver if available but if not, select Update device then select Browse my computer for driver software. Select Let me pick from a list of available drivers on my computer.

On the next page, see if previous versions of the Intel® Wi-Fi 6 AX201 160MHz is available. If yes, select the version prior to the version current installed and click Next. Select Close then check if the Driver version of the driver installed changed to the version that you selected on the list. If yes, click Close then restart

So that should be this that you have done as per above : https://www.elevenforum.com/t/roll-back-device-driver-to-previous-version-in-windows-11.13178/

Re-check the driver make sure it is NOT the March 15th but is prior to it. 

If yes follow this : NOTE Specific Driver : https://www.tenforums.com/tutorials/146562-prevent-windows-update-updating-specific-device-driver.html and as mention the difference between PRO and HOME is the ability to use some of the above but since do not have Group Policy Editor use what you can.

NOTE : Microsoft can still over ride this and install a driver. re being Windows Home.

So now TEST with the Older Driver if it has been installed.

Note : there are other ways to block drivers : https://www.elevenforum.com/t/how-to-stop-windows-update-from-installing-device-drivers.8292/ (Think this is Global, SEE Post # 14 

If No Joy (Stallone movie, lol) Reverse the above changes to block.

You want to try the next option which

is Download the Intel Driver and Support Assistant : https://www.intel.com/content/www/us/en/support/detect.html install the Intel® Wi-Fi 6 AX200 160MHz this should be the newest driver. EDIT NOTE: drop browser down as the installers will be behind the browser window.

OR : Download INTEL Pro Set from here : https://www.intel.com/content/www/us/en/support/articles/000046918/wireless.html

Make sure in Device Manager that netwtw10.sys is current version and if so Block it from being updated.

TEST.

NOTE : Save these somewhere safe due to pending End of Life.  Would check back and get a newer Version and save as well.  Will be hooped when End of Life and have not saved Drivers that Work. (there is always the several gigabyte package the drivers will be on, but is a pain).

(Note why I know all the above I have a frigging Intel Wi-Fi 6 AX201 160MHz that the Wifi craps out on.)

IT is Painful.

So have a go at it.

Edited by Pkshadow, 03 October 2024 - 07:35 AM.

Recently managed to update using the Intel Assistant. Will update if theres stability changes.

Perfect. If it BSODs again run the Sysnative data collection app again and upload the new output.

Didn't run sysnative data collection app in case it triggers a string of BSODs again so I just collected these manually

https://we.tl/t-VdH38h2uzO

Of those five dumps four cannot be read, I get a 0x80070057 error which can be caused by many things, bad hardware being one of them. One dump is readable and is similar to earlier dumps in that it fails with a 0xC0000005 exception code again (memory access violation) and it contains a checksum error for the BTHport.sys driver - it's curious that it's always that driver. Added to four of the dumps being unreadable I'm pretty confident that you have a hardware error on there, with a laptop that can be catastrophic because the only hardware you can typically replace is RAM and storage drives.

Fortunately the most likely culprits here are RAM or a storage drive. You've tested your RAM with Memtest86 but I think it wiser at this point to remove the one RAM stick that you can to fully eliminate that from the problem. I also suggest that at minimum you run a chsksdk /f on both partitions to check the NTFS filesystems. Also download the WD Dashboard tool and use that to test the drive and check for updated firmware and/or drivers.

There is an outside possibility that this could be a flaky third-party driver, so it will be worth enabling Driver Verifier and seeing whether that can catch a misbehaving driver...

Driver Verifier subjects selected drivers (typically all third-party drivers) to extra tests and checks every time they are called. These extra checks are designed to uncover drivers that are misbehaving. If any selected driver fails any of the Driver Verifier tests/checks then Driver Verifier will BSOD. The resulting minidump should contain enough information for us to identify the flaky driver. It's thus essential to keep all minidumps created whilst Driver Verifier is enabled.

To enable Driver Verifier do the following:

1. Take a System Restore point and/or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar). It is possible that Driver Verifier may BSOD a driver during the boot process (some drivers are loaded during boot). If that happens you'll be stuck in a boot-BSOD loop.

If you should end up in a boot-BSOD loop, boot the Windows installation media and use that to run system restore and restore to the restore point you took, to remove Driver Verifier and get you booting again. Alternatively you can use the Acronis, Macrium Reflect, or similar, boot media to restore the disk image you took.

Please don't skip this step. it's the only way out of a Driver Verifier boot-BSOD loop.

2. Start the Driver Verifier setup dialog by entering the command verifier in either the Run command box or in a command prompt.

3. On that initial dialog, click the radio button for 'Create custom settings (for code developers)' - the second option - and click the Next button.

4. On the second dialog check (click) the checkboxes for the following tests...

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Then click the Next button.

5. On the next dialog click the radio button for 'Select driver names from a list' - the last option - and click the Next button.

6. On the next dialog click on the 'Provider' heading, this will sort the drivers on this column (it makes it easier to isolate Microsoft drivers).

7. Now check (click) ALL drivers that DO NOT have Microsoft as the provider (ie. check all third-party drivers).

8. Then, on the same dialog, check the following Microsoft drivers (and ONLY these Microsoft drivers)...

• Wdf01000.sys
• ndis.sys
• fltMgr.sys
• Storport.sys

These are high-level Microsoft drivers that manage lower-level third-party drivers that we otherwise wouldn't be able to trap. That's why they're included.

9. Now click Finish and then reboot. Driver Verifiier will be enabled.

Be aware that Driver Verifier will remain enabled across all reboots and shutdowns. It can only be disabled manually.

Also be aware that we expect BSODs. Indeed, we want BSODs, to be able to identify the flaky driver(s). You MUST keep all minidumps created whilst Driver Verifier is running, so disable any disk cleanup tools you may have.

10. Leave Driver Verifier running for 48 hours, use your PC as normal during this time, but do try and make it BSOD. Use every game or app that you normally use, and especially those where you have seen it BSOD in the past. If Windows doesn't automatically reboot after each BSOD then just reboot as normal and continue testing. The Driver Verifier generated BSODs are these...

• 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
• 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
• 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
• 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
• 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
• 0xE6: DRIVER_VERIFIER_DMA_VIOLATION

If you see any of these BSOD types then you can disable Driver Verifier early because you'll have caught a misbehaving driver.

Note: Because Driver Verifier is doing extra work each time a third-party driver is loaded you will notice some performance degradation with Driver Verifier enabled. This is a price you'll have to pay in order to locate any flaky drivers. And remember, Driver Verifier can only test drivers that are loaded, so you need to ensure that every third-party driver gets loaded by using all apps, features and devices.

11. To turn Driver Verifier off enter the command verifier /reset in either Run command box or a command prompt and reboot.

Should you wish to check whether Driver Verfier is enabled or not, open a command prompt and enter the command verifier /query. If drivers are listed then it's enabled, if no drivers are listed then it's not.

12. When Driver Verifier has been disabled, navigate to the folder C:\Windows\Minidump and locate all .dmp files in there that are related to the period when Driver Verifier was running (check the timestamps). Zip these files up if you like, or not as you choose. Upload the file(s) to the cloud with a link to it/them here (be sure to make it public).

Edited by ubuysa, 09 October 2024 - 01:00 AM.