Reply to thread

You could try to run driver verifier; 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)
  • 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.zipand then:
    1. Open an elevated command prompt (right-click on windows start button, click command prompt (admin)
    2. Type (copy/paste) in it: [code]powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1[/code]
    3. Press enter
    4. The previous command will modify your bcdedit settings and it will set the necessary driver verifier settings.
      It will (more precisely):[HIDE]
      - export/save your current bcdedit system store content in c:\DEFAULT-BCDedit-SystemStoreContent
      - show the current bcdedit content in "BCDoriginal.txt" (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" (on your desktop)
      - find non-microsoft drivers and set the necessary driver verifier settings
      - restart your PC after two 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 if it should cause a BSOD.
      It should appear something like:[CODE]
      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
      ndis: rules.default
      Verified Drivers:
      More data is available.
      The system reboot is required for the changes to take effect.[/CODE][/HIDE]
    5. 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: [code]verifier /reset[/code]
      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:[code]md "%userprofile%\desktop\minidump" && copy c:\windows\minidump "%userprofile%\desktop\minidump"[/code]


Back
Top