ASUS Laptop - frequent BSODs

[DaveA]

OS - Windows 10, 8.1, 8, 7, Vista ? **win-10-Pro
· x86 (32-bit) or x64 (64-bit)? ** 64
· What was the originally installed OS on the system? ** Originally came with win-10-Home -- upgraded to Pro
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? ** OEM
· Age of system (hardware) ** 1.5 years
· Age of OS installation - have you re-installed the OS? ** no

· CPU ** i58250U
· Video Card ** Intel UHD Graphics 620
· MotherBoard - (if NOT a laptop) ** N/A
· Power Supply - brand & wattage (if laptop, skip this one)

· System Manufacturer ** ASUS
· Exact model number (if laptop, check label on the bottom) ** UX331UA

Thank you!

 

[Sysnative Windows Update]

Hi!

Please start by testing your RAM: Test RAM with PassMark MemTest86

 

[MrPepka]

Update BIOS - ASUS ZenBook 13 UX331UA Driver & Tools | Laptops | ASUS USA
Check in Windows Update if there any updates of system

 

[DaveA]

Thanks for the responses. I've not run MemTest86, but I have run the built-in Windows memory check which says memory is OK. I've made sure Windows updates are installed, I've run chkdsdk, DISM, and sfc. We'll see if any of this helps! I haven't done the BIOS update yet.

Dave

 

[DaveA]

Still getting BSODs --- Kernel Security Check Failure. Does a BIOS update seem likely to fix this?
Thanks
Dave

 

[xilolee]

Still getting BSODs --- Kernel Security Check Failure. Does a BIOS update seem likely to fix this?
Thanks
Dave

Hi.
If I have to guess, updating the wireless driver will solve the problem: Download Windows® 10 Wi-Fi Drivers for Intel® Wireless Adapters .
Otherwise, if the BSODs should continue, I'd try to run verifier.
Instructions are below (click the "show" button, near read more).

Read More:

Please read CAREFULLY the following instructions:

• Create a restore point
• Create a system image
  (macrium reflect free is a good program, if you don't already have one... Make sure to create a recovery media - i.e., a CD or a USB stick with macrium installed - and test if it works and boot your machine/pc)
• Backup your important files (the files you don't want to lose)
• Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
• Read some other tutorials/guides and WARNINGS on internet.
• Unzip on your desktop the file I attached View attachment verifier.zip and then:
  1. Open an elevated command prompt (right-click on windows start button, click command prompt (admin)
  2. Type (copy/paste) in it:

     bcdedit /export c:\DEFAULT-BCDedit-SystemStoreContent
     powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"

  3. Press enter
  4. The previous commands will modify your bcdedit settings, will set the necessary driver verifier settings, will reboot your PC in three minutes (but you can reboot it before).
     It will (more precisely):
     Read More:

     
     - export/save your current bcdedit system store content in c:\DEFAULT-BCDedit-SystemStoreContent
     - show the current bcdedit content in "BCDoriginal.txt" (in the folder Created-by-verifier-script on your desktop)
     - change the bcdedit {bootmgr} displaybootmenu setting from No to Yes
     - change the bcdedit {bootmgr} timeout setting to 30 seconds
     - change the bcdedit bootmenupolicy setting from standard to legacy
     - show the modified bcdedit content in "BCDmodified.txt" (in the folder Created-by-verifier-script on your desktop)
     - find non-microsoft drivers and set the necessary driver verifier settings
     - restart your PC after three minutes (you can abort this with "shutdown -a" in an elevated command prompt)
     - the boot menu should appear at every restart and it should allow you to select windows advanced boot options (SAFE MODE included).
     I've added the parameter /bootmode resetonbootfail.
     This should reset driver verifier settings, if they should cause a BSOD.
     It should appear something like:

     Verifier Flags: 0x0002892b
     
     Standard Flags:
     
     [X] 0x00000001 Special pool.
     [X] 0x00000002 Force IRQL checking.
     [X] 0x00000008 Pool tracking.
     [ ] 0x00000010 I/O verification.
     [X] 0x00000020 Deadlock detection.
     [ ] 0x00000080 DMA checking.
     [X] 0x00000100 Security checks.
     [X] 0x00000800 Miscellaneous checks.
     [X] 0x00020000 DDI compliance checking.
     
     Additional Flags:
     
     [ ] 0x00000004 Randomized low resources simulation.
     [ ] 0x00000200 Force pending I/O requests.
     [ ] 0x00000400 IRP logging.
     [ ] 0x00002000 Invariant MDL checking for stack.
     [ ] 0x00004000 Invariant MDL checking for driver.
     [X] 0x00008000 Power framework delay fuzzing.
     [ ] 0x00010000 Port/miniport interface checking.
     [ ] 0x00040000 Systematic low resources simulation.
     [ ] 0x00080000 DDI compliance checking (additional).
     [ ] 0x00200000 NDIS/WIFI verification.
     [ ] 0x00800000 Kernel synchronization delay fuzzing.
     [ ] 0x01000000 VM switch verification.
     [ ] 0x02000000 Code integrity checks.
     
     [X] Indicates flag is enabled.
     
     Boot Mode:
     
     Resetonbootfail
     
     Rules:
     
     All rules are using default settings
     
     Extensions:
     
     wdm: rules.default
     
     Verified Drivers:
     
     More data is available.
     The system reboot is required for the changes to take effect.

  5. After the reboot, open a command prompt and check if verifier settings are enabled with this command

     verifier /querysettings

     If they are enabled, let verifier run from 24 to 72 hours.
     If they are not enabled, inform me.
     If you'll get a very fast BSOD after you logged into windows, or after some dozens (tenths?) of minutes, the option resetonbootfail should reset driver verifier settings (and should allow you to boot your machine in a normal state)... But if this won't happen, you'll need to go to safe mode to reset verifier settings. Once safe mode is available, from an elevated command prompt you'll type:

     verifier /reset

     Sometimes it is necessary to use a system restore point (or a system image).
• Post here the new verifier dump; from an elevated command prompt, launch this command:

  md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"

 

[usasma]

Just a guess here, but try uninstalling McAfee with the McAfee Removal Tool
This reminds me of problems I saw with it when I was working as a PC Technician.