How to diagnose bluescreen errors (easy method)

[Pierre Dabrunst]

I don't know if this has been made on this forum before, but here's a simple guide for how to diagnose bluescreen errors.

LTT has good videos as well but I thought that I could write a guide as well here on the forums.

This comes from my own experience that I tested and got it working.  by brothers PC got some errors that I managed to fix by doing what I wrote in this guide. I thought I would share how I fixed it.  It might benefit someone else at some point.

 

Before we start, I just want to say sorry for any spelling errors.  I don't have English as my native language. My native language is Swedish, but i'll do the best I can. Also my grammar might be abit off, but noone is perfect.

 

Step 1: Figure out the bluescreen error

The easiest way to find it is to read at the top of the error that pops up.  It's usually at the first 5 lines of the error message.''

 

Step 2: Remove drivers

If you installed any new driver versions, boot your PC into SafeMode with Networking enabled and uninstall all the recently updated drivers you installed since you installed your OS just to make sure that there are no conflicting drivers anywhere. There is no need to remove the network drivers.  You will need those for the next step if you don't have any other way to get your drivers.

 

Step 3: Test your system

Boot up the PC normally and see if you still have the bluescreen error.  If you have the bluescreen error "irql_not_less_or_equal", boot into safemode again and remove the storage driver(s). That error is often related to storage drive error.

 

Step 4: Installing drivers

Now it's time to install all your drivers. Download all your drivers, but install them one by one and do a full restart after each driver is installed and let the system be at idle for about 5-10 minutes at the desktop and then open up your browser (chrome, firefox, IE or whatever you use, I don't judge anyone) and then play around for a bit with other stuff and see if your system is stable (not getting bluescreen).  Repeat this step for each driver,  This might take a while but it's to see what driver is causing the issue in the first place.

 

Step 5: Testing in larger scale

If you have all your drivers installed successfully, launch a heavier application (benchmark, game or something that requires abit of performace) and see if your computer works as intended.

 

Step 6: Make sure your disk drives are funtional

This is not required, but it's recommeded to do it.  You can run it once per month to check that your drives are heatly and working.

Open up the command promt (cmd) and type

Quote

#For your C drive

chkdsk C: /f

#For any other drive you want to check

chkdsk <drive-letter>: /f

this will check and fix any errors your selected drive might have.  You need to schedule the check to start on the next system reboot / startup.  it might take a while to do depending on your setup, but let it run.  It can also help you drive performance abit since it fixes errors.  That can boost the drives performance.

 

I know this guide might be abit obvious for alot of pepole, but sometimes even professionals are "too smart" to think about the most obvious troubleshooting guides.

 

 

Common bluescreen errors and how to fix them (updated over-time with new bluescreen fixes)

irql_not_less_or_equal

boot into safemode and remove your diskdrive drivers and reboot into normal mode.  Then let Windows install it's default diskdrive drivers and reboot your PC when promted to.  If it works, try install your drivers from your motherboard website and reboot,  If you get error again, then you know what causes the error. if this is the cause of your error, just use the Windows diskdrive driver that installs automatically.  It works just fine.

 

 

If you have any bluescreen errors, post them in the comments and I will try to help you fix them and I will also add in the guide how to fix them if it worked for you to help others that might have the same errors.

 

i do this because I know how frustrating this things can be for pepole since I have this issues myself from time to time when I help pepole with their computers that has this type of errors.  I don't do it for benefits or anything at all.

A like or two would be nice, but i don't ask for it.

 

I hope this helped you guys.  I will keep the guide updated as much as I can.

 

Until nect time, have a great day!

[themctipers]

Good post, but there's a thing called BSOD code, which you can google.  

[Pierre Dabrunst]

1 minute ago, themctipers said:

Good post, but there's a thing called BSOD code, which you can google.  

well yeah, but some pepole might not understand what the BSOD code is and can't write it down quick enough.  Also alot of pepole might not be able to google the error since there is like 50.000 different solutions.

my post is written based on my own experience with the issues.

If someone get's an error, I try to replicate the error on my "crash test pc" and try to figure out the most efficent way to solve it that the end user might be able to solve with the guide I wrote for them.

[themctipers]

 

4 minutes ago, Pierre Dabrunst said:

well yeah, but some pepole might not understand what the BSOD code is and can't write it down quick enough.  Also alot of pepole might not be able to google the error since there is like 50.000 different solutions.

my post is written based on my own experience with the issues.

If someone get's an error, I try to replicate the error on my "crash test pc" and try to figure out the most efficent way to solve it that the end user might be able to solve with the guide I wrote for them.

¯\_(ツ)_/¯ for me I usually just google it. 

 

For the IQRL less or equal thing, I've set my ram from 1600mhz to 1333mhz and that fixed it (sticks are 1600/cas9 however)

[Pierre Dabrunst]

Just now, themctipers said:

 

¯\_(ツ)_/¯ for me I usually just google it. 

 

For the IQRL less or equal thing, I've set my ram from 1600mhz to 1333mhz and that fixed it (sticks are 1600/cas9 however)

That might also do it, however I wrote it due from my experience with the issue.  The computer I solved the issue of recently was disk drivers errors.  The computer has been working for at least 3 years no problem what so ever.  All BIOS stuff has been at factory defaults the entire time.

[JohnnyCorporalTech]

Great post, Very informative for people who may not have much experience with blue screens. 

[Pierre Dabrunst]

1 minute ago, JohnnyCorporalTech said:

Great post, Very informative for people who may not have much experience with blue screens. 

Thank you   That was the intention of the guide / post.

[xAcid9]

Kindly mention useful software to diagnose BSOD log file  like bluescreenview or whocrashed. 

 

Also you can upload BSOD crash log to  http://www.osronline.com/page.cfm?name=Analyze for better analysis. 

[Pierre Dabrunst]

15 hours ago, xAcid9 said:

Kindly mention useful software to diagnose BSOD log file  like bluescreenview or whocrashed. 

 

Also you can upload BSOD crash log to  http://www.osronline.com/page.cfm?name=Analyze for better analysis. 

I only recommend stuff that I tried personally that I know can solve the issue.  But good idea.  I will try get a bluescreen on my "crash build" and use some software and see what I can recommend.