How do I get rid of this blue screen

FinestRyeBread

Limp Gawd
Joined
Mar 10, 2017
Messages
161
I don't know how to start looking for what's wrong.
Got the error code: irql_not_less_or_equal
System specs:
6800k stock
gtx 1080 stock
2x8gb of g. skill 2133
x99 asrock pro gaming i7
EVGA G1 750w
 
Last edited:
step1: start with basics hardware testing

ram: memtest86
CPU : prime95
GPU: Furmark
Systmeload/hat: Prime95+ Furmark
Storage: HDD manufactores test tool and/or crystal diskinfo for S.M.A.R.T info

Step2: then basic software testing
Sfc /scannow
Chkdsk C: (or hatevr you windows dir is)
AV scan with you built in solutions as well as dr web cureit (Free standalone scanner)

Step3: Reinstallation
Reinstall chipset drivers ( from chips manufacturers site:
Reinstall GPU driver ( from chips manufacturers site)
Reinstall network driver ( from chips manufacturers site)
Reinstall Audio Driver ( guess from where)

Reinstall windows


The above recipie will correct/detect many general instability issues
 
Please run memtest first. I would also reset all bios settings and use a XMP profile or lower.
EDIT, not much to add after previous post...
 
Did everything bus reinstalls. Everything hardware wise works fine. Got a new error now. Error code: Driver_irql_not_less_or_equal
What failed: Wdf01000.sys
 
Load optimized defaults in BIOS and then if you still get the issue, reinstall Windows from scratch...
 
Lol.... it's tough getting info out of you.

Are you running third party ant-virus?

.
 
Lol.... it's tough getting info out of you.

Are you running third party ant-virus?

.
No I'm not. Hard to get info because idk what you need.
Memtest86 is great, but FWIW, Windows has had a pretty comprehensive memory test built in since Win7:
http://www.thewindowsclub.com/windows-memory-diagnostics-tool-in-windows-7
Did memtest nothing wrong still getting the error. Will reinstall windows from scratch.
in my testing on defective memory. The windows built in is definatly in the top, but does not compared to or beat memtest86. However i would still recommend it if memtest86 is not available

HCI memtest and Docmem are pretty poor to find errors in comparison to the above two
Will reinstall windows
 
if memtest is ok try bumping your ram voltage a bit. its not uncommon to need to do so.
 
if memtest is ok try bumping your ram voltage a bit. its not uncommon to need to do so.
I would at least disagree with the uncommon part. I have never seen a PC that needed more ram voltage to be stable if it passed a proper memtest86 test.
 
Sounds like you need a full wipe if Memtest comes up clean....

(I've encountered that error in the past, and a format always fixed it)
 
Are you running the Creator's Update?

You might be able to do an "upgrade re-install" to fix it so you don't lose your data/apps.
I've had that fix a lot of weird things.

You just re-install as if you were upgrading from Windows 7/8 and make sure that it's set
to save your data/apps during the install. No need to enter a key, skip that.

https://www.microsoft.com/en-us/software-download/windows10


It's still good to backup everything just in case it doesn't go as planned.

.
 
WFD01000.sys is not the driver that bugchecked, a driver underneath it bugchecked which uses the driver framework. Is there somewhere you can upload the memory dumps? Reinstalling the O/S won't fix it, if it's hardware or the same driver get's reinstalled with the problem. This probably would have caught peeps sooner in the Operating System forum.

Can you please post the memory.dmp or minidumps from the blue screen somewhere?
https://hardforum.com/threads/how-to-help-me-help-you.828696/

The above post is my personal views and opinions, not that of my employer.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
>>Reinstalling the O/S won't fix it, if it's hardware or the same driver get's reinstalled with the problem.

Excellent point and I should have mentioned that too.

If this was an upgrade from Windows 7/8 to Windows 10, then go ahead and backup your stuff and do
a fresh install. You don't want to keep carrying over junk from the old OS.

You could even do an install on a spare drive for testing purposes. Just disconnect the current drive.

If you still get the BSOD after re-installing, then that strongly points to a hardware problem.

.
 
Back
Top