BSOD's right after startup as a result of improperly using verifier?

  1.    06 Apr 2017 #1

    BSOD's right after startup as a result of improperly using verifier?

    Okay, the following is partially my mistake, yet all methods of fixing the following did not help:

    Going back a few weeks, my computer started to land BSOD's fairly frequenstly, about once a day, error code either ATTEMPTED_SWITCH_FROM_DPC, or the normal overload bsod (can't remember the name, the one which is most common). Today i looked for a fix, and found a thread suggesting to run verifier. I did so, but i ran it in recommended settings. After experiencing BSOD's every time it rebooted, i tried to remove the verifier. Running cmd as administrator worked, i removed the verifier (verifier /reset), and restarded (well it BSOD'd shortly after so it kinda stole my job). Long story short it didn't fix it. Next attempt was running cmd in startup, did the verifier /start(something) resetonbootfailure (not sure how exactly it went) which also didn't fix it. Last attempt was to change startup settings (7), but that was also to no success.. All crashes were always the same, not DPC but the other one. Basically if i run my pc it will crash within 15 seconds of being on the desktop.

    Some things to note:
    - I have an SSD
    - I have installed Windows 10 about a month ago
    - I also have an external harddrive aswell as an HDD.
    - Never experienced a single BSOD in windows 7, so this is already annoying :/
    - I have not tried to completely restore anything because i'm not sure what to restore.
    - My PC isn't all that old, maybe 1.5-2 years, and is in pretty good shape so i can't really blame it on him
    Help is really appreciated, i'd love to get it running again. Kind regards, Henni

    PS: I can't install the exe you want me to for obvious reasons, as i wouldn't be able to be fast enough...

    --- EDIT : My dad and i were able to fix it by going into safe mode, deinstalling the graphics card drivers, going into CMD with verifier /reset and then shutdown /s /t 0. ---
    Last edited by Henni; 07 Apr 2017 at 04:28. Reason: Fixed
      My ComputerSystem Spec

  2.    06 Apr 2017 #2

    The crash i'm now experiencing is SYSTEM_THREAD_NOT_HANDLED
      My ComputerSystem Spec

  3. Ztruker's Avatar
    Posts : 6,606
    Windows 10 Pro X64 1809 17763.134
       06 Apr 2017 #3

    Please read and follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions
      My ComputersSystem Spec


Related Threads
Solved BSOD After Running Verifier from Cmd Prompt in BSOD Crashes and Debugging
I started off with a Kernel_Security_Check_Error that had been happening for awhile during Elite: Dangerous. I read on another forum to use Verifier to see if that would solve it. It then gave me this>> driver_verifier_iomanager_violation...
I have another post where people are helping me with BSODs on my gaming pc whenever I play games and they suggested I run driver verifier and send them the two more bsod minidump files. My question is once I enable driver verifier how long should I...
Windows Driver Verifier BSOD in BSOD Crashes and Debugging
So I have an old Alienware Aurora R1 and after about 5 years the liquid cooling tube burst and fried the motherboard. I figured it was time for an upgrade anyway, but I liked the case and didn't want to buy a new PC. So I got an ASRock Z97M Pro4...
Hi! Ever since I updated to Windows 10 i keep getting these random freezes(sometimes when i am playing or even when i am just browsing the internet) and it came up with this electric like buzzing in the speakers(also in headphones so it is not the...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:50.
Find Us