Blue screen on Windows 10 - Happens many times in one day every week

[idbanet]

Hello,
i uploaded the file here SysnativeFileCollectionApp.zip
(It's a test page of mine, couldn't find another way)

I think my problem is my SSD NVMe Kingston skc1000480g, because i changed the motherboard and the RAM (also did a format with the changes) but blue screen still happening.

 

[x BlueRobot]

Please attach the .zip folder using the attach files button.

 

[idbanet]

Here is the file.

 

[x BlueRobot]

There doesn't appear to be any dump files in the folder you attached nor any saved on your drive.

(also did a format with the changes)

Did you reinstall Windows then?

 

[idbanet]

Yes, but the problem still remains. Like i said i think it's the SSD NVMe Kingston skc1000480g 500GB, i just need to make sure of it.

 

[x BlueRobot]

When the system crashes again, use the Sysnative collection tool again and upload a new .zip, then we'll be able to hopefully determine what is causing the issue.

 

[idbanet]

The system crushed again and i run the Sysnative collection, here is the zip.

 

[xilolee]

No minidumps... Download and install:

• MoBo GA-H270-HD3: Intel Management Engine Interface, 1‎914.12.0.1256, 29 May 2019
• MoBo GA-H270-HD3: Intel INF installation, 1‎0.1.18243.8188, 10 Mar 2020
• Intel.com: Rapid Storage Technology installer, 18.0.1.1138, 15 Oct 2020
• Intel.com: Graphics DCH Driver, 27.20.100.8935, 6 Nov 2020 (W10 x64, i3-7100, HD Graphics 630)
• Intel.com: Ethernet Connection I219-V driver for W10 x64, 25.5, 10 Nov 2020

If you'll get other BSODs or crashes, post here the new logs (using sysnative bsod collection app).
If you won't get minidumps, we'll try to run verifier.

---

Please read CAREFULLY the following instructions:

• Create a restore point
• Create a system image.
  You can follow this tutorial, if you shouldn't know how to do: Using Macrium Free to Backup or Image your drives
• 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 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 ResetOnUnusualShutdown.
     This should reset driver verifier settings, if they should cause a BSOD.
     You will see something like:

     Read More:

     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:
     
     ResetOnUnusualShutdown
     
     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.

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

  verifier /querysettings

  Press enter.
  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 of minutes, the option ResetOnUnusualShutdown (rous) 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

  Press enter.
  Sometimes it is necessary to use a system restore point (or a system image).
• If you get a verifier BSOD in next 24-72 hours, 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"

If you won't get BSODs at all, we'll wait the next BSOD in next days/weeks.

---

When we have finished and hopefully solved the BSOD, to restore the previous bcdedit settings you'll type (copy/paste) in an elevated command prompt:

bcdedit /import "c:\DEFAULT-BCDedit-SystemStoreContent"

Press enter.