[SOLVED] BSOD Driver verifier violation detected

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

ruanwagenaar27

Honorable
Sep 5, 2017
120
0
10,680
I did a memtest in win 10 and came back with a error reporting something about my ram. tried driver verifier and got BSOD upon restart Driver verifier detected violation. Got blue screen view and saved the dump file it looks like two errors came up Caused By Driver (nordlwf.sys) & Caused By Address (nordlwf.sys+2b0b) & Crash Address (ntoskrnl.exe+3f5780)

here is link with blue screen view Dump file and link with c:/windows/minidump file.

https://drive.google.com/file/d/11zWxfDq6_FWJLndIL9Er__XpWbmbe-ox/view?usp=sharing

https://drive.google.com/file/d/1NG8R42X04zjwyISqoKARMpq64kCb1oo5/view?usp=sharing
 
Last edited:

ruanwagenaar27

Honorable
Sep 5, 2017
120
0
10,680
you don't need to test Microsoft services
if memtest finds no errors now but did before, we have to wonder if the problem isn't a slot on motherboard then. As you only test in 1 slot, maybe its one of the others causing errors.

this might help
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:

Repair-WindowsImage -Online -RestoreHealth
and press enter


SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

it checks windows, much better than driver verifer does.

At the moment im testing in 3 slots only removed slot 4 ram module and so far no errors came up again looks like i took a lucky guess and dimm 4 or the ram module is faulty, will do that sfc /scannow when memtest is done and give feedback.

I used before system optimizers like sytem mechanic,cc cleaner and iobit but like ive read on this forum that optimizers are doing actually more damage to your software than fixing them.
 

ruanwagenaar27

Honorable
Sep 5, 2017
120
0
10,680
ok thanks sfc didnt find anything just running the resore health after that if everything turns up fine i guess the problem is fixed? You said i dont have to run verifier again if memtest came back with 0 errors and sfc found nothing?
 

Colif

Win 11 Master
Moderator
You said i dont have to run verifier again if memtest came back with 0 errors and sfc found nothing?
i checked, I said you don't have to run it on windows services, not that you don't have to run it.

Ok memtest came back with 0 errors, i went to bios and optimized defaults, running sfc /scannow. if sfc doesnt pick up errors must i still run image restore health online?
so the main problem was faulty ram module im just happy i guessed and picked the correct faulty one otherwise i would sit here till tomorrow with memtest running.

Both can't be right? is a stick bad or not?

Bad ram can lead to freezes.

powershell result is fine then.
 

ruanwagenaar27

Honorable
Sep 5, 2017
120
0
10,680
i checked, I said you don't have to run it on windows services, not that you don't have to run it.




Both can't be right? is a stick bad or not?

Bad ram can lead to freezes.

powershell result is fine then.

A stick is bad (what i meant) i removed ram module in dimm 4 slot and did the memtest again while the other 3 ram modules were still present and memtest came back with 0 errors. The first test i stopped at pass 3 because errors count were 230 and exceeding

Removed the one stick in dimm 4 and all was well in memtest

So i guess it must be the stick