Jump to content

Constant BSOD after verifying

Go to solution Solved by Commissar,

F8 doesn't do anything but after the failed fix I typed verifier /reset in the cmd as admin and it just "changes were not saved" or something like that.

 only thing left to do is reinstall  windows.

Heyo, my first topic here and I'm already sorry if it sucks. I'm sorta panicking here.

So I've been having this problem of BSOD's after setting computer to sleep mode (the IRQL_NOT_LESS_OR_EQUAL deal) and tried to fix that today with verifier. I rebooted my computer and got into an endless BSOD loop. After Welcome Screen I can select the boot fix (or whatever you call it, my Windows is in Finnish) or the normal boot-up. If I choose the normal, I get a quick blue screen and sent back to the boot selection screen. If I try the fixing option, it "starts looking for the problem and fixing it" which has resulted in a failure 3 times already (Windows wasn't able to boot up normally). Now I'm sorta stuck.
- i5 2500k (not OC'd)
- n570gtx twin frozer or w/e
- asrock z68 extreme gen 3
- super flower golden green pro 80+ gold (can't remember or find the wattage god dammit)
- 2x8gb ripjaws X
- 2T caviar black and 500gb blue

Don't have a picture of the BS but got the "Windows wasn't able to boot up normally do you want to send an error report to blahblah" thingy. Sorry my awful English but now I'm really stressed, I got a metric frak ton of essays to do. :-| Ask questions, I'm sure I forgot to mention something.

E: Okay, so now I noticed this: http://i.imgur.com/TsvR8Fb.jpg I'll try my best to translate:
1. Boot-up fix
2. System restore (tried it, won't let me do it)
3. System image restoration
4. Windows memory diagnostics
5. Cmd (I'm sure you got that one by yourself)
What should I try?

Link to comment
https://linustechtips.com/topic/57590-constant-bsod-after-verifying/
Share on other sites

Link to post
Share on other sites

Never heard of Verifier. What does it do?

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

"I didn't die! I performed a tactical reset!" - Apollolol

Link to post
Share on other sites

Never heard of Verifier. What does it do?

Apparently it's Window's own driver verifier of some sort. I just typed it Start menu searchbox and it was there. "Create Standard Settings", Next, "Automatically select all drivers installed on this computer" and Finish as instructed when someone else was having the same problem as I with the BSOD after sleep mode. Then I reset the computer and here I am, computer all fraked up. I read it here: http://www.techspot.com/community/topics/bsod-when-going-into-sleep-mode.162165/

Okay, not sure why my text looks like this now.

Link to post
Share on other sites

Driver verifier is used to check for driver problems. to disable, you need to boot into safe mode.

once booted, open up the verifier.exe, and select the option to delete settings.

 

but, if you're using windows 8, it's a difficult task to get to safe mode... f8 doesn't work anymore, and most methiods require booting into normal windows....

http://pcsupport.about.com/od/repair-recovery/a/force-or-stop-safe-mode-windows.htm

follow that guide if you use win8

Former Teksyndicate Forum Moderator, IT student

my build: http://pcpartpicker.com/b/FnC

Link to post
Share on other sites

Just like I thought. I forgot to mention the os, win7. And I also thought about the safe mode boot but the problem is there is no safe mode option when booting up. Luckily I have a friend coming by today to see what can be done.

ummm.... it doesn't say safe mode, but just spam the f8 button on boot, as if you wanted to access the bios... not that difficult

 

and waht you want to do, is open cmd as admin, and type verifier /reset then reboot

Former Teksyndicate Forum Moderator, IT student

my build: http://pcpartpicker.com/b/FnC

Link to post
Share on other sites

F8 doesn't do anything but after the failed fix I typed verifier /reset in the cmd as admin and it just "changes were not saved" or something like that.

 only thing left to do is reinstall  windows.

Former Teksyndicate Forum Moderator, IT student

my build: http://pcpartpicker.com/b/FnC

Link to post
Share on other sites

  • 2 weeks later...

only thing left to do is reinstall windows.

Done. Boots normally again. Now I have a problem with driver installation. When I tried to install my mobo drivers, the computer reboots and asks: "Generate Serial ATA driver diskette Y/N?" "Yes" says it couldn't find a 1.44mb floppy disk and tells me to press any key to reboot. "No" just instantly tells me to reboot with any key. Any advice? Apperently this is a pretty common thing with Asrock boards :|
Link to post
Share on other sites

So you can get into windows now? What "motherboard drivers" do you need to install?

2500k @ 4.8, R9 290x, 256GB Vertex 4, Filco Majestouch 2 Tenkeyless Brown, Logitech G602 Mouse, Kingwin Lazer 1000w Platinum PSU, Corsair Dominator Platinum RAM 8GB @1866, Asrock Extreme 3 Gen 3, Xonar U7, Sennheiser 598, Switch 810, Coolermaster Hyper 212 with 1x Noctua nf-f12

Link to post
Share on other sites

What drivers are you attempting to install?

"It pays to keep an open mind, but not so open your brain falls out." - Carl Sagan.

"I can explain it to you, but I can't understand it for you" - Edward I. Koch

"I didn't die! I performed a tactical reset!" - Apollolol

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×