Windows 10: I keep getting bsod after using verifier and now I can't turn it off. I tried safe mode...

I keep getting bsod after using verifier and now I can't turn it off. I tried safe mode and still won't work to stop it. Help!

:)

 

Password not accepted in Safe mode

Hi,

Thank you for posting your query on Microsoft Community forum.

Have you tried all the above steps suggested by Sangeeta Sarkar on September 13, 2015.

I would suggest you to provide some information to help you better.

• Are you trying to login the Microsoft account or the Local account in safe mode?
• Did you try with only safe mode or safe mode with networking?
• What is the critical error you are getting?

If you are using Windows 10. To go to safe mode you have to follow the below steps.

If you are able to go to login screen in normal mode try the below steps to go to safe mode with networking.

• 
  At the login screen click on the power symbol.
  
• 
  Hold SHIFT + Click Restart.
  
• 
  After restarting your system, select the Troubleshoot option.
  
• 
  Select advanced options under
  Troubleshoot screen.
  
• 
  Click on Startup Settings.
  
• 
  Click Restart and follow the onscreen steps to go to
  Safe Mode with networking and check if you are able to login.
  

[*]

Please get back with more information, we will be glad to help you further.

 

How to get into safe mode on Toshiba satellite

I have had run into this problem:
Laptop Boots and a Stop Error code X (BSOD) - BSOD Code List is useful but not Important, or just want to get to into SAFE MODE -Holding the Shift Key, F8, Shaking it, lighting Sage and Chanting would not Boot into Windows, so could not run MSCONFIG, Shift +Restart Options,etc.

Toshiba and Microsoft will try to recover and won't start until it tries automatically. A good thing and bad thing, and when it fails to do so on their own it will turn it over to you. These are the screen option steps to get to Safe Mode.

TO BOOT INTO SYSTEM REPAIR AND THEN TROUBLESHOOT/ADVANCED DIAGNOSTIC TO GET TO SAFE MODE-
1. Press [Power Button] OFF (If On), then [Power BUTTON] ON - When the Toshiba Screen shows up, [Power BUTTON] OFF
On the 3rd Attempt, (or before) - "Preparing to Auto Repair, then Diagnosing ... and arrive at Blue screen, TO GET TO SAFE MODE:

Select [ADVANCED OPTIONS],
[TROUBLESHOOT],
[SEE MORE OPTION],
[STARTUP SETTINGS]-Change Startup Behavior.
The screen will describe the what Safe Mode settings
[RESTART]
On this Restart, you SHOULD Arrive at The Safe Mode you desperately seek.

If this it fails to Restart in Safe Mode, you have discovered the source of the problem. I disagree with nearly everything posted about what to do next, because it is complicated and not only didn't help, it caused more harm than good. Without venturing into those issues and going off topic, I offer the Safe Mode procedure which worked for me; I can share what worked beyond when Safe Mode boot didn't work or could not there using the above either.

 

KMODE_EXCEPTION_NOT_HANDLED on fresh install. Safe mode works fine.

Version 2004 (OS Build 19041.508)Attachment 297834
Error: KMODE_EXCEPTION_NOT_HANDLED
This is a fresh install of windows. The only thing that has been installed is the video card driver & software.

Note: I can only run windows in normal mode for a couple minutes before I get BSOD. The included log .zip file is while I am in safe mode. I DO NOT GET BSOD IN SAFE MODE.

Things I have already tried:

• Uninstalling then updating my video card drivers.
• Clean boot.
• Removing any unnecessary hardware e.g. web cam, card reader

I still hit the same error every time. Sometimes the BSOD comes in a few seconds, other times I can use my PC for up to 10 minutes before getting it. Usually it is sometime in 3-5 minutes after logging into Windows.
Originally I was getting this BSOD error and in my troubleshooting I made things worse to the point my drive would not launch windows and all repair attempts failed. So I gave up and used my other hard drive and did a fresh install of Windows. I am getting the same error that I was before, KMODE_EXCEPTION_NOT_HANDLED.

I have done various troubleshooting steps but am willing to start from scratch to narrow down if this is hardware and if so what piece of hardware.

For context here is some of the programs I have tried and the summarized outcome:

• Driver Verifier - No issues
• sfc - corrupt files detected that were unrepairable (CBS LogAttachment 297844)
• dism - no corruption detected