Jump to content

I turned on driver verifier to check my drivers because something kept causing bsod but when I got a bsod in windows it restarted then said preparing repairs then it pulled up windows defender offline and scans then restarts . When it restarts I get DRIVER VERIFIER DETECTED VIOLATION then restarts and repeats the process over and over again and still has not stopped sometimes when it restarts it will just spin with the windows logo like its gonna boot but it will do nothing for hours and the hdd doesnt even blink when that happens. I tried disabling driver verifier in cmd with repair my computer on the bootable windows 10 usb but it didnt work. Any help is extremely appreciated!!!

Link to comment
https://linustechtips.com/topic/815612-driver-verifier-detected-violation/
Share on other sites

Link to post
Share on other sites

What driver verifier? I’ve never heard of it. Did you download it?

Gaming PC NAS Laptop Workstation

CPU: i5 12600KF 6P+4E Ryzen 7 3700X M4 SoC 4P+6E Xeon X5690 6c12t

Cooler: Noctua NH-D15S Wraith Stealth w/NF-A9 Passive Apple CPU Cooler

Motherboard: ASRock Z690 ITX/ax ASUS Pro B550M-C/CSM Apple J713AP Mac-F221BEC8 (Mac Pro 5,1)

RAM: 2x16GB 3600Mhz DDR4 2x16GB 2400MHz DDR4 24GB Micron LPDDR5 4x8GB 1333MHz ECC DDR3

GPU: Sapphire Pulse Radeon 9060 XT 16GB Radeon WX2100 M4 SoC 10C Radeon RX 5700

Storage: 1TB MP34 + 2TB P41 500GB SSD + 2x4TB IronWolf Pro in ZFS Mirror Apple AP0512Z 1TB Crucial MX500

ODD: LG WH14NS40 None LG GP65NB60 USB DVD Writer Don't know

PSU: EVGA 850W GM Silverstone SST-TX300 53.8Wh LiPo Battery Delta DPS-980BB

