Getting a blue screen

Bowl of Rice

Reputable
Dec 8, 2015
9
0
4,510
[Started Yesterday]
My computer wouldn't start at first I would get irql_not_less_or_equal as an error, I proceeded to repair startup and load my computer from 5 days ago hoping whatever caused my continual blue screen would stop. This is not true as now I am able to fully use my computer from the look except the fact that a Nvidia High Definition Audio driver has a problem, because of this my computer doesn't recognize any audio devices. When I troubleshoot it picks up on this and when I try to install the drivers missing I crash from irql_not_less_or_equal ntoskrnl.exe.
Any solutions for this would be appreciated thanks. :jap:

Screenshot of BlueScreenView If It Helps:https://gyazo.com/62691890104dc9fb56baf13f39accd5f
Screenshot of Audio Troubleshoot: https://gyazo.com/261a44c1849ce794f428f0fb6c7f53ee
 
Solution
in your screen capture, you need to expand the column for parameter 1. it has the error code in it but it is cut off.

here is the list of error codes for bugchek 0x1a
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx

be sure to go to your motherboards vendors website and install the latest windows 10 updates. It is pretty common for the motherboard to have a driver that corrupts memory. Look for a motherboard audio driver update. A old motherboard audio driver can interfere with the GPU sound support in the graphics driver, this can make the graphics card to not respond.
in your screen capture, you need to expand the column for parameter 1. it has the error code in it but it is cut off.

here is the list of error codes for bugchek 0x1a
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx

be sure to go to your motherboards vendors website and install the latest windows 10 updates. It is pretty common for the motherboard to have a driver that corrupts memory. Look for a motherboard audio driver update. A old motherboard audio driver can interfere with the GPU sound support in the graphics driver, this can make the graphics card to not respond.
 
Solution
ok, it was a bugcheck 0xa where a driver tried to read from a bogus memory location (memory address zero)
look for updates to the motherboard drivers.

put your memory dump from c:\windows\minidump directory on to a public server like microsoft one drive, share the files as public and post a link and I can see if I can take a quick look in the windows debugger.