Case: Silverstone Sugo 14 Dell Inspiron 530S Mac16,12 chassis (13" MBA) 2009-2012 Mac Pro "Cheese Grater"

OS: Gentoo Linux TrueNAS Scale macOS 26 Tahoe Fedora Linux

 

Display: LG 27UK650-W (4K 60Hz IPS panel)

Mouse: EVGA X17

Keyboard: Corsair K55 RGB

 

Mobile/Work Devices: 14" M5P MacBook Pro (work) - iPhone 17 Pro - Apple Watch S11

 

Other Misc Devices: iPod Video (Gen 5.5E, iFlash Solo w/128GB SD Card, Rockbox), Nintendo Switch

 

Vehicles: 2002 Ford F150, 2003 Harley-Davidson Sportster 1200, 2022 Kawasaki KLR650, 1994 DR350SE

Link to post
Share on other sites

1 minute ago, TheGTXman said:

No its built into windows look it up.

Aaaahhhhh. Wanted to make sure it isn’t a sneaky malware package. Can you boot into safe mode and disable it, then remove and reinstall drivers?

Gaming PC NAS Laptop Workstation

CPU: i5 12600KF 6P+4E Ryzen 7 3700X M4 SoC 4P+6E Xeon X5690 6c12t

Cooler: Noctua NH-D15S Wraith Stealth w/NF-A9 Passive Apple CPU Cooler

Motherboard: ASRock Z690 ITX/ax ASUS Pro B550M-C/CSM Apple J713AP Mac-F221BEC8 (Mac Pro 5,1)

RAM: 2x16GB 3600Mhz DDR4 2x16GB 2400MHz DDR4 24GB Micron LPDDR5 4x8GB 1333MHz ECC DDR3

GPU: Sapphire Pulse Radeon 9060 XT 16GB Radeon WX2100 M4 SoC 10C Radeon RX 5700

Storage: 1TB MP34 + 2TB P41 500GB SSD + 2x4TB IronWolf Pro in ZFS Mirror Apple AP0512Z 1TB Crucial MX500

ODD: LG WH14NS40 None LG GP65NB60 USB DVD Writer Don't know

PSU: EVGA 850W GM Silverstone SST-TX300 53.8Wh LiPo Battery Delta DPS-980BB

Case: Silverstone Sugo 14 Dell Inspiron 530S Mac16,12 chassis (13" MBA) 2009-2012 Mac Pro "Cheese Grater"

OS: Gentoo Linux TrueNAS Scale macOS 26 Tahoe Fedora Linux

 

Display: LG 27UK650-W (4K 60Hz IPS panel)

Mouse: EVGA X17

Keyboard: Corsair K55 RGB

 

Mobile/Work Devices: 14" M5P MacBook Pro (work) - iPhone 17 Pro - Apple Watch S11

 

Other Misc Devices: iPod Video (Gen 5.5E, iFlash Solo w/128GB SD Card, Rockbox), Nintendo Switch

 

Vehicles: 2002 Ford F150, 2003 Harley-Davidson Sportster 1200, 2022 Kawasaki KLR650, 1994 DR350SE

Link to post
Share on other sites

2 minutes ago, Zando Bob said:

Aaaahhhhh. Wanted to make sure it isn’t a sneaky malware package. Can you boot into safe mode and disable it, then remove and reinstall drivers?

I can't seem to get into safe mode. Is there any otherway to get into safe mode?

Link to post
Share on other sites

8 minutes ago, Zando Bob said:

Aaaahhhhh. Wanted to make sure it isn’t a sneaky malware package. Can you boot into safe mode and disable it, then remove and reinstall drivers?

I don't know what to do anymore and its becoming very frustrating!!!

Link to post
Share on other sites

4 minutes ago, TheGTXman said:

I need some sort of cmd trick to use??
 

Hmmm. I’d boot into Linux from a USB, copy your files to an external drive, then reinstall Windows. It’ll reinstall the drivers as well, so it’s not all bad. 

Gaming PC NAS Laptop Workstation

CPU: i5 12600KF 6P+4E Ryzen 7 3700X M4 SoC 4P+6E Xeon X5690 6c12t

Cooler: Noctua NH-D15S Wraith Stealth w/NF-A9 Passive Apple CPU Cooler

Motherboard: ASRock Z690 ITX/ax ASUS Pro B550M-C/CSM Apple J713AP Mac-F221BEC8 (Mac Pro 5,1)

RAM: 2x16GB 3600Mhz DDR4 2x16GB 2400MHz DDR4 24GB Micron LPDDR5 4x8GB 1333MHz ECC DDR3

GPU: Sapphire Pulse Radeon 9060 XT 16GB Radeon WX2100 M4 SoC 10C Radeon RX 5700

Storage: 1TB MP34 + 2TB P41 500GB SSD + 2x4TB IronWolf Pro in ZFS Mirror Apple AP0512Z 1TB Crucial MX500

ODD: LG WH14NS40 None LG GP65NB60 USB DVD Writer Don't know

PSU: EVGA 850W GM Silverstone SST-TX300 53.8Wh LiPo Battery Delta DPS-980BB

Case: Silverstone Sugo 14 Dell Inspiron 530S Mac16,12 chassis (13" MBA) 2009-2012 Mac Pro "Cheese Grater"

OS: Gentoo Linux TrueNAS Scale macOS 26 Tahoe Fedora Linux

 

Display: LG 27UK650-W (4K 60Hz IPS panel)

Mouse: EVGA X17

Keyboard: Corsair K55 RGB

 

Mobile/Work Devices: 14" M5P MacBook Pro (work) - iPhone 17 Pro - Apple Watch S11

 

Other Misc Devices: iPod Video (Gen 5.5E, iFlash Solo w/128GB SD Card, Rockbox), Nintendo Switch

 

Vehicles: 2002 Ford F150, 2003 Harley-Davidson Sportster 1200, 2022 Kawasaki KLR650, 1994 DR350SE

Link to post
Share on other sites

Just now, bcguru9384 said:

trick is insert windows install disc

then enter bios on boot and tell boot order dvd drive first(or usb if usb)

then boot and select repair or cmd prompt

Yea ive been there multiple times I just need something to enter into cmd that will fix my problem.

Link to post
Share on other sites

4 hours ago, TheGTXman said:

It doesnt help that I can't read any replies on microsoft.com to the forums!!

if you have access to another windows same as yours then go to run box

regedit

now do search (f3 i think) for "driver verifier"

when this found export this key from registry to usb drive then get cmd access on other system

type regedit import regkey file saved

reboot system as registry now repaired

DO NOT JUST EXPORT WHOLE REGISTRY only export the exact key(s) needed

Link to post
Share on other sites

11 hours ago, bcguru9384 said:

if you have access to another windows same as yours then go to run box

regedit

now do search (f3 i think) for "driver verifier"

when this found export this key from registry to usb drive then get cmd access on other system

type regedit import regkey file saved

reboot system as registry now repaired

DO NOT JUST EXPORT WHOLE REGISTRY only export the exact key(s) needed

I just reinstalled windows but Ive gotten 1 bsod memory_management so my my mind goes straight to ram . Which I think has something to do with it but its strange,when I try to boot my system from being off for awhile it doesnt boot right off it does the the same as when you take the ram out so I thought ok maybe a stick is bad so I take out one stick put in a 1gb + one of the 4gb sticks that was already in it and boots no problem, but it does the same with both sticks. So I said I will just put both original 4gb sticks in another pc well it didnt boot either but when I take one out it boots but it doesnt matter which one you take out . I don't know if its a compatibility issue of my ram with my specific motherboard or what it is but I know that I'm really confused ,but after repetitively turning on and off the pc a few times it will boot I'm actually typing this on it . Is all of my ram completlely bad???

Link to post
Share on other sites

1 hour ago, TheGTXman said:

I just reinstalled windows but Ive gotten 1 bsod memory_management so my my mind goes straight to ram . Which I think has something to do with it but its strange,when I try to boot my system from being off for awhile it doesnt boot right off it does the the same as when you take the ram out so I thought ok maybe a stick is bad so I take out one stick put in a 1gb + one of the 4gb sticks that was already in it and boots no problem, but it does the same with both sticks. So I said I will just put both original 4gb sticks in another pc well it didnt boot either but when I take one out it boots but it doesnt matter which one you take out . I don't know if its a compatibility issue of my ram with my specific motherboard or what it is but I know that I'm really confused ,but after repetitively turning on and off the pc a few times it will boot I'm actually typing this on it . Is all of my ram completlely bad???

was test system 32bit or 64bit OS???

what is the ram type(ddr ddr2 ddr3 etc) and its clock rate?

some rams are really really finicky with supply voltages and with memory controller not wanting see both at same time im leaning towards ram too fast for mobo(3200mhz sticks in some mobos are single stick only)

Link to post
Share on other sites

1 minute ago, bcguru9384 said:

was test system 32bit or 64bit OS???

what is the ram type(ddr ddr2 ddr3 etc) and its clock rate?

some rams are really really finicky with supply voltages and with memory controller not wanting see both at same time im leaning towards ram too fast for mobo(3200mhz sticks in some mobos are single stick only)

Well the ram I'm currently using for the tests were actually some random 1333 ddr3 overclocked to 1600 because I was gonna use them in an upcoming video. It is 64-bit . Which is odd because 1gb sticks of 1333 worked fine , I was leaning towards maybe 1333 was not supported but it is . It is currently running ok but I'm not sure how it will hold up to the lengthy benchmarks and games.

Link to post
Share on other sites

5 minutes ago, TheGTXman said:

Well the ram I'm currently using for the tests were actually some random 1333 ddr3 overclocked to 1600 because I was gonna use them in an upcoming video. It is 64-bit . Which is odd because 1gb sticks of 1333 worked fine , I was leaning towards maybe 1333 was not supported but it is . It is currently running ok but I'm not sure how it will hold up to the lengthy benchmarks and games.

run memtest on them in both 1333 and 1600 modes see what it says about stability

different rams have different CAS and such settings so you maybe running into these timers as the issues

Link to post
Share on other sites

4 hours ago, bcguru9384 said:

run memtest on them in both 1333 and 1600 modes see what it says about stability

different rams have different CAS and such settings so you maybe running into these timers as the issues

Its been running for just over 4 hours and I'm on pass 3 of 4 about to start 4 soon and so far it has found 48 errors but all of them have been on test 6??

Link to post
Share on other sites

21 minutes ago, TheGTXman said:

Its been running for just over 4 hours and I'm on pass 3 of 4 about to start 4 soon and so far it has found 48 errors but all of them have been on test 6??

thats good

what is test 6 and what are errors???

is test results repeatable???

if yes then 

is it possible tell cpu treat error same way chdsk treats bad sectors???

Link to post
Share on other sites

8 minutes ago, bcguru9384 said:

thats good

what is test 6 and what are errors???

is test results repeatable???

if yes then 

is it possible tell cpu treat error same way chdsk treats bad sectors???

It happens everytime on test 6 which is block move ,64-byte blocks

and explain what you mean by "is it possible tell cpu treat error same way chdsk treats bad sectors???".

Link to post
Share on other sites

20 minutes ago, bcguru9384 said:

thats good

what is test 6 and what are errors???

is test results repeatable???

if yes then 

is it possible tell cpu treat error same way chdsk treats bad sectors???

file:///F:/EFI/BOOT/MemTest86-Report-20170801-165202.html   that is the report.

 

Link to post
Share on other sites

46 minutes ago, bcguru9384 said:

thats good

what is test 6 and what are errors???

is test results repeatable???

if yes then 

is it possible tell cpu treat error same way chdsk treats bad sectors???

 

MemTest86-Report-20170801-165202.html

Link to post
Share on other sites

3 hours ago, TheGTXman said:

It happens everytime on test 6 which is block move ,64-byte blocks

and explain what you mean by "is it possible tell cpu treat error same way chdsk treats bad sectors???".

if hard drives get an area of the disk platter that is not usuable its marked as such(unusuable) in drives file table map

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

